# Meta Conversions API (CAPI) Set-Up

Source: https://dijitulmarketing.co.uk/meta-conversions-api/
Updated: 2026-11-20

> dijitul marketing sets up the Meta Conversions API (CAPI) for UK businesses from £145 + VAT one-off. We connect server events alongside your Meta pixel through Shopify, WooCommerce, Meta's Conversions API Gateway or server-side Tag Manager, deduplicate them with a shared event_id, check Event Match Quality and make sure consent choices are respected.

Price: From £145 + VAT

## Problems this solves

- Meta Events Manager shows far fewer purchases or leads than you actually received.
- Meta reports double the sales because pixel and server events are not deduplicated.
- Events Manager keeps warning about low Event Match Quality.
- A plugin turned on CAPI years ago and nobody knows if it still works.
- Leads close offline in your CRM and Meta never learns which ones became customers.
- Server events fire even when a visitor declined advertising cookies.

## Key facts

- Meta Conversions API set-up starts from £145 + VAT one-off.
- Meta's developer documentation recommends using the Conversions API in addition to the Meta pixel, sending the same events through both.
- Per Meta's deduplication guide, the pixel eventID must match the server event_id and the event names must match; duplicates within 48 hours are discarded.
- Meta's best practices page says Event Match Quality is scored out of 10 and is currently available for web events only.
- Meta's developer documentation says the Conversions API Gateway runs in a cloud account the business owns, on AWS or Google Cloud, and its only cost is cloud resource or partner fees.
- WooCommerce says its official Facebook for WooCommerce extension deduplicates pixel and Conversions API events with a unique event ID.
- Server events must follow the same consent choices as the pixel under UK PECR and UK GDPR.

## Pixel and Conversions API: why you want both

The Meta pixel is JavaScript in the visitor's browser. It sees clicks and page views well, but it can be blocked by browser settings, ad blockers or a declined consent banner, and it cannot see anything that happens after the visit, such as a lead turning into a sale.

The **Conversions API** sends events from a server instead. Meta's developer documentation recommends using it in addition to the pixel, not instead of it, and sharing the same events through both. That redundant set-up gives Meta's delivery system a fuller picture to optimise Facebook and Instagram ads against.

dijitul marketing sets this up **from £145 + VAT** one-off, as part of our wider conversion tracking work or on its own.

## Which set-up route fits your site

- **Shopify**: Meta's Facebook and Instagram sales channel for Shopify includes Conversions API. The data sharing level chosen in the app decides how much is sent, so we check it.
- **WooCommerce**: the official Facebook for WooCommerce extension supports Conversions API, and WooCommerce says it deduplicates pixel and server events with a unique event ID.
- **Conversions API Gateway**: Meta's developer documentation describes it as a self-serve option in Events Manager that runs in a cloud account you own, on AWS or Google Cloud, with no coding. Meta says the only cost is the cloud resources or partner fees.
- **Server-side Google Tag Manager**: best when one event stream feeds GA4, Google Ads and Meta together. See server-side tracking.
- **Direct integration**: your developer or CRM sends events straight to the API, useful for offline sales.

We recommend the simplest route that does the job. If CRM events need custom development, dijitul developments builds integrations.

## Deduplication with event_id

Sending every purchase twice is easy. Counting it once takes care. Meta's deduplication guide says the pixel's **eventID** must match the server event's **event_id**, and the pixel event name must match the server **event_name**. Matching events received within 48 hours of the first are discarded after the first, and Meta says it generally prefers whichever arrives first.

There is a fallback using fbp and external_id, but Meta says it only works when the browser event arrives before the server event. A shared event_id is more dependable, so we generate one value per action, push it to the data layer and send it with both events.

We then test with real orders or form submissions and check Events Manager shows the events as deduplicated, not doubled.

## Event Match Quality

Meta's best practices page describes **Event Match Quality** as a score out of 10 showing how well an event's customer information may match it to a Meta account. It is currently available for web events only.

