Tracking, explained
How server-side events, consent and ad platforms really behave. Written while building TallyHost.
Consent Mode v2 and server-side tracking: who needs what
Server-side tracking doesn't bypass consent. The four Consent Mode v2 signals, what Meta, TikTok, GA4 and Google Ads each need, and how consent reaches the server.
IAB TCF or Google Consent Mode: which one your shop needs
How IAB TCF and Consent Mode v2 differ, how TCF maps onto Google's signals, and what a TCF banner means for Meta, TikTok, GA4 and Google Ads.
Paid orders with no conversion: the missing thank-you page
Why orders paid by online transfer or through a payment gateway go missing in Meta, GA4 and Google Ads, how to spot them, and how to send them from your server.
Server-side tracking for online shops: what it fixes
A practical guide for shop owners: how server-side tracking works, which lost orders it brings back to Meta, TikTok, GA4 and Google Ads, and what it can't change.
Server-side tracking for WooCommerce: how to set it up
What WooCommerce should send from the server and what from the browser, the plugins that double-count, how refunds work per platform, and how to check it all.
GA4 shows fewer orders than WooCommerce: where they go
Why GA4 records fewer purchases than your WooCommerce shop, how to find which cause it is, and what sending the purchase from the server fixes.
Meta Pixel and Conversions API: how deduplication works
How Meta matches the Pixel and Conversions API copies of one purchase, the setups that still count it twice, and how TikTok, GA4 and Google Ads do it.