> 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-analytics.md).

# Google Analytics

Connect GA4 to bring sessions, conversions and traffic sources into your AdPage reports.

Connect Google Analytics 4 so AdPage can read your sessions, conversions and traffic sources alongside your advertising and order data. The connection is **read-only**: AdPage asks for `analytics.readonly` and nothing else, so it can never change a property, a conversion definition or a data stream.

### Before you start

You need a Google account with at least **Viewer** access to the GA4 properties you want to use. You do not need to be an administrator.

The account you approve with matters more than it looks. AdPage keeps reading through that account, so approving with a personal account belonging to someone who may leave is the most common cause of a connection that breaks months later. A shared account, or one owned by the agency that manages the property, survives staff changes.

You also need a container selected in AdPage. The connection is stored per container.

### Connect Google Analytics

{% stepper %}
{% step %}

#### Open the tile

Go to **Integrations**, select the container at the top of the page, and open the **Google Analytics** tile.
{% endstep %}

{% step %}

#### Approve access at Google

Select connect. Google asks which account to use and shows what AdPage is requesting: your identity, and read-only access to Analytics. Approve it and you are returned to AdPage.
{% endstep %}

{% step %}

#### Choose your properties

AdPage lists every GA4 property the approved account can reach, which for an agency account can be hundreds. Search by name, tick the properties that belong to this container, and save.

Only ticked properties are ever queried. A property you leave unticked stays invisible to AdPage even though the account can technically reach it.
{% endstep %}
{% endstepper %}

The tile then shows which properties are connected. You can come back and change the selection at any time without reconnecting.

### What you get

GA4 feeds the sessions and traffic-source side of your reports: which channels brought visitors, how they moved through the funnel, and what GA4 itself counted as a conversion.

It also gives the Data Assistant something to compare against. When your server-side tracking and GA4 disagree, that gap is itself the finding — it usually means events are being lost in the browser, and the **Data Quality** section is built to show exactly that.

### Reading the numbers

**GA4 will not match your ad platforms, and should not.** GA4 attributes on its own model over its own lookback window; Google Ads counts a conversion at the moment of the click that led to it. Both are right by their own definition. Use GA4 for behaviour and traffic mix, and the ad platforms for what each platform delivered.

**GA4 samples and thresholds.** On large properties GA4 applies sampling, and it hides rows when a report could identify individuals. A number that moves when you change the date range slightly is usually one of these two, not a tracking fault.

**Server-side tracking is the fuller picture.** Where GA4 depends on the browser, AdPage Tracking sits on your own server-side container and does not lose events to ad blockers or short-lived cookies. Where the two disagree, the server-side number is generally the more complete one.

### Troubleshooting

**No properties appear.** The approved Google account cannot see any GA4 property. Check in Google Analytics under **Admin → Property access management** that the account is listed. Beware of approving with the wrong account when several are signed in on the same browser — Google picks one silently.

**Universal Analytics properties are missing.** Only GA4 is supported. Universal Analytics stopped processing data in 2024 and its API is gone, so there is nothing to read.

**The tile says the connection expired.** Google is refusing the stored access. Usually the password changed, AdPage was removed from the account's connected apps, or the account lost access to the property. Reconnect from the tile.

**Google Ads and Tag Manager broke at the same time.** They share one Google access. Reconnect each of the three tiles you use — fixing one does not fix the others.

**The numbers dropped to zero on one day.** Check whether the property is still receiving data at all in GA4 itself. If GA4 is empty too, the problem is upstream of AdPage.

Still stuck? Contact <support@adpage.io> with the container and the property 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 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.adpage.io/data-and-insights/marketing-integrations/google-analytics.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.