> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/analyze/ad-insights-google.md).

# Ad Insights (Google)

## How to correctly track contacts

For contacts to appear on the Google Ads Insights panel it is necessary that:

1. The contact acquires [UTM tags](/en/topics/system-settings/tracking/tracking-utm-tag.md) as follows: **utm\_source** with the value `GoogleAds` and the **utm\_content** with the ad ID as the value. The URL would appear as follows: `https://sprinthub.com/?utm_content=726027236388&utm_source=GoogleAds`
2. A [Google Ads account](/en/topics/integrations/integration-google-ads-and-gmail.md)  is integrated within the instance.

In the example below, you can see the contact being correctly identified by a Google campaign, with the information displayed in the UTM Tags tab and recorded in the Activity History.

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

<figure><img src="/files/7a07500ff4fbe08eec3b1052ec7ba5dc5f22ff5d" alt=""><figcaption></figcaption></figure>


---

# 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.sprinthub.com/en/topics/analyze/ad-insights-google.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.