INDEPENDENT MINDS. SHARED AMBITION.
Back to the newsfeed
Measurement1 min read

Google Tag · Status at source date: Newsletter archive

Google Tag Manager fixes containers installed on the wrong path

Written by Paid Media Collective
IN BRIEF

Simo Ahava has flagged that Google Tag Manager now automatically restores full capabilities to containers installed on the /gtag/ path rather than /gtm/, which previously ran only Google tags. A GTM container ID (GTM-XXXX) in either snippet now unlocks all tags, while a Google tag ID, such as G- or AW-, still permits only Google tags.

Original newsletter image: Google Tag Manager fixes containers installed on the wrong path
Via the Paid Media Collective newsletter. Original visual creator unverified.View full-size image

What changed

Google says it affects a small share of containers and has emailed the owners.

THE COLLECTIVE PERSPECTIVE

Why it matters for advertisers

For you, this means a previously limited setup may quietly start working, so check whether any of your containers sat on the gtag path and retest their tags.

Perspective from the original PMC newsletter.

Sources & contributor credit

  1. Newsletter coverage · Paid Media Collective newsletter

    Original newsletter text, contributor labels and media for this update.

  2. Source referenced in newsletterTag Manager Help

    Linked from the original newsletter. The source publication date has not been independently confirmed.

  3. Source referenced in newsletterLinkedIn

    Linked from the original newsletter. The source publication date has not been independently confirmed.

Original creator unverified

The names below are source credits. The original creator and first-reporting priority have not yet been independently verified.

Attribution evidence and limitations

Full attribution review pending.

A source link alone does not establish original authorship.

Original image and video creators have not yet been verified.

FOLLOW THE PEOPLE BEHIND THIS UPDATE
Published on this site

This update reflects the dated source reporting. Availability may have changed. Further coverage of this same development will be added to this page.

Explore the source reporting
Original newsletter text and archive evidence

Google Tag Manager fixes containers installed on the wrong path

Simo Ahava has flagged that Google Tag Manager now automatically restores full capabilities to containers installed on the /gtag/ path rather than /gtm/, which previously ran only Google tags. A GTM container ID (GTM-XXXX) in either snippet now unlocks all tags, while a Google tag ID, such as G- or AW-, still permits only Google tags. Google says it affects a small share of containers and has emailed the owners. For you, this means a previously limited setup may quietly start working, so check whether any of your containers sat on the gtag path and retest their tags.

Source captured . No explicit first-contributor label was provided for this update.

Newsletter coverage (1)Issue 221 · 13 Jul 2026