Google Tag Manager

A simple example

Your store confirms a purchase. GTM can use that action and its order information to run the appropriate measurement tag, under the agreed consent rules.

The three pieces to understand

A tag sends or processes information. A trigger decides when it runs. A variable supplies values used by the tag or trigger. A data layer provides structured information from the site, so a purchase can be described consistently instead of inferred from a fragile page element.

Why a data layer matters

Google describes the data layer as a queue processed in order. For a business, the design question is what information belongs with each action. Put an event name and its relevant values together. Document which application owns that event and which destinations receive it.

How to manage a change

• Record the reason, expected event and affected destinations.
• Use the preview tools to inspect the trigger and values on real journeys.
• Check consent behavior and remove overlapping implementations.
• Save a named container version and a rollback note.
• Recheck after checkout, theme or consent-platform changes.

Common failure pattern

A store integration already sends purchases, then an additional GTM tag sends the same action again. More tags can produce less trustworthy data. Map the existing implementation before adding anything, and give one person responsibility for approving measurement releases.

Organise changes before adding more tags

Consider a store where marketing requests a new conversion tag while a developer is changing checkout. Publishing both changes without a shared event definition makes later diagnosis difficult. A tagging plan should identify the action, the data required, the trigger, the destination and the person responsible for testing it. Container access alone does not establish that plan.

Our recommended handover is a small implementation register that the next person can understand. Record why each tag exists, which consent conditions apply in the agreed design, and how its behaviour was checked. Keep business logic in a documented data layer rather than relying on fragile page text wherever the platform allows it. Treat an unexplained tag as a question to investigate, rather than automatically deleting it.

• Test a complete journey, including failed or abandoned actions, before publication.
• Keep a known working version and an agreed rollback owner for each release.
• Recheck important events after changes to checkout, templates or consent controls.

Explore tag implementation →