A Pre-Publish QA Checklist

QA shouldn't be improvised. Run the same checklist every time and the silent failures stop reaching production.

Before you publish

• Each new/changed tag fires on the intended event, and only then (check a few pages where it should not fire).
• Key parameters are present and the right type (verify in the Network request, not just Preview).
• The destination received it (GA4 DebugView / vendor test tool).
• No tag double-fires (no duplicate collect requests).
• Consent behaves: denied → held, granted → fires.
• Name the version clearly and write what changed, so you can roll back.

After you publish

• Spot-check the live site (Preview uses a draft; production can differ).
• Check realtime reports an hour later for volume anomalies.
• Keep the previous version handy, one click to revert if numbers move wrong.