The same buyer action needs the same meaning across platforms.
PageView, Lead, InitiateCheckout and Purchase are mapped to the exact page or checkout state that creates them, so the buyer is not optimizing against guessed signals.
Meta + Google + TikTok tracking QA
Checkout tracking that proves event, value and buyer exclusion before campaign changes.
This proof shows the first useful tracking pass for a sales page and custom checkout: event map, payload checks, browser/server deduplication, value reconciliation and remarketing exclusion rules that can be validated inside client-owned accounts.
Synthetic proof-of-process, not a client case. No ROAS promise, certification claim or live account operation.
Purchase value is checked before it reaches ad reporting.
The pass compares price source, currency, order ID and item context before trusting revenue events in Meta, Google or TikTok.
Buyers should leave the wrong remarketing audiences.
The proof includes a clean exclusion/update rule for people who purchased, so remarketing does not keep chasing the wrong segment.
Event contract
The first artifact is a buyer-readable event map.
A useful implementation does not start with random tags. It starts with an event contract that says where the event fires, what data travels with it, how it is tested and what decision it supports.
Event
Source
Payload check
Done when
PageView
sales page and checkout entry
url, channel, UTM, click id
all platforms see the same entry path
Lead
form submit or qualified intent
lead id, event_id, campaign context
lead is not confused with purchase
InitiateCheckout
custom checkout opened
product, price source, event_id
checkout starts once per real attempt
Purchase
confirmed payment/order state
value, currency, order_id, dedupe key
report value matches checkout record
Payload lab
The invisible part becomes inspectable before scale.
{
"event": "Purchase",
"event_id": "ord_7842_purchase",
"value": 297.00,
"currency": "BRL",
"order_id": "7842",
"utm_source": "paid_social"
}Value and currency are compared against the confirmed order or payment state, not guessed from the landing page.
Browser pixel and server/API event use a shared event_id so platforms can deduplicate instead of double-counting.
Campaign and click context are checked from first page to checkout completion when the custom flow changes domains or state.
Deduplication and remarketing
Two failure modes that waste money quietly.
Browser + server should not double-count one purchase.
The implementation proves how the browser pixel and server/API event meet on one dedupe key, then records what still needs validation inside the platform event manager.
Remarketing should stop chasing confirmed buyers.
The first pass maps buyer exclusion and audience update logic so campaign operators can validate the rule without us owning ad account strategy, billing or approvals.
Acceptance gates
What a paid tracking QA slice can safely promise.
Gate
Evidence
Done when
Event firing
PageView, Lead, InitiateCheckout, Purchase map
each event has a source and test path
Value integrity
value, currency, order_id and item source
purchase value matches checkout record
Dedupe
browser/server event_id relationship
one buyer action is not counted twice
Audience rule
buyer inclusion/exclusion map
purchasers are routed out of the wrong remarketing pool
Client account validation
notes for Meta, Google and TikTok checks
account owner can verify without sharing billing/KYC ownership
Smallest useful input
What the buyer sends after acceptance.
- Sales page URL and custom checkout path.
- One safe test product or plan with expected price/currency.
- Current pixels, tags, server endpoint or GTM setup if one exists.
- Desired event names and buyer-exclusion rule.
- Platform invites only after scope and platform payment are in place.
Boundaries
What this proof does not claim.
No ad management, no ROAS guarantee, no certification claim, no account approval promise, no billing/KYC ownership, no unsupported bypass and no promise of perfect attribution.