How it works
- User clicks ad
- Facebook appends fbclid parameter to end of landing page URL (facebook click ID)
- User taken to this landing page with Meta pixel installed
- Meta pixel runs:
- If fbclid URL parameter is present, _fbc cookie is created which stores the fbclid value in the format the CAPI requires
- _fbp cookie is created which stores the browser ID (this happens regardless of the fbclid parameter being present or not)
- Pixel fires 'pageView' event
- All available metrics are passed to the embedded survey:
- _fbc and _fbp values (primary identifiers for attribution)
- all UTM parameters
- landing page URL
- User completes survey, clicks submit:
- Workflow triggered → values sent from Survey Sparrow to CAPI server-side endpoint on Meeting Place code repo
- CAPI endpoint checks all data, formats it correctly and sends to facebook as 'lead' event
Note: There is no need for de-duplication as Meta pixel and CAPI integration fire off different events ('pageView' vs 'lead').