How do you measure Facebook and Instagram ads with the Meta Pixel?
The Meta Pixel is an ID you paste into your store so Facebook and Instagram know what visitors from your ads do. Woven installs it per store and additionally sends purchases from its server through the Conversions API, so you don't lose conversions the browser blocks.
Updated
What the Pixel measures
It reports the moments that matter in your store to Meta: viewing a product page, adding to cart, and purchasing. That last one is what finally lets you say which ad produced orders, not just clicks.
Without a Pixel you fly blind: Meta optimises toward clicks, because clicks are all you gave it. With the Pixel, it optimises toward buyers.
Why add the Conversions API
The classic Pixel fires from the visitor's browser: an ad blocker, a privacy setting or a strict browser is enough to make it vanish. The Conversions API sends the same purchase from the server, where nothing can intercept it.
| Criterion | Browser Pixel | Conversions API (server) |
|---|---|---|
| Where the event fires from | The visitor's browser | Woven's server |
| Blocked by an ad blocker | Yes | No |
| What you configure | The Pixel ID | The ID plus an access token |
| Duplicate purchases | — | Avoided: the purchase carries the order ID |
Both channels send the same purchase with the same order ID, and Meta recognises it as one sale. So you don't have to choose: browser alone works, browser plus server works better.
Install the Pixel on your store
- Create the Pixel in Meta's Events ManagerFrom your Meta business account. You come out with a numeric ID — that's all Woven needs to get going.
- Paste the ID into the Marketing sectionIn your seller dashboard, Marketing section, store by store. Each store has its own Pixel: your numbers never mix.
- Add the Conversions API tokenOptional but recommended. Generate it in the Events Manager and paste it in the same place. Without a token the browser Pixel keeps working normally.
- Place a test orderOpen a product page, add to cart, complete the order, and watch the events land in Meta's manager.
- Run the ad optimising for purchaseOnce purchases are flowing, pick purchase as the optimisation goal instead of clicks or views.
Check that it works
- In the Events Manager, the test purchase should appear with the right value in dinars.
- If you added the token, the purchase should show as received from both channels, without duplication.
- Redo the test after every Pixel change: a mistyped ID never warns you.
What the Pixel doesn't replace
The Pixel tells Meta about your advertising; it doesn't tell you about your store. Your own statistics — views, add-to-carts, purchases, conversion rate — remain the measure of what happens on your side, including for visitors who came from no ad at all. Watch both, not one.
The detail of what the platform collects is available in the privacy policy.
Frequently asked questions
Do I need one Pixel per store or a single one for everything?
One per store. The Pixel is configured at store level, which keeps each brand's numbers separate. If you run several stores, each has its own ID and its own audiences.
Does the Pixel work without the Conversions API?
Yes. If you enter only the ID, browser tracking works fully. The API token adds server-side sending of purchases, which recovers conversions lost in the browser — a gain, not a requirement.
Does Meta see my customers' data?
Meta receives the events you choose to send by installing a Pixel — views, add-to-carts, purchases and their value. Nothing is sent until you configure your ID, and informing your visitors about that measurement is up to you.
Why does Meta show fewer sales than my store?
Because Meta only counts what it can attribute to an ad, and browser events are sometimes blocked. Your store statistics count every order. The Conversions API narrows the gap but doesn't close it.