Server-Side Tracking

Stop letting iOS updates ruin your Meta and Google Ads

By Benjamin Taini · Founder, Bouletteproof

Every iOS update chips away at your ad performance. Not because your ads got worse, but because the browser stopped letting you see what’s working.

Why does the Meta browser pixel lose data?

The Meta browser pixel fires a JavaScript event from the visitor’s browser. Two things break it:

The result: your Meta Ads Manager shows fewer conversions than actually happened. Your CPA looks inflated. Your campaigns get paused or downscaled based on incomplete data.

How does server-side GTM (sGTM) fix this?

Server-side GTM moves the conversion event from the browser to a server. Instead of waiting for a JavaScript pixel to fire in the visitor’s browser, the server sends the event directly to Meta Conversions API (CAPI) and Google Enhanced Conversions.

This is not a workaround. It’s the architecture Meta and Google both recommend for accurate conversion tracking.

Does the current stack support server-side campaign flows?

Yes. For short links on all paid tiers (Pro, Growth, and Professional), HikrLink’s redirect backend logs the click event at the server and forwards it through sGTM, so every click counts regardless of the visitor’s browser settings. Note that sGTM is not available on the Starter tier or for bio pages.

Personal data is hashed (SHA-256) before transmission to Meta or Google. The event_id is matched on both client and server to prevent deduplication issues.

Why should I care about a "structured server-side flow"?

Think of it as a shared playbook that everyone on your team follows — the same way of tagging campaigns, the same way of building trackable links, the same way of pulling reports. Without a playbook, every campaign ends up with slightly different names, missing tags, or broken links, and the numbers stop lining up.

With it, every campaign follows the same logic from setup to reporting, making performance easier to understand and trust.

Can the stack support advanced paid media workflows?

Yes. HikrLink’s paid tiers include API access, with Growth and Professional adding geo-targeting and priority support. This allows campaigns to extend beyond simple link tracking into full marketing workflows.

The API also exposes campaign attribution endpoints. Campaign data can be queried by campaign ID and date range, making reporting more structured and easier to work with.

Create your free artist page

Frequently asked questions

Why does the Meta browser pixel lose conversion data?
Safari ITP blocks the tracking cookie before the pixel fires. Ad blockers block the request to connect.facebook.net at the network level. Combined, this causes 15–40% data loss depending on audience demographics.
What is server-side GTM (sGTM)?
sGTM moves conversion events from the visitor’s browser to a server. The server sends directly to Meta Conversions API (CAPI) and Google Enhanced Conversions. No browser involvement, so no ad blocker interception.
Does HikrLink use sGTM?
HikrLink logs every click server-side, before any browser JavaScript runs, so clicks are counted regardless of ad blockers or visitor browser settings. Forwarding those events onward to Meta CAPI via sGTM is in progress and not yet live.
Can HikrLink support advanced tracking workflows?
Yes. Paid tiers (Pro, Growth, and Professional) include API access, while Growth and Professional add geo-targeting and priority support.
Can the stack support attribution exports?
Yes. The HikrLink API lets you query attribution data by campaign ID and date range, so you can pipe it straight into dashboards, sponsor reports, or internal reviews.
Does this page make any A/B testing claim?
No. A/B testing is not part of this doc.

Related pages