How-to · Updated October 11, 2026
Find where GA4 is installed when it isn't in Tag Manager
Updated October 11, 2026
20 minutes
In GA4, open your web data stream, click Configure tag settings and note every tag ID on your Google tag. An AW- ID there means GA4 can load through the Google Ads tag, which the container's tag list never shows. Then use Tag Assistant to see which ID the site loads before adding any GA4 tag.
Before you start
- Editor access to the GA4 property. Google requires Editor or above to open a data stream and find its tag ID.
- Access to the site's Tag Manager container, to search it for the IDs you find.
- Google Chrome, for Tag Assistant and the Network tab.
List the tag IDs that send to your property
One Google tag can carry several tag IDs and send to several products, so start from the GA4 property and list every ID connected to it.
- In GA4, click Admin, then under Data collection and modification, click Data streams, and click your web stream. Copy the Measurement ID, which usually starts with G-.
- Under Google tag, click Configure tag settings. Under Your Google tag, click the Google tag at the left side of the diagram and read every ID under Tag details.
- If an ID starting AW- is listed, your Google Ads tag and GA4 share one Google tag. Google's setup advice is to install the Google tag in one product and add the other as a destination, so when the AW- tag loads on a page it can send to GA4 too.
- On the Google tag screen, click the Admin tab, then Manage Google tag, and read the Destinations list. Every product listed receives data from this tag. Find out who owns any account you don't recognize before changing anything.
Find which ID the site loads, and from where
Once you know the IDs, the live site tells you which one actually loads, and the container tells you whether Tag Manager is what loads it.
- Go to tagassistant.google.com, click Add domain, enter your website address and click Connect. Note the IDs in the Google tags found list.
- In Tag Manager, open the container's tag list and look for a Google tag whose tag ID is one of those IDs. A Google tag with an AW- ID may be the one carrying GA4. The container may have no Google tag with a G- ID, even if GA4 Event tags in it show one.
- As a shortcut, open the Google tags tab in Tag Manager and click the tag name to reach its Google tag settings, where the destinations are listed. This works only if you have access to the account that owns that Google tag.
- In Chrome, open the menu (three dots), then More Tools, Developer Tools (on a Mac you can also use View, Developer, Developer Tools). Select the Network tab, reload the page and filter for gtag/js. Each request shows the ID it loads in its address. An ID here that no container holds is loaded by the site's code or a website builder setting.
- Look for a second Tag Manager container too. Tag Assistant lists the containers it finds, and an ID loaded from a container you don't manage still counts.
Write it down and keep one path
GA4 loading through the Google Ads tag is a valid setup, and the mistake to avoid is adding a second GA4 tag because the container seems to have none.
- Record which tag ID carries GA4 and where it loads: the container and tag name, or the site setting. Keep it with your other account notes so the next person does not repeat the search.
- Do not add a G- Google tag to the container while GA4 is still a destination of a tag the site loads. Two tags sending to one property can count page views twice.
- If you add one anyway, watch DebugView with Tag Assistant connected while you load one page. One page_view per load is right. Two usually means two senders: check that the second is not a page view from a browser history change, then remove the extra tag.
Google warns that adding a destination or combining tags can be difficult to undo, so make that kind of change only when you mean to keep it.
Check it worked
Connect Tag Assistant to your site, which turns on debug mode for your browser, then in GA4 open Admin and, under Data display, click DebugView. Accept analytics cookies on the site if it asks, since events don't show in debug mode without that consent. Load one page: one page_view should arrive. Click to another page: one more.
Your notes should now name the tag ID that carries GA4 and the place it loads from, and Tag Assistant's Google tags found list should match them.
Why an audit says there is no GA4 tag
Some tools that read a Tag Manager container look only for a Google tag with a G- ID. When GA4 is a destination of the Google Ads Google tag, that setting lives in Google's tag settings, outside the container, so a container-only check reports GA4 missing while data arrives normally.
Moving GA4 into its own tag in Tag Manager
It is optional. If you want GA4 managed in the container, Google's tag management screen lets you remove a destination, but it asks you to connect that destination to an existing tag or a new one. Plan the container change for the same sitting, preview it, and check DebugView afterwards for one page_view per load.