UTMCraft campaign launch QA record
Revision: 2026-10-07 | https://utmcraft.com/how-to-test-utms/

Campaign / stable ID:
Owner / reviewer:
Launch date:
Published placement:
Approved URL:
Test date / browser / device:
Consent state tested:
GA4 property / web stream:
CRM test record (internal reference only):

1. Naming: source, medium and campaign match the approved register.
   No personal information; no duplicate parameters; no unresolved tokens.
   Preserve opaque click identifiers exactly as supplied.
   Result / evidence:

2. Delivery: test the published ad, delivered email, shared link or final QR.
   Follow every wrapper and redirect. Compare the final decoded values.
   Result / evidence:

3. Collection: confirm the intended property receives the landing event.
   Enable personal-device debug mode via Tag Assistant / GTM Preview.
   Inspect the collected page URL and consent-dependent behavior.
   DebugView is a collection check, not final attribution proof.
   Result / evidence:

4. Conversion: complete a permitted test form or sandbox checkout.
   Check the saved campaign bundle, conversion event and duplicate handling.
   Repeat payment return, multi-page and mobile paths where applicable.
   Result / evidence:

5. Reporting: after processing, inspect Session source / medium and campaign.
   Compare manual and platform dimensions with the same reporting scope.
   Review unwanted referrals and channel classification where applicable.
   Result / evidence:

6. Release: record the approved version, remaining limits and next review.
   Remove debug setup as appropriate; check developer-filter settings.
   Keep test screenshots private and redact identifiers before sharing.
   Approval / remaining issues:

A URL syntax checker does not validate redirect behavior, tag installation,
consent, platform token expansion, CRM capture or final attribution.