Platform Guide

Recover the conversions your Meta Pixel misses

Generate server-side CAPI event code, deduplication logic, and test steps — in 3 minutes. No sGTM required.

Ready-to-deploy server-side event code

Built-in event_id deduplication

Meta Test Events validation guide

Generate CAPI code free →See demo →

No sGTM · No server hosting · Free to start

Why Pixel alone fails

iOS 14+ privacy restrictions

Apple's privacy changes block ~20–30% of Meta Pixel signals. Server-side events bypass this entirely.

Ad blockers

Browser-based scripts are blocked by ~15% of users. CAPI sends events directly from your server — unblockable.

Client-side limits

The Pixel can't track server-confirmed events like payments processed outside the browser. CAPI fills this gap.

What Sytrics generates for Meta CAPI

Server-side Purchase event

Complete event payload with hashing, currency, value, and order ID — ready to deploy.

Built-in deduplication

event_id generated and matched between Pixel + CAPI to prevent double-counting in Events Manager.

Token & endpoint setup

Access token configuration and endpoint URL included — no need to read the docs.

Test Events validation

Step-by-step guide to verify in Meta Events Manager before you go live.

Sample generated output

// Meta CAPI — Purchase Event
const response = await fetch(
  `https://graph.facebook.com/v18.0/${PIXEL_ID}/events`,
  {
    method: 'POST',
    body: JSON.stringify({
      data: [{
        event_name:  'Purchase',
        event_time:  Math.floor(Date.now() / 1000),
        event_id:    generateEventId(),    // deduplication
        user_data: {
          em: hashEmail(userEmail),        // SHA-256
          ph: hashPhone(userPhone),        // SHA-256
        },
        custom_data: {
          value:    orderValue,
          currency: 'USD',
          order_id: orderId,
        },
        action_source: 'website',
      }],
      access_token: ACCESS_TOKEN,
    }),
  }
);

✓ Test in Meta Events Manager in 2 steps — Sytrics includes exact test steps.

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

✓ Sytrics generates both setups automatically — no manual docs needed.

From URL to live CAPI in 5 steps

1
Enter your site URL
Go to sytrics.io, paste your website URL, and select your business sector.
2
Select Meta as platform
Choose Meta from the platform list. Sytrics generates both Pixel and CAPI code.
3
Copy the generated code
Copy the server-side event code. Templates provided for the most common server environments.
4
Add your access token
In Meta Events Manager → Data Sources → Settings → Conversions API → Generate Access Token.
5
Test in Events Manager
Use Meta's Test Events tool to confirm events are arriving before going live.

Standard Meta CAPI events Sytrics supports

PurchaseBOFU

Completed transaction — most important for ROAS optimization

LeadBOFU

Form submission, demo request, or contact form completion

AddToCartMID

Item added to shopping cart — key mid-funnel signal

InitiateCheckoutMID

Checkout process started

CompleteRegistrationBOFU

Account signup or trial activation

ViewContentTOFU

Key page view (product page, pricing page)

SearchTOFU

Site search performed

ContactMID

Phone call or contact attempt

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.

Start recovering conversions today

No sGTM setup needed

No server hosting cost

Free plan — no credit card

Generate CAPI code free →See demo first →