Send AppIn clicks to Meta
Two values from Events Manager and your clicks reach Meta as server events, at the moment they happen.
Meta documents the destination itself in its Conversions API developer docs; this page is about the two values AppIn needs from it.
What you need
- Your Pixel ID
- A Conversions API access token
Where to find them
- Open Events Manager and select your data source.
- Settings shows the Dataset ID. That is your Pixel ID.
- On the same page, Conversions API → Generate access token.
For a token that outlives you, create it from Business Settings → System Users
with the ads_management permission instead. A personal token dies when the person
who made it leaves the business account, and the destination stops delivering with
nothing on your screen to explain why.
What to enter in AppIn
Open Settings → Measurement → Add destination, choose Meta, and paste the Pixel
ID and the token. The event names default to ViewContent for a link view and Lead
for a store redirect; change them if your reporting uses different ones.
How to check it worked
Events Manager → Overview, not Test Events. Test Events only shows traffic
carrying a test code, and we send real events. Yours should appear within about
twenty minutes with Server as the source.
Press Send test event in AppIn first if you would rather not wait for real traffic.
The mistake people make
Setting up the same pixel here and in your own server container, and renaming the
event in one of them. We stamp every event with an event_id and Meta deduplicates
on event_id together with the event name — so if the name differs, Meta sees two
different events and counts both.