How server events survive the browser

What CAPI fixes#

Browser signal leaks: blockers strip the Pixel, privacy prompts refuse it, and flaky connections drop fires mid-flight. CAPI bypasses the browser entirely, sending events from your server with customer details, click IDs and order data that the browser never reliably carries. The result is fuller counts, better matching and steadier optimisation. Meta own CAPI overview states the case.

CAPI complements the Pixel rather than replacing it: browser events carry rich page context fast, server events carry confirmed outcomes durably. Together with shared event IDs they form one counted stream. How the pairing deduplicates is covered in our dedup guide.

Setup routes compared#

Partner integrations are the fast lane: Shopify, WooCommerce and major platforms connect catalogue, Pixel and CAPI in one maintained flow with Enhanced or Maximum data sharing. Tag-server routes suit teams already running server tagging, and the direct API suits custom stacks with engineering time. Pick the route your team will maintain, because abandoned plumbing rots fastest.

Budget reality check: partner lanes take hours, tag servers take days, direct builds take sprints. Start at the Meta Ads hub, confirm the Pixel fires first via Pixel setup, then layer the server route that matches your stack.

Matching parameters#

Server events match to people on hashed customer data: email, phone, name, postcode and IP plus browser click IDs fbp and fbc. Send everything the order or form honestly holds; each extra field lifts match quality, and match quality decides how much server signal optimisation can use. Hashing happens before or during transit, so raw customer data never sits in logs.

Prioritise the click IDs: fbp and fbc tie server events to the ad click that caused them, which is the join attribution and bidding both lean on. Capture them at the event source and forward them server side. Developer field reference is at CAPI parameters.

Dedup keys that hold#

Every action the Pixel and CAPI both report needs one shared event ID plus a matching event name, so Meta counts it once. Generate the ID at the source of truth, the order confirmation or the validated form handler, and pass the same value to both streams. Random IDs per stream guarantee double counting.

Confirm dedup in Test Events with both streams live: paired fires collapse to one, strays stay doubled and named. Keep the key scheme documented beside standard events notes, and recheck after checkout rebuilds. Dedup detail continues the method.

Proving cover#

Proof has three numbers: event match quality scores trending up, server share of total events rising toward the majority on key actions, and platform counts reconciling with your order book inside tolerance. Run a real test order before launch, refund it, and exclude it from reporting; sandbox tests miss currency, value and dedup faults that only money reveals.

Hold a monthly signal review: match quality, diagnostics, dedup health and count reconciliation in one sitting. Shops with feeds should cross-check catalogue ID alignment via catalogue setup. Ask our team for a cover audit when counts drift.

Maintenance rhythm#

Server plumbing needs a calendar, not just a launch: review match quality monthly, re-verify dedup after every checkout or form release, and rotate tokens and credentials before they expire mid-quarter. Assign one owner to signal health, because shared ownership means nobody notices the slow drift until optimisation complains.

Keep a change log of integration updates, token rotations and parameter additions beside your event map. When counts move, the log names the suspect in minutes. Pair the routine with offline conversions uploads where store or phone sales close the loop.

Frequently asked questions#