Server-Side Tracking for Meta Pixel and Conversions API screenshots

Real screenshots from our CS-Cart and Multi-Vendor test stores with the add-on installed and the English interface.

Debug view (illustration of the real data, overlay drawn for the screenshot): Product page with the console overlay: PageView, ViewContent and AddToCart with their event IDs and custom data.

Settings, General: pixel ID, Conversions API access token, test event code, Graph API version.

Events tab: browser and server events, content ID source, currency and purchase value.

Advanced matching tab: hashed customer fields, IP address and first-party _fbp/_fbc cookies.

Consent tab: consent handling, CS-Cart cookie dialog, Limited Data Use, current behavior and detected consent source.

Meta events log: events with event ID, pixel, test code, customer data keys, status (Sent, HTTP 200) and the payload.

Debug view (illustration of the real data, overlay drawn for the screenshot): Product page with the console overlay listing PageView, ViewContent and AddToCart.

Server events tab: delivery mode, log retention, queue status, last 24 hours counters and the cron command.

Catalog feed tab: feed key, currency, brand, description, out-of-stock products and the CSV / XML feed URLs.

The catalog feed in XML in the browser: id, title, description, availability, price and sale_price, link, images, brand, product_type, mpn.

Status block after “Send a test event”: browser pixel and Conversions API ready, test mode, and the “Meta accepted the test event” notice.

Status block warning that the core Facebook Pixel add-on is also active and would count PageView and other events twice.

Multi-Vendor vendor panel, profile Add-ons tab: the vendor’s Meta Pixel block (pixel ID, token, test code, Save pixel settings, own catalog feed URL).

Admin, Downloaded add-ons filtered to Kavio Labs, with Server-Side Tracking for Meta Pixel and Conversions API highlighted and active (version 1.0.3).