Free website audit for growing businesses: find out what's holding your site back. Get yours

Meta Pixel and Conversions API, set up properly

We install the Meta Pixel and the Conversions API together, deduplicate events, raise event match quality and test real purchases and leads.

  • Pixel and CAPI together
  • Deduplicated, so nothing counts twice
  • Tested on real conversions
  • Meta Business Suite
  • Google Tag Manager
  • Shopify

Meta misses a third of your sales

Purchases last month

  • Your store412
  • Meta: Pixel only251
  • Missing161

Meta can only learn from sales it sees

How we fix itThe Conversions API sends purchases from your server, so blocked browsers don’t hide them.

Purchases counted twice

Events Manager

  • Pixel: Purchase398
  • CAPI: Purchase402
  • Deduplicated0%

Meta reports 800 sales from 412 orders

How we fix itThe same event ID on the Pixel and the server event, so Meta keeps one.

Event match quality is poor

Event match quality

  • Purchase4.2 / 10
  • Lead3.8 / 10
  • Email sentNo

Meta can’t tell who bought

How we fix itHashed email, phone and other customer data sent with each event.

Tracking broke after a site change

Purchase event, last 14 days

  • Before the theme update18 a day
  • After the update0
  • Noticed after9 days

Campaigns optimised on nothing for nine days

How we fix itEvents rebuilt and tested on the new site, then checked every week.

Meta never hears which leads were good

Lead quality

  • Leads from Meta240
  • Qualified in CRM38
  • Sent back to MetaNone

Meta keeps finding cheap, poor leads

How we fix itCRM stages sent back, so Meta learns which leads turn into customers.

Signs your Meta tracking is missing sales

Meta can only optimise towards the conversions it sees. These are the problems we find most often.

  1. The Pixel runs in the browser, so ad blockers, iPhone privacy settings and short cookies hide a share of your sales. Meta then thinks your ads work worse than they do, and learns from fewer buyers.

    We add the Conversions API, which sends purchases from your server or store. Together with the Pixel, Meta sees close to every sale, and your reported results match your store far more closely.

  2. When the Pixel and the Conversions API both send a purchase without the same event ID, Meta counts both. Results look great, but they’re wrong, and bidding chases sales that never happened.

    We send one event ID with both versions of every event, so Meta keeps one. Then we check the deduplication rate in Events Manager and compare purchases with your store.

  3. Event match quality shows how well Meta can link an event to a person. With low scores, Meta can’t tell who bought, so it can’t find more people like them.

    We send hashed customer data with each event: email, phone, name, city and Meta’s click and browser IDs, with consent. Scores usually rise to “Good” or “Great”.

  4. A new theme, checkout app or cookie banner can quietly remove events. Campaigns keep spending while Meta sees nothing, and nobody notices for days.

    We rebuild the events on the current site, test them, and set an alert if purchases stop arriving, so a site change can’t break tracking silently again.

  5. Many stores switched on an app or plugin years ago and never checked it. Some send only page views, some send purchases without values, and some stopped working long ago.

    We check every event in Events Manager: where it comes from, what data it carries and whether it matches your store. Then we fix what’s missing and write it all down.

  6. For lead generation, Meta only knows someone filled in a form. It never learns which leads became customers, so it keeps finding cheap leads that don’t buy.

    We send CRM stages back through the Conversions API, such as qualified, booked and won, so Meta can optimise for leads that turn into revenue.

Meta learns from what you send it

When Meta sees more of your sales, it finds more people like your buyers, and your cost per result falls.

Get this fixed

Meta Pixel and Conversions API, done properly

One fixed-scope project, quoted after a short call. No retainer needed.

Meta Pixel and Conversions API setup

Fixed price, quoted after a 30-minute call

  • An audit of your Pixel, events and Events Manager
  • Conversions API through Shopify, WordPress, a gateway or server-side Tag Manager
  • Standard events and parameters (value, currency, content IDs)
  • Deduplication with event IDs
  • Customer information parameters for better match quality
  • Domain verification and event priority
  • CRM events for lead quality
  • A test report

Usually done in 5 to 10 working days

Request a quote

A tracking specialist and a developer

Your Meta specialist plans the events and checks them in Events Manager. One of our developers sets up the server side, so nothing is left half-done.

  • Every event tested
  • Checked against your store
  • Written down for your team

Pixel and Conversions API

