Tag Hygiene & Delivery: Recap And Verify

5 questions. Answer all of them, then submit; you need 4 of 5 to pass.

1. 1. A framework bug pushes the same purchase_attempt event twice per click. Your conversion tag's firing option is Once per event, yet it still fires twice. Why?

   Once per event has a known race condition with fast clicksEach push is a brand-new dataLayer event, so Once per event happily fires the tag once for each of themThe trigger needs a Just Links type insteadThe dataLayer deduplicates pushes only after 500 ms
2. 2. Which Tag firing option actually stops a re-pushed duplicate event from firing the tag twice on one page load?

   Once per eventUnlimited, plus a longer trigger delayOnce per pageThere is no such option; duplicates cannot be stopped in GTM
3. 3. When is a Custom HTML tag the right choice?

   Whenever you want full control over a vendor's scriptFor all conversion tags, since they need exact timingNever; Custom HTML is deprecatedOnly when no official template or native tag type exists for what you need
4. 4. Your Custom HTML pixel can end up injected twice when its triggers overlap. What is the standard in-script defence?

   An id guard: mark the first injection (for example with a flag or element id) and bail out if it already existsCalling document.write twice is safe, so no defence is neededSetting the tag's priority to 100Wrapping the script in a setTimeout
5. 5. Even with Once per page set, the same purchase can be reported on two different page loads (a refresh of the thank-you page). What protects the data?

   Once per page persists across reloads, so nothing more is neededBlocking refreshes with an exception triggerSending a stable transaction_id, which GA4 uses to deduplicate the purchase in reportingLowering the tag's priority