Set up Meta Pixels and Conversions API
Wevion auto-imports Meta Pixels from connected ad accounts. Browser pixel + Conversions API for full attribution with deduplication.
Written By Salvatore Sinigaglia
Last updated About 4 hours ago
Wevion auto-imports Meta Pixels from connected ad accounts. Browser pixel + Conversions API for full attribution with deduplication.
Set up Meta Pixels and Conversions API
Meta Pixels are imported automatically from connected ad accounts — view at /pixels after the first sync. The browser pixel (snippet on your site) is the basic version; the Conversions API (CAPI) is the server-side counterpart for iOS 14.5+ ATT and ad-blocker resilience. Wevion has built-in CAPI support — combine browser pixel + CAPI for the most accurate attribution.
Who is this for
E-commerce and lead-gen mediabuyers running conversion-objective Meta campaigns. Anyone whose Meta attribution dropped after Apple iOS 14.5 (App Tracking Transparency) — CAPI is the answer.
Why both pixel AND CAPI
Together with deduplication (matching events via event_id), they give you the most complete picture. Industry-standard setup since 2021.
Browser Pixel — auto-imported
When you connect Meta, all pixels associated with your imported ad accounts are auto-discovered:
- Pixel rows created in Wevion DB (via
pixel_ad_account_linktable per CLAUDE.md) - Visible at
/pixelswith: pixel ID, name, status (Active / Inactive / Error), event types received, daily counts
The pixel JavaScript snippet itself lives on your site (installed before </head> ideally). Wevion doesn't install it for you — that's a one-time setup in your CMS / GTM / dev code via Meta Events Manager.
If you don't have a pixel on your site yet:
- Meta Business Manager → Events Manager → Connect Data Sources → Web → Set up Meta Pixel
- Install the generated snippet on your site
- Within 15 minutes after the snippet fires, Wevion's next sync picks it up
Conversions API (CAPI) — server-side events
Wevion has a built-in server-side CAPI provider that forwards conversion events from Wevion's server to Meta's Conversions API endpoint. This is Wevion's internal server-side tracking path — there is no self-serve "Conversions API" section on /connect/meta today where you paste a per-account EAAB… access token.
What this means in practice:
- The browser Meta Pixel remains the piece you install and manage on your site (see above).
- The server-side CAPI counterpart is handled by Wevion's tracking pipeline rather than through a per-account token you configure in the UI.
- For richer, server-side commerce events, e-commerce platform integrations (Shopify, WooCommerce) are the path — see the PRD-14 commerce articles when published.
If you need a per-account CAPI token configuration exposed in the UI, treat it as not currently available and check the changelog for updates.
Verify deduplication
Where both browser and server events flow for the same conversion, Meta Events Manager → Test Events marks each event as Browser + Server (deduplicated). If you see duplicate counts, the event_id isn't matching between the browser pixel and the server-side event.
Standard events Wevion supports
Custom events also supported (any string event name) — pixel + CAPI must use the same name to dedupe.
Pixel health at /pixels
Open /pixels to see the imported pixels list. Each row shows:
- Status badge: Active (events last 7d), Inactive (no events 7d), Error (Meta reports config issue)
- Event counts per type per day (last 7d sparkline)
- Source domains (where events fire from)
- Test events button → links to Meta's Test Events tool
A healthy pixel for an active e-commerce site: 100s-1000s of events/day, Active badge, no domain warnings.
When to use pixel vs CAPI vs both
What you'll see
A correctly configured pixel + CAPI:
/pixelsshows the pixel with Active badge + green health- Event counts visible per day
- In Meta Events Manager: events tagged Server + Browser (deduplicated)
- In Campaign Creator: pixel selectable as conversion source for Sales/Leads objectives
- After 50+ conversions: optimization improves vs browser-only
Common issues
- Pixel shows Inactive despite site traffic: pixel installed after
</head>(load order issue) or blocked by ad blocker on your test browser. Test in incognito. - Duplicate event counts in Meta:
event_idmismatch. Check that the browser pixel passes aneventIDparameter matching the server-side event'sevent_id. - Server events arriving but with $0 value: the source (e-commerce platform integration) isn't sending a
valuefield. Check pixel + server payloads in Events Manager Test Events. - Domain not verified warning: Meta requires domain verification for iOS 14.5+ attribution. Verify in Meta Business Settings → Brand Safety → Domains.
- Pixel showing in Wevion but not Meta Events Manager: cache. Force sync from pixel detail drawer.
Aggregated Event Measurement (AEM)
For iOS 14.5+ users who opt out of tracking, Meta uses Aggregated Event Measurement — you must:
- Verify domain in Meta Business Settings
- Prioritize up to 8 events per domain (Meta Events Manager → Aggregated Event Measurement → Configure Web Events)
- Optimize campaigns for higher-priority events (Meta uses priority for attribution)
Wevion doesn't manage AEM directly — it's a Meta-side configuration. But Wevion respects the AEM-configured events when launching campaigns.
FAQ
Are Meta Pixels imported automatically into Wevion?
Yes. When you connect Meta, all pixels associated with your imported ad accounts are auto-discovered and appear at /pixels after the first 15-minute sync. Each pixel row shows its ID, name, status (Active / Inactive / Error), event types received, and daily counts. Wevion does not install the pixel JavaScript snippet on your site — that's a one-time setup in your CMS, GTM, or via Meta Events Manager.
Why should I use both the browser Pixel and the Conversions API?
The browser Meta Pixel tracks events in the user's browser and is affected by ad blockers, iOS 14.5+ ATT, and third-party cookie deprecation, while the Conversions API (CAPI) sends events server-to-server and isn't. Together with deduplication (matching events via event_id) they give the most complete attribution — the industry-standard setup since 2021. Wevion has built-in CAPI support.
How does the Conversions API work in Wevion?
Wevion has a built-in server-side CAPI provider that forwards conversion events from Wevion's server to Meta's Conversions API endpoint. It runs as part of Wevion's tracking pipeline — there is no self-serve "Conversions API" section on /connect/meta today where you paste a per-account EAAB… access token. The browser Meta Pixel remains the piece you install and manage on your site; for richer server-side commerce events, use the Shopify / WooCommerce integrations.
Why am I seeing duplicate event counts in Meta?
Duplicate counts mean the event_id isn't matching between your browser pixel and CAPI. Check that the browser pixel passes an eventID parameter matching your CAPI event_id. When deduplication works, Meta Events Manager Test Events marks each event as Browser + Server rather than counting it twice.
Does Wevion manage Aggregated Event Measurement (AEM) for iOS?
No. AEM is a Meta-side configuration — you verify your domain in Meta Business Settings, prioritize up to 8 events per domain in Events Manager, and optimize campaigns for higher-priority events. Wevion doesn't manage AEM directly, but it respects the AEM-configured events when launching campaigns.