Tracking Architecture Standards
Garbage in, garbage out. The algorithm cannot optimise what it cannot see accurately. These tracking architecture standards form the foundation that makes Smart Bidding work rather than guess.
Garbage In, Garbage Out
Every Smart Bidding decision is based on the conversion data you feed it. If that data is wrong, every bid is wrong. If revenue values are inflated, every ROAS calculation is fiction.
This is not optional configuration. It is the foundation that determines whether optimisation is possible or just expensive noise.
Architecture Standard: Required
Before any scaling, all items on this checklist must be verified. No exceptions.
Conversion Taxonomy
Not all conversions are equal. The taxonomy must reflect this:
| Type | Conversion | Setting | Purpose |
|---|---|---|---|
| Primary | Purchase | Optimise | Smart Bidding targets this |
| Secondary | Add to Cart | Observe only | Reporting visibility, no bid impact |
| Secondary | Newsletter | Observe only | Reporting visibility, no bid impact |
Never feed soft metrics as primary signals
Setting "Add to Cart" as a primary conversion teaches Smart Bidding to find cart-adders, not buyers. The algorithm will optimise for exactly what you tell it.
GA4 & Value Accuracy
Configure GA4 for pure ecommerce events with accurate value:
- • Exclude tax/shipping from value: Inflated values create inflated ROAS that does not match reality
- • UTM discipline: Consistent, enforced tagging across all channels
- • Event parameters: Include transaction ID for deduplication
- • Currency handling: Match backend currency to prevent conversion errors
Modern Tagging Standards
Server-Side Tagging (CAPI)
Server-side tagging is mandatory for accurate conversion data in a privacy-first world. Browser-side tracking alone loses significant conversion data to ad blockers, ITP, and consent restrictions.
Consent Mode v2
Consent Mode v2 must be active. This is not optional. Without it, you lose conversion modelling and remarketing capabilities in the EU and UK.
Deduplication Keys
Transaction IDs must be present on all purchase events. Without them, the same conversion can be counted multiple times, inflating reported ROAS.
QA & Drift Monitoring
Tracking verification is not a one-time task. It is an ongoing discipline:
- • Monthly test orders: Place a test order and trace it through GA4, Google Ads, and backend
- • Variance check: Compare GA4 vs Platform vs Backend. If variance exceeds 5%, stop scaling and fix
- • Change monitoring: Track checkout updates, plugin changes, and cookie policy modifications
The "Set and Forget" Trap
Tracking breaks silently
Checkout updates, plugin changes, and cookie policies degrade data daily. What worked last month may be broken today. This is why we audit monthly.
"Clean Inputs = Stable Outputs. Every tracking compromise creates bidding compromise."