Providers

Connect Meta Pixel & CAPI

Meta Pixel powers conversion tracking and ad optimization for Facebook and Instagram campaigns. The Conversions API (CAPI) adds a server-side channel that survives ad blockers. VibesAnalytics connects both and maps them to your canonical events.

Before you start

  • A Meta Business account with a Pixel (or the permission to create one).
  • Your VibesAnalytics project created.

Connect

Have your agent call connect_provider with provider meta for your project. VibesAnalytics auto-discovers the pixels available to your business account so you don't paste pixel IDs by hand.

Pixel + CAPI

The integration contract sets up two complementary paths:

  • Meta Pixel (client-side) — the browser pixel that fires Purchase, Lead, and standard events.
  • Conversions API (server-side) — sends the same conversions from your server, so blocked browser pixels don't cost you the conversion.

Event mappings

Your canonical events map to Meta's standard events automatically:

  • signup_completed → Lead (or CompleteRegistration)
  • purchase_completed → Purchase (with value and currency)

Use the same event names everywhere; the contract handles the per-provider translation.

Verify

Use Meta's Events Manager Test Events tab to confirm both the Pixel and CAPI events arrive, then call validate_tracking in VibesAnalytics. ROAS for Meta then flows into your normalized metrics.