Google Ads Remarketing Tag Setup Guide | Client-Side Tags

Tag configuration

Navigate to the Tag Marketplace to add a new tag. Read the Tag Overview article for general instructions on how to add a tag.

When adding the tag, configure the following settings:

Conversion ID
- Enter the value of the google_conversion_id here.
- This value is provided in your code snippet and also available in your Ads control panel.
Page Type
- Select the page type of your site where you are tracking conversions with this tag instance.
- This is also the value of the custom ecomm_pagetype‘parameter in your code snippet.
Conversion Value
- Enter a value that you want to assign to the conversion action.
- You cahn leave this field blank if you prefer to use the order subtotal value or otherwise set it dynamically via the Data Mapping toolbox.

You can optionally set all of the above settings in the Data Mappings toolbox.

Load rules

Load the tag on all pages or set conditions for when your tag will load. For more information about load rules, see the Load Rules documentation.

Data mappings

Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see data mappings.

Standard

Map to these destinations for dynamically sending (or overriding) the values under tag settings.

The following table describes destination names and descriptions for Standard variables.

Destination Name	Description
Conversion ID `google_conversion_id`	Value of the `google_conversion_id` parameter.
Conversion Label	Set a default label here and use mapping to dynamically override this value. Use a comma-separated list to send data for multiple labels. This list can use a matching number of Conversion Labels as Conversion IDs or use a single label for all Conversion IDs.
Conversion Value (value)	Set a default value here or leave this blank to use the Subtotal value from the E-Commerce extension. Use mapping to dynamically override this value and the E-Commerce extension value. When you use conversion tracking, you can assign the same value to all conversion actions of a certain type (a static value) or let a conversion action have different values (dynamic, representing transaction-specific values). If you assign values to your conversions, you will be able to distinguish the total value driven by your advertising across different conversions and be able to identify and focus on high-value conversions. If you leave this field empty, the tag will auto-fill using the E-commerce value for subtotal ( `_csubtotal`).
Global Object	The name of the Global Object used for the event queue. If not specified, “gtag” is used. Not required for most implementations.
Data Layer Name	By default, the data layer initiated and referenced by the global site tag is named dataLayer. Rename the data layer only if your project requires a separate name.
Enable Remarketing	Values are On or Off. Default value is Off. When Remarketing is enabled, this tag will automatically pull in data from the E-Commerce Extension to populate the Google Ads “Retail” parameters (prefix `ecomm_`). Mapping directly to the “Retail” tab in the toolbox will override the data pulled in via the E-Commerce Extension.
Page Type `pagetype`	Type of page where you are tracking conversions. Select a default page type here and use mapping to dynamically override this value.
Cross-Tracking Domains	A comma-separated list of domains to use with Cross-Domain Tracking (setAllowLinker). Should be the top level domain, such as “tealiumiq.com”.
Custom	You may define customized parameters not predefined by Google Ads. See “Advanced” below for more information.

Retail

We recommend setting up the E-Commerce Extension for this tag since it will automatically send the necessary product and order details to the appropriate Ads parameters. You also have the option to override the Extension variables via Mapping.

The following table describes destination names and descriptions for Retail variables.

Destination Name	Description
`ecomm.prodid`	Required. This is the product ID of the product or products displayed on the current page - the IDs used here should match the IDs in your feed. When using the E-commerce extension, mapping this parameter overrides `_cprod`.
`ecomm.totalvalue`	This parameter should be used on product, cart and purchase page types and should contain the value of a single product on product pages, or the total sum of the values of one or more products on the cart and purchase pages.
`ecomm.category`	This parameter contains the category of the currently viewed product or category pages. When using the E-commerce extension, this parameter overrides `_ccat`.
`ecomm.pagetype`	Recommended. Indicates the type of page that the tag is on. Use one of the following values: `home` `searchresults` `category` `product` `cart` `purchase` `other` Used when your page does not fit into the page types listed above, for example, a “Contact Us” or “About Us” page. If you choose to include this parameter, map your data source to `ecomm.pagetype`.
`ecomm.value`	Deprecated. This parameter is no longer used by Google Ads for this Remarketing tag.
`ecomm.quantity`	Deprecated. This parameter is no longer used by Google Ads for this Remarketing tag.
`Custom`	You may define customized parameters not predefined by Google Ads. See “Advanced” below for more information.

