Debug Mode

Debug Mode prints a readable trace of everything the Vendo pixel does on your storefront — including the raw Shopify events and the transformed payloads sent to each connected destination. It’s the fastest way to confirm that tracking is working correctly, or to share evidence with Vendo support when something looks off.

How to turn it on

Append ?vendo_debug=1 to any storefront URL in your browser:


https://your-store.myshopify.com/?vendo_debug=1

That’s it. The setting is stored in your browser’s local storage, so it stays on as you navigate between pages — no need to keep the parameter in the URL after the first load.

A small green Vendo Debug Mode ON banner appears in the bottom-right corner of the page so you always know when debug is active.

How to turn it off

Visit any page with ?vendo_debug=0:


https://your-store.myshopify.com/?vendo_debug=0

The banner disappears and the console returns to its normal (quiet) state.

What you’ll see in the console

Open your browser’s DevTools console (Cmd+Option+J on Mac, F12 on Windows) after enabling debug. You’ll see:

1. A header block on page load


═════════════════════════ Vendo Pixel ═════════════════════════
 Debugger Status:     On
 Pixel Version:       1.3.0 (2026-04-22T02-07-11)
 Tracking Mode:       dual
 Active Integrations: server_side_tracking, mixpanel, onesignal
 Local Storage Keys:  vendo, vendo_identity, vendo_debug
════════════════════════════════════════════════════════════════

This tells you at a glance:

Pixel Version — the deployed version running on your storefront.
Tracking Mode — client, server, or dual. Dual means events go to both the browser SDKs and Vendo’s server-side pipeline.
Active Integrations — which destinations the pixel is forwarding events to. server_side_tracking is the Vendo ingest API (what Vendo uses internally to enrich and route events server-side).
Local Storage Keys — which Vendo-owned storage entries are present in this browser. Useful when diagnosing identity or attribution issues.

2. For every event that fires

Each storefront event produces two collapsible rows:


▶ [Vendo] Shopify Event: product_viewed
▶ [Vendo] (mixpanel) Event: product_viewed
▶ [Vendo] (onesignal) Event: product_viewed
▶ [Vendo] (server_side_tracking) Event: product_viewed

Shopify Event — the raw event as Shopify’s Web Pixel API emits it. Click to expand and inspect the full payload (context, document info, product/cart data, etc.).
(destination) Event — the transformed payload Vendo is actually sending to that destination. One row per connected destination.

Click any row to expand and inspect the full object. The objects are interactive — you can drill into nested fields, copy values, etc.

Common uses

Confirm a new destination is receiving events. Save your destination config, hit the store with ?vendo_debug=1, browse a product, and check that a (your_destination) Event: product_viewed row appears in the console.
Compare payloads across destinations. If an event looks different in Mixpanel vs. OneSignal, expand both rows side-by-side to see exactly what Vendo sent to each.
Share with Vendo support. If something is off, enable debug, reproduce the issue, then screenshot the console output or copy the expanded payload. This gives us exactly what we need to diagnose without having to reproduce locally.
Verify UTM / attribution capture. The Local Storage Keys line shows whether vendo (attribution blob) is populated. Click around with UTM parameters on the URL and re-check.

Notes

Debug Mode only affects your browser. Other shoppers on your store see nothing — no banner, no console logs.
Debug output is cosmetic. It never changes what Vendo actually tracks or forwards to destinations.
If you don’t see any output, double-check that the Vendo app is installed and at least one destination is configured. The pixel only attaches to the storefront when the app is connected.