CODlino Pixel Tracking with Meta and TikTok
CODlino Pixel connects your WooCommerce store to your own Meta and TikTok data sources. It supports standard WooCommerce checkout and optional CODlino COD Order Forms . This is an independent plugin by Taha Belmezrar, the developer of CODlino COD Order Forms. It is not affiliated with, endorsed by,
About this tool.
CODlino Pixel connects your WooCommerce store to your own Meta and TikTok data sources. It supports standard WooCommerce checkout and optional CODlino COD Order Forms .
This is an independent plugin by Taha Belmezrar, the developer of CODlino COD Order Forms. It is not affiliated with, endorsed by, or an official product of Meta or TikTok. Those names identify the third-party services it integrates with.
- Up to 10 unique Meta Pixel IDs with separate tokens and test codes.
- Direct Meta Conversions API Purchase delivery, without an intermediary service.
- One TikTok browser Pixel; TikTok Events API is not included.
- Browser events: PageView, ViewContent, InitiateCheckout and Purchase.
- Shared Meta event IDs for browser/server deduplication.
- Independent server jobs, transient-failure retries and per-Pixel delivery status.
- Arabic, French and English dashboard with per-user language preferences.
- Responsive, RTL-aware interface and locally bundled Arabic fonts.
- WooCommerce order CRUD APIs and HPOS compatibility declaration.
Tracking is disabled by default. Marketing consent is required by default; connect your existing cookie banner before enabling tracking. No cookie banner is included.
For COD, Purchase means an accepted order, not delivery or payment. Product IDs use variation IDs; values come from order totals. No AddToCart or historical tracking.
External services and privacy
External services are optional and must be configured by the merchant. Installing or activating this plugin alone does not initialize tracking. A test button sends synthetic data only after an administrator requests it.
Meta Pixel and Conversions API
Purpose: advertising measurement and conversion reporting in the merchant’s Meta account. When: browser tracking runs when configured, enabled and consented (unless immediate tracking is configured). Server Purchase events are queued after consented orders and delivered asynchronously when CAPI is enabled. A saved Test Event Code routes events to Meta’s test mode. Connections: connect.facebook.net/en_US/fbevents.js, Meta’s SDK endpoints, and graph.facebook.com/{version}/{pixel-id}/events. The API version is configurable. Data: browser requests expose IP address, user agent, page information and event data to Meta. Server Purchase data includes time, event ID, order ID, currency, total, product IDs/quantities, customer IP/user agent and fbp/fbc cookies when available. Email, phone and billing country are normalized and SHA-256 hashed for matching where available. Hashing is not anonymization. Moroccan local mobile numbers are normalized to 212; ambiguous local numbers outside Morocco are omitted. Server events use the store home URL, not the secret confirmation URL. Service: https://developers.facebook.com/docs/marketing-api/conversions-api/ Terms: https://www.facebook.com/legal/technology_terms Privacy: https://www.facebook.com/privacy/policy/
