Meta CAPI, deduplicated. Each lead counted once.
Running the Pixel and the Conversions API together is right. Sending the same event twice without a shared ID is how Meta ends up reporting double.
source
Browser + server
What usually breaks
If any of this sounds familiar, the numbers are off.
- 01
Double-counted leads
Pixel and CAPI both send Lead, but deduplication sits near 0% in Events Manager.
- 02
Plugin-sent events
A WordPress or Shopify plugin sends server events nobody configured or tested.
- 03
Low event match quality
Server events arrive without the customer data Meta needs to match them.
- 04
Wrong events optimised
Campaigns optimise for events that fire on page load, not on real actions.
What we check
The check, line by line.
- 01Every event received from browser and server
- 02Deduplication rate per event and the event_id strategy
- 03Event match quality and the customer parameters sent
- 04Which tool sends server events: plugin, gateway or custom
- 05Event timing and the triggers behind each event
- 06Aggregated event measurement and domain verification
What you get
Fixed in your client's accounts, and proven.
- One event_id generated per action, shared by Pixel and CAPI
- Duplicate or rogue server events disabled
- Hashed customer parameters for better match quality
- Events mapped to the actions campaigns should optimise for
- Test Events log with screenshots
Pricing
Included in Essentials: $390 one-time per client account. Starts with a free tracking check.
How we prove it
Nothing is “done” until a test lead says so.
Meta Test Events for every path
Deduplication stats before and after
Event match quality before and after
Meta Conversions API setup: questions
4 questions
Both. The Pixel catches browser context, CAPI survives ad blockers and browser limits. They only work together if each event carries the same event_id so Meta can deduplicate.
Yes. Often the plugin is fine and only needs its settings corrected; sometimes it duplicates events and we replace it with a cleaner setup. We'll tell you which after the audit.
Events Manager access for the relevant dataset, plus GTM. We work in the client's assets and never move anything to our own accounts.
If the client already has a server container, we send CAPI events through it. If not, it's an option, not a requirement; see our server-side tracking service.
Read more
Other tracking services
- Google Ads conversion trackingConversions that fire once, on the right action, with enhanced conversions on.
- GA4 setup & auditKey events that fire once, clean naming, and reports the client can read.
- Call & form trackingEvery call and form counted, including AJAX forms.
- Server-side trackingServer-side GTM and Conversions API for data that survives browsers.
- CRM lead attributionEvery lead arrives in the CRM with its campaign, so deals trace back to spend.
- Offline conversionsSend qualified leads, bookings and sales from the CRM back to Google and Meta, so bidding learns from real outcomes.
- Conversion value rulesTell bidding which leads are worth more, with real values and value rules.
- Ads vs CRM reconciliationFind out why the ad platform and the CRM report different numbers, and fix it.
- Monthly monitoringRe-tested every month, with alerts when tracking breaks after site or form changes.
- Privacy & consentConsent Mode v2 and privacy-safe setups for regulated industries, with no personal data sent to ad platforms.
Got an account that doesn't add up?
Send us one account. We review it for free and send a short video of what's working and what isn't.