Multiple GA4 IDs on one store: what does it mean?
Several Google Analytics 4 (GA4) IDs on one store means your data goes to more than one GA4 property. Sometimes that is deliberate, for example an agency property next to yours. Often it is a leftover from an old agency, a test or an app. The fix starts with finding out where each ID sends data and who owns it.
Symptom
A tag checker lists two or more different G- IDs on your store. Or your GA4 numbers differ from what your agency reports, and it turns out you are each looking at a different property. Or you can't find one of the IDs in any GA4 account you have access to.
This is a different problem from the same ID loading twice. Here the IDs are different, so each property receives its own copy of the data.
Possible causes
- Cause A: intended destinations. A store sends to its own property and an agency's property, or to a brand property and a roll-up property. This can be reasonable if it is documented.
- Cause B: a leftover property. A previous agency, freelancer or theme developer set up their own property and it was never removed.
- Cause C: two installs that disagree. A platform app is connected to one property while Google Tag Manager (GTM) or a theme snippet uses another. On Shopify this often happens when the Google and YouTube app was connected after GTM was already in the theme.
- Cause D: a test or migration property. A property created for testing, or one created during the move from Universal Analytics, was left live.
- Cause E: one Google tag, several destinations. A single Google tag can be set to send to more than one destination. One loader on the page can therefore feed two properties.
How to check
- List the IDs and where they come from. Use Tag Assistant and the page source. For each ID, note the source: theme, GTM, app, plugin or custom pixel.
- Match each ID to a property. In each GA4 account you can access, open Admin, Data streams. Any ID you can't find belongs to a property you don't control. Write that down: it matters for data protection as well as reporting.
- See which events go where. In DevTools, Network, filter on
collectand walk from product page to cart. Note thetidandenpair on each request. For the purchase, use a test order or the platform's preview tools where available. - Check the Google Ads link. In each property, Admin, Product links, Google Ads links. If you import GA4 key events into Google Ads, the linked property is the one your bidding depends on.
- Check Google tag destinations. In GA4, Admin, Data streams, your stream, Configure tag settings. The tag page lists the destinations a Google tag sends to.
An illustrative finding, with invented IDs:
| ID | Source | Events seen | Owner |
|---|---|---|---|
| G-AB12CD34EF | Shopify app pixel | page_view, add_to_cart, purchase | Store owner |
| G-ZY98XW76VU | Theme snippet | page_view only | Unknown, not in any account we can access |
In this example the second property gets page views but no ecommerce events. Anyone reporting from it would see traffic without sales.
What the result means
- All IDs known, owned and documented: cause A. No fix needed, but make sure each property receives the events its owner relies on.
- An ID nobody owns: cause B or D. That property collects your visitors' data for someone you don't work with any more.
- Different events in each property: cause C. Two people can read two "correct" reports that disagree.
False positive. Some GTM containers hold a lookup table that picks a different GA4 ID per country site or domain. A scan of the container finds several IDs, but only one fires on each site. Our public check ignores lookup tables of country IDs for this reason. Confirm with the network requests on each domain.
Our public research. In our check of 975 Shopify stores on 14 November 2026, 38 showed several GA4 IDs. That is a screening observation, not a confirmed fault: some of those may be intentional, and a public-page check can't confirm whether purchase tracking works.
How to fix it
- Decide which property is the record for the business, and who owns it. The store owner should hold admin access to it.
- For each additional ID, either document why it exists and who uses it, or remove it.
- If two properties must stay, send both the same ecommerce events from one place, rather than maintaining two parallel installs.
- Make sure the Google Ads link and any imported key events point at the record property.
- After the change, repeat step 3 and confirm each remaining ID gets exactly the events you intended.
What not to do
- Don't remove an unknown ID before asking who uses it. An agency's bidding or a finance report may depend on it.
- Don't switch your reporting to a new property mid-month without noting the date. Comparisons across the switch will mislead.
- Don't keep an ownerless property running "just in case".
When to request help
A GA4 and GTM audit traces every destination, the events each one receives and which property your ads rely on, then gives you a written recommendation.
Related guides:
- Why is the same GA4 tag loading twice?
- Found Universal Analytics code on your store?
- Why doesn't GA4 revenue match your store?
Not sure what's wrong?
Send us your store address. Mikael will review the visible tracking signals and explain what can be checked from your public pages.
Sources and updated date
- Google Analytics Help: Configure your Google tag settings
- Google Tag Manager Help: Google tag ID
- Google Analytics Help: Add a Google Analytics property to a site that already has Analytics
- Google Analytics Help: Measurement ID
Last checked against official documentation: 18 November 2026.