Set up Meta Ads tracking
Connect Meta so Ferb can send booking and purchase conversions to Meta Ads, both from the browser (Pixel) and server-side (Conversions API). Tracking only fires with the customer's advertising consent.
You need the owner or admin role, and a Meta Business account with Events Manager set up.
Get your Meta details
In Meta Events Manager, get:
Your Pixel ID or Dataset ID.
A Conversions API access token (Settings -> Conversions API -> generate an access token).
Optionally, a Test event code (from the Test Events tab) to verify the setup.
Connect in Ferb
Go to Integrations -> Add integrations and install Meta Ads (see Browse and install integrations).
Paste your Pixel ID / Dataset ID and Conversions API access token, and the Test event code if you have one.
Choose which paths to use with Browser Pixel enabled and Server Conversions API enabled.
Click Send test event, then Enable once it passes.
Your access token is stored encrypted and is never shown again.
What Ferb sends
Ferb maps studio activity to Meta events: page views, view content, initiate checkout, Schedule (a free booking), Purchase (a paid checkout), Subscribe (a membership), and Complete registration. The connected page has an event guide and delivery health.
Tracking is consent-gated: the browser Pixel loads, and server events send, only after the customer gives advertising consent.
Troubleshooting
The test fails. Check the Pixel or Dataset ID and the access token, and that the token is a current Conversions API token from Events Manager.
No conversions show in Meta. Confirm the integration is enabled, and remember events only fire with advertising consent.
You cannot set this up. It needs the owner or admin role.
Related
Browse and install integrations
Connect Klaviyo