> 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/why-are-google-adwords-and-google-ads-dynamic-remarketing-split-in-jentis.md).

# Why are Google AdWords and Google Ads Dynamic Remarketing split in JENTIS?

Google Ads and Google Ads Dynamic Remarketing were originally split for historical reasons. The older JENTIS setup treated standard Google Ads tracking and dynamic remarketing as separate implementations, so each one had its own connector and tag templates.

That split is no longer needed.

In June 2026, we merged Google Ads Dynamic Remarketing into the main Google Ads connector. This keeps pageview tracking, conversion tracking, and ecommerce remarketing events in one setup and reduces configuration effort.

### What this means now

If you are starting from scratch, use the **Google Ads** connector only.

If you still use legacy Google Ads Dynamic Remarketing tags, migrate them to the current setup. The old tags are deprecated.

Read the migration guide here:

[Google Ads Dynamic Remarketing - Connector Migration](/data-activation/connectors/google-ads/google-ads-dynamic-remarketing-connector-migration.md)


---

# 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/why-are-google-adwords-and-google-ads-dynamic-remarketing-split-in-jentis.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.