Data & Storage · Integration
Facebook Conversions
Add Facebook Conversions to your product for your customers, and give your AI agents governed access to it.
The Conversions API is Meta's server-side path for the events a browser pixel used to carry alone, and it exists because the browser is no longer a dependable place to report a purchase from. Every event goes to a dataset, formerly called a pixel, carrying an event name, an event time, user data and custom data. Three rules decide whether it works at all. Customer information has to be normalised and SHA-256 hashed before it leaves your servers, and hashing a slightly wrong string quietly produces an event nobody can match. The same event sent from both the browser and your server must share an event id and event name or it is counted twice. And events can be sent up to seven days late, which makes a backfill possible and also makes an unthrottled one a good way to burn through a customer's allowance. Match quality and event counts are readable per dataset, so your product can tell a customer their events are landing badly before their reporting does.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer point at their own dataset, so events land in the account whose ads they are optimising and never in a shared one.
Normalise and hash customer information on your servers before it is sent, so nothing leaves in the clear and every event stays matchable.
Send the same event id from your server and from the browser pixel, so one purchase is counted once rather than twice.
Backfill up to seven days of past events at a throttled rate when a customer first connects, instead of firing their history all at once.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports a dataset's event match quality and names which parameter is dragging it down.
An agent sends a test event and confirms it arrived before anybody trusts a new mapping.
An agent compares server and browser event counts and flags where deduplication is failing.
Example prompt
Are our purchase events reaching this dataset, and is the browser pixel double-counting any of them?
Set up Facebook Conversions in 4 steps
- 01Enable the Facebook Conversions connector in your fastn dashboard.
- 02Have each customer authorise their own dataset and access token, so events land in the ad account they are optimising.
- 03Map your product's events to Meta's event and parameter names, normalise and hash customer information, and agree an event id scheme with your browser pixel.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Facebook Conversions integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Facebook Conversions integration without building it. Your customers connect their own Facebook Conversions account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Facebook Conversions update is not your on-call problem.
- One integration serves your product and your agents. The same governed Facebook Conversions connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
Google Tag ManagerWorks well with
Facebook MarketingOften used alongside
Tools the same teams tend to run next to Facebook Conversions, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceFacebook Conversions integration FAQ
How do I add a Facebook Conversions integration to my product?
Enable the Facebook Conversions connector in your fastn dashboard, then let each customer authenticate their own Facebook Conversions account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Facebook Conversions client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Facebook Conversions account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Facebook Conversions account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Facebook Conversions integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reports a dataset's event match quality and names which parameter is dragging it down.
Who maintains the Facebook Conversions integration?
fastn does. When Facebook Conversions changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the Facebook Conversions integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large Facebook Conversions reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the Facebook Conversions integration?
A common starting point: let each customer point at their own dataset, so events land in the account whose ads they are optimising and never in a shared one. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Facebook Conversions integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Facebook Conversions does not change your per-connector cost. You can start free with 3 connected accounts.
Add Facebook Conversions to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.