Meta CAPI for UK brands — server-side tracking after iOS privacy changes
Browser Pixel data under-reports UK conversions. How to implement Meta Conversions API with deduplication, offline events, and event match quality that Smart Bidding can trust.
UK iOS share broke browser-only Meta reporting
British audiences skew iOS-heavy in many B2C categories. Meta's browser Pixel fires fewer purchase and lead events than actually occur — campaigns optimize on partial data, CPMs drift up, and reported ROAS lies.
Conversions API (CAPI) sends events server-side from your website, CRM, or checkout — with hashed customer parameters for matching.
UK implementation checklist
- Pixel + CAPI both fire with deduplication via matching
event_idon every event. - Event match quality monitored weekly — email, phone,
fbp,fbcpopulated consistently. - Offline events for phone sales, showroom visits, and CRM qualified-lead stages when ecommerce isn't the model.
- Domain verification and aggregated event measurement configured for your
.co.ukproperties. - Test events validated in Events Manager before scaling prospecting budgets.
Download our technical spec: Meta CAPI setup spec.
GDPR and consent alignment
UK brands must align CAPI with consent mode and privacy policies — not as an afterthought. We map:
- Which events fire pre-consent vs. post-consent.
- What customer data is hashed before transmission.
- How your privacy policy describes Meta data sharing.
Legal review is yours; we implement the technical layer correctly.
Creative and landing pages still decide outcomes
CAPI fixes attribution. It doesn't fix weak offers. We test hooks, formats, and landing paths as a unit — especially on mobile where most UK feed traffic lands.
Education and lead-gen case proof: Prostuty Online runs Meta at $1.10 cost per paid purchase because the funnel optimizes for purchases, not signups.