Skip to main content

Connecting Meta Conversion API

Meta Conversion API (also known as Conversions API or CAPI) sends order event data from Zimam's server directly to Meta, instead of relying only on the browser pixel. This is a separate app from Facebook Pixel and complements it: the pixel tracks from the browser, while Conversion API sends events from the server — which makes tracking more accurate and reduces events lost to browser cookie blocking or ad blockers.

Connecting Meta Conversion API​

  1. From your dashboard, open the Apps section, then the Pixels & Analytics card.
  2. Select the Meta Conversion API app.
  3. Enter your store's Meta Pixel ID — the same ID used for Facebook Pixel, which you can get from Meta Events Manager.
  4. Enter your Conversion API Access Token. You can get it from the Conversions API settings in Meta Events Manager, for the same pixel.
  5. Click Save API Settings.

Every save shows a brief confirmation message, "Pixel settings saved successfully." Above the access token field, a persistent status indicator also shows the current state: a green "Access token configured" badge once a token is saved, or an amber "No access token configured" badge if none is saved yet. For security reasons, the access token is never shown again once saved — if you need to change it later, enter a new one in the field (it will show a placeholder prompting "Enter a new token to replace the existing one"); leaving the field blank when saving keeps the stored token unchanged.

Why this matters​

  • More accurate ad measurement: some events are lost when relying on the browser pixel alone (due to cookie blocking or privacy tools). Sending the same event from the server reduces that loss and gives Meta a more accurate picture of your campaign performance.
  • Deduplicated data: the event sent from the server carries the same order identifier Meta uses to avoid counting the same purchase twice (once from the browser, once from the server).
  • Works alongside Facebook Pixel: Conversion API does not replace installing the pixel — it complements it. For the best coverage, enable both together.

Important notes​

  • This app may not be available on your current plan — if the card shows a "Locked" badge and a "Not included in current plan" message, the feature is only available starting from a higher plan, and the "Upgrade Plan" button will take you to the plans page instead of the settings screen.
  • You can connect only one access token per store.
  • You don't need to re-enter the pixel ID or token every time — once saved, the connection stays active until you change or remove it yourself.
  • If you see a "Could not load token status" message, retry using the "Retry" button; this is just a page-load error and does not mean the connection is broken.