Postback vs pixel — which to use

Both are conversion tracking mechanisms with different trade-offs. Pixel = browser-side JavaScript snippet. Postback = server-to-server HTTP call. For most setups: use both with deduplication. For specific scenarios, one is mandatory and the other inappropriate.

Who is this for

Mediabuyers choosing between (or combining) tracking methods, especially anyone who lost attribution after iOS 14.5 (browser pixel less reliable) or runs affiliate funnels (browser pixel often unavailable).

At a glance

Use cases per method

Use browser pixel when

• Direct e-commerce on your own site: customer browses your store, you control the funnel end-to-end

• Lead-gen forms on your site: form submission happens on your domain

• Awareness / engagement signals: page views, time on site, scroll depth (these don't need server-side)

• Initial setup: pixel is fastest to deploy (Meta Pixel, Google Tag = 5-10 min)

• Augmenting CAPI/postback: pixel for browser-side, CAPI/postback for server-side, dedup'd via event_id

Use postback (S2S) when

• Affiliate funnels: conversion happens on the offer site you don't control; can't install pixel there

• App installs: tracker logs install via MMP (AppsFlyer, Adjust, etc.); ad platforms need server-side signal

• Off-site conversion events: CRM updates, ticket purchases on third-party platforms

• iOS-heavy audience: ATT opt-outs invalidate browser pixel; postback unaffected

• Privacy-conscious users: ad blockers don't affect server-to-server

• Server-side data you already have: your backend logs conversions; just fire to Wevion

Use BOTH (recommended for high-value conversions)

For purchases or other high-value conversions:

• Install pixel for fast/easy initial signal

• Add CAPI (meta-105) or postback (com-110) for resilience

• Match via event_id for deduplication

• Wevion handles both surfaces; ad platforms count as 1 conversion via dedup

This is industry-standard since iOS 14.5 (2021).

Decision tree

Is conversion on YOUR site?
├─ YES → install pixel + CAPI (for Meta) or postback (for tracker-driven setups)
│       Both fire, both attribute, dedup via event_id
│
└─ NO → must use postback (or equivalent server-side)
    Pixel cannot fire on a domain you don't control

What you lose without each

Lose pixel: you lose

• Easy initial attribution signal

• Browser-side enrichment (user-agent, referrer, page details for context)

• Automatic event triggering (no integration needed)

Lose postback: you lose

• Server-side resilience (iOS, ad blockers)

• Off-site conversions

• Tracker-driven funnels

• Late-binding conversions (e.g. refunds processed days later via tracker)

Real-world examples

Example A: D2C e-commerce on Shopify

• Setup: Meta Pixel (browser) + Meta CAPI (server via Wevion using Shopify orders) + Wevion's postback NOT needed

• Why: Shopify handles server-side via Wevion's CAPI integration (meta-105)

• Result: > 95% attribution accuracy across iOS + Android + desktop

Example B: Affiliate lead-gen via Keitaro

• Setup: Keitaro tracker → Postback to Wevion → Meta CAPI / Google Conversions

• No browser pixel: offer site is partner-owned, can't install

• Why: postback is the only way; pixel is not possible

• Result: server-side accuracy, no iOS/ATT impact

Example C: Multi-platform e-commerce with mixed funnels

• Setup: pixel + CAPI on direct funnel; postback for tracker-driven affiliate channel

• Why: different funnels, different mechanisms

• Result: unified attribution across all funnels in Wevion analytics

What you'll see when both are firing

In Wevion /pixels:

• Pixel events with counts (browser side)

In Wevion /connect/postback:

• Postback events with counts (server side)

• Deduplication rate (% of events with matching event_id from both surfaces)

In Meta Ads Manager → Events Manager → diagnostics:

• Events labeled "Browser + Server" (deduplicated)

• High deduplication rate (90%+) means correct setup

Common questions

• "Will I be double-counted if I run both?": no, IF you use event_id matching for deduplication. Pixel and postback fire with the same event_id; ad platform counts as 1.

• "Which is more accurate?": postback wins on iOS / ad-blocker / privacy contexts. Pixel wins on browser context enrichment. Combined = best.

• "Can I just use postback and skip the pixel?": yes for tracker-driven funnels. For direct e-commerce, pixel adds easy attribution + faster setup.

• "Do I need event_id if I only use one method?": not for dedup (only one source), but still helps with debugging.

• "What if my tracker doesn't send event_id?": most trackers can pass a conversion ID as event_id. Configure in tracker postback URL builder.

Related

• Postback (S2S) tracking overview — postback deep dive

• Set up Meta Pixels and Conversions API — pixel + CAPI deep dive

• Set up your first pixel — pixel basics