Conversions API System User and Access Token: How to Get One and Keep It Safe
Sooner or later every Conversions API setup asks for the same thing: an access token. And around the same time, people notice a mysterious user called something like "Conversions API System User" in their Business Settings and wonder whether it's safe to delete.
Here's what both of these are and how to handle them without breaking your tracking.
Why the Conversions API needs a token
The pixel runs in a browser, so it doesn't need a password — anyone can send browser events. The Conversions API is different: it lets a server send events straight into your dataset (pixel), including sales data. Meta needs to know the sender is allowed to do that. The access token is that permission.
Tokens for CAPI belong to a system user — a non-human account inside your Meta Business portfolio, designed for server-to-server integrations. Unlike a personal token, it doesn't depend on any employee's Facebook account, so it keeps working when people leave or change passwords.
Option 1: Generate the token in Events Manager (easiest)
- Open Events Manager and select your dataset (pixel).
- Go to the Settings tab.
- Find the Conversions API section and, under "Set up manually", click Generate access token.
- Copy the token and store it somewhere safe — you'll paste it into your integration.
The link is only visible to people with developer-level access to the business. If you don't see it, ask a business admin to give you full control of the dataset.
When you do this, Meta automatically creates a Conversions API app and a Conversions API system user behind the scenes. That's the user you'll later see in Business Settings. According to Meta, this path requires no App Review and no extra permission requests.
Option 2: Create a system user yourself
Agencies and developers often prefer to control this explicitly:
- Go to Business Settings → Users → System users and add a system user.
- Click Add assets, choose Datasets (pixels), select the pixel and give it full control.
- Click Generate new token, pick your app, and generate the token.
This route is useful when one integration sends events to several pixels, or when you want a clearly named user per client.
"Conversions API system user" — can I delete it?
Only if you're sure nothing uses it. Deleting the system user (or removing its access to the pixel) instantly invalidates every token it issued. Any integration using those tokens — your website plugin, a CRM connector, an agency's server — will start getting errors, and events stop arriving. Meta won't warn the integration; it just fails.
Before deleting, check which integrations are connected in Events Manager under your dataset's Settings and Overview → Manage integrations. If you're cleaning up after an old agency, revoke their access first, then watch your event volume for a day before removing anything else.
When the system user isn't assigned to the pixel
A common problem after setting things up manually: the token is valid, but Meta rejects events with a permission error. Usually it means the system user exists, but the pixel was never added to its assets. Fix it in Business Settings → System users → (the user) → Add assets → Datasets, then retry. You don't need a new token.
Keeping the token safe
- Treat it like a password. Anyone with the token can send events into your pixel and pollute your data.
- Never put it in website JavaScript. If it's in your page source, it's public. CAPI calls must come from a server.
- Don't paste it in chats or tickets. If it leaked, generate a new one and update your integration.
- One token per integration makes it easy to revoke one without breaking the others.
Skipping the token entirely
Manual tokens are fine for one pixel. They get painful when you manage several businesses or clients: different portfolios, different admins, tokens scattered across tools.
With LeadMe you don't copy tokens at all. You click Connect with Facebook, choose the ad account, and pick an existing pixel or create a new one. LeadMe uses Meta's official Facebook Login for Business with approved permissions, stores the access server-side, and sends events for you. If you prefer, you can still paste a manual token — both options are supported.
Quick answers
Does a Conversions API token expire?
System user tokens are meant for long-running integrations. When generating a token in Business Settings you may be asked to choose an expiration — for a server integration, pick the longest option so tracking doesn't silently stop. If events suddenly stop with an authentication error, an expired or revoked token is the first thing to check.
Do I need App Review to use the Conversions API?
Not for your own pixel: Meta's documentation says the Events Manager route needs no App Review. Platforms that send events for other businesses (like LeadMe) go through review themselves.
Can I use one token for several pixels?
Yes, if the system user has access to all of them. Many teams still prefer one token per pixel or client for easier cleanup.
Related: What Is Meta Conversions API · Set up Conversions API without a developer