Connect Meta's Conversions API
Two things to copy from Meta — your Pixel ID and an access token — and git-royal handles the rest. Here's what CAPI is, why it matters, and exactly where to click.
The short version: the Meta pixel lives in the visitor's browser and reports what people do on your page. But browsers increasingly block it — iOS App Tracking Transparency, ad blockers, privacy modes — so a big share of your real conversions never get reported. When Meta can't see conversions, it can't optimize your ads or build accurate audiences.
The Conversions API (CAPI) fixes that by sending those same events a second way: server to server, straight from git-royal to Meta, where a browser can't block them. Each event is sent with a shared ID so Meta deduplicates the browser and server copies — you never double-count, you just stop losing data.
You don't write any code. git-royal does the server-side sending for you. You only need to give it two values from your Meta account so it sends to your pixel: a Pixel ID and a Conversions API access token.
Server-side
Events sent from our servers, not the browser — nothing to block.
Deduplicated
Shared event IDs mean the browser + server copies never double-count.
Your data
Events flow to your own Meta pixel and dataset. You own it.
Get your Pixel ID + access token
- 1
Open Meta Events Manager
Go to business.facebook.com/events_manager and sign in with the account that runs your ads. In the left sidebar, open Data sources.
- 2
No pixel yet? Create one
If you don't already have a pixel/dataset, click Connect data sources → Web → give it a name (e.g. “git-royal”) and create it. If you already have one, skip to the next step.
- 3
Copy your Pixel ID
Select your pixel in the Data sources list. The Pixel ID (also called a Dataset ID) is the long number shown under its name — or open the Settings tab and copy the Dataset ID there. It looks like
1071246072087823. - 4
Generate an access token
With your pixel selected, open the Settings tab and scroll to the Conversions API section. Click Set up manually (or “Generate access token”). Meta creates a private token tied to this pixel — copy it now, as it's only shown once. It starts with
EAAB…. - 5
Paste both into git-royal
In git-royal, go to Settings → Connect Meta, paste your Pixel ID and access token, and save. That's it — server-side tracking is live. Your token is stored privately and never shown in your browser again.
Keep the access token private — it can send events to your pixel. Treat it like a password. If it's ever exposed, you can revoke and regenerate it in the same Conversions API settings.
Common questions.
Do I need to be a developer?+
No. git-royal does all the server-side sending. You only copy two values (Pixel ID + token) from Meta once and paste them into Settings.
Will this double-count my conversions?+
No. git-royal sends each event with a shared event ID, which Meta uses to deduplicate the browser pixel and the server copy. You get accuracy, not inflation.
Does it work with a pixel I already use elsewhere?+
Yes. Connect the same Pixel ID and git-royal's events flow into your existing dataset alongside everything else you track — it makes that pixel more accurate, not fragmented.
Meta's screens look a little different from these steps.+
Meta changes Events Manager fairly often, so labels may move. The path is always: Data sources → your pixel → Settings → Conversions API → generate token. If you get stuck, Meta's own docs (linked below) stay current.
Is my access token safe with git-royal?+
It's stored privately server-side and is never sent back to your browser or exposed on your public pages. Only git-royal's servers use it to forward your events to Meta.
Official reference: Meta's Conversions API — Get Started.