Example store, after our setup

  • Page viewYesYesOnce
  • View contentYesYesOnce
  • Add to cartYesYesOnce
  • CheckoutYesYesOnce
  • PurchaseYesYesOnce · 9.1
  • Lead won (CRM)—YesOnce

Both send every event with the same ID, so Meta counts each one once. The score is event match quality.

Set up, then tested in Events Manager

First a call, then five steps. You see the results at each one.

A call back within 24 hours

Tell us about your site. A tracking specialist calls you back within one working day to look at your Events Manager with you, before any work starts.

  • A real person
  • No obligation
  • Plain English
  1. We look at your Pixel, events, parameters, domain and current match quality, and compare Meta’s numbers with your store or CRM.

    You get: A list of what’s missing, broken or counted twice.

    • Every event in Events Manager
    • Pixel and Conversions API sources
    • Match quality and deduplication
    • Meta vs store or CRM numbers
  2. We agree which events to send, from where, with which data, and how your cookie banner affects them.

    You get: An event plan you approve before we build.

    • Events and their values
    • Pixel, server or both
    • Customer data and consent
    • CRM stages for lead quality
  3. Our developer sets up the Conversions API through your platform, a gateway or server-side Tag Manager, with event IDs for deduplication.

    You get: Both sides sending the same events.

    • Pixel events cleaned up
    • Conversions API connected
    • Event IDs on both sides
    • Domain verified and events prioritised
  4. We place test purchases and submit test leads, then check each one in Events Manager: received, deduplicated, with the right value and data.

    You get: Every event passed, or fixed and tested again.

    • Test purchases and leads
    • Desktop, iPhone and Android
    • Deduplication and match quality
    • Store and CRM compared
  5. You get a test report and a walkthrough call. We check Events Manager again after two weeks to make sure nothing has slipped.

    You get: Tracking you can trust, and know how to keep.

    • A test report
    • A walkthrough call
    • An alert if purchases stop
    • A two-week check

What we set up

Eight parts of Meta tracking, set up and tested

For each one: why it matters, what we set up, what we usually find and what you get.

Area 1 of 8

Pixel events

The Pixel still matters: it sees browsing behaviour and sends events quickly. It just can’t see everything on its own.

What we set up

  • Base code on every page
  • Standard events
  • Value, currency and content IDs
  • Custom conversions
  • One Pixel per business
  • Test events

What we usually find

  • Two Pixels on the same site
  • Purchase firing on page reload
  • No value on purchases
  • Events from an old theme

What you get

  • One clean Pixel
  • Standard events in the right places
  • Values and content IDs on every purchase
  • Old events removed

Area 2 of 8

Conversions API

The Conversions API sends events from your server or store, so blocked browsers and short cookies don’t hide them.

What we set up

  • Shopify or WordPress integration
  • Conversions API gateway
  • Server-side Tag Manager
  • Events sent from the server
  • Access token and security
  • Error monitoring

What we usually find

  • An app switched on but sending nothing
  • Only page views sent from the server
  • An expired access token
  • Errors in Events Manager nobody saw

What you get

  • The right connection for your platform
  • Key events sent from the server
  • Errors checked and fixed
  • An alert if events stop

Area 3 of 8

Deduplication

With both the Pixel and the Conversions API on, every event arrives twice. Without the same event ID, Meta counts both.

What we set up

  • Event ID on Pixel events
  • Same ID on server events
  • Event names that match
  • Timing
  • Deduplication rate
  • Purchases vs orders

What we usually find

  • No event IDs at all
  • Different IDs on each side
  • Event names that don’t match
  • Twice as many purchases as orders

What you get

  • One event ID shared by both
  • Matching event names
  • Deduplication checked in Events Manager
  • Purchases that match your orders

Area 4 of 8

Event match quality

The more Meta can match events to people, the better it targets and reports. Customer data, sent safely, is the key.

What we set up

  • Hashed email and phone
  • Name, city and country
  • Click ID (fbc) and browser ID (fbp)
  • External ID
  • IP and user agent
  • Consent

What we usually find

  • No customer data sent
  • Email sent unhashed
  • Click ID lost on redirects
  • Data sent without consent

What you get

  • Hashed customer data with every event
  • Click and browser IDs kept
  • Consent respected
  • Scores of “Good” or “Great”

Area 5 of 8

Domain and event setup

