How Server-Side Tracking Improves Your Meta Ads Performance

The Problem Meta Is Trying to Solve

iOS 14's App Tracking Transparency (ATT) framework significantly reduced the volume of identifiable conversion signals Meta receives from iOS users. Combined with ad blockers that block the Meta Pixel and browser restrictions on cookies, Meta's ability to attribute conversions and optimise ad delivery has declined substantially.

Meta's Conversions API (CAPI) — combined with server-side tracking — restores much of this lost signal by sending conversion events from your server directly to Meta, bypassing the browser-side restrictions entirely.

What Event Match Quality Means

When you send a conversion event to Meta, Meta tries to match it to a user in its system. It uses identifiers in the event data: email address, phone number, browser cookie (fbp), click ID (fbc), IP address, user agent.

Event Match Quality (EMQ) is Meta's score for how well it can match your conversion events to users. Higher EMQ = more conversions attributed to the right ad = better optimisation of ad delivery.

• EMQ 7-10: Excellent — most conversions matched to specific users
• EMQ 5-6: Good
• EMQ 3-4: Poor — many conversions unattributed
• EMQ below 3: Very poor — most conversions lost to attribution

CAPI-only events (from the server) without any user identifiers score very low. CAPI events combined with hashed customer data (email, phone) score high.

How Server-Side GTM Routes to Meta CAPI

The server-side GTM approach for Meta CAPI:

1. Your website sends events to your sGTM server (at collect.yoursite.com)
2. sGTM's Meta CAPI tag receives the events
3. The tag forwards events to Meta's Graph API server-to-server, including hashed customer data from your event payload

The client-side Meta Pixel can still run alongside — Meta's deduplication handles events received from both the browser Pixel and the server CAPI using the event_id parameter.

What to Include in CAPI Events for High EMQ

To maximise Event Match Quality, include as many of these identifiers as possible in your server-side conversion events:

• Email (hashed): the customer's email address, hashed with SHA-256. This is the most powerful identifier.
• Phone (hashed): customer's phone number, hashed with SHA-256.
• Facebook Browser ID (fbp): the _fbp cookie value — captures the Meta Pixel's browser ID for the user
• Facebook Click ID (fbc): the _fbc cookie value from a Meta ad click (fbclid URL parameter)
• External ID: your internal customer ID, hashed — helps Meta cross-reference with previous purchases
• IP address: the user's IP address (available to your server)
• User agent: the user's browser string

Setting Up Meta CAPI in sGTM

1. In your server GTM container: add the Meta Pixel tag (from the community template gallery)
2. Configure the tag with your Meta Pixel ID and system access token (from Meta Events Manager)
3. Set up event mapping: map standard events (purchase, lead, viewcontent) to corresponding Meta standard events
4. Configure customer data mapping: map your data layer variables for email, phone, fbp, fbc to the tag's user data fields
5. Enable event deduplication: set the event_id parameter to a unique event identifier (order ID for purchases, form submission ID for leads)
6. Publish the server container

Measuring the Improvement

In Meta Events Manager, after implementing server-side CAPI:

• Check Event Match Quality scores — target 7+ for purchase events
• Check "Deduplication" metrics to confirm browser Pixel and server CAPI events are being properly deduplicated (not double-counted)
• Compare conversion volume before and after — a significant increase suggests events that were previously lost to ad blockers or iOS privacy changes are now being captured

Summary

Server-side tracking via sGTM and Meta CAPI recovers conversion signals lost to iOS privacy changes, ad blockers, and browser restrictions. Including hashed customer identifiers (especially email) dramatically improves Event Match Quality, leading to better ad attribution and improved campaign optimisation.

See our Server-Side Tracking service and Facebook Conversion API Setup service.

Want to improve your Meta Ads performance with CAPI? Contact Adslytics.