Create and apply URL templates

Properties for URL templates

Use this format when creating a URL template:
Redirect URL{unescapedlpurl}{escapedlpurl}, {lpurl}, or {lpurl+nURL parameters ]

For example:

  • {unescapedlpurl}?campaign=[*Campaign*]
  • https://example.tracker.com?c_id=123&t_url=
    {escapedlpurl}%3Fcampaign%3D[*Campaign*]

​See more examples below.

Formatting details

Redirect URL

Optionally specify a URL for a third-party tracking service. Search Ads 360 will redirect clicks to this URL.

Here’s an example redirect URL:
https://example.tracker.com?c_id=123&t_url=

If you sign into an engine and enter a URL in a tracking template, when you sync in the change Search Ads 360 automatically changes the URL to start with HTTPS. This change is to ensure compatibility with parallel tracking.

Note that Search Ads 360 only updates the first URL in your tracking template to specify HTTPS. If your tracking template contains multiple tracking URLs, make sure they all specify HTTPS. Parallel tracking requires all tracking URLs to specify HTTPS.

After the sync completes, Search Ads 360 adds its clickserver URL to the beginning of the tracking URL and traffics the updated tracking URL out to the engine.

Landing page placeholder

Specify any of the following placeholders for the landing page URLs you've defined:

{unescapedlpurl}{escapedlpurl}, {lpurl}, {lpurl+2}, or {lpurl+3}:

Note the differences between the placeholders:

  • {unescapedlpurl} inserts the landing page URL exactly as you entered it when you created the ad, keyword, or sitelink.

    This is the placeholder to use if you are not specifying a redirect URL. It can appear at the beginning of a URL template.

  • {escapedlpurl} is intended to be used with a redirect URL. It encodes the landing page URL before inserting it. If you add URL parameters to template, you'll need to encode them manually (assuming the redirect service requires you to encode them).

    It cannot appear at the beginning of a URL template.

  • {lpurl}, {lpurl+2}, or {lpurl+3} is intended to be used with a redirect URL.

    {lpurl} is equivalent to {escapedlpurl} in non-Google Ads accounts. In Google Ads accounts, there is a subtle difference between {lpurl} and {escapedlpurl}. Learn more about the differences between {escapedlpurl} and {lpurl} in Google Ads accounts.

    {lpurl+2} escapes the landing page URL twice.

    {lpurl+3} escapes the landing page URL three times.

    If you add URL parameters to template, you'll need to encode them manually (assuming the redirect service requires you to encode them).

    This placeholder cannot appear at the beginning of a URL template.

    Landing page tests: If the URL template in effect for a keyword uses the {lpurl+2} or {lpurl+3} placeholder, you can't include that keyword in a landing page test. Only keywords with URL templates that use {unescapedlpurl}, {escapedlpurl}, or {lpurl} can be in landing page tests.

 

URL parameters

Optional URL parameters to append to {unescapedlpurl}{escapedlpurl}, or {lpurl}.

In accounts that use parallel tracking, URL templates should only contain third-party tracking URLs and parameters used by the third-party tracking service. URL parameters that your landing pages require should be placed in a Final URL Suffix or directly in the landing page URL. Parameters in a URL template might not be sent to the landing page, depending on how you encoded the parameters in your URL template. Learn more

It's recommended that you start the URL parameters in a template with the ? character. If necessary, Search Ads 360 or the engine itself will change ? to & automatically. That is, if the landing page URL already specifies a query string, the leading ? in the URL template will be replaced with &.

If you specify neither ? nor & in front of the query string, the result depends on whether the URL template is in an engine account with shared templates:

  • In an account with shared templates, Search Ads 360 traffics the URL template to the engine, and the engine applies the template. Therefore, the engine's own logic determines what happens. For example, Google Ads does not insert ? or & if they are missing. So this URL template in a Google Ads account:
    https://tracker.com?url={escapedlpurl}pid%3D1245
    Results in a tracking URL such as:
    https://tracker.com?url=https%3A%2F%2Fexample.compid%3D1245

  • In an account without shared templates, Search Ads 360 applies the URL template and inserts ? or & if they are missing. So this URL template in an account without shared templates:
    {escapedlpurl}campaign=[*Campaign*]
    Results in a landing page URL such as:
    http://example.com/shoes?campaign=Shoes-Brand

If you need these URL parameters to be encoded, enter the encoded string in the template. Search Ads 360 does not encode parameters specified in the template, even if you use the {escapedlpurl} placeholder for the landing page URL.

Accounts that don't use parallel tracking show an Insert parameter list which displays all Search Ads 360 macros. Use Search Ads 360 macros anywhere in your URL template to dynamically generate landing page URLs that contain campaign or keyword-specific values. (In accounts that do use parallel tracking, use Search Ads 360 custom parameters instead of macros.)

To append a Search Ads 360 macro to your landing page URLs, you can select one from the list or type it yourself.

Here’s an example of what you might enter:
{unescapedlpurl}?campaign=[*Campaign*]&keyword=[*KeywordID*]&src={param2}