Domain verification shows Meta the site is yours, and event priority decides what counts for iPhone users who opt out.

What we set up

  • Domain verification
  • Aggregated event measurement
  • Event priority
  • Checkout on other domains
  • Subdomains
  • Business portfolio ownership

What we usually find

  • Domain never verified
  • Purchase not the top-priority event
  • Checkout on a domain Meta can’t see
  • Pixel owned by a former agency

What you get

  • Domain verified
  • Events prioritised by value
  • Checkout domains covered
  • Pixel owned by your business

Area 6 of 8

Consent and privacy

Tracking must respect your cookie banner and privacy laws, or events go missing in some places and break the rules in others.

What we set up

  • Cookie banner and consent mode
  • Which events need consent
  • Hashing before sending
  • Data processing terms
  • Privacy policy
  • Country rules

What we usually find

  • The Pixel firing before consent
  • The banner blocking everything, including the server side
  • Unhashed data sent
  • Privacy policy not mentioning Meta

What you get

  • Events that follow your banner
  • Data hashed before it leaves your site
  • A privacy policy that covers it
  • Settings checked for each market

Area 7 of 8

CRM and offline events

For lead generation, the most useful event happens later: a qualified lead, a booking, a sale. Sending it back teaches Meta which leads matter.

What we set up

  • Lead IDs from forms and lead ads
  • CRM stages: qualified, booked, won
  • Values for each stage
  • HubSpot, Salesforce or Zoho
  • Offline sales
  • Daily or real-time sending

What we usually find

  • Meta only sees the form submission
  • Lead ad leads never matched to sales
  • CRM data exported by hand
  • No values on leads

What you get

  • CRM stages sent back to Meta
  • Values on qualified and won leads
  • Campaigns that can optimise for quality
  • No manual exports

Area 8 of 8

Testing and monitoring

Tracking that isn’t tested is a guess. And tracking that isn’t watched breaks with the next site change.

What we set up

  • Test purchases and leads
  • Test events tool
  • Desktop, iPhone and Android
  • Meta vs store or CRM
  • Alerts if events stop
  • A two-week check

What we usually find

  • Never tested after setup
  • No one checks Events Manager
  • Site changes break events silently
  • Numbers never compared with the store

What you get

  • Every event tested and recorded
  • Meta compared with your store
  • Alerts when events stop
  • A short checklist for site changes

Why Meta tracking goes wrong

The causes we find most often, what they look like in Events Manager and how we fix them.

  • Purchases counted twice

    The Pixel and the Conversions API both send purchases, without a shared event ID.

    Events Manager

    • Purchases reported800
    • Orders in store412

    One event ID on both, so Meta keeps one, then checked against your orders.

    After our fix

    • Purchases reported412
    • DeduplicatedYes
  • Poor event match quality

    No customer data sent with events, so Meta can’t tell who bought.

    Match quality

    • Purchase4.2
    • Lead3.8

    Hashed email, phone and click IDs sent with each event, with consent.

    After our fix

    • Purchase9.1
    • Lead8.4
  • Pixel only

    No Conversions API, so blocked browsers and iPhone settings hide a share of your sales.

    Purchases seen by Meta

    • Share of orders61%
    • Server eventsNone

    The Conversions API added through your platform, a gateway or server-side Tag Manager.

    After our fix

    • Share of orders96%
    • Server eventsAll key events
  • Broken after a site change

    A theme, checkout or cookie banner update removed events, and nobody noticed.

    Purchase event

    • Per day0
    • Days unnoticed9

    Events rebuilt and tested on the new site, with an alert if purchases stop.

    After our fix

    • Per day18
    • AlertOn
  • No lead quality signal

    Meta only sees form submissions, so it keeps finding cheap leads that never buy.

    Lead quality

    • Qualified leads16%
    • Sent back to MetaNone

    CRM stages sent back, so campaigns can optimise for leads that become customers.

    After 60 days

    • Qualified leads34%
    • Sent back to MetaDaily

Need something more custom?

