> 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/knowledge-base/ecommerce-best-practice-for-first-time-setup/add-your-google-ads-account.md).

# Add your Google Ads account

Add your Google Ads secondary conversions

* We recommend that you also create a secondary set of conversions \[ Note: Blotout Edgetag automatically duplicates between client and server side so create two conversions ]
  1. A browser side \[ click based ] conversion
  2. A server side \[ CRM based ] conversion
  3. Ensure both conversions are setup as secondary
  4. We recommend you create conversions for Lead \[ Site ] and Purchase \[ HubSpot conversion ]
     1. You have to create a browser and a server pair
* Once done with setting up conversions as secondary install Google by following instructions [here](https://app.gitbook.com/o/c0Wts1N48p0Ba5S58p8v/s/ZJWZKbUk0hRISkCIj2p4/channels/google-ads)

​Critical events that need to register?

1. Client side Lead events and \[ other ] conversion events need to be mapped and registering
2. Server side will register if Lead events are blocked client side \[ aka de-duplicated ]
3. Finally all conversions should be secondary while you are testing


---

# 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.edgetag.io/knowledge-base/ecommerce-best-practice-for-first-time-setup/add-your-google-ads-account.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.