Debug Mode

Debug Mode prints a readable trace of the Vendo pixel on your storefront. The trace includes the raw Shopify events and the event properties that Vendo gives to each pixel destination. Use it to confirm that tracking works, or to share evidence with Vendo support when something looks wrong.

How to turn it on

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

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

Your browser keeps the setting in local storage, so Debug Mode stays on when you go to other pages. After the first page load, you do not need to keep the parameter in the URL.

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

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

After you turn on Debug Mode, open the DevTools console in your browser (Cmd+Option+J on Mac, F12 on Windows). The console shows:

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 block gives you a quick summary:

• Pixel Version: the deployed version that runs on your storefront.
• Tracking Mode: client, server, or dual. In dual mode, events go to both the browser SDKs and the Vendo server-side pipeline.
• Active Integrations: the destinations that the pixel forwards events to. server_side_tracking is the Vendo ingest API. Vendo uses it internally to enrich and route events server-side.
• Local Storage Keys: the Vendo-owned storage entries that are in this browser. This helps when you diagnose identity or attribution problems.

2. For every event that fires

Each storefront event produces two types of collapsible row:

▶ [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 the Shopify Web Pixel API emits it. Click the row to expand it and inspect the full payload (context, document information, product or cart data and other fields).
• (destination) Event: the event properties that Vendo gives to that destination. The destination changes them into its own format before it sends them. There is one row for each pixel destination that has this event enabled.

Click any row to expand it and inspect the full object. The objects are interactive. You can open nested fields, copy values and do other tasks in the console.

Show log messages for some destinations only

The vendo_debug_destinations local storage key turns on the Vendo log messages for the destinations that you name. It does not show the header block or the event rows. Those show only when Debug Mode is on.

The value is a comma-separated list of destination keys: mixpanel, onesignal, google_tag_manager, segment or ingest_api.

1. On your storefront, open the DevTools console.
2. Set the key:

localStorage.setItem('vendo_debug_destinations', 'onesignal,mixpanel')

3. Reload the page.

To stop these log messages, remove the key:

localStorage.removeItem('vendo_debug_destinations')

Common uses

• Confirm a new destination is receiving events. Save your destination configuration. Open the store with ?vendo_debug=1 and browse a product. Then check that a (your_destination) Event: Product Viewed row appears in the console. If the destination receives events server-side, look for the (server_side_tracking) row.
• Check which destinations get an event. Each destination row shows that Vendo gave the event to that destination. Expand the row to see the properties that Vendo gave it.
• Share with Vendo support. If something is wrong, turn on Debug Mode and reproduce the problem. Then take a screenshot of the console output or copy the expanded payload. This gives us exactly what we need to diagnose the problem, without reproducing it locally.
• Verify UTM / attribution capture. The Local Storage Keys line shows whether vendo (the attribution blob) is populated. Click through pages with UTM parameters on the URL, then check the line again.

Notes

• Debug Mode affects only your browser. Other shoppers on your store see nothing: no banner and no console logs.
• Debug output is cosmetic. It never changes what Vendo actually tracks or forwards to destinations.
• If you do not see any output, make sure that the Vendo app is installed and that at least one destination is configured. The pixel attaches to the storefront only when the app is connected.