Not every business fits a plugin. If your setup is unusual, tell us what you need. We’ll get on a call, understand the requirement and send you a written quote. Here are custom Conversions API projects we’ve built for other clients.

  • Custom-built or headless stores

    A store built on its own code, or a headless storefront with a separate checkout, where no plugin works.

    What we built: Purchase and checkout events sent from the backend through the Conversions API, with event IDs matched to the browser side.

    • Next.js
    • Laravel
    • Shopify Hydrogen
  • CRM stages and offline sales

    Leads that turn into sales weeks later, in a CRM or over the phone, that Meta never hears about.

    What we built: Qualified, booked and won stages sent back automatically, with values, matched to the original lead.

    • HubSpot
    • Salesforce
    • Zoho
  • Subscriptions and renewals

    A subscription business where the first order is only the start, so Meta undervalues every customer.

    What we built: Sign-ups with a predicted value, and renewals and cancellations sent from payment webhooks.

    • Stripe
    • Recharge
    • Webhooks
  • Bookings, calls and WhatsApp

    Customers who book through a booking system, call, or message on WhatsApp instead of buying online.

    What we built: Bookings, qualified calls and WhatsApp conversations sent as conversion events, with consent.

    • Booking systems
    • Call tracking
    • WhatsApp
  • In-store and point-of-sale purchases

    Shops where people see the ad online but buy in store, so Meta only sees a fraction of the sales.

    What we built: Point-of-sale purchases matched to customers and sent as offline events every day.

    • POS
    • Loyalty data
    • Daily uploads
  • Several brands, countries or Pixels

    One platform running several brands or countries, each with its own Pixel and ad account.

    What we built: Events routed to the right Pixel by brand or country, with one server setup that is easy to maintain.

    • Multi-brand
    • Multi-country
    • Server-side Tag Manager

Tell us what you need

Describe your setup and what you want Meta to see. A tracking specialist calls you back within 24 hours.

  1. 1A call to understand the requirement
  2. 2A written plan and quote
  3. 3Built, tested and documented
Tell us what you need

Your tracking test report

A report you keep, so anyone on your team, or a future agency, can check the setup and keep it working.

Download a sample report

A real report layout with example data, so you know exactly what you’ll receive.

  1. 01

    Event map 1 page

    Every event, where it comes from, what data it sends and how it is deduplicated.

  2. 02

    Test results 2–3 pages

    Each test purchase and lead, with screenshots from Events Manager.

  3. 03

    Match quality 1 page

    Before and after scores for each event, and what raised them.

  4. 04

    Changes made 1 page

    Everything we added, changed or removed, and why.

  5. 05

    Keeping it working 1 page

    What to check after site changes, and the alerts we set up.

Cover of the sample report Sample · example data

Businesses we’ve set up Meta tracking for

Who they are, why they came to us, what we found and what changed. Pick a business to read its story.

OakenFurniture

Furniture storePixel and Conversions API · 8 days

The company
A Shopify store selling solid wood tables, chairs and storage, with most sales from Meta ads.
Why they came to us
Meta reported far fewer sales than the store, and the team was about to cut a campaign that was actually working.
What we found
  • Pixel only, with no Conversions API
  • Two Pixels on the site
  • No value on most purchases
  • Event match quality of 4.2
What changed
Conversions API on, one Pixel, values on every purchase and match quality above 9. Meta now sees almost every sale, and the campaign stayed on.

Before vs after

  • Purchases Meta sees

    Before 61%
    After 96%

    57% higher

  • Reported return on ad spend

    Before 1.9
    After 3.1

    63% higher

VelvoBeauty

Cosmetics brandDeduplication fix · 5 days

The company
A direct-to-consumer cosmetics brand selling across the Gulf and Europe.
Why they came to us
Meta’s results looked too good to be true: twice as many purchases as orders.
What we found
  • No shared event ID
  • Event names that didn’t match
  • Purchases counted twice for months
  • Budgets raised on false results
What changed
One event ID on both sides and matching names. Meta’s purchases now match the store, and budget decisions are based on real sales.

Before vs after

  • Purchases reported vs orders

    Before +94%
    After +2%

    98% lower

  • Duplicate purchases a month

    Before 1,130
    After 14

    99% lower

TrailmarkOutdoor

Outdoor gear storeTracking rebuild · 1 week

The company
A WooCommerce store selling tents, packs and hiking gear.
Why they came to us
Purchases stopped showing in Meta after a new theme went live, and campaigns kept spending for nine days.
What we found
  • Purchase event removed by the theme
  • Cookie banner blocking the server side too
  • No alert when events stopped
  • Checkout on a payment domain Meta couldn’t see
