How do I set up Meta Conversions API, and what data does it send?
Meta Conversions API (CAPI) is configured from Apps > Meta Pixel > Conversion API, using an access token from your Meta Business account. It sends phone number, IP address, and user agent with each event, plus fbc (Click ID) and fbp (Browser ID) whenever those are available from the visitor's browser cookies — it does not send email, which is why Event Match Quality may still score lower than a fully matched setup.
Steps
- In Meta Events Manager, open your pixel's settings and generate an Access Token for the Conversions API (Business Settings > Data Sources > your pixel > Conversions API).
- In Dropify, go to Apps > Meta Pixel > Conversion API and fill in: Account Name (any label), Pixel ID, Access Token, and optionally a Test Event Code to verify in Meta's Test Events tool before going live.
- Choose Conversion Type: Purchase or Lead.
- Click Save Conversion API.
- Confirm it's working by placing a test order and checking Meta Test Events for a server-side event alongside the browser event — Dropify deduplicates these automatically so you won't see double conversions.
Common problems
- Event Match Quality (EMQ) score is low, e.g. 4–5/10Dropify's CAPI sends phone (ph), IP address, user agent, and fbc/fbp when the visitor's browser has those cookies set — but not email, which some other platforms also send. This is a platform limitation, not a misconfiguration on your store.
- Worried you'll create duplicate conversions by adding CAPIyou won't; deduplication between the browser pixel and server-side Purchase event works correctly.
- Updated the Pixel ID or token but nothing changedre-save the form and re-check the funnel/landing page link you're testing; changes only apply going forward, not to past events.
- Orders "aren't showing correctly" after setting up CAPIthis is usually unrelated to CAPI itself — check for an outdated mobile app version or a store sync issue first.