Education

The following table describes destination names and descriptions for Education variables.

Destination Name	Description
`edu.pid`	Required. This parameter is the ID of the program that the visitor is currently viewing on either the program or lead page types. This ID must match a value in the “Education Program” in your feed.
`edu.plocid`	This parameter is the ID for the location of the program that the user is currently viewing on either the program or lead page types. This ID must match a value in the “Location ID” in your feed.
`edu.pagetype`	Recommended. Indicates the type of page that the tag is on. Use one of the following values: `home` `searchresults` `program` `lead` `complete` or `other` Used when your page does not fit into the page types listed above, for example, a “Contact Us” or “About Us” page. If you choose to include this parameter map your data source to `edu.pagetype`.

Flights

The following table describes destination names and descriptions for Flights variables.

Destination Name	Description
`flight.originid`	This parameter is the origin of the flight itinerary being viewed on search results, cart and purchase page types. This ID must match a value in your feed though Google recommends you use three-letter airport codes.
`flight.destid`	Required. This parameter is the destination of the flight itinerary being viewed on search results, cart and purchase page types. This ID must match a value in your feed though Google recommends you use three-letter airport codes.
`flight.totalvalue`	This parameter should be used on the cart and purchase page type and should contain the total value of the flight itinerary. Do not include any currency symbols.
`flight.startdate`	The date when the flight itinerary starts. Should be in the `YYYY-MM-DD` format.
`flight.enddate`	The date when the flight itinerary ends. Should be in the `YYYY-MM-DD` format.
`flight.pagetype`	Recommended. Indicates the type of page that the tag is on. Use one of the following values: `home` `searchresults` `offerdetail` `cart` `purchase` `cancel` or `other` Used when your page does not fit into the page types listed above, for example, a “Contact Us” or “About Us” page. If you choose to include this parameter map your data source to `flight.pagetype`.

Hotels and rental

The following table describes destination names and descriptions for Hotels and Rental variables.

Destination Name	Description
`hrental.id`	Required. This parameter is the ID of the hotel or rental property that the visitor is currently viewing on the property page type. This ID must match a value in your feed.
`hrental.startdate`	The date when the booking is to begin. Should be in the `YYYY-MM-DD` format.
`hrental.enddate`	The date when the booking is to end. Should be in the `YYYY-MM-DD` format.
`hrental.totalvalue`	This parameter should be used on the conversion intent and conversion page types and should contain the total sum of the values of all properties in the visitor’s cart. Do not include any currency symbols.
`hrental.pagetype`	Recommended. Indicates the type of page that the tag is on. Use one of the following values: `home` `searchresults` `offerdetail` `conversionintent` `conversion` or `other` Used when your page does not fit into the page types listed above, for example, a “Contact Us” or “About Us” page. If you choose to include this parameter map your data source to `hrental.pagetype.`

Jobs

The following table describes destination names and descriptions for Jobs variables.

Destination Name	Description
`job.id`	Required. This parameter is the ID of the job opening being viewed on `searchresults`, `offerdetail`, `conversionintent` and `conversion` page types. This ID must match a value in your feed.
`job.locid`	This parameter represents a location ID or name and is used as a secondary matching key in your feed allowing for multiple job_ids of the same value, but using separate location IDs and should be present on search results, offer detail, conversion intent and conversion page types.
`job.totalvalue`	This parameter should be used on the conversion intent and conversion page types and should contain the total value of the job listings that the user has selected. Do not include any currency symbols.
`job.pagetype`	Recommended. Indicates the type of page that the tag is on. Use one of the following values: `home` `searchresults` `offerdetail` `conversionintent` or `other` Used when your page does not fit into the page types listed above, for example, a “Contact Us” or “About Us” page. If you choose to include this parameter map your data source to `job.pagetype.`

