Imagine paying for ads every month while the platform has no idea who bought and who left. What happens? Your ad gets shown to anyone, and the campaign optimises for clicks instead of sales. That is exactly what a missing or broken pixel does. This article walks you through setting it up right the first time.
01The Pixel and the Conversions API: what is the difference?
The Pixel is a small piece of code that runs in the visitor's browser and tells Meta about every step: a page view, an add to cart, a purchase. The Conversions API (CAPI) does the same job, but the events are sent from your own server straight to Meta.
Depends on the visitor's browser
Browser and server both send
Affected by ad blockers and privacy settings
The server still reports when the browser blocks the code
Events get lost without you knowing
A fuller picture of who actually bought
The algorithm learns from incomplete data
The algorithm learns from clearer data
The rule: don't pick one. Install both, and have them send the same event with the same unique ID so Meta counts it once.
02The events you must record
You don't need twenty events. You need the ones that follow the customer from first look to payment, each in its right place:
PageView- Fires when
- Any page of your site opens
- Why it matters
- The base: without it there is no retargeting audience
ViewContent- Fires when
- A product or service page opens
- Why it matters
- Shows which product attracts, and lets you retarget viewers
AddToCart- Fires when
- «Add to cart» is clicked
- Why it matters
- A strong buying signal and a golden audience for reminder ads
InitiateCheckout- Fires when
- The checkout page opens
- Why it matters
- Reveals where people stop between cart and payment
Purchase- Fires when
- The «order confirmed» page shows
- Why it matters
- The key event: sales campaigns optimise on it, and it must carry value and currency
Lead- Fires when
- A contact or booking form is sent
- Why it matters
- For service businesses, instead of Purchase
03The steps, in order
- Create the dataset
In Events Manager inside your Meta business account, create a dataset and link it to your business.
- Install the Pixel
If your store runs on a ready platform, it usually has a direct integration where you paste the Pixel ID. On a custom site, the base code goes in the head of every page.
- Turn on CAPI
Ready platforms usually offer a switch in their settings. A custom site needs the developer to send events from the server with an access token.
- Share one event ID
Every event sent by both browser and server must carry the same event_id, or Meta counts the purchase twice.
- Send value and currency
A Purchase without value and currency is useless for value campaigns. Use your store's currency: SAR, OMR or another.
- Verify your domain
In your business account's security settings, verify your website domain.
04How do you know it works?
Don't trust «connected» alone. Test it yourself:
05Mistakes I see often
- Purchase on the «Pay» button
It must fire after a successful payment, on the thank-you page, not on the click. Otherwise you count unpaid orders.
- Two pixels on one site
One from the developer and one from the platform: every number doubles.
- The thank-you page reloads
The customer refreshes and the purchase is recorded again. Fix: one fixed event_id per order.
- Forgetting CAPI
The Pixel alone loses part of the events to browsers and ad blockers.
06The bottom line
The Pixel is not a technical chore you finish and forget. It is what the algorithm learns your buyers from. Install the Pixel and CAPI together, place the six events correctly, and test with a sample order before you spend a single riyal. If you'd like us to review your setup together, book a free intro call.
I help companies grow through marketing strategies built on results.