To connect Meta (Facebook and Instagram) to Claudphic Ads CRM, go to Marketing → Meta Settings and enter your Pixel ID and a Conversions API access token, both from Meta Events Manager. That's the minimum to go live; a test event code is optional but worth using first, so you can confirm events are landing correctly before turning it on for real traffic.
Plan requirement: Meta conversion tracking ships on the same plan gate as Google Ads — Growth and Scale. If Meta Settings isn't in your sidebar, that's the reason; see pricing for what's included on each plan.
Find your Pixel ID
In Meta Events Manager, select the pixel connected to the ad account running your campaigns (if you've never created one, Events Manager will prompt you to create it from here — it takes under a minute and doesn't require any code on your website for this use case, since the CRM sends events server-side). The Pixel ID is a numeric string shown under the pixel's name at the top of its dashboard. Enter it as digits only in the CRM's Pixel ID field — the form rejects anything else.
Generate a Conversions API access token
Still in Events Manager, with your pixel selected, go to Settings → Conversions API and find Generate access token under the manual setup option. This produces a long-lived token scoped specifically to server-to-server event uploads for this pixel — it is not your personal Facebook login and doesn't expire the way a user session would, though Meta can revoke it if the underlying ad account's access changes. Paste it into the CRM's Access token field.
Treat this token like a password: anyone who has it can send events (or fabricated conversions) into your ad account's reporting. It's stored server-side in the CRM and never exposed to the browser.
Test before you rely on it
Events Manager has a Test Events tab, and it generates a short-lived test event code — paste that into the CRM's optional Test event code field, save, then trigger a real action in the CRM (log a lead activity, or move a lead into a mapped stage if you've already set up Meta event actions). The event should appear in the Test Events tab within a few seconds, tagged with a status of Received. Once you've confirmed it, remove the test event code and save again — leaving it in place stops events from counting toward your real reporting, since test events are deliberately excluded from Meta's optimisation and attribution.
Set your default currency and go live
Set Default currency to match what your ad account bills in (INR unless you've specifically set up a different billing currency in Meta Business Manager), set Status to Active, and save.
Connecting the pixel is the transport layer — it doesn't decide what gets reported. That's configured separately in Marketing → Meta Event Actions, where you map pipeline stages to specific Meta event types the same way Google Ads conversion actions get mapped to stages. See mapping conversion actions to pipeline stages for the equivalent Google Ads walkthrough — the Meta version follows the same pattern.
If leads are coming from Meta Lead Ads specifically
Everything above covers reporting outcomes back to Meta. If you're also running Meta's native Lead Ads (the in-platform lead form, rather than sending traffic to your own landing page), that's a separate, inbound connection — see setting up the Meta Lead Ads webhook to get those leads flowing into the CRM in the first place.