Local

The following table describes destination names and descriptions for Local variables.

Destination Name	Description
`local.id`	Required. This parameter is the ID of the offer or deal being viewed on search results, offer detail, conversion intent and conversion page types. This ID must match a value in your feed.
`local.totalvalue`	This parameter should be used on the conversion intent and conversion page types and should contain the total value of the offer or offers that the user has purchased. Do not include any currency symbols.
`local.pagetype`	Recommended. Indicates the type of page that the tag is on. Use one of the following values: `home` `searchresults` `offerdetail` `conversionintent` `conversion` or `other` Used when your page does not fit into the page types listed above, for example, a “Contact Us” or “About Us” page. If you choose to include this parameter map your data source to `local.pagetype`.

Real estate

The following table describes destination names and descriptions for Real Estate variables.

Destination Name	Description
`listing.id`	Required. This parameter is the ID of the property being viewed on search results, offer detail, conversion intent and conversion page types. This ID must match a value in your feed.
`listing.totalvalue`	This parameter should be used on the conversion intent and conversion page types and should contain the total value of the property Do not include any currency symbols.
`listing.pagetype`	Recommended. Indicates the type of page that the tag is on. Use one of the following values: `home` `searchresults` `offerdetail` `conversionintent` `conversion` or `other` Used when your page does not fit into the page types listed above, for example, a “Contact Us” or “About Us” page. If you choose to include this parameter map your data source to `listing.pagetype`.

Travel

The following table describes destination names and descriptions for Travel variables.

Destination Name	Description
`travel.destid`	Required. This parameter is the ID of the travel destination being viewed on search results, conversion intent and conversion page types. This ID must match a value in your feed.
`travel.originid`	Optional. This parameter is the ID of the travel origin location being viewed on search results, conversion intent and conversion page types. This value is used as a secondary matching key in your feed and does not need to represent anything, but Google recommends that you use three-letter airport codes or two-letter country codes.
`travel.startdate`	The date when the travel itinerary starts. Should be in the `YYYY-MM-DD` format.
`travel.enddate`	The date when the travel itinerary ends. Should be in the `YYYY-MM-DD` format.
`travel.totalvalue`	This parameter should be used on the conversion intent and conversion page types and should contain the total value of the travel itinerary. Do not include any currency symbols.
`travel.pagetype`	Recommended. Indicates the type of page that the tag is on. Use one of the following values: `home` `searchresults` `offerdetail` `conversionintent` `conversion` `cancel` or `other` Used when your page does not fit into the page types listed above, for example, a “Contact Us” or “About Us” page. If you choose to include this parameter map your data source to `travel.pagetype`.

Phone conversion options

Use phone call conversion tracking to help you see how effectively your ads lead to phone calls from your website. When someone visits your website after clicking one of your ads, website call conversion tracking can help you identify and measure calls from your site. This kind of conversion tracking tracks a call as a conversion when it lasts longer than a minimum length you set

The following table describes destination names and descriptions for Phone Conversion option variables.

Destination Name	Description
`phone_conversion_number`	Required. In the following example, replace “REPLACE WITH VALUE” with your business phone number. Ensure that the number matches the number on your page exactly and includes any relevant country codes.
`phone_conversion_css_class`	Required. Enter a CSS class name. All elements of that class will have their contents replaced with a formatted telephone number.

Other

The following table describes destination names and descriptions for variables categorized as “Other”.

