Study first
Review the ideas behind the questions
Review the GTM controls that decide when a tag fires and what value it receives. Focus on frequency, order, schedules, published-only behavior, lookup tables, and value cleanup before you judge a container change.
Choose the firing frequency deliberately
A tag can fire more often than the business event needs. Intermediate GTM checks whether the firing option matches the event, page load, and duplicate-risk behavior.
- Unlimited firing lets a tag fire whenever its triggers tell it to fire.
- Once per event can prevent the same tag from firing more than once on a single event.
- Once per page fits tags that should load only once during the page load.
In Practice
Frequency is not a trigger fix
Firing options control how often a tag runs after trigger logic is evaluated. They do not make a broad trigger specific or prove that the right event was chosen.
Page-load controls need SPA review
A page-load-only choice can be wrong when the site changes views without a full reload. For single-page apps, check whether the action creates the event that should fire the tag.
Common mistakes
Using Once per page to hide a tag that has the wrong trigger.
Fix the trigger or event first, then choose the firing option that matches the intended frequency.
Q&A
When should Once per event be considered?
Use it when one event could otherwise cause the same tag to fire more than once.
What should be checked before choosing Once per page?
Check whether the tag truly needs only one page-load fire, especially if the site changes views without reloading.
Use sequencing when order matters
Some tags need another tag to run directly before or after them. Sequencing is the GTM control for that ordered setup, while priority only influences firing order and still needs careful interpretation.
- A setup tag can fire immediately before the primary tag.
- A cleanup tag can fire immediately after the primary tag finishes.
- Tag Firing Priority affects order, but tags still fire asynchronously.
In Practice
Failure behavior must be explicit
A setup or cleanup sequence can include a fail-safe choice. Decide whether the main tag should stop when setup fails, or whether cleanup should run only after the primary tag succeeds.
Current-event values need the right method
When a setup tag changes a value for the current event, the documented approach is the Tag Manager data layer set method, not a normal data layer push.
Common mistakes
Treating tag priority as proof that one tag finished before another tag started.
Use tag sequencing when the order relationship needs to be precise, because priority does not remove asynchronous firing behavior.
Q&A
What should block the primary tag if setup fails?
Use the setup-tag sequencing option that prevents the primary tag from firing when the setup tag fails.
Shape variables before tags use them
Variables can make GTM setups easier to reuse, but only when the selected variable type and formatting rule match the value the tag needs.
- A lookup table can map one variable value to another output value.
- A RegEx Table can match patterns when exact lookup rows are not enough.
- Format Value can normalize returned values, such as case, null, undefined, true or false, and numbers.
In Practice
Mapping should be reviewable
A lookup table is useful when a small, explicit mapping can be checked by the team. If the logic depends on many moving page patterns, a RegEx Table or cleaner source data may be safer.
Formatting is not data repair
Format Value can normalize the value a variable returns, but it should not be used to hide missing or wrongly collected data. Check the source value first when the variable is blank or unreliable.
Common mistakes
Using a lookup table to cover up inconsistent source values that should be fixed upstream.
Use a lookup table for clear mappings, and fix the source data when the incoming value itself is unstable or wrong.
Q&A
When is a lookup table a good fit?
Use it when one known input value should return one planned output value, such as mapping a page pattern to a conversion ID.
What should Format Value be used for?
Use it to normalize the value returned by a user-defined variable, such as case, numbers, or empty values.