Platform Guide

Meta Conversions API (CAPI) Setup Guide

Meta Conversions API (CAPI) is a server-to-server integration that sends conversion events directly from your server to Meta's ad platform, bypassing browser-based tracking restrictions. Unlike the Meta Pixel — which can be blocked by ad blockers or iOS privacy settings — CAPI runs outside the browser entirely. Sytrics generates the CAPI event code and deduplication configuration needed to implement this setup without a developer.

What is Meta CAPI?

Meta Conversions API (CAPI) is a server-to-server integration that sends conversion events directly from your server to Meta's ad platform. Unlike the Meta Pixel — which runs in the visitor's browser and can be blocked by ad blockers or iOS privacy restrictions — CAPI bypasses the browser entirely. Meta recommends using both Pixel and CAPI together to maximise event match quality and recover conversions that browser-only tracking misses.

Pixel vs CAPI: What's the difference?

Meta Pixel

Easy to install via GTM

Real-time browser data

Tracks pageviews natively

Blocked by ad blockers

Affected by iOS 14+ restrictions

Third-party cookie limitations

Misses ~20–30% of conversions

Meta CAPI

Not affected by ad blockers

Works after iOS updates

Server-controlled data quality

Recovers lost conversions

Requires server-side implementation

More complex to set up

Needs deduplication with Pixel

What does Sytrics generate for Meta CAPI?

Server-side event code

Ready-to-use code templates to send events (Purchase, Lead, AddToCart, etc.) from your server to Meta's Graph API.

Event deduplication

Unique event_id generation logic so events sent via both Pixel and CAPI are counted only once in Meta Events Manager.

User data hashing

SHA-256 hashing for email, phone, and name fields as required by Meta's privacy policy.

Test & validation steps

Step-by-step guide to verify your CAPI events appear in Meta's Test Events tool before going live.

Standard Meta CAPI events Sytrics supports

Purchase

Completed transaction — most important event for ROAS optimization

Lead

Form submission, demo request, or contact form completion

AddToCart

Item added to shopping cart — key mid-funnel signal

InitiateCheckout

Checkout process started

CompleteRegistration

Account signup or trial activation

ViewContent

Key page view (product page, pricing page)

Search

Site search performed

Contact

Phone call or contact attempt

How to set up Meta CAPI with Sytrics

1
Enter your site URL in Sytrics
Go to sytrics.io and paste your website URL. Select your business sector (e-commerce, lead gen, SaaS, etc.).
2
Select Meta as a platform
Choose Meta from the platform list. Sytrics will generate both Pixel event code and CAPI server-side code.
3
Copy the CAPI code
Copy the generated server-side code. Sytrics provides templates for the most common server environments.
4
Add your Meta Access Token
In Meta Events Manager → Data Sources → your Pixel → Settings → Conversions API → Generate Access Token. Paste this into the code.
5
Deploy and test
Deploy the code to your server and use Meta's Test Events tool (Events Manager → Test Events tab) to confirm events are arriving.

Frequently asked questions

Do I need sGTM to use Meta CAPI?

No. Server-side GTM (sGTM) is one option for implementing CAPI, but it requires hosting a GTM server container ($20–$90+/month). Sytrics generates direct server-to-server integration code that runs on your existing server — no sGTM required.

Will I double-count conversions if I use both Pixel and CAPI?

Not if deduplication is set up correctly. Sytrics includes unique event_id generation in the code it produces. When the same event is sent via both Pixel and CAPI with the same event_id, Meta counts it once.

How do I know my CAPI events are working?

Open Meta Events Manager → your Pixel → Test Events tab → enter your site URL and trigger a conversion event. If the event appears in the Test Events panel, CAPI is working.

Is Meta CAPI GDPR compliant?

CAPI is a data transmission method. GDPR compliance depends on what user data you send and whether you have valid consent. Sytrics generates code that hashes user data (email, phone) using SHA-256 before transmission, which is Meta's required approach for privacy compliance.

How does Meta CAPI compare to sGTM for e-commerce?

Both achieve server-side tracking. sGTM routes all tags through your server and extends cookie lifetimes — it's the right choice if you manage a complex multi-tag setup. CAPI is Meta-specific and sends conversion data directly to Meta's API. For most e-commerce stores, starting with CAPI (no hosting cost) is the faster path to recovering lost iOS conversions.

Generate your Meta CAPI code in 3 minutes

No sGTM. No server hosting required. No monthly fee to start.

Get CAPI code free →