Destination Name	Description
`dynx.itemid`	Required. This parameter is the ID of the product being viewed on search results, offer detail, conversion intent and conversion page types. This ID must match a value in your feed.
`dynx.itemid2`	Optional. This parameter is the secondary ID of the product being viewed on search results, offer detail, conversion intent and conversion page types. This ID must match a value in your feed.
`dynx.totalvalue`	This parameter should be used on the conversion intent page type and should contain the total value of the products that the visitor has purchased. Do not include any currency symbols.
`dynx.pagetype`	Recommended. Indicates the type of page that the tag is on. Use one of the following values: `home` `searchresults` `offerdetail` `conversionintent` `conversion` `cancel` `other` Used when your page does not fit into the page types listed above, for example, a “Contact Us” or “About Us” page. If you choose to include this parameter map your data source to `dynx.pagetype`.

Advanced

The following table describes destination names and descriptions for Advanced variables.

Destination Name	Description
Recommended Product IDs `custom.ecomm_rec_prodid`	This parameter may be used to pass product IDs of recommended products on the page.
Visitor’s Age `custom.a`	This parameter may be used to pass a visitor’s age.
Visitor’s Gender `custom.g`	This parameter may be used to pass a visitor’s gender.
Visitor Has Account `custom.hasaccount`	This parameter may be used to indicate if the visitor has an account.
Customer Quality Score `custom.cqs`	This parameter can be used to report a visitor’s customer quality score.
Repeat Purchaser `custom.rp`	This parameter can be used to identify if the visitor is a repeat purchaser.
Visitor Loyalty Score `custom.ly`	This parameter is used to identify the visitor’s loyalty score.
Visitor High Spender Score `custom.hs`	This parameter is used to identify the visitor’s high spender score.
Custom `custom.myvar`	This parameter can be used to pass any customized parameters. Replace `myvar` with your own parameter name.

E-Commerce

The following table describes destination names and descriptions for E-Commerce variables.

Destination Name	Description
Order ID `_corder`	Represents the unique identifier assigned to the final order. One advantage of using Ecommerce parameters is the tag will automatically use `_csubtotal` for the total value for any business type you configure. For example, for the Retail business type, the value of `ecomm.totalvalue` will use `_csubtotal`.
Sub Total `_csubtotal`	Represents the sub total amount of the final order. The value within `_csubtotal` will automatically use `_csubtotal` for the total value for any business type being reported. For example, for the Retail business type, the value of `ecomm.totalvalue` will use `>_csubtotal`.
List of Product IDs `_cprod`	Represents the unique identifier of each product in the product array. When present, a custom parameter ecomm.prodid will contain the contents of `_cprod`.
List of Categories `_ccat`	Represents the category of each product in the product array. When present, a custom parameter ecomm.category will contain the contents of `_ccat`.
List of Quantities `_cquan`	Represents the quantity of each product in the product array. When present, a custom parameter ecomm.quantity will contain the contents of `_cquan`.
List of Prices `_cprice`	Represents the product unit price of each product in the product array. When present, a custom parameter ecomm.pvalue will contain the contents of `_cprice`.
This tag automatically pulls in data from the E-Commerce extension to populate the following “Retail” parameters: `ecomm.prodid` - from `_cprod` `ecomm.category` - from `_ccat` `ecomm.totalvalue` - from `_csubtotal` when `_corder` is present or one of the page types includes purchase, conversion, cart, or conversionintent.

Verifying the tag

You will need the Chrome Web browser to use Google Tag Assistant. If the browser is already installed on your computer, install the Google Tag Assistant from the Google Chrome Store. Once successfully installed, follow these steps:

Go to your site and open the target page.
Click on the assistant icon at the top right corner in your browser.
Click Check this page now.

The color indicator on the icon may display red instead of green since you are implementing the tag through Tealium and not the traditional way.

Once the Tag Assistant runs, you will be able to see the values being populated. The following sample use case shows testing the homepage. In the example, you will notice the request is ‘working’ and the data sources are being grabbed. Also note that the ecomm_pagetype is populated with a value of home, but, ecomm_value and ecomm_prodid are not populated because the homepage does not contain those values.

The following example shows how Tag Assistant looks for Product Detail pages.

Vendor documentation

For additional information, see the following vendor documentation: