New post

server-side tracking gets mentioned a lot. most explanations make it sound more complicated than it is.

here is the plain version.

client-side tracking: a tag fires in the user's browser when they take an action. the browser sends data to Google. if the user has an ad blocker, a strict browser privacy setting, or if the page loads slowly and the tag doesn't fire in time, the conversion is missed.

server-side tracking: when a user takes an action, your server sends the conversion data directly to Google. the data goes server to server, not through the browser. ad blockers don't affect it. browser privacy settings don't affect it. it's more reliable.

the practical difference: accounts with significant ad blocker usage (often B2B audiences, developer audiences, privacy-conscious consumers) can see 15-30% more conversions attributed when server-side is implemented correctly. accounts selling to general consumers in less tech-aware markets see smaller gains.

whether you need it: if your GA4 and Google Ads conversion counts differ by more than 10% from what your CRM or Stripe shows, server-side is worth implementing. if your numbers align reasonably well, client-side is probably sufficient.

the two ways to implement: Google Tag Manager server-side container (requires a hosting cost, usually $30-50/month for low traffic) or Google's native Conversion API for Google Ads (simpler, free, but only sends to Google).

this is not a weekend project if you haven't done it before. it's a solid afternoon for someone who has.

the Revenue Forensics engagement covers server-side setup as part of the gap analysis when it's warranted: https://paidmedialab.com/book

saku