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

# Google Ads

Connect Google Ads to pull campaign cost, clicks and conversions into your reports and the Marketing Mix Model.

Connect Google Ads so AdPage can read what you spent and what it returned. The connection is **read-only** by default: AdPage reads campaigns, cost and conversions, and never changes a bid, a budget or a campaign.

{% hint style="info" %}
AdPage can create and rename conversion actions in Google Ads, but only as a separate, explicitly confirmed step during tracking setup — never as part of this connection.

The one thing this connection can write is a correction for returns. With [Returns to Google Ads](https://docs.adpage.io/optimize-your-setup/returns-to-google-ads) switched on in the container settings, AdPage retracts or lowers the conversions of returned orders. It stays off until you switch it on.
{% endhint %}

### Before you start

You need a Google account with at least **read access** to the Google Ads accounts you want to connect. An MCC (manager) account works and is usually the better choice: approve once, then pick the client accounts you need.

To send returns to Google Ads, that Google account needs at least **Standard** access to the Google Ads account; Admin is not needed. Read-only access is not enough, because Google only lets users who can make changes adjust conversions.

Have your **customer ID** to hand — the ten-digit number at the top right of the Google Ads interface, written as `123-456-7890`. You will need it if the account does not appear in the list by itself.

As with all Google platforms, the access lives with the account you approve with. Use one that will still exist next year.

### Connect Google Ads

{% stepper %}
{% step %}

#### Open the tile

Go to **Integrations**, select the container, and open the **Google Ads** tile.

<figure><img src="https://1954565367-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK5kjEu8mwstNkOrvFl6S%2Fuploads%2FTbbgGE427ZFYhQpjMKSn%2Fintegrations-google-ads-tile-en.webp?alt=media" alt="Google Ads tile opened on the Integrations page"><figcaption><p>The Google Ads tile on the Integrations page.</p></figcaption></figure>
{% endstep %}

{% step %}

#### Approve access at Google

Select connect. Google shows what is being requested — your identity, and access to Google Ads. Approve it.
{% endstep %}

{% step %}

#### Choose your accounts

AdPage lists the Google Ads accounts the approved account can reach. Tick the ones that belong to this container and save.

If an account you expect is missing, type its customer ID into the manual field. This is common with accounts reachable through an MCC that the list API does not return.
{% endstep %}
{% endstepper %}

### What you get

Google Ads cost and conversions appear in the **Channel KPIs** and **Campaigns & Attribution** sections, next to every other paid channel on the same basis, so blended ROAS actually means something.

Spend also feeds the **Marketing Mix Model**. Google Ads is usually the largest single line in the model, and its history is what lets the model separate what advertising caused from what would have happened anyway.

Keyword-level performance is available to the Data Assistant, so you can ask which search terms carried a campaign without building a report for it.

### Reading the numbers

**Google Ads conversions are not last-click.** Google attributes with its own model across its own window, and reports a conversion on the date of the *click*, not the date of the sale. AdPage measures last-click on the day the order happened. The two will differ — most visibly right after a campaign change.

**Cost is final, conversions are not.** Spend settles quickly. Conversions keep being added to past days for up to about a month as Google closes its attribution window, so yesterday's ROAS will rise slightly over time.

**Currency comes from the account.** An account reporting in a different currency than your other sources will not be converted. Connect accounts that share a currency, or read them separately.

### Troubleshooting

**No accounts appear.** The approved account cannot see any Google Ads account, or only through an MCC the API does not enumerate. Enter the customer ID manually.

**"Customer not enabled" or a permissions error.** The account is cancelled, suspended, or the approved user was removed from it. Check in Google Ads that the account is active and the user is still listed.

**The tile says the connection expired.** Reconnect from the tile. If Google Analytics or Tag Manager also stopped, that confirms it: all three share one Google access and all three need reconnecting.

**Spend shows but conversions do not.** The account is reachable but has no conversion actions recording, or they are not set to be included in the "Conversions" column. That is a Google Ads configuration question, not a connection one.

Still stuck? Contact <support@adpage.io> with the container and the customer ID.


---

# 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.adpage.io/data-and-insights/marketing-integrations/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.
