Skip to main content

We integrated Conversion Tracker and placed a test order, but cannot see the data

Troubleshooting Conversion Tracker: No Sales Data​

If you’ve placed a test order but cannot see the sales data under the show’s Stats page in the workspace, here’s a checklist to help identify and resolve potential issues. You’ll need to use your browser DevTools for the steps below.

How to Open the DevTools​

  • Chrome/Edge: Right-click on the page, select Inspect, and navigate to the Console or Network tab.
  • Firefox: Right-click on the page, select Inspect Element, and open the Console or Network tab.
  • Safari: Enable Develop Mode in Preferences, then use Develop > Show Web Inspector.

Checklist for Troubleshooting​

1. Testing with a "Test Show"​

Cause:
If the test order was placed under a show marked as a "test show" in Bambuser, sales data might not sync with the Stats page.

Solution:
Create a new show and ensure it is not marked as a "test show." Then, place a test order through this non-test show to verify that the Conversion Tracker is working as expected.

2. Incorrect Tracking Library URL Based on Server Location​

Cause:
The tracking library URL varies depending on the server location for your Bambuser workspace. Using the wrong URL may cause the library to fail to load.

Solution:

  • If you log in to your Bambuser workspace via https://lcx.bambuser.com/, use the Global servers URL:
    https://cdn.liveshopping.bambuser.com/metrics/bambuser.min.js
  • If you log in to your Bambuser workspace via https://lcx-eu.bambuser.com/, use the European servers URL:
    https://cdn.liveshopping.bambuser.com/metrics/bambuser-eu.min.js

Confirm with your developer that the correct tracking library URL is implemented based on your workspace’s server location.

3. CSV Export Delay​

Cause:
The show Stats data, including conversion details, may take time to populate fully. Bambuser's systems require some time to process and sync this data.

Solution:
Wait for a few minutes and try exporting the CSV again. Note that this delay is usually short, but larger datasets or server delays could increase processing time.

4. Ensure the Bambuser Tracking Library Is Loaded​

Cause:
The Bambuser Tracking Library might not be correctly loaded on the order confirmation page.

Solution:
Check the Network tab in DevTools and confirm that the following script is loaded before your purchase script or GTM tag is fired:
https://cdn.liveshopping.bambuser.com/metrics/bambuser.min.js

img

5. Verify Necessary Cookies Are Set​

Cause:
The player sets first-party cookies required for tracking. If these cookies are missing, sales data won’t appear.

Solution:

  • Ensure the necessary cookies are present in your browser.
  • If cookies are missing, you must watch a LiveShopping show in the same browser session. This will automatically set the required cookies.

img

6. Check Network Calls for Metrics​

Cause:
The Conversion Tracker may not be sending the correct metrics data to Bambuser’s servers.

Solution:
When completing the purchase, monitor the Network tab and look for a call to:
https://cl.liveshopping.bambuser.com/metric

  • Ensure the request has a 200 status.
  • Verify that the payload contains the necessary purchase data, including order ID and revenue.

img

7. Tracking Library Loaded After Purchase Event​

Cause:
If the Bambuser Tracking Library is loaded after the purchase event has been triggered, it will fail to track the order.

Solution:
Confirm the correct order of execution. The tracking library must be loaded before the purchase script or GTM tag is fired.

8. Blocking of Tracking URL by CSP Headers​

Cause:
Content Security Policy (CSP) headers on your website may block Bambuser’s tracking URL, preventing the metric calls from being sent.

Solution:
Check the Console tab in DevTools for CSP-related errors. If you see errors indicating that https://cl.liveshopping.bambuser.com or related URLs are blocked, update your CSP rules to allow these URLs.

Ensure the following domains are whitelisted in your CSP policy:

  • https://cdn.liveshopping.bambuser.com
  • https://cl.liveshopping.bambuser.com

9. Review Console Errors​

Cause:
Script execution errors can prevent the Conversion Tracker from functioning properly.

Solution:
Open the Console tab in DevTools and check for errors. Resolve any issues related to missing resources or incorrect script configuration.