> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/data-activation/connectors/google-ads/google-ads-dynamic-remarketing-connector-migration.md).

# Google Ads Dynamic Remarketing - Connector Migration

Google Ads Dynamic Remarketing (GADR) and Google Ads used to be separate connectors in JENTIS Tag Manager. We merged them into a single Google Ads connector to reduce setup complexity and keep all Google Ads functionality in one place. Use this guide to migrate your existing setup, as GADR tags are now deprecated.

### Overview

This overview shows how the previous GADR tag templates map to the current Google Ads tag templates.

<table><thead><tr><th width="449.90234375">GADR Tag Template (deprecated)</th><th>Google Ads Tag Template</th></tr></thead><tbody><tr><td>Google Ads Dynamic Remarketing - Purchase</td><td>Ecommerce Event (Client Side)<br>(by default 1:1 mapped)</td></tr><tr><td>Google Ads Dynamic Remarketing - AddToCart<br>Google Ads Dynamic Remarketing - Cart view<br>Google Ads Dynamic Remarketing - View Item<br>Google Ads Dynamic Remarketing - View Item List<br>Google Ads Dynamic Remarketing - View Search Result</td><td>Ecommerce Event (Client Side)<br>(needs event name and trigger adjustment)</td></tr><tr><td>Google Ads Dynamic Remarketing - Pageview</td><td>GTAG Configuration (Client Side)</td></tr><tr><td>Google Ads Dynamic Remarketing - Conversion</td><td>Conversion (Client Side)</td></tr></tbody></table>

### Migration steps in detail

Pageview and conversion tags map directly to their new equivalents. Ecommerce events need one extra adjustment, because you must update the event name and trigger. Start with the Pageview and Conversion tags.

Google Ads defines both pageview and conversion tracking with a Google tag (`gtag`) snippet.

#### Pageview tag

For pageview tracking, Google provides a snippet like this:

```html
<script async src="https://www.googletagmanager.com/gtag/js?id=TAG_ID"></script>
<script>
    window.dataLayer = window.dataLayer || [];
    function gtag(){dataLayer.push(arguments);}
    gtag('js', new Date());

    gtag('config', 'TAG_ID');
</script>
```

In JENTIS, this maps to the Google Ads tag template `GTAG Configuration (Client Side)`.

Set the tag up with your account ID, usually in this format: `AW-1223456790`. When the tag fires, JENTIS initializes the Google tag library, `dataLayer`, and `gtag` object, then sends the matching `config` event.

#### Conversion Tag

The regular conversion snippet (for non Merchant Center Google Ads conversions) where no further products (item) data is to be tracked the snippet you receive from Google will look like this:

```html
<script>
  gtag('event', 'conversion', {
      'send_to': 'AW-1234567890/kPf8COSvfRDwvcb2Ax',
      'value': 0.01,
      'currency': 'EUR',
      'transaction_id': ''
      // 'new_customer': true /* calculate dynamically, populate with true/false */,
  });
</script>
```

Use the Google Ads tag template "Conversion (client side)" to implement this equivalent on your website.

#### Ecommerce conversion - purchase

Legacy GADR tag templates did not let you customize the event value sent to `gtag()`. The `Google Ads Dynamic Remarketing - Purchase` tag therefore always sent the `purchase` event. In the current Google Ads connector, the `Ecommerce Event` tag still uses `purchase` as the default event name and trigger, but you can change both in the main tag settings.

Here is the equivalent Google Ads conversion snippet:

```html
<script>
gtag('event','purchase', {
      'value': 639.74,
      'items':[{
      'origin': 'LHR',
      'destination': 'LAX',
      'start_date': '2019-04-20',
      'end_date': '2019-04-21',
      'google_business_vertical': 'flights'
}]
});
</script>
```

Please note that those examples lack the `send_to` parameter (as they are generic examples from the official [Google Ads dynamic remarketing documentation](https://support.google.com/google-ads/answer/7305793)). All JENTIS Tag Templates work configuration specific and will submit the `send_to` property with the conversion ID value to match your account. This is true for all client side Google Ads tag templates.

Use the Google Ads tag template "Ecommerce Event (Client Side)" to implement this code to your website.

#### Ecommerce Conversion - All Other

For all of the following other ecommerce events please follow the next steps:

* view\_search\_results
* view\_item\_list
* view\_item
* add\_to\_cart
* remove\_from\_cart
* begin\_checkout
* view\_cart

Here you must select the generic Google Ads tag template "Ecommerce Event". By default it holds the value `purchase` in the event field but you can simply replace it to any of the required values (ie. `view_item`).

Here is an according code snippet as it is required by Google to implement on your website:

```html
<script>
gtag('event','view_item', {
  'value': 998.55,
  'items': [
    {
      'id': 1234,
      'google_business_vertical': 'retail'
    },
    {
      'id': 45678, 
      'google_business_vertical': 'retail'
    }
  ]
});
</script>
```

In the JENTIS tag edit view adjust the value `purchase` to `view_item`:

<figure><img src="/files/aENUKPYPlGhcXMSPxQyB" alt=""><figcaption></figcaption></figure>

Your setup is now ready. JENTIS sends the `gtag()` call with the `view_item` event and its matching properties based on your selected trigger.

### Conclusion

In short, pageview and standard conversion tags map directly to their new Google Ads equivalents. Ecommerce remarketing tags now use the `Ecommerce Event (Client Side)` template, where you set the required event name and trigger for each use case. After this migration, your Google Ads setup stays easier to manage, because all client-side Google Ads tracking runs through one connector.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.jentis.com/data-activation/connectors/google-ads/google-ads-dynamic-remarketing-connector-migration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.