Overview
Meta's Conversions API (CAPI) sends conversion events to Facebook and Instagram ads server-side — from your systems rather than the browser pixel. With browser tracking eroded by iOS privacy changes and ad blockers, CAPI is how Meta's algorithm keeps learning who actually converts. The CRM integration takes it further than page-view events ever could: it reports the conversions that happen offline and downstream — lead qualified, deal won — back to the campaign that generated the click.
This closes the optimisation gap that wastes most SMB ad budgets. The pixel tells Meta who submitted a form; the CRM tells Meta who became revenue. Feed deal-won events with values back through CAPI and Meta optimises delivery toward people who resemble your buyers, not your form-fillers — the practical difference between campaigns that generate enquiries and campaigns that generate customers.
What data is involved
- CRM lifecycle events — lead created, qualified, deal won — sent to Meta as server-side conversions.
- Deal value passed with won events for value-based bidding.
- Hashed customer identifiers (email, phone) matched to ad clicks per Meta's requirements.
- Event deduplication with the browser pixel via shared event IDs.
- Lead source and campaign attribution recorded on the CRM record.
- Configurable event mapping: which CRM stages fire which Meta events.
Step-by-step setup
Setup at a glance (3-5 bullets)
- Settings → Integrations → Meta CAPI.
- Enter Pixel ID and access token.
- Choose CRM events to send (e.g. lead, purchase).
Sign in or sign up at HelloGrowthCRM. Open the login page, enter your credentials (or use Google), or choose Sign up if you need a new account. You must be signed in before you can open Settings and connect this integration.
Open login page(opens in a new tab)app.hellogrowthcrm.com/login
Open Settings. In the left sidebar, under Admin, click Settings (you will land on the Settings area; the URL is app.hellogrowthcrm.com/settings).
Open Settings(opens in a new tab)app.hellogrowthcrm.com/settings
Go to Integrations. On the Settings screen, use the middle settings menu. Under COMMUNICATION, click Integrations (star icon). Then find and configure this connector—the connector-specific steps below pick up from here.
Open Settings (Integrations)(opens in a new tab)app.hellogrowthcrm.com/settings
- Settings → Integrations → Meta CAPI.
- Enter Pixel ID and access token.
- Choose CRM events to send (e.g. lead, purchase).
Best practices
- Send qualified and won events, not just leads — the whole point is teaching Meta the difference between a form-fill and a buyer.
- Pass real deal values with won events and use value-based optimisation once volume allows.
- Keep the pixel running alongside CAPI with event deduplication; Meta explicitly recommends redundant setup.
- Allow for your sales cycle in attribution windows — a 30-day close means most won events land near or past the click window, so judge campaigns on qualified events too.
- Verify your event match quality score in Meta Events Manager after setup; low match rates usually mean phone formats need normalising.
Best for & common use cases
More reliable Facebook and Instagram attribution under privacy constraints.
- iOS and cookie limitations mitigated with server events.
Expected outcomes
- Faster lead handoff between tools and CRM owners
- Cleaner activity history for follow-up and reporting
- Lower manual copy-paste errors in the pipeline
Troubleshooting
- Events not received: the access token lacks the ads_management scope or expired — regenerate it in Meta Business settings.
- Low event match quality: phone numbers missing country codes — normalise to E.164 in the CRM and match rates recover.
- Duplicate conversions: pixel and CAPI sending without a shared event ID — enable deduplication in the integration settings.
FAQ
Governance
Treat API keys and webhooks as production secrets. Align field mapping with your privacy policy and regional regulations (GDPR, marketing consent, telemarketing rules). Your admin controls which roles can install or edit integrations.
Related integrations in this category
GA4 Measurement Protocol: send CRM lifecycle events (e.g. lead_qualified, deal_won) into Google Analytics.
Offline conversions and performance data: upload CRM milestones (qualified lead, won deal) to Google Ads using GCLID.
Auto-ingest leads from Meta Lead Ads (Facebook and Instagram) with campaign and form attribution.
Auto-ingest leads from Google Ads lead form extensions and in-ad capture.
Auto-imports buyer inquiries from IndiaMART Lead Manager into CRM leads with source attribution.
Turns JustDial notification emails into CRM leads via forwarding rules or a direct webhook POST to the ingestion URL shown in the app.
B2B lead capture from LinkedIn Lead Gen Forms and sponsored campaigns into CRM with UTM and campaign IDs.
Form submission ingestion to CRM leads via native connectors or webhooks (Typeform, Tally.so, Google Forms).