Meta (Facebook) CAPI

Prism delivers events to Meta through the Conversions API — server to server. No Meta pixel is required on the site (Prism generates the _fbp browser ID itself), though running both is fine: Prism sends deduplication IDs so events aren't double-counted.

What you need

Two values, both from Meta Events Manager:

1. Pixel / Dataset ID — Events Manager → your dataset → Settings.
2. Conversions API access token — same Settings page → Generate access token.

That's it — no app review, no system-user setup, no Marketing API permissions. The token only grants event delivery for that one dataset.

Connecting

In the Adsidian dashboard, open the client → Connect Meta (or Reconfigure Meta). The wizard:

1. Takes the pixel ID, access token, and your landing domain.
2. Runs live preflight checks — token validity, dataset reachability, domain verification, category restrictions, AEM priority.
3. Fires a test event and confirms Meta received it (visible in Events Manager → Test events).

Event mapping

Meta optimizes on standard event names (Lead, Purchase, Schedule, …). Your on-site event names are mapped to Meta names per client — e.g. site event AppointmentRequest → Meta Schedule. Events without a mapping pass through under their own name.

Restricted categories

For advertisers Meta classifies into special ad categories (health, housing, credit, employment, politics), Meta silently drops standard events like Lead — they're accepted with a 200 but never appear in the dataset. Prism's diagnostics detect this; the fix is mapping your events to custom (non-standard) names, which your agency configures in the dashboard.

Ongoing health

Prism runs hourly automated checks per client (token validity/scope, dataset reachability, category restrictions, AEM setup) and reconciles daily how many events Prism sent vs. how many Meta reports receiving — surfaced on the client page as Integration Health and Event delivery cards, plus Event Match Quality when available.