Meta Pixel on Vareons for online stores in Egypt
Meta Pixel on Vareons connects your online store to a Meta Pixel so storefront events (such as PageView, AddToCart, and Purchase) are sent to Meta Events Manager without pasting a script on every page.
Last verified: 2026-09-17
Vareons is an e-commerce platform for businesses selling online in Egypt. Meta Pixel is a built-in marketing capability under Tracking & Pixels in the merchant dashboard.
What problem does it solve? Many Egyptian merchants run Facebook and Instagram ads and need measurable storefront signals: page views, add to cart, checkout start, and completed orders. Without a store-connected pixel, conversion data is incomplete or depends on fragile manual script installs.
How does the flow actually work? The merchant opens /dashboard/tracking, clicks Connect on the Meta Pixel card, enters a Pixel ID (15–16 digits), and saves. Vareons upserts a TrackingIntegration document with provider meta. The public storefront loads connected integrations from GET /api/public/tracking and injects Meta’s fbevents.js with fbq('init') and fbq('track','PageView').
Commerce events are also emitted from storefront logic via emitMarketingEvent: product view (ViewContent), AddToCart, InitiateCheckout, and Purchase. On the thank-you page, purchase tracking runs after the order is loaded; an additional Lead event may fire when the customer email is present.
This setup fits fashion, cosmetics, and Meta-ads-led stores in Egypt, and it works alongside common Egyptian checkout methods (such as COD and Paymob) because tracking happens on the storefront, not inside the payment gateway.
Setup steps in Vareons
Open Tracking & Pixels
In the merchant dashboard, open /dashboard/tracking (Tracking & Pixels). Staff need tracking view permission; merchants need the plan to allow the marketing/tracking page.
Select the Meta Pixel card and click Connect
From the tracking providers grid, open the Meta Pixel card. The UI describes it as tracking conversions and optimizing Facebook & Instagram ads.
Enter the Pixel ID from Meta Events Manager
Copy the Pixel ID from Meta Events Manager. It must be a 15- or 16-digit number; the API rejects other formats. Paste it into the Meta Pixel ID field and click Connect.
Optional “Manage via GTM only” checkbox
The connect dialog shows “Manage via GTM only”. The value is stored in settings.viaGTMOnly. Today, storefront script filtering skips direct GA4 injection when viaGTM is set and GTM exists; the Meta card still injects Meta’s script unless you disconnect the integration.
Save and verify on the storefront (not the dashboard)
After a successful connect, status becomes connected and connectedAt is refreshed. Open the public storefront and confirm events in Meta Events Manager (for example PageView, then AddToCart). Scripts load for visitors via /api/public/tracking, not inside the dashboard.
Disconnect when needed
Disconnect opens a confirmation dialog, then deletes that provider’s TrackingIntegration row. After deletion, Meta injection stops on the next public tracking load.
Storefront events sent to Meta
PageViewViewContentAddToCartInitiateCheckoutPurchaseLeadViewItemListSelectItemRemoveFromCartViewCart
Frequently asked questions
Does Vareons support Meta Pixel?
Yes. Merchants connect a Pixel ID from Tracking & Pixels in the dashboard, and the script is injected on the storefront for integrations with status connected.
Where do I enable Meta Pixel in Vareons?
At /dashboard/tracking on the Meta Pixel card: Connect → enter Pixel ID → save.
What Pixel ID format is accepted?
A 15- or 16-digit number only (validated in pages/api/tracking/[provider].js). Any other format is rejected with an error message.
Which events does a Vareons storefront send to Meta?
PageView from the injected script and navigation handling, plus commerce events via emitMarketingEvent such as ViewContent, AddToCart, InitiateCheckout, and Purchase, and custom events such as ViewItemList, SelectItem, RemoveFromCart, and ViewCart. On the thank-you page, Lead may fire when customer email is present.
Does Meta Pixel change orders or inventory?
No. Connecting stores tracking settings and injects storefront scripts only. It does not create orders or change inventory.
Does Vareons include Meta Conversions API (server-side) tracking?
From the current codebase: Meta storefront tracking uses browser fbq (client-side script). Server-side Meta Conversions API purchase sending was not verified.
Why do Egyptian stores running Facebook ads need Meta Pixel?
Because Facebook and Instagram ads rely on storefront events to measure conversions and optimize campaigns. Vareons provides dashboard connection plus event emission from catalog, cart/checkout, and thank-you flows.
Troubleshooting
If events do not appear in Meta: 1) Confirm the integration status is connected and the Pixel ID is saved (15–16 digits). 2) Test the public storefront, not dashboard pages. 3) Disable browser tracking blockers during the test. 4) After connecting, reload the storefront so TenantTrackingProvider refetches /api/public/tracking. 5) For thank-you Lead: it fires only when the order includes a customer email.
Important limitations
• Meta tracking here is client-side (fbq), not Meta Conversions API from the server. • “Manage via GTM only” is stored for Meta, but current skip logic primarily targets direct GA4 injection when GTM is present. • Consent Mode in the connect dialog is available for GA4, not for the Meta card. • The current UI does not expose a loadOnStorefront toggle; connect defaults to loading on the storefront. • Disconnect permanently deletes that provider’s database row.