Meta · Pixel
Meta Pixel setup with the purchase value it should be reporting
A pixel can fire on every page and still count the wrong things. Installed on every page, firing on every load, and still reporting purchases that never happened or missing the ones that did. We set the standard event set up properly.
Meta Pixel setup at a glance
- Service
- Standard events, correct purchase value, no second pixel on the page
- Price
- from $150, quoted before any work starts
- Covers
- Standard event set, purchase value and currency, deduplication, verification
- Platforms
- Shopify, WooCommerce, Google Tag Manager
- You get
- Events verified in Events Manager and reconciled against your orders
- Next step
- Conversions API when you want the events the browser cannot send
When a pixel is installed but not working
The pixel is the easiest thing to install and one of the easiest to get wrong.
What the Meta Pixel work covers
How it runs
What a Meta Pixel setup costs
- 01
Access
Meta Business Manager, store admin, GTM where it is used.
- 02
Audit
We map every pixel and event currently firing on a real purchase journey.
- 03
Fix
Duplicates removed, standard events and parameters put right.
- 04
Verify
Reconciled against real orders in Events Manager, then handed over.
FAQ
Meta Pixel and Facebook pixel questions
Why is my Meta pixel not tracking purchases?
Usually it fires on the wrong surface. Checkout often renders in a context the page-level pixel never reaches, so page views look healthy while purchases do not arrive. The report shows an installed pixel either way.
Why does Meta report more purchases than my store?
Two pixels on the page, the same event sent by both an app and a container, or a thank-you page a visitor can reload. All three count a sale more than once, and they are fixed in different places.
What are the standard Meta events?
The set Meta defines for a store, from content views through add to cart and checkout to purchase. We implement that set rather than custom event names, because the ad platform optimises against the standard ones.
Is the purchase value supposed to include tax and shipping?
It should match the figure you are actually willing to count as revenue, and it should match it consistently across platforms. Most reporting gaps we see are a value sent one way to Meta and another way to Google Ads.
Do I need the Conversions API as well?
Not to fix a pixel. You need it when you want the conversions the browser cannot report, and the two then have to be deduplicated by event ID. That work is scoped separately so you do not pay for it before you need it.
Can you fix a pixel installed by a previous agency?
Most of this work is exactly that. We read what is there, remove what duplicates, and leave one implementation you can point at when a number looks wrong.
How do you check it afterwards?
Events Manager tells you the event arrived. Your order records tell you whether the right number of events arrived with the right values, and that is the comparison we hand over.
The pixel is one of five platforms
The full system joins Google, Meta, TikTok, Pinterest and Microsoft spend to revenue in your own BigQuery, with validated tracking underneath and a standard dashboard set on top.
Describe what your pixel is reporting
Send the symptom, the platform and a screenshot if you have one. We come back with what we think is happening, what it would take to fix, and a fixed price, before any work starts.