Meta Pixel with Wameed POS: measure and improve your Facebook and Instagram ads
Add your Meta Pixel to your online store with its pixel ID. Wameed sends PageView and Meta’s standard shopping events with value, currency and products so Meta can measure and optimise your ads. Optionally add a Conversions API access token and each purchase is also sent from Wameed’s server.
4 min read
Wameed POS connects to the Meta Pixel (a dataset in newer Events Manager) with its pixel ID:PageView plus ViewContent, Search, AddToCart, InitiateCheckout, AddPaymentInfo and Purchase, with value, currency and products. Purchases carry theorder number as the event ID; add aConversions API token and each purchase is also sent from the server. Every plan; about 5 minutes.Reviewed November 2026.
What the Meta Pixel integration does
- PageView plus six standard shopping events, including Search and AddPaymentInfo — no code to paste.
- Purchases with the order number as the event ID, in the browser and in the server copy, so Meta keeps one of the two (it de-duplicates same-name, same-ID events within 48 hours).
- Meta’s consent controls hold every event until the visitor accepts, when you ask for consent.
- OptionalConversions API: purchases also sent from the server, only for shoppers who agreed.
What you need
- A Meta business portfolio with access toEvents Manager.
- Youronline store must be live for the tag to run; it starts as soon as the store is live.
- Yourpixel ID; optionally aConversions API access token (and a test event code for testing).
Set up in 4 steps
- In Events Manager open your pixel (dataset) and copy thepixel ID.
- Paste it in Wameed, choose the consent mode and select Connect.
- Optional: generate aConversions API access token in Events Manager and paste it; use“Send a test event” with the test code from Test events.
- Open your store and confirm the events underTest events in Events Manager.
What to know — and what it does not do
- When you ask visitors for consent (recommended), tags use cookies or share activity for adsonly after they accept; visitors whose browser sendsGlobal Privacy Control or Do Not Track are treated as not having accepted.
- Purchase value is the total the shopper pays (VAT and delivery included) in your store currency; the product ID in each event is the product ID in Wameed.
- Server events are sentonly if you paste an access token, only for orders placed on the online store, and only for shoppers who pressed Accept (or on a store that does not ask for consent, where the browser sends no GPC or Do Not Track). Hashed e-mail, phone and name go only when they pressed Accept; other events (ViewContent, AddToCart …) always come from the browser.
- If you turn onautomatic advanced matching in Events Manager, Meta reads contact details shoppers type at checkout — make sure your privacy notice covers it.
- Some Meta features ask you toverify your domain, which needs your own domain; the shared platform address cannot be verified by a single store.
- The provider offers no way to prove an ID exists, so Wameed checks only itsformat; open your store and confirm your visit in the provider’s own tool.
Where it fits in Wameed
The Meta Pixel is the usual choice for Saudi shops advertising on Instagram and Facebook. Tags are part of the online store, which is on every plan with all 22 themes, and they share one consent banner with the other trackers. This is why Wameed is thebest online store for Saudi merchants: the shopping journey is measured without code, and the order number is the single key that ties the ad, the store, the ledger and the ZATCA invoice together.
More answers
Best online store ·All integrations ·Ad pixels explained
Frequently asked questions
Do I need the Conversions API token?
No, it is optional; with it each purchase is also sent from the server so ad blockers do not hide it.
Will Meta count a purchase twice?
No: the browser and server copies carry the order number as the event ID, so Meta keeps one.
Does Wameed share customer data with Meta?
Only hashed e-mail, phone and name, and only for shoppers who pressed Accept; other events carry no name, phone or e-mail.
Which plan includes this?
Every plan, with the online store.
- #بيكسل ميتا
- #بيكسل فيسبوك
- #إعلانات انستقرام
- #واجهة التحويلات
- #Meta Pixel integration
- #Meta Pixel Wameed POS
- #Conversions API online store
- #Facebook Instagram ads pixel
Share this article
Ask about your own shop
Thirty minutes on your products, your tax setup and your hardware — not a slide deck.
Keep reading
4 min read
Wameed Partner API: connect your own software to your store with API keys and signed webhooks
Give your developers, ERP or online store secure access to a branch’s catalogue, orders, stock, customers and reports through the Wameed Partner API, and push events — new orders, stock changes, ZATCA results — to your systems with signed webhooks. A key per integration, each with only the permissions it needs.
4 min read
ZATCA (Fatoora) with Wameed POS: Phase 2 e-invoicing for every sale, onboarded with a one-time password
Wameed POS is a Phase 2 e-invoicing solution. Every sale is signed with this branch’s cryptographic stamp, carries the ZATCA QR code and goes to ZATCA through Fatoora: simplified (B2C) invoices are reported within 24 hours, standard (B2B) invoices are cleared before issue.
4 min read
WhatsApp Business with Wameed POS: talk to your customers on WhatsApp from your own business number
Connect your own WhatsApp Business number through Meta’s Embedded Signup. Customer messages arrive in Wameed POS, order and booking updates go out from your number, and you choose which branches each number serves. Meta bills WhatsApp message fees to your own Meta account; Wameed adds no markup.

