Study first
Review the ideas behind the questions
These notes cover GTM decisions that affect data quality, consent behavior, debugging, and release recovery.
Data layer and custom events
Intermediate GTM work often depends on clear data layer events instead of fragile page scraping. A good event tells Tag Manager what happened and includes the values the tag needs at that moment.
- Use named data layer events for important app interactions that do not create normal page loads.
- Push values before or with the event that triggers the tag.
- Keep data layer variable names consistent across pages and templates.
- Avoid relying on delayed DOM reads for values needed by a tag at fire time.
Trigger and variable diagnosis
Triggers decide when tags fire, and variables decide what values tags and trigger rules can use. Most tracking bugs come from a trigger that is too broad, too narrow, or reading the wrong variable.
- Enable built-in click variables before using Click ID, Click Classes, Click Text, or Click URL.
- Narrow broad click triggers with stable conditions or a dedicated custom event.
- Use exception triggers when a tag should be blocked in specific situations.
- Use a trigger group only when multiple trigger conditions must happen before a tag fires.
Consent, preview, and recovery
Important tag changes should be tested before publishing. Consent setup needs special care because it can affect whether analytics and advertising tags are allowed to run.
- Use Consent Initialization for tags that establish consent state before other tags evaluate.
- Use preview mode to inspect the event timeline, variables, and tags that fired or did not fire.
- Publish clear versions so changes are easier to review later.
- If a publish breaks measurement, review versions and restore or publish a known-good version.