> For the complete documentation index, see [llms.txt](https://docs.patagon.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patagon.ai/en/marketing-and-attribution/google-campaigns.md).

# Google Ads

You can drive WhatsApp conversations from Google Ads too. There are two ways to do it, and they differ in one important way: **whether Patagon AI can attribute the resulting leads.**

| Path                                  | What it is                                                                        | Patagon attribution                                                                                 |
| ------------------------------------- | --------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| **Landing → WhatsApp**                | A Google ad sends people to your landing page, where they click a WhatsApp button | ✅ The landing page runs the Patagon AI script, which captures the `gclid` and your UTMs             |
| **Click-to-WhatsApp (Message Asset)** | A Google ad opens WhatsApp directly, with no landing page                         | ❌ No landing page means no script, so the conversation reaches your agent but appears **untracked** |

**Landing → WhatsApp is the recommended route** whenever you want attribution — it's the only Google path Patagon AI can currently measure.

## What you can optimize for today

Patagon AI doesn't send conversions back to Google yet, so you can't optimize Google campaigns for *qualified* leads the way you can with Meta. For now, **optimize for conversations initiated** — set up the WhatsApp click as a conversion in Google and optimize your campaigns for that.

{% hint style="info" %}
**Coming soon.** Google offline conversions (using the `gclid`) are on our roadmap — that's why capturing the `gclid` now matters. Once it ships, you'll be able to send qualified-lead conversions back to Google, just like Meta.
{% endhint %}

## In this section

* [How to create landing → WhatsApp campaigns with Google Ads](/en/marketing-and-attribution/google-campaigns/landing-to-whatsapp.md) — the recommended, attributable setup.
* [How to create Click-to-WhatsApp campaigns with Google Ads](/en/marketing-and-attribution/google-campaigns/click-to-whatsapp.md) — Message Assets, and why they're untracked in Patagon AI.
* [How to set up Google Ads attribution (UTMs)](/en/marketing-and-attribution/google-campaigns/google-utm-tracking.md) — auto-tagging and the UTM final URL suffix that make attribution show up in Patagon AI.


---

# 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.patagon.ai/en/marketing-and-attribution/google-campaigns.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.