You can include Search Ads 360 macros or Google Ads ValueTrack parameters in the template, but Search Ads 360 will convert any spaces in the substituted value to the + character.

For example, if a customer searches for winter coat, a URL template that specifies the kw=[*searchterm*] query string will pass kw=winter+coat to the landing page.

Reserved parameters 

The parameter names listed below are reserved for Search Ads 360 internal use only. If you add them to a landing page URL, Search Ads 360 will report an error and will not traffic the item to the engine.

  • ds_e_adid
  • ds_e_cmpid
  • ds_e_device
  • ds_e_kwdid
  • ds_e_kwgid
  • ds_e_matchtype
  • ds_e_placement
  • ds_e_product_id
  • ds_e_product_target_id
  • ds_e_searchquery
  • ds_e_searchterm
  • ds_e_source
  • ds_s_adid
  • ds_s_cmpid
  • ds_s_kwgid
  • ds_s_sleid
  • ds_s_sli
  • ds_url_v
  • lid
  • sadid
If you're already using any of these parameter names for your own tracking purposes, you'll need to change the landing page parameter option in the engine accout to Include full URL (unencoded). With this option, Search Ads 360 wraps your landing page URLs and enables you to use any parameter name.

Example landing pages and templates

Landing page

URL template

URL after applying the template

https://example.com/shoes {unescapedlpurl}
?campaign=[*Campaign*]
https://example.com/shoes
?campaign=[*Campaign*]

https://example.com/shoes
?p_id=42

https://example.tracker.com?c_id=123&t_url=
{escapedlpurl}
%3Fcampaign%3D[*Campaign*]

https://example.tracker.com?c_id=123&t_url=
https%3A%2F%2Fexample.com%2Fshoes
%3Fp_id%3D42%26campaign%3D[*Campaign*]

https://example.com/shoes
?p_id=42

Non-Google Ads account:
https://example.tracker.com?c_id=123&t_url=
{lpurl}
%3Fcampaign%3D[*Campaign*]

https://example.tracker.com?c_id=123&t_url=
https%3A%2F%2Fexample.com%2Fshoes
%3Fp_id%3D42%26campaign%3D[*Campaign*]

https://example.com/shoes
?p_id=42

Google Ads account:
https://example.tracker.com?c_id=123&t_url=
{lpurl}

Final URL Suffix:
campaign={_dscampaignid}

https://example.tracker.com?c_id=123&t_url=
https://example.com/shoes
%3Fp_id%3D42%26campaign%3Dbrand-shoes

URL fragments

Support for URL fragments varies depending on whether an engine supports shared templates.

In accounts that use parallel tracking, fragments that you define in a URL template will not be included in the landing page URL. For these accounts, define URL fragments directly in the landing page URL or in a Final URL Suffix. Learn about URL fragments in Google Ads accounts.

URL fragments in accounts with shared templates

In accounts with shared templates, add URL fragments at the end of the URL template. Don't specify URL fragments in the landing page URLs.

If you add a fragment to the end of the landing page URL, any URL parameters in the template will be interpreted as part of the fragment. For example:

  1. A URL template specifies parameters after the landing-page placeholder:
    {unescapedlpurl}?c=d

  2. A landing page URL contains a URL fragment:
    https://example.com?a=b#frag1

  3. When the engine applies templates, it will not move the URL fragment to the end of the effective landing page URL, and the URL parameters appearing after the placeholder will become part of the URL fragment.
    For example: https://example.com?a=b#frag1&c=d

  4. Because web browsers do not pass URL fragments to web sites,  your web site won't see the "c=d" parameter. Instead, the "c=d" parameter will be treated as part of the URL fragment by the browser.

Instead, put the URL fragment at the end of the URL template. After the engine applies templates, the fragment will be at end of the landing page URL. For example:

Landing page

URL template

URL after applying the template

https://example.com?a=b {unescapedlpurl}?c=d#frag1 https://example.com?a=b&c=d#frag

URL fragments in accounts that don't support shared templates

In accounts that do not support shared templates, if you add fragments to each landing page URL Search Ads 360 will move the URL fragment to the end of the landing page URL after it applies URL templates.

If you use redirect URLs and you have landing page URLs with {ifmobile} / {ifnotmobile} parameters, do not place URL fragments within the parameters themselves.

For example, if you create this URL template:
https://tracker.com?url={escapedlpurl}

A landing page that looks like this is not valid in Search Ads 360:
https://{ifmobile:a.com#frag1}{ifnotmobile:b.com#frag2}

Instead, do either of the following:

  • Specify a URL fragment outside of the {ifmobile} / {ifnotmobile} parameters. This effective landing page is valid in Search Ads 360:
    https://tracker.com?url=https://{ifmobile:a.com}{ifnotmobile:b.com}#frag1
  • Don't use a redirect URL. This effective landing page is valid in Search Ads 360:
    https://{ifmobile:a.com#frag1}{ifnotmobile:b.com#frag2}​​
Was this helpful?
How can we improve it?