Welcome to Bambuser Knowledge Base. Whether you're seeking information, looking for solutions, or simply exploring, we're here to assist you every step of the way.

Live
Video Consultation
Shoppable Video
Chat

Reports

Overview

The Data Report feature in Bam Hub allows users to generate detailed reports on video player sessions and purchase activities. These reports are available in CSV or JSON formats, making them easy to download and integrate into your own business intelligence (BI) systems or analytics tools. By analyzing these reports, merchants can gain a deeper understanding of how users engage with video content and how video-driven interactions contribute to conversions. Leveraging these reports enables you to better understand how Bambuser products impact your customer journey and make more informed decisions for future campaigns.

 

Availability and Access Requirements

The Data Report feature is available for the Social Commerce products Live and Shoppable Video. To access this feature, you need "Stats" or "Statistics" permissions enabled for the Live and/or Shoppable Video product.

 

Why Download These Reports?

Advanced Data Analysis 

Import the reports into your own BI system for further analysis and to create custom dashboards. This allows you to combine Bambuser data with other business metrics, helping you make data-driven decisions.

 

Customer Journey Mapping and Segmentation 

Use session reports to track user interactions and follow their engagement with video content all the way through to a purchase. Additionally, use geolocation and user data to segment your audience and tailor content or marketing strategies based on user demographics and behavior.

 

Custom Tracking Tags 

To gain even more granular insights into customer behavior, you can send in your own tracking tags when loading Bambuser products on your site. These custom tags will appear in the session reports, allowing you to link specific user actions to Bambuser interactions. Read more about setting up custom tracking tags here.

 

 

Available Reports

Player Sessions Report

This report provides a detailed view of how users interact with your video content. It includes data such as when sessions started and ended, the devices and platforms viewers used, the duration of their engagement, and their geographical location. The Player Sessions Report captures all interactions related to video views, whether they occur during a live broadcast or through on-demand replays.

 

Data shown in the Player session report:

 

Field

Description

org_id

The ID of the Bam Hub that published the video viewed during the session.

video_id

The ID of the Live show or Shoppable video that was viewed during the session.

user_id

The Bambuser generated ID of the user who viewed the video during the session.

player_session_key

The Bambuser generated unique identifier for the player session.

user_agent

Information about the device and browser version used to view the video.

source_app

The type of player in which the video was viewed. 
- player-web = Bambuser player for Live
- vod-player-web = Shoppable video full size player 
- vod-player-web-components = Shoppable video preview player.

started_at

The timestamp (with timezone) indicating when the video view started.

ended_at

The timestamp (with timezone) indicating when the video view ended.

view_duration_s

The total number of seconds the video was watched.

video_content_duration_s

The duration of the video content in seconds.

is_test_show

Indicates whether a Live show is a test show (true or false).

is_live

Indicates whether the video was broadcast live (true or false).

is_view

Indicates whether the session qualifies as a "view" (sessions longer than 3 seconds are counted).

viewing_segments_json

A JSON containing start and end times for each segment of the video that was viewed.

interactions_json

A JSON capturing viewer interactions within the player during the session, including timestamps.

geolocation_json

A JSON containing the viewer's timezone, postal code, country, and city.

customer_tags_json

A JSON containing IDs provided from merchant integration code when the viewer loaded the player on their site.

 

 

Purchases Report

This report tracks purchases influenced by your video content, offering insights into transactions made after users engage with a video. The report includes details like order values, product IDs, the user's country, and the domain where the purchase was made.

 

Data shown in the Purchases report:

Field

Description

org_id

The ID of the Bam Hub or organization associated with the purchase.

order_id

The unique identifier for the order placed by the user.

user_id

The unique identifier for the user who placed the order.

order_product_ids

The list of product IDs included in the order.

order_value

The total monetary value of the order.

order_currency

The currency in which the order was placed (e.g., USD, EUR).

order_country

The country associated with the order placement.

purchase_domain

The domain (e.g., website) where the purchase was made.

inserted_at

The timestamp (including timezone) when the order was recorded.

last_session_at

The timestamp (including timezone) of the user's last session associated with this order.

sessions_json

A group of distinct player_session_keys with start and end times that can be matched against session rows in the player session report.

customer_tags_json

A JSON object containing custom tags or identifiers sent by the customer when the order was created.

 

For the Purchases report, it's important to note the following delimitations:

 

  • Session Dependency 
    • Purchases are only included if they are directly connected to a session in the Player Sessions Report. If a user completes a purchase without having a recorded video session, it will not appear in the Purchases Report.
  • Conversion Tracking Requirement 
    • This report is only available to customers who have implemented the conversion tracking script on their site. If conversion tracking is not set up, the Purchases Report will not capture any data. You can learn more about how to implement conversion tracking here.
Related Questions