> For the complete documentation index, see [llms.txt](https://docs.edgetag.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.edgetag.io/channels/google-ads.md).

# Google Ads

Google Ads integration enables a seamless connection between your Google Ads account and your website, utilizing both browser pixel and server-side tracking. Our integration would attempt to send event data through the browser first (via gtag), and if that didn't work, we would fall back to server-side tracking and send the event data. The integration provides a straightforward setup with simple configuration options to get you started quickly.

### Details

Channel name: googleAdsClicks

NPM package: [@blotoutio/providers-google-ads-clicks-sdk](https://www.npmjs.com/package/@blotoutio/providers-google-ads-clicks-sdk) 

Server API version: [v20](https://developers.google.com/google-ads/api/reference/rpc/v20/overview)

### Event Flow

Our Google Ads integration has multiple event flow options that you can select, i.e., send conversions via Google Ads api only, send conversions via browser (gtag) only, or try sending conversions via browser (gtag) first, and in case that fails, fallback to sending the conversion via the ads api. This integration requires specific conversion actions to be set up in your Google Ads ad account for proper tracking.

{% hint style="info" %}
Please refer to the instructions [here](https://app.gitbook.com/o/c0Wts1N48p0Ba5S58p8v/s/ZJWZKbUk0hRISkCIj2p4/~/changes/95/channels/google-ads/faq#how-to-create-browser-and-server-conversion-actions) to create conversion actions.
{% endhint %}


---

# 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.edgetag.io/channels/google-ads.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.