> 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/data-studio/stores-and-ga4-properties.md).

# Stores and GA4 properties

One container, several webshops? Link each GA4 property to the shop it measures, so Data Studio adds up sessions and GA4 revenue across all of them.

When one AdPage container serves several webshops — a shop per country, or a second brand — Data Studio shows a **Store** filter in its toolbar. Next to it, the gear links each GA4 property to the shop it measures.

Until that link exists, every GA4 number in Data Studio comes from a single property: the default one. Sessions, conversion rate and the new customers behind the CAC then describe one shop, while orders and revenue come from all of them.

### When you see the Store filter

The filter appears as soon as AdPage receives orders from more than one shop in the last 90 days. A Shopify storefront counts as a shop and shows under its public domain, such as `www.yourshop.de`. With a single shop there is nothing to choose, and the filter stays hidden.

<figure><img src="https://1954565367-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK5kjEu8mwstNkOrvFl6S%2Fuploads%2FXvSJkfQbcDnifYvRCJDv%2Fstore-filter-toolbar-en.webp?alt=media" alt="The Store filter in the Data Studio toolbar, with the gear and the note that GA4 is not linked yet"><figcaption><p>The Store filter, the gear, and the note that shows while no GA4 property is linked.</p></figcaption></figure>

### Link your GA4 properties

{% stepper %}
{% step %}

#### Open the settings

In Data Studio, select the gear next to **Store**, or **Link a GA4 property** in the note below it.
{% endstep %}

{% step %}

#### Choose a shop for each property

Under **GA4 properties**, pick the shop each property measures. Every choice is saved straight away; **Done** only closes the window.

<figure><img src="https://1954565367-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK5kjEu8mwstNkOrvFl6S%2Fuploads%2FcTTrNxScbIYt0X28mXsw%2Fstore-mapping-dialog-en.webp?alt=media" alt="Link integrations to stores: each GA4 property with the shop it belongs to"><figcaption><p>Each shop's property linked to its shop. The roll-up property stays on Not linked.</p></figcaption></figure>
{% endstep %}

{% step %}

#### Leave roll-up properties on Not linked

A property that collects several shops at once — a roll-up property, or one a profit tool writes to — stays on **Not linked**. Linking it would count those shops twice.
{% endstep %}
{% endstepper %}

The links belong to the container, so everyone who opens it sees the same result.

### What changes

**All stores adds up the linked properties.** Sessions, conversion rate, GA4 revenue and the GA4 new customers now cover every shop instead of the default property alone.

**One store narrows everything to that shop.** Select a store and GA4 reads only its property, while orders and revenue follow the same shop. Google Ads and Meta show only the campaigns you linked to that shop in the same window, so link those too if you want to look at one shop at a time. A store without linked campaigns shows no Google Ads or Meta spend.

### Troubleshooting

**There is no Store filter.** AdPage saw orders from only one shop in the last 90 days. If you do run several shops, check that each of them sends its orders to this container.

**A property is missing from the list.** Only the properties ticked under [Google Analytics](https://docs.adpage.io/data-and-insights/marketing-integrations/google-analytics.md) appear. Tick it there, then open the window again.

**The totals look about twice as high.** A roll-up property is linked next to the shops it contains. Set it back to **Not linked**.

**The note disappeared, but GA4 still looks low.** The note goes away once one property is linked. Link the other shops' properties as well.

Still stuck? Contact <support@adpage.io> with the container and the property IDs.


---

# 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/data-studio/stores-and-ga4-properties.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.
