A tracking QA checklist template for campaign launches

Tracking problems are cheaper to find before the spend starts than after the report looks wrong. A short QA pass before launch, and a check on day one, finds them while the spend is still small.

Measurement and reporting · 5 min read · Updated 2026-10-07

Before launch

  • Events: each conversion event is listed with its name and its trigger in the definitions sheet.
  • Test order: a test purchase fires each event once, and the result is checked in every tracking tool the account uses.
  • Values: the purchase value matches the order total under the definition the client signed off, with shipping and tax treated as agreed.
  • Duplicates: one order gives one purchase event, including after a refresh of the thank-you page.
  • Consent: the consent setup is tested for each market served, and the events behave as the client's policy says.
  • Links: every destination link carries its UTM tags, checked with the UTM builder.

Day one

  • Compare store orders with platform purchases for the same hours, and write any gap in the log.
  • Check that each event still fires on the live page, on a phone and on a desktop.
  • Mark every gap as explained, suspected or not measured. Never as zero.

Record

  • Date, tester, the version of the tag setup, and pass or fail on every line.
  • A failed line blocks the spend that depends on it until a read-back passes.
Made-up scenario: a made-up store launches with a thank-you page that fires the purchase event on every refresh. The test order shows two purchases for one order. The fix is approved and logged, the duplicate is removed, and the day-one check counts the orders again before the spend is raised.

Tick it off

Your ticks stay in this browser only.

Built for shop owners, creators and agencies. Stock photos, not customers.

Run the next client review from one screen.

We open one agency at a time, with your own accounts connected read-only first.

Request access

How we plan to price it