> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/activate/event-streaming/destinations/advertising/google-ads.md).

# Google Ads

Google Ads is Google's advertising platform. Chord sends conversions to Google Ads from the browser and from the server. Use both so each order is counted, even when a browser blocks the Google tag.

## What each version does

* [**Google Ads Gtag**](/activate/event-streaming/destinations/advertising/google-ads/google-ads-gtag.md) runs in the shopper's browser. It sends conversions and supports dynamic remarketing and enhanced conversions.
* [**Google Ads Conversions**](/activate/event-streaming/destinations/advertising/google-ads/google-ads-conversions.md) runs on Chord's servers. Purchases still count when a browser blocks the Google tag or the order is completed somewhere the tag can't run.

## Why use both

The browser version sees what shoppers do on the page. The server version survives ad blockers and closed tabs. The two are designed to run together, as a second data source for the **same conversion actions**.

**Google holds server-side data out of bidding for its first 14 days.** For 14 days after the first conversion arrives, Google Ads shows it in reporting but doesn't use it for bidding or let it update the tag's conversion values. Plan for this when you switch over from another server-side tool.

## How they deduplicate

Both versions send the order ID as the transaction ID. Google merges the two copies of a conversion that carry the same transaction ID, so an order counts once. Use the same conversion actions in both destinations.

Events without an order or cart ID use the event's message ID as the transaction ID on the server version. That keeps them unique, but they can't be merged with a tag conversion, so an event like `Product Added` sent by both destinations to the same conversion action is counted twice. Send such events through one destination only.

## Set up

* [Google Ads Gtag](/activate/event-streaming/destinations/advertising/google-ads/google-ads-gtag.md)
* [Google Ads Conversions](/activate/event-streaming/destinations/advertising/google-ads/google-ads-conversions.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.chord.co/activate/event-streaming/destinations/advertising/google-ads.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.