To create URL parameters that contain the name of the engine account, campaign, ad group, or keyword that generated a click on an ad, use one of the following Search Ads 360 features:
- In engine accounts that use parallel tracking, use custom parameters. In these accounts, Search Ads 360 automatically creates custom parameters that contain the name and ID of each engine account, campaign, ad group, and keyword. If you include these custom parameters in a Final URL Suffix or in your landing page URLs, the data will be available to the landing page when a customer clicks your ad. (URL parameters defined in a URL template might not be sent to the landing page, depending on how you define the template. The best practice is to place tracking parameters that your landing pages require in a Final URL Suffix.)
- In engine accounts that don't use parallel tracking, use macros. You can specify a macro as the value of a URL parameter in your URL templates or landing page URLs. When a click on an ad is redirected through Search Ads 360, Search Ads 360 replaces macro with the name of the engine account, campaign, ad group, or keyword that generated the click.
Search Ads 360 custom parameters and macros are not available in social or engine track accounts.
It's recommended that you don't use custom parameters in Google Ads local inventory ads. In most cases, Google will remove custom parameters from the landing page URLs of local inventory ads. This applies to custom parameters you create and to Search Ads 360 custom parameters.
List of Search Ads 360 custom parameters and macros
The following table describes Search Ads 360 custom parameters and macros.
The custom parameter names in the table below are reserved. If you try to use these names when creating new custom parameters in Search Ads 360, Search Ads 360 will report an error and will not traffic the parameters you created to the engine.
Macro names are case sensitive. Custom parameter names are not case sensitive.
Custom parameter | Macro | Description |
---|---|---|
{_dsaccountid} Location: Campaign custom parameters |
[*EngineAccountID*] |
The full Search Ads 360 ID of an engine account. Examples In an account that doesn't use parallel tracking, add this to a URL template or landing page URL: For clicks attributed to an engine account with an ID of "700000000025606", the following appears in the landing page URL: |
{_dsaccounttype} Location: Campaign custom parameters |
[*EngineAccountType*] |
The type of engine account in all capital letters, such as GOOGLE, MICROSOFT, YAHOO_JAPAN. Examples In an account that doesn't use parallel tracking, add this to a URL template or landing page URL: For clicks attributed to a Google Ads engine account, the following appears in the landing page URL: |
{_dscampaign} Location: Campaign custom parameters |
[*Campaign*] |
The name of a campaign, with + substituted for spaces. Examples In an account that doesn't use parallel tracking, add this to a URL template or landing page URL: For clicks attributed to a campaign named "RLSA Brand Terms", the following appears in the landing page URL: |
{_dscampaignid} Location: Campaign custom parameters |
[*CampaignID*] |
The full Search Ads 360 ID of a campaign. Examples In an account that doesn't use parallel tracking, add this to a URL template or landing page URL: For clicks attributed to a campaign with an ID of "71700000002467374", the following appears in the landing page URL: |
{_dsadgroup} Location: Ad group custom parameters |
[*Adgroup*] |
The name of an ad group, with + substituted for spaces. Examples In an account that doesn't use parallel tracking, add this to a URL template or landing page URL: For clicks attributed to an ad group named "Branded Terms", the following appears in the landing page URL: |
{_dsadgroupid} Location: Ad group custom parameters |
[*AdgroupID*] |
The full Search Ads 360 ID of an ad group. Examples In an account that doesn't use parallel tracking, add this to a URL template or landing page URL: For clicks attributed to an ad group with an ID of "58700000049629024", the following appears in the landing page URL: |
{_dssearchterm} Location: Keyword custom parameters (not visible in Search Ads 360) |
[*searchterm*] |
Keyword text with + substituted for spaces. Examples In an account that doesn't use parallel tracking, add this to a URL template or landing page URL: For clicks attributed to a keyword named "red shoes", the following appears in the landing page URL: |
Sitelinks inherit these custom parameters. |
[*TrackerID*] |
The full Search Ads 360 ID for a Search Ads 360 item that can specify a landing page:
Examples In an account that doesn't use parallel tracking, add this to a URL template or landing page URL: For clicks attributed to an item with an ID of "43700000771348238", the following appears in the landing page URL: |
Sitelinks inherit these custom parameters. |
[*KeywordID*] |
The short-form ID for a Search Ads 360 item that can specify a landing page:
The short form ID is the letter p followed by the last digits of the full Search Ads 360 ID that are not preceded by zeros. Examples In an account that doesn't use parallel tracking, add this to a URL template or landing page URL: For clicks attributed to an item with an ID of "43700000771348238", the following appears in the landing page URL: |
Don't add the
{gclid} parameter to landing pages in your Microsoft Advertising accounts. |
[*GCLID*] |
To identify specific clicks on ads, Google Ads, Microsoft Advertising, or Search Ads 360 can generate case-sensitive IDs called click IDs. Learn more about click IDs and when they are generated. Learn more about the If a click ID has been generated, the ID appears in a URL parameter named Prior to Microsoft Advertising parallel tracking, the accounts used the
[*GCLID*] macro . Any Microsoft Advertising accounts that still use the [*GCLID*] macro will soon automatically be migrated to use the {msclkid} parameter. Learn more about how Search Ads 360 migrates Microsoft Advertising accounts to parallel tracking.If you want the click ID to be available in an additional parameter with a name other than Examples In an account that doesn't use parallel tracking, add this to a URL template or landing page URL: The following appears in the landing page URL: Note that the click ID appears twice: once in the parameter you manually added and once again in the parameter that is added automatically. |
In accounts that use parallel tracking, Search Ads 360 automatically adds the gclsrc parameter to a Final URL Suffix |
[*GCLSRC*] |
If a click ID has been generated, Search Ads 360 also appends the If you want the click source to be available in an additional parameter with a name other than
Examples In an account that doesn't use parallel tracking, add this to a URL template or landing page URL: The following appears in the landing page URL: Note that the click source data appears twice: once in the parameter you manually added and once again in the parameter that Search Ads 360 adds automatically. |
Not available in accounts that use parallel tracking | [*AffiliateID*] |
The short-form ID of an engine account.
The short-form ID for an engine account is the letter k followed by the last digits of the full Search Ads 360 ID that are not preceded by zeros. Example For clicks attributed to an engine account with an ID of "700000000025606", the following appears in the landing page URL: |
Not available in accounts that use parallel tracking | [*KeywordIDNL*] |
The short-form ID without a letter. That is, the last digits of the full Search Ads 360 ID that are not preceded by zeros. Example For clicks attributed to a keyword with an ID of "43700000771348238", the following appears in the landing page URL: |
Not available in accounts that use parallel tracking | [*Part_Site*] |
The name of a Search Ads 360 engine account, with + substituted for spaces. Example For clicks attributed to an engine account named "US - NonBrand ID 123-456-7890", the following appears in the landing page URL: |
Not available in accounts that use parallel tracking | [*Part_Comp*] |
The type of an engine account in all capital letters, such as MICROSOFT, YAHOO_JAPAN. Example For clicks attributed to a Yahoo Japan engine account, the following appears in the landing page URL: |
[ltd] |
Search Ads 360 won’t generate a gclid if the limited parameter is set to 1.
|
Campaign Manager 360 macros
Campaign Manager 360 macros are not supported in accounts that use parallel tracking.
If your organization uses Campaign Manager 360, engine accounts that don't use parallel tracking can include Campaign Manager 360 macros as well as Search Ads 360 macros to pass data to your landing pages.
For example, the %m
Campaign Manager 360 macro expands into an encrypted DoubleClick cookie ID if browser settings make cookies available. (This macro is needed if you upload offline conversions from the Campaign Manager 360 API and use encrypted user IDs to identify the conversions.)
%m
macro for users in California. Learn more about changes to Data Transfer.Campaign Manager 360 macros are available for search ads because both Campaign Manager 360 and Search Ads 360 use the same clickserver. That is, the Search Ads 360 clickserver URL and the Campaign Manager 360 clickserver URL redirect clicks to the same server. If the server detects Search Ads 360 macros or Campaign Manager 360 macros, it will provide any available values before redirecting to the landing page.
When including Campaign Manager 360 macros in Search Ads 360 landing page URLs or URL templates, you need to URL encode the % at the beginning of the macro name. The URL code for the percent character is %25
. For example, here's how you specify the %m
macro in a Search Ads 360 URL template:
{unescapedlpurl}?user_id=%25m
Note that for clicks on search ads, the clickserver won't have values for some Campaign Manager 360 macros. For example, %b isn't applicable to search ads. If you include it in a Search Ads 360 URL template or landing page URL, the clickserver won't return a value and the URL parameter in the landing page URL will be empty.
Next steps
Add URL parameters that contain custom parameters or macros.