Every optimisation decision you will ever make sits on top of your tracking. If the foundation under-reports by 30%, you will kill winning campaigns and scale losing ones — confidently, with charts. That is why tracking is Session 1, not an appendix.
Why the browser pixel alone is no longer enough
Between iOS privacy prompts, ad blockers and browsers throttling third-party scripts, a browser-only Meta Pixel now commonly misses 20–35% of real conversions. The platform then optimises on incomplete data — and you pay for its blind spots.
The dual setup
- Meta Pixel + Conversions API together. The browser pixel fires client-side; CAPI sends the same events server-side. Meta deduplicates via event IDs and recovers most of what the browser loses.
- GA4 as the neutral referee. Both ad platforms grade their own homework. GA4 gives you one source of truth when Meta and Google both claim the same sale.
- UTM discipline on every link. Source, medium, campaign — consistent, lowercase, no exceptions. The naming convention is decided once, in writing, before the first ad runs.
Verify, then trust
A tracking setup is not done when the code is pasted. It is done when you have fired a real test event and watched it arrive — deduplicated — in Events Manager and GA4 real-time.
Students leave Week 1 with this running on their own property, verified live in class. It is the least glamorous session of the course and the one graduates say mattered most.