Skip to main
← Index

Connect Meta CAPI (Facebook / Instagram)

Send your conversions to the Meta Conversions API with a Pixel ID + access token, and deduplicate cleanly against your browser pixel.

Walityk sends your events to the Meta Conversions API (CAPI), server-side. Every event carries a stable event_id: if a browser Meta pixel also runs on the site, Meta deduplicates automatically.

Takes 5 minutes.

Prerequisites

  • A dataset (pixel) in Meta Events Manager.
  • Admin access to the Business Manager to generate the token.

1. Get the Pixel ID and Access Token

  1. Open Meta Events Manager and select your dataset (pixel).
  2. The Pixel ID (digits only) is shown at the top of the dataset.
  3. Settings tab → Conversions API section → Generate access token. Copy it. No Facebook app needed.

2. Configure the destination

  1. Walityk dashboard → Destinations → your site → Meta CAPI card.
  2. Paste the Pixel ID and Access Token.
  3. Optional: a Test Event Code (Events Manager “Test events” tab) to verify reception without polluting your stats. Remove it once testing is done.
  4. Pick the events to forward (everything checked = everything goes), then Save.

3. Deduplication with your browser pixel

Three cases:

  • No Meta pixel on the site: nothing to do. CAPI alone is enough.
  • You enable Walityk “Pixel deduplication” (site setting, also in the Shopify app): the Walityk tag initializes the Meta pixel and re-fires each browser event with the same event_id as the server copy. Remove your own fbq('track', …) calls — otherwise your manual events, lacking the shared event_id, get double-counted. The base fbq('init') can stay or go: Walityk initializes the pixel itself.
  • You keep your manual pixel without Walityk deduplication: expect double counting on events sent from both sides. Narrow the event selection on the Walityk side, or enable deduplication.

4. Verify

  1. Check that events arrive → after saving, or Destinations → your site → Meta CAPI (delivery log).
  2. On the Meta side: Events Manager → Test events (with the Test Event Code) then the Overview tab — events arrive with the “Server” source.

Common errors

  • Invalid or expired token (code 190): regenerate a token in Events Manager → Settings → Conversions API, paste it again.
  • HTTP 400: wrong Pixel ID (make sure it’s the dataset’s numeric ID).
  • “Skipped” events in the log = the visitor declined advertising consent, or the event type is unchecked. Normal, not an outage.

Next steps

Need help? hi@walityk.com.