Guides / Connect Meta
Sign in with Facebook, approve access, pick the dataset. No tokens, no Events Manager spelunking — and a test event that proves the pipe before any real lead depends on it.
⏱ About 2 minutesOpen the location in Pipeline Signals → Connections → the Meta card. Clicking the button opens a new tab with Facebook's sign-in (from inside your CRM this always opens a fresh tab — finish there and come back; the page catches up on its own).
Sign in with a Facebook account that can manage the client's business portfolio.
Facebook walks you through choosing the business and the pixels/datasets to share. Include the dataset this client's ads use — you'll pick the exact one in the next step. Approve, and you're sent straight back to the app.
Choose which dataset (pixel) receives this location's conversion events. Optionally paste a test event code from the dataset's Test events tab — then click Finish connecting.
Proof it works: a ConnectionTest event is delivered the moment you connect. With a test code in place it appears in the Test events tab within seconds (keep that tab open — it's a live feed and only shows events that arrive while you're watching).
Remove the test code before going live. While a test event code is saved, events go to the Test events tab instead of powering ads. When mapping tests look right: Update connection → leave the test-code field empty → Save. Changing datasets works the same way — no re-connect needed.
Prefer a system-user token? The old way still works: on the Meta card, open "Advanced: connect with an access token instead" and paste a Dataset ID + Conversions API token (dataset → Settings → Conversions API → Generate access token). One-click is easier for almost everyone.
How match quality works: every event carries the strongest keys available for that contact, in Meta's priority order — Lead ID (from Lead Ads), then browser click data (fbc), then hashed email and phone. The Activity tab shows exactly which keys each event used.
Pipeline Signals · dedup, retries, expiry windows and consent flags handled automatically