Pixel signal CAPI
Meta Conversions API (CAPI) setup and implementation
Bypass browser cookie blocks completely.
Direct server-to-server attribution feeds sent straight to ad networks.
The Meta Conversions API (CAPI) sends conversion events from your server to Meta, alongside the browser pixel. It exists because the pixel alone now misses a meaningful share of what happens on your site: browser privacy features, blockers, consent choices and short cookie lifetimes all remove events before Meta sees them. When Meta optimises against an incomplete record of who bought or became a lead, it finds more people like the ones it happened to observe — not more people like your best customers.
We implement CAPI so that it actually improves the signal rather than just adding a second stream. That means deduplicating server and browser events, passing the customer information parameters that raise Event Match Quality, attaching values to purchase and lead events, and — for lead businesses — sending CRM outcomes back so Meta can optimise for qualified leads. Everything is built in your Business Manager and your infrastructure, and stays there.
The problem
Browser privacy updates block standard web pixels, leading to lost conversion tags and degraded ad bidding. Recovering signal requires server-side event tracking.
What we do
- Configure server-side tracking containers
- Integrate platform conversion APIs
- Implement event deduplication parameters
- Map offline deals back to campaigns
What you get
- Conversions API integration plans
- Server tracking container setups
- Event quality reports
- Offline data sync maps
A browser-independent signal connection feeding ad platforms complete conversion data.
How it runs
- Deploy Server. We set up a cloud server container to manage server-side signal events.
- Map Events. We sync front-end browser events with server-side API conversions.
- Hash Data. We implement secure first-party data hashing before sending conversion logs.
- Verify Sync. We check ad platform match scores, verifying event quality indices are high.
Who this is for
- Brands spending meaningfully on Meta whose Ads Manager numbers no longer match orders, revenue or CRM outcomes
- Shopify, WooCommerce and custom-stack stores where the pixel is the only signal, or where a plugin CAPI setup was never checked
- Lead-generation businesses that want Meta to optimise for qualified leads rather than form fills
- Teams preparing for Meta's 2026 measurement changes and wanting reporting they can reconcile
What's included
- Audit of current pixel, CAPI, deduplication and Event Match Quality in Events Manager
- Server-side implementation via server-side Google Tag Manager, a platform integration or direct API, chosen for your stack
- Event schema: standard events, values, currency, content IDs and a new-customer flag
- Customer information parameters hashed with SHA-256, plus fbp/fbc, IP and user agent, filtered by consent
- CRM event feed for lead businesses (Conversions API for CRM / conversion leads optimization)
- Monitoring for event volume, match quality and deduplication, with a written runbook
How a CAPI implementation goes wrong
The most common failure is duplication. When the pixel and the server both send a purchase without the same event_id and event_name, Meta counts one sale twice. Reported ROAS rises, the algorithm learns from inflated data, and the gap between Ads Manager and your store widens. The second failure is a thin payload: a server event that arrives with only an IP address cannot be matched to a person, so it does little for optimisation. The third is timing — events sent in batches hours later are less useful for delivery than events sent as they happen.
Platform plugins can work well, but they are rarely checked after installation. We regularly find setups where the plugin sends server events for some actions and not others, where values are missing, or where consent settings block the server events that should still fire for consenting users. The audit tells you which of these apply before anything is rebuilt.
Choosing an implementation route
There are three common routes. Native platform integrations, such as Shopify's Meta channel, are quickest and fine when your events are standard and the integration is configured fully. Server-side Google Tag Manager, hosted on your own subdomain, gives you one place to send events to Meta, Google and others, with control over what is sent and when. A direct integration from your backend or CRM is best when the event that matters — a qualified lead, a closed deal, a delivered order — lives outside the website.
Many accounts end up with a combination: platform or server-side tagging for website events, and a CRM feed for downstream lead stages. We recommend the simplest route that sends complete, deduplicated, consented events, and we document it so your team can maintain it. For lead businesses, the CRM feed is often where most of the value is; our guide to fixing signal loss between HubSpot and Meta CAPI shows how that connection works.
Consent, privacy and what you may send
Server-side tracking does not remove consent obligations. In the UK and EU, advertising events depend on users agreeing to tracking; in the US, a growing number of state laws give users rights to opt out of targeted advertising; India's Digital Personal Data Protection Act sets consent and purpose rules. We build CAPI to respect the consent signal you already collect, hash identifiers before they leave your systems and send only the fields optimisation needs.
Regulated categories need extra care. Healthcare, finance and some education advertisers must limit what is sent from sensitive pages. We map those constraints before building, and your legal or compliance team signs off on what is transmitted. This is technical implementation, not legal advice.
Frequently asked questions
Do I still need the Meta pixel if I set up the Conversions API?
Yes. Meta recommends running both. The pixel captures browser context the server may not have, and the Conversions API captures events the browser loses. With a shared event_id, Meta deduplicates them so each conversion counts once.
What Event Match Quality score should we aim for?
Meta scores match quality from 0 to 10 per event. There is no universal target, but higher is better: it rises when events carry more customer information parameters such as hashed email and phone, plus fbp and fbc. We show you the score per event before and after the work.
How long does a Conversions API implementation take?
A standard e-commerce or website implementation is usually done within two to four weeks, including testing. A CRM feed for lead stages takes longer because stages, IDs and upload cadence need agreeing with sales and engineering.
Will CAPI lower our cost per purchase?
Often, but it is not guaranteed. CAPI improves the data Meta optimises against. Accounts with large signal loss usually see better delivery and more accurate reporting; accounts whose pixel already captured most events see smaller changes. We measure the effect against your own revenue, not Ads Manager alone.
Can you set up CAPI on Shopify without a developer?
Often yes, through Shopify's Meta integration set to its maximum data-sharing level, followed by checks in Events Manager for deduplication and match quality. Custom events, subscriptions and post-purchase upsells usually need additional server-side work.
Why is the Conversions API (CAPI) necessary?
Browser updates and ad blockers prevent standard pixels from firing. The Conversions API sends events directly from your server, recovering lost signals.
Does the Conversions API replace the web pixel?
No, they run together. We set up event deduplication rules so the ad platform matches them without duplication.
What platforms do you set up the Conversions API for?
We integrate the Conversions API for Meta, Google Ads (Offline Conversions), TikTok, and LinkedIn.
Pricing: monthly retainers by region
Every engagement is a monthly retainer priced on scope — never a percentage of ad spend. The range depends on the number of channels, markets and the depth of tracking and CRM work involved.
| Region | Monthly retainer |
|---|---|
| United States | $2,500–$6,000 per month |
| India | ₹1,00,000–₹5,00,000 per month |
| United Kingdom | £2,200–£5,000 per month |
| United Arab Emirates | AED 4,000–AED 10,000 per month |
| Australia | A$3,000–A$7,000 per month |
| Canada | C$3,000–C$7,000 per month |
| Singapore | S$3,000–S$7,000 per month |
| Europe | €2,500–€5,000 per month |