Field notes on server-side tracking.
Long-form pieces on what actually changes when you stop renting tracker domains. Adblock-immune dispatch, Google Ads developer-token politics, hybrid-mode dedup, and where Beaconry sits next to Stape and GTM Server-Side. Written for performance-marketing leads who would rather read a tech-deep-dive than a pitch deck.
Why "server-side tracking" still loses 25 % of conversions to adblockers
Most "server-side" setups still bootstrap from a third-party domain in the browser. Filter lists catch up within weeks. The fix is not faster fallback, it's same-origin from the very first byte.
Google AdsGoogle Ads developer-token approval: the 6-week wait, and how to skip it
Server-side conversion uploads via the Google Ads API need a developer-token that takes 4 to 6 weeks to approve. A central broker abstracts the token without ever seeing your conversion data, here's the architecture.
ComparisonBeaconry vs Stape vs GTM Server-Side: same outcome, very different mechanics
All three claim "server-side tracking", all three end up with different adblock-resistance, different DNS setup, different monthly bills. Side-by-side teardown of the dispatch path on each.
EngineeringHybrid mode: when to put the browser pixel back in
Server-side alone covers 100 % of consenting visitors. Hybrid mode adds first-party fbp / _ttp / li_fat_id cookies for better match-rate. Stable event_id dedup is what keeps it from double-counting. Walkthrough.
TikTokTikTok Events API on WordPress: what's required, what isn't
TikTok asks for AAM, first-party cookies, enhanced postback by default during onboarding. None of those are required, all of them are GDPR risk. The actual minimum config in two screens.