CAMPAIGN TO CHECKOUT
Use a tagged test visit and check that the campaign source survives programme selection and any hosted checkout handoff.
One tagged visit EXAMPLE
yourfirm.com/2-step?utm_source=meta&
Same visit, tag kept at every step
Reconcile reported conversions with paid challenge orders. Bring a campaign and programme where the numbers disagree, and we’ll trace the exact step where reporting changes.
Same period, different countsOne programme, one campaign
EXAMPLE DATAextra purchases in the ad reportCompare the reporting window and individual order IDs.
Follow a test order across the landing page, checkout, payment confirmation and reporting. Record the order ID at each handoff.
Use a tagged test visit and check that the campaign source survives programme selection and any hosted checkout handoff.
One tagged visit EXAMPLE
yourfirm.com/2-step?utm_source=meta&
Same visit, tag kept at every step
Find which system confirms a successful payment. Compare GA4 purchases with paid challenge orders on a stable transaction ID.
Match on one ID EXAMPLE
T-10482The paid order is the source of truth
Check refreshes, provider retries, failed payments and refunds. Decide which event should fire, and which system owns it.
Event log EXAMPLE
purchaseT-10482CountedpurchaseT-10482 · refreshDuplicatepayment_failedT-10490No purchaserefundT-10477ReversedCheck when tags load, which fields are sent and where attribution can drop. Keep measured gaps apart from normal differences between platforms.
Consent first EXAMPLE
We use cookies to measure what sells.
AcceptDeclineFIELDS SENT WITH A PURCHASE
The event map identifies the authoritative trigger, owner and acceptance check for every reported conversion. Pair it with an order and refund export to see what was counted.
Event mapSample firm “Your Firm”
EXAMPLEview_programmeFires whenA programme page opensOwnerSiteFires once per viewbegin_checkoutFires whenA buy button is clickedOwnerSiteIntent only, not a salepurchaseFires whenPayment is confirmedOwnerCheckout providerMatches a paid order IDrefundFires whenAn order is refundedOwnerOrder systemReverses the purchaseBring its integration docs, or ask the provider which events and exports it supports. We work from what it can send.
INTENT IS NOT PAYMENT
A checkout clickshows intent
The paid order recordproves payment
Start with a redacted sample of paid and refunded orders, the corresponding reporting period and the platform that owns checkout.
Call checklistThree things to have open
Your public landing and checkout URLsThe pages a trader sees, from the ad to payment
The tools you useAnalytics, ad platforms, checkout and order system
One example of the mismatchOne programme, one month: what the ads say and what was paid
Use test data or totals for the first call, never customer records.
See how the programme selection is carried into checkout, plus the QA checklist for verifying price, currency and the selected package.
Bring one reporting discrepancy. We’ll identify which handoff needs to be reproduced and which records should agree afterward.
Allow Google Analytics to help us understand which pages people use and where they start booking. You can change your choice in Cookie settings.