The same page lists email (em), phone (ph), first and last name (fn, ln) and IP address as examples of high-quality parameters, and says to include external_id and event_id for all events and the client user agent for website events. It notes that the fbp and fbc cookie values change, so they must be kept fresh.

Personal data such as email and phone is normalised and hashed with SHA-256 before it is sent. We only send what you collect lawfully at checkout or on your forms, and we never add fields just to push the score up.

## Consent and data protection

A server-side connection does not change the law. In the UK, the pixel's cookies need consent under PECR, and the ICO's storage and access guidance says advertising purposes are not exempt. The Conversions API sends personal data, even when hashed, so UK GDPR applies too: you need a lawful basis and a privacy notice that mentions Meta.

We wire your consent banner so that when a visitor declines advertising cookies, neither the pixel nor the matching server event is sent for that visitor. Shopify and WooCommerce integrations respect consent in different ways, so we test both accepted and declined journeys before signing off.

## What you get

- An audit of your current pixel, events and Events Manager diagnostics
- Conversions API connected by the right route for your site: commerce platform, Gateway, server-side Tag Manager or direct
- One event_id generated per action and sent with both pixel and server events
- Customer information parameters mapped and hashed to improve Event Match Quality
- Consent wiring so server events only send when the visitor has agreed
- Testing in Events Manager's test events tool and a written handover

## FAQs

### How much does Meta Conversions API set-up cost?

dijitul marketing sets up Meta Conversions API from £145 + VAT one-off. The fixed price depends on your platform and how many events you track. Any cloud hosting for the Gateway or server-side Tag Manager is paid separately to the provider.

### Can I turn off the pixel once CAPI is running?

We do not recommend it. Meta's documentation advises using the Conversions API in addition to the pixel. The pixel captures browser detail the server cannot see, and deduplication stops double counting.

### What is event_id and why does it matter?

It is a unique value for each action, such as an order. Meta's documentation says when the pixel and server send the same event name with the same event ID within 48 hours, Meta keeps one and discards the duplicate.

### What is a good Event Match Quality score?

Meta scores it out of 10, and higher means better matching. The score depends on which customer details you can lawfully send, such as email and phone. We improve it where we can but do not promise a number.

### Does Shopify already include the Conversions API?

Yes, Meta's Facebook and Instagram channel for Shopify supports it. It still needs checking: the data sharing level, consent behaviour and deduplication are the usual problems we find when we audit an existing Shopify store.

### Does CAPI get round cookie consent?

No. Server events must follow the same consent choices as the pixel under PECR and UK GDPR. We set it up so declined visitors are not sent to Meta for advertising.

## Prices and contact

Prices (all from, + VAT; ad spend separate): Google Ads management £150 a month; Paid social (Meta, LinkedIn, TikTok) £150 a month; ChatGPT, Copilot, Reddit, Snapchat, Pinterest and Amazon ads £150 a month; Social media management £125 a month; Email marketing £95 a month; Marketing automation set-up £195; SMS marketing £75 a month; GA4 set-up £95; Conversion tracking £145; Data Studio (Looker Studio) dashboard £145; Conversion rate optimisation £195 a month; Content marketing £195 a month; Connected TV, Spotify, X, Nextdoor, Threads and Apple ads £150 a month; WhatsApp Business marketing £75 a month; Affiliate marketing management £150 a month; B2B lead generation and LinkedIn outreach £195 a month; Consultancy, audits and strategy £45 an hour. All prices are "from" and exclude VAT. Ad spend is separate and paid directly to Google, Microsoft, Meta, LinkedIn or TikTok. Paid media management is from £150 a month or 10 to 15% of ad spend, whichever is higher. You own every ad account, pixel, audience and email list we set up. Contact: https://dijitulmarketing.co.uk/contact/ · 01623 650333 · info@dijitul.uk
