Data Loss Prevention with Meta Conversions API (CAPI) and Server-Side Google Tag Manager (sGTM)

Meta Conversions API (CAPI) and Server-Side Google Tag Manager (sGTM) duo is the most powerful and sustainable way to prevent data loss by bypassing browser restrictions (iOS 14+, Safari ITP, AdBlockers) today.

To reduce data loss to zero and increase advertising performance with this structure;

1. Hybrid Installation (Deduplication / Deduplication)

The first rule to prevent data loss is to install a Hybrid Structure that sends both browser and server data at the same time. Feeding both channels, rather than just passing to the server, ensures the accuracy of the data.

• Sending the Same Event Twice: When a user makes a purchase on your site, this data is sent via both the Meta Pixel in the browser and the Meta CAPI over sGTM.

• Preventing Double Counting (Deduplication): To prevent Meta from counting the same conversion twice, the outgoing event from both channels is sent via Meta CAPI.

• the same Event ID (event_id) and Event Name (event_name)must be assigned. Meta matches these two data, deletes the one from the browser, and accepts the complete data from the server.

2. Maximize Advanced Matching Parameters (User Data)

Meta needs Customer Information Parameters to match incoming server data with a user on its platform. Preventing data loss is not just reporting the "event" but reporting "who" did it correctly.

• Basic Data to be Sent: E-mail (em), Phone (ph), Name (fn), Surname (ln), City (ct), Country (co).

• Device Data to be Sent: Client IP Address (client_ip_address), User Agent (client_user_agent), fbc (Facebook Click ID) and fbp (Facebook Browser ID) You can send it.

3. Use a Custom Domain

Instead of using the default URL that Google gives you during sGTM installation (eg: sgtm-xyz.appspot.com), use your own subdomain (eg: ss.eticaretsiteniz.com).

• Bypass AdBlockers: Ad blockers and Safari ITP block known analytics and ad servers.

• First-Party Cookie: Own the data flow. When you execute traffic through your domain (ss.siteadi.com -> siteadi.com), browsers see this traffic as "secure and first-party". Thus, cookie lifetimes are extended and data loss does not occur.

4. Track the Quality Score

An Event Match Quality score between 1 and 10 appears for each event in the Meta Event Manager panel. Increasing this score directly prevents data loss.

Score Level

Status

What to Do

Low (1 - 4)

There is Serious Data Loss

Only event_name may be going. IP and User Agent must be added.

Medium (5 - 6)

Standard Installation

Basic customer information such as e-mail and telephone must be added by hashing (SHA-256).

High (7 - 10)

Perfect Data

Both fbp/fbc cookies, device information and user information. It means the information is complete.

5. "Conversion API Gateway" (CAPI Gateway) or Meta Tag Usage in sGTM

There are two popular methods to prevent Meta data loss in sGTM:

• Meta Conversions API Webtag: By using the official Meta tag in sGTM, you can automatically convert GA4 (Google Analytics 4) event data from the browser into Meta parameters and send it from the server. Its installation is flexible.

• Data Verification (Fail-safe): By logging on sGTM, you can monitor Meta requests that do not go through or give errors (400, 500 errors), and prevent data interruptions caused by the server.