Analytics
Connects your storefront to Google Analytics so you can see where visitors come from and what they do.
| Section | Settings → Apps |
| Panel route | /admin/analytics-settings |
| Access needed | Platform → Settings → View list |
The settings
| Field | Accepts | Notes |
|---|---|---|
| GA4 measurement ID | Starts with G- | Leave empty to disable Google Analytics |
| Google Tag Manager container ID | Starts with GTM- | Only if you run your own container |
| Ask visitors for consent | On or off | On means no analytics cookie until the visitor accepts |
| Consent cookie domain | A domain such as .example.com | Shares the consent choice with your subdomains |
| Action | Does |
|---|---|
| Save | Applies the settings |
| Reset | Discards unsaved changes |
Where to find your measurement ID
In Google Analytics: Admin → Data streams → your web stream. It starts with G-.
Tag Manager
Only fill this in if you already run your own Google Tag Manager container.
If you add a GA4 configuration tag for the same measurement ID inside your Tag Manager container, every hit is counted twice. Use one route or the other.
Consent
| Setting | Behaviour |
|---|---|
| On | No analytics cookie is written until the visitor accepts |
| Off | Analytics runs immediately |
The screen says exactly this. Cookie consent rules vary by market and the safe default is to ask.
Consent cookie domain shares a visitor's choice across your subdomains — set .example.com if you also run something at blog.example.com. Leave it empty to keep the choice to this domain only.
What customers see
With consent on, a consent banner on their first visit, offering Accept all, Reject all and Customize, where they can switch Analytics and Advertising on or off separately (Necessary is always on). A Cookie settings link in your footer lets them change their choice later. Their choice is remembered across the domain you configured.
With consent off, there is no banner and no Cookie settings link.
Scenarios
Basic setup
Enter the GA4 measurement ID, leave Tag Manager empty, leave consent on, leave the cookie domain empty.
You run a blog on a subdomain
Set the consent cookie domain to .example.com so visitors are asked once rather than on each subdomain.
Your numbers look doubled
You have a GA4 configuration tag for the same measurement ID inside your Tag Manager container as well as here. Remove one.
Stop collecting analytics
Clear the measurement ID, and the container ID if you set one, then save.
Questions
Do I need Tag Manager? No. It is only for sellers who already run their own container.
Will analytics work if consent is on? Yes, for visitors who accept. Those who decline are not tracked.
Can I connect something other than Google Analytics? Not from this screen.
Why is my ID rejected? A measurement ID looks like G-XXXXXXXXXX, a container ID like GTM-XXXXXXX, and a cookie domain like .example.com. The cookie domain must also be your storefront's own domain or a parent of it: .example.com is accepted for a store at shop.example.com, a domain you do not run is not.
Related
- Build your storefront
- Content Pages — your privacy policy · Platform Settings