The Facebook Pixel is a short piece of JavaScript you put on your website so Meta can see what people do after they click your ad. It’s free, it takes an afternoon, and without it your ad account is guessing. Meta renamed it the Meta Pixel a while back, but almost everyone still calls it the Facebook Pixel, and both names point at the same snippet of code.
If you deliver your own orders, the pixel does something more specific than it does for a normal online store. It can tell you which ads produced orders that went out on a van and which ones produced orders that got collected at the counter. Those are different businesses with different margins, and Meta gives you a parameter to keep them apart. That’s the part most setup guides skip.
This page covers what the pixel is, what it records, and what it’s worth once delivery is part of the purchase. When you’re ready to put it on your site, the walkthrough lives in our guide to setting up a Facebook Pixel step by step: Events Manager, base code, events, testing, the lot.
Metrobi drivers are rated 4.97/5
Trusted by local businesses for:
- Background-checked professionals
- Specialized in business deliveries
- Same drivers for consistency
- 4.97/5 average delivery rating
The Bottom Line
- The Facebook Pixel is a tracking script that reports website actions back to Meta Ads Manager, so you can measure conversions instead of clicks.
- For a business that delivers, the useful extra is
delivery_category, a parameter with three values (home_delivery,curbsideandin_store) that tags each purchase with how the customer received it. - Tag your orders that way and you can finally answer the question that matters: which ads are buying delivery revenue, not just revenue.
- A browser-only pixel loses a large share of events in 2026 to ad blockers, iOS opt-outs and cookie refusals. Pairing it with the Conversions API is now standard practice, not an advanced move.
- Install the pixel before your first ad, not after. It only learns forward, so it can tell you nothing about last month’s traffic.
What a Facebook Pixel actually is
Strip away the marketing language and it’s two things: a tiny 1×1 image and a JavaScript snippet that sits in the <head> of your website. When someone loads a page, the snippet runs and sends a small message to Meta saying what happened: a page was viewed, an item was added to a cart, an order was placed.
Meta matches that message against Facebook and Instagram accounts. If the visitor who bought your $85 flower arrangement clicked one of your ads three days earlier, Meta connects the two and reports it as a conversion in Ads Manager.
That matching is the whole value. Your website analytics can tell you an order happened. Only the pixel can tell Meta which ad caused it, and Meta’s bidding algorithm needs that feedback to find more people like the buyer.
The pixel sets its cookies (_fbp and _fbc) as first-party cookies, because the script runs on your own domain. That’s why it still functions in browsers like Safari and Firefox that block third-party trackers outright. As we’ll get to, “still functions” is doing some work in that sentence.
What the Facebook Pixel tracks on a delivery order
Out of the box the pixel fires one event: PageView. Everything else you configure. Meta provides 17 standard events, and a delivery business realistically uses five or six of them.
- ViewContent — someone looked at a product, a menu item, or a bouquet.
- AddToCart — an item went in the basket.
- InitiateCheckout — they started the order form. For local delivery this is often where the address entry happens, which makes it the step where out-of-zone customers drop out.
- Purchase — the order was paid for. This is the one that needs
valueandcurrencyattached, so Meta can bid toward revenue rather than order count. - Lead — a quote request or catering enquiry, which matters more than checkout for wholesale and event work.
Each event can carry parameters that describe the action: value, currency, content_ids, and the delivery parameter we’re about to get into. Events without parameters still count, but they give Meta far less to optimize against. A Purchase with no value attached tells the algorithm that a $12 cookie order and a $900 catering order are the same thing.
The delivery_category parameter: separating home delivery from pickup
Here’s the piece that makes the Facebook Pixel for local delivery different from a standard e-commerce install.
Meta supports a predefined parameter called delivery_category on purchase events. It accepts three values: curbside, in_store, and home_delivery. You set it on every purchase event based on what the customer chose at checkout.
fbq('track', 'Purchase', {
value: 115.00,
currency: 'USD',
contents: [{ id: 'SKU-4410', quantity: 1 }],
content_type: 'product',
delivery_category: 'home_delivery'
});Two things become possible once that’s in place.
Measuring each fulfilment method separately is the first. Meta’s own documentation describes this as the point of the parameter: measuring purchases made using each delivery method. So when Ads Manager shows you a campaign returned $4,200, you can see how much of that went out for delivery versus how much was collected. If your delivery orders carry a $9 route cost and your pickup orders carry none, that split changes which campaign is actually profitable.
Building audiences from it is the second. Meta lets you create a Custom Audience from purchase events filtered by a specific delivery_category value. Customers who chose home delivery once are a different retargeting group from customers who walked in. One group you remind about your delivery window; the other you probably shouldn’t pay to reach with a delivery ad at all.
This is the most under-used parameter in local advertising, largely because the big setup guides are written for stores that ship by carrier, where every order is the same shape.
Why the pixel matters more when you deliver than when you ship
A business that hands orders to a national carrier has one fulfilment cost curve and a national customer base. A business that runs its own routes has neither.
Your delivery zone has a hard edge. Someone eleven miles out is a customer you cannot profitably serve, and every dollar you spend reaching them is wasted. The pixel is what tells you this is happening: you’ll see healthy InitiateCheckout numbers and a Purchase count that doesn’t follow, which is people entering an address and discovering they’re out of range.
Your costs also vary by order in a way a shipping business’s don’t. Two orders of identical value can cost very different amounts to fulfil depending on where they sit on the route. Tagging purchases by delivery method is the first step toward feeding that reality back into ad spend instead of optimizing blind toward gross revenue.
The payoff shows up in the numbers: accounts running the Conversions API alongside the pixel report roughly 18–20% higher return on ad spend than accounts relying on browser tracking alone, according to conversion-tracking analyses published in 2026. That gap comes almost entirely from Meta having better data about who converted.
Facebook Pixel custom audiences built from delivery behaviour
Once events are flowing, the audience-building gets specific. A few that work well for local operations:
- Delivery buyers, last 90 days. Purchase events with
delivery_category: home_delivery. Your reorder list. - Checkout abandoners inside your zone.
InitiateCheckoutwithoutPurchase. Give them a small budget and a reminder of your cutoff time. - Repeat browsers who never ordered. Multiple
ViewContentevents, no purchase. Usually a pricing or minimum-order objection. - Exclusion list. Everyone who bought in the last 14 days, removed from acquisition campaigns so you stop paying to advertise to people who already ordered.
Lookalike audiences work off the same data. A lookalike built from your delivery purchasers beats one built from all site visitors, because it’s modelled on people who accepted your delivery fee and your time window.
The Facebook Pixel vs the Conversions API
These are not competing options and you should stop thinking of them that way. The pixel reports from the browser; the Conversions API reports from your server. Meta’s guidance is to run both and deduplicate them.
| Facebook Pixel | Conversions API | |
|---|---|---|
| Where it runs | Visitor’s browser | Your server |
| Blocked by ad blockers | Yes | No |
| Affected by iOS tracking opt-out | Yes | Much less |
| Needs cookie consent | Yes | Yes |
Captures browser signals (_fbp, _fbc) | Yes | Only if passed through |
| Setup difficulty | Low | Medium to high |
The reason for running both is that each catches what the other misses. The pixel collects browser context that improves matching; the server-side copy gets through when the browser copy is blocked. You prevent double-counting by sending the same event_id on both copies of the same event, which Meta uses to recognise them as one action.
Event Match Quality, a 0–10 score in Events Manager, tells you how well this is working. Six or above is considered a healthy score; eight to ten means you’re sending rich customer data. It refreshes on a rolling 48-hour window, so you can change something and see the effect within two days.
What the pixel misses in 2026
Be realistic about the gaps, because the marketing copy around pixels rarely is.
Browser-only tracking now loses a meaningful share of conversions. Industry estimates for 2026 put iOS tracking opt-outs somewhere around 75–85% of iOS users, and desktop ad-blocker use at 30–40%. Add visitors who decline cookie consent and you’re looking at a browser pixel that sees a fraction of reality on some traffic mixes.
There’s also a compliance layer you can’t skip. The Meta Pixel sets marketing cookies, and in jurisdictions covered by GDPR those need explicit consent before the script runs. A correct 2026 implementation gates both the browser pixel and the server-side calls behind that consent, and updates mid-session if someone changes their mind. If you sell into the EU or UK, treat the consent banner as part of the pixel install rather than a separate project.
None of this makes the pixel pointless. It makes a pixel-only setup incomplete.
Is the Facebook Pixel still worth setting up?
Yes, and the reasoning is short.
Without it, Meta optimizes toward clicks and link taps, which correlate poorly with orders. With it, Meta optimizes toward purchases, and its bidding model is good at finding more of whoever is already buying from you. That’s the single biggest lever available in a small ad account, and it costs nothing but setup time.
One caveat: the pixel has no memory of the past. It starts collecting the day you install it. If you’re planning to advertise in November, the pixel should go on in September, so the audiences have something in them when you need them.
Frequently asked questions
Is the Facebook Pixel the same as the Meta Pixel? Yes. Meta renamed it, the code and the function are unchanged, and fbq is still the function name in the snippet. The two terms are interchangeable.
Do I need a pixel if I’m not running ads yet? Install it early anyway. The pixel builds your website audiences from day one, and those audiences take weeks to reach a useful size. Installing it the week before your first campaign means launching with nothing to retarget.
Can one pixel cover more than one website? One pixel can cover every page of one site, which is the normal setup. You can technically use a single pixel across multiple domains, but if the businesses are separate, separate pixels keep the data readable.
Does the pixel slow my site down? Marginally. It loads asynchronously, so it doesn’t block your page from rendering. The bigger performance risk is installing it several times over through different plugins, which also inflates your event counts.
What’s the difference between a standard event and a custom conversion? A standard event is one of Meta’s 17 named events that you fire from your code. A custom conversion is a rule you define in Events Manager, usually based on a URL, without touching your site. Custom conversions are quicker to create; standard events carry richer parameters, including delivery_category.
Sources: Meta for Developers: Meta Pixel documentation, Meta Business Help Centre: Specifying Delivery Methods With Facebook Pixel Parameters, Meta Pixel Standard Events reference, 2026, Conversions API Event Match Quality in 2026, AdBeacon, Improve Facebook Ads Conversion Tracking, Cometly.
