Skip to main content
Start free

Language

Log in Create my store

Meta Pixel and Conversions API on your store

Paste your Pixel ID and access token: Yalla Souk sends visits, add-to-carts and purchases to Meta, from the browser and from the server, without a line of code.

In Yalla Souk the Meta Pixel is connected in Integrations › Marketing & analytics › Meta Pixel: paste the Pixel ID (digits) and, ideally, the Conversions API access token. The pixel loads on every page of the store, and the key events, including the purchase, are also sent from the server with the same ID so that Meta deduplicates them.

Behaviour checked in the product and Meta documentation read on 22 October 2026.

Meta Pixel in Yalla Souk at a glance

Where to connect it Integrations › Marketing & analytics › Meta Pixel › Configure
What you enter Meta Pixel ID (digits only, for example 123456789012345) and, as a recommended option, the Conversions API access token.
Browser PageView, ViewContent, AddToCart, InitiateCheckout, Contact, Purchase and the custom QualifiedVisit event.
Server (Conversions API) ViewContent, AddToCart, InitiateCheckout, Purchase, and Lead for WhatsApp orders.
Currency sent to Meta TND store: value converted to USD, dinar amount kept alongside. Other currencies: sent as they are.
Cost Included, no fee. Your campaigns stay in your own ad account.

Pixel and Conversions API: why both?

The pixel runs in the customer’s browser: an ad blocker or iOS restrictions can stop it from loading, and the purchase is then never counted. The Conversions API sends the same events from Yalla Souk’s server, whether or not the browser blocked the pixel.

To avoid counting one purchase twice, Meta deduplicates a browser event and a server event when they share the same event name and event ID and arrive within 48 hours. Yalla Souk uses the order ID as the event ID for the purchase, on both the browser and the server side.

How do I install the Meta Pixel on Yalla Souk?

  1. In Meta Events Manager, open your pixel and copy its Pixel ID.
  2. Still in Events Manager, Settings tab, Conversions API section, click Generate access token under “Set up manually”. Meta notes the link only shows for users with developer rights on the business.
  3. In Yalla Souk, open Integrations, Marketing & analytics category, then Configure on Meta Pixel.
  4. Paste the Meta Pixel ID and the token in Conversions API - Access Token, then save.
  5. Visit your store and check that events arrive in Events Manager.

The token is optional: without it, only the browser pixel works. To disconnect, clear the ID in the integration settings.

Which events does Yalla Souk send to Meta?

WhenEventBrowserServer
Every page viewPageViewYesNo
Product page openedViewContentYesYes
Add to cartAddToCartYesYes
Checkout startedInitiateCheckoutYesYes
Click on a contact or order-by-message buttonContactYesNo
Visit of at least 15 seconds with 50% of the page scrolled, once per sessionQualifiedVisit (custom)YesNo
Order placedPurchaseYesYes
Order left through “Order via WhatsApp”LeadNoYes
That WhatsApp order confirmed by youPurchaseNoYes

QualifiedVisit gives Meta a signal of a genuinely interested visitor, useful to optimise a traffic campaign or build an audience while purchases are still rare.

Why do my dinar purchases show in dollars?

The Tunisian dinar is not among the currencies Meta ad accounts accept. So that a TND purchase keeps a usable value in your reports, Yalla Souk sends the value converted to US dollars and adds the original dinar amount in the value_local and currency_local parameters. A store in a currency Meta accepts (euro, dollar…) sends its own currency as is.

In practice: read ROAS in Meta as an order of magnitude, and keep your real dinar figures in Yalla Souk’s reports, which also know about parcels refused on delivery.

Which customer data goes to Meta, and how?

  • For the Conversions API, email, phone, first name, last name, city, country and postal code are hashed with SHA-256 before sending, as Meta requires.
  • The customer’s IP address and browser, and the Meta fbp and fbc cookies, are sent in clear because Meta needs them to match events.
  • The Meta, Google Analytics and Clarity scripts load once the page is displayed, so they do not slow the first paint; conversions are doubled on the server, so this delay loses no purchase.

Frequently asked questions about the Meta Pixel and Yalla Souk

Do I need to code to install the Meta Pixel?

No. Paste the Pixel ID and, if possible, the Conversions API token in Integrations › Marketing & analytics › Meta Pixel. Yalla Souk loads the pixel on every page and sends the events itself.

Is the Conversions API token required?

No, but it is recommended. Without it, purchases by customers who block the pixel are not counted. With it, Yalla Souk also sends events from the server, and Meta removes duplicates using the order ID.

Where do I generate the Conversions API access token?

In Events Manager: pick your pixel, Settings tab, Conversions API section, Generate access token link under Set up manually. Meta only shows the link to users with developer rights.

Why does Meta show my sales in dollars?

The Tunisian dinar is not one of the currencies Meta accepts. Yalla Souk therefore sends the value in dollars and keeps the dinar amount in value_local and currency_local. Your exact figures stay in Yalla Souk’s reports.

Are orders placed through WhatsApp counted as purchases?

Not straight away. An order left through Order via WhatsApp sends a Lead. The Purchase is only sent when you confirm that order, so requests that go nowhere do not inflate your results.

Does the pixel slow my store down?

It loads after the page is displayed, like Google Analytics and Clarity, so it does not weigh on the first paint. Key conversions are also sent from the server, so this deferred loading loses no purchase.