What changed
Events rebuilt for the new theme, consent set up properly and an alert if purchases stop. Tracking has stayed stable through two more site updates.

Before vs after

  • Purchases a day in Meta

    Before 0
    After 21

    Up from zero

  • Days to notice a break

    Before 9
    After 1

    89% lower

ClearviewEye Clinic

Eye clinicCRM events · 2 weeks

The company
An eye clinic running Meta lead ads for laser eye surgery consultations.
Why they came to us
Leads were cheap, but few booked a consultation, and Meta kept finding more of the same.
What we found
  • Meta only saw the form submission
  • Bookings tracked in HubSpot, never sent back
  • No values on leads
  • Lead form with no qualifying question
What changed
Qualified, booked and treated stages sent back from HubSpot, with values. Campaigns now optimise for bookings, not form fills.

Before vs after

  • Leads that book

    Before 12%
    After 29%

    142% higher

  • Cost per booking

    Before $310
    After $170

    45% lower

SproutKitchen

Meal kit subscriptionsSubscription events · 10 days

The company
A meal kit company selling weekly subscriptions online.
Why they came to us
Meta only saw first orders, never renewals, so it treated every customer as worth one box.
What we found
  • Only the first purchase tracked
  • Subscription renewals never sent
  • No predicted value on sign-ups
  • Match quality of 5.1
What changed
Sign-ups sent with a predicted value and renewals sent from the server. Meta now finds customers who stay longer.

Before vs after

  • Event match quality

    Before 5.1
    After 8.7

    71% higher

  • Customers still subscribed after 3 months

    Before 31%
    After 44%

    42% higher

NorraWatches

Watch brandPixel and Conversions API · 10 days

The company
A watch brand with a custom-built store and a checkout on a separate domain.
Why they came to us
Meta couldn’t see any purchases, because checkout happened on a domain the Pixel didn’t cover.
What we found
  • Purchase event on a domain Meta couldn’t see
  • Domain not verified
  • Pixel owned by a former agency
  • No Conversions API
What changed
Server-side Tag Manager sending purchases from checkout, domain verified and the Pixel moved to the brand’s own business.

Before vs after

  • Purchases Meta sees

    Before 0%
    After 95%

    Up from zero

  • Cost per purchase in Meta

    Before $410
    After $120

    71% lower

What it’s like to work with us

01 / 03

Intella Digital delivered a website that perfectly captured our brand and vision. Their attention to detail, responsiveness, and ability to turn ideas into reality made the entire process smooth and enjoyable.

Andra-Simina Mocanu

CEO & Founder, The Other Glasses

ProjecteCommerce design and build

Meta Pixel and Conversions API questions, answered

Can’t find your answer? Ask us on a free 30-minute call.

Do I need the Conversions API if I already have the Meta Pixel?

Yes, for most businesses. The Pixel runs in the browser and misses conversions because of ad blockers, browser limits and iPhone privacy settings. The Conversions API sends them from your server, and the two together give Meta the most complete picture.

Why is my Facebook Pixel not tracking purchases?

Common causes: the purchase event isn’t on the order confirmation, a theme update removed it, consent settings block it, or checkout happens on another domain. We test and fix each case.

What is event match quality?

A score from 0 to 10 that shows how well Meta can match your events to people. Sending hashed email and phone numbers with events usually raises it.

How does deduplication work?

When the Pixel and the Conversions API send the same event, both include the same event ID. Meta keeps one and discards the duplicate.

Can you set up CAPI on Shopify or WordPress?

Yes. Shopify and WordPress have their own integrations, and for other sites we use server-side Tag Manager or Meta’s gateway.

Is the Conversions API allowed under privacy laws?

Yes, when it respects consent and customer data is hashed before it is sent. We set it up to follow your cookie banner and update your privacy policy where needed.

Let Meta see all of your sales

Give us access to Events Manager. We’ll call you back within 24 hours with what’s missing.

What happens next

  1. 1
    We look at your account first

    Spend, tracking, campaigns and landing pages, before we talk.

  2. 2
    A 30-minute call

    Your goals, your margins and what a good lead is worth.

  3. 3
    A plan and fixed quote

    What we’d fix first, what we’d test, and what it costs.

Prefer to talk? contact@intelladigital.com · +1 (431) 293-2026

Request a free account review

  • Fixed quote, usually within one working day
  • Read-only access is enough
  • Your details stay private
All services