Access Bambuser Analytics Data

Integrate Bambuser analytics data with your current analytics system

As a client of Bambuser Live Video Shopping, you may want to integrate LiveShopping player analytics data within your current analytic system. Bambuser provides you different ways to access and use the LiveShopping player analytic data.

There are four ways to access the client-side analytic data:

1. Listen to Player Events

Bambuser LiveShopping player emits different types of player events as well as user-interaction events.


To see a full list of player events and user interaction events, read Player Metrics‍.

You can listen to a 'bambuser-liveshop-tracking-point' to get all emitted events.


window.addEventListener('bambuser-liveshop-tracking-point', ({detail}) => {
  console.log(detail.event); // e.g. "on-load"

Now if you open a Bambuser LiveShopping player, you should see the event data on the console.

2. Pick up event data from dataLayer

If you use Google Tag Manager and have the dataLayer object available on the page have the player embedded, all emitted player, user interactions (learn more on Player Metrics‍), and purchase events (learn more on Purchase Tracking‍) are pushed to the dataLayer object.


  • dataLayer object is available
    Make sure that you have the GTM container code included in the landing page that you have the Player embedded in.

    Analytics tools such as Google Analytics, Abobe Analytics, Tealium, etc. that use the dataLayer object are able to pick up Bambuser events from there.

  • Bambuser tracking library
    You should add the following script-tag in the pages you have the LiveShopping player embedded.

    <script src=""></script>
    It adds more tracking features such as pushing player metric events to the dataLayer. This library has a very small size of 4kB which does not affect your website performance.

3. Export CSV

You can export all stats in CSV format. Then you are able to import that to your analytic system. Note that importing this CSV file may need some configuration or development effort.

4. REST API coming soon

Was this article helpful?