GTM. Tag pause and resume. Stop bad hits during checkout incidents fast.

What this means for your store

When checkout breaks, the fastest lever is often in GTM - not a theme rollback. Every tag can be paused from the container UI: it stays in the workspace but does not fire after publish. During a gateway outage or a duplicate purchase bug, pausing the offending conversion tags stops polluted data reaching GA4 and Google Ads while engineering fixes the root cause.

Scenario on a real storefront

Payment errors spike at 2 p.m. ET. Orders complete in Shopify but thank-you pages still push purchase with value: 0. You pause GA4 purchase and Ads conversion tags until checkout is stable:

Tags → GA4 - purchase → ⋮ → Pause tag
Tags → Google Ads - Purchase Conversion → Pause tag
Submit → Publish version "INC-4421 pause purchase tags"

// Resume after fix verified in Preview:
Tags → select paused tags → Resume tag
Publish "INC-4421 resume purchase after gateway fix"

// Link workspace description to the incident ticket

What to do next

• Maintain a runbook of tags safe to pause (remarketing) vs tags that need stakeholder sign-off (consent initialization).
• Paused tags still fire in Preview - confirm sequencing before you resume and pollute live reports again.
• If the bug is in dataLayer, pausing tags is a bandage; fix the push and add a QA trigger that blocks publish when value is zero.

Bottom line

Pause and resume is the emergency brake in GTM. Use it to stop bad conversion data during checkout incidents, then publish a clean resume version once orders look right.