Meta Pixel

Example

A cosmetics shop runs ads with no pixel. The report shows €500 bought 1,250 clicks, and nothing after the click. Once the pixel is in place and the purchase event carries a value, the same €500 comes back as 26 orders worth €2,340. The spend has not changed; what appeared is the number decisions are made on: 2,340 ÷ 500 = €4.68 of revenue per euro spent.

From there you compare campaigns instead of hunches. The one returning 4.68 gets more budget; the one returning 0.9 is switched off.

Why it matters for a business

Without a pixel, an ad is optimised for the click. The system finds people who click, not people who buy. With a pixel it gets feedback from the site and starts looking for profiles that resemble your buyers. The same data makes it possible to show ads again to people who left a basket, and to exclude the ones who already bought.

The pixel also creates an obligation. It records what people do, so it may only run after consent in the cookie banner, and withdrawing that consent has to be as easy as giving it. What happens after the click is judged by the conversion rate, not by the number of events.

What to ask

• Which events are sent, and do they use the standard names Meta recognises?
• Does the purchase event carry a value and a currency, or only the fact that an order happened?
• If the site sends events from the browser and from the server, is each order counted once?
• Does the pixel stay off when consent is declined, and who checks that it does?
• Who owns the dataset — the company or the agency?

Setting the events up and checking them is part of Facebook and Instagram ads, because until they are right the ad report and the till tell different stories.