Meta setup

Connect Meta Pixel and CAPI

Meta setup validates the Dataset or Pixel ID and CAPI access token before events are sent.

Fields to prepare

Open Events Manager in Meta and use the dataset or pixel that belongs to the client's business.

  • Connection name is optional and is only for the UI.
  • Dataset / Pixel ID identifies where events go.
  • Access Token (CAPI) authorizes server-side event sending.

Validation behavior

The Meta row should remain off until backend validation succeeds. If validation fails, keep the modal open so the token or dataset can be corrected.

  • Invalid token: fix the token and save again.
  • Missing permission: create a token with the required dataset access.
  • Wrong dataset: check the Pixel/Dataset ID in Events Manager.

Events sent

The default client-facing Meta flow focuses on valuable CRM outcomes rather than raw form noise.

  • Qualification Lead means the CRM says the lead became qualified.
  • Converted Lead or Purchase comes from CRM revenue/outcome.
  • Unqualified Lead is sent only when business rules allow it.