Analytics model

This is for:

Developer

These tables organize the real-time events data collected by Qubit into a single data model with clear, defined relationships between them. This model is designed for use with business intelligence tools such as Looker and Tableau.

Tip
Leading-practice

This data model updates on a daily basis and is designed for historical analytics. For real-time data, query the events tables directly.
Note

Contact your Qubit Customer Success Manager if you have not been onboarded onto this feature.

What does the model offer?

  • Organizes events data into a single data model with clear, defined relationships between each table

  • Combines data items from multiple events into single tables for segments, views, experiences, and other reporting entities.

    For example the product view combines the ecProduct (product views), ecBasketItem (basket items), and ecBasketItemTransaction (item purchases) event tables to enable easy funnel analysis

  • Bakes in best practice joins between tables to ensure efficient data access and avoid double-counting of event activity

The model covers a common set of metrics and subject areas, with a selection of the most useful metrics and dimensions for analytics.

Tip
Leading-practice

You can still directly query the event tables if a dimension or measure you require is not available in this model. It’s also possible to expand the model by editing the model SQL - speak to your Qubit CSM for details.

Ecommerce model

eComm

The following table provides the underlying BigQuery object name, key columns, and contents for the core business views.

Name BigQuery View Key(s) Contents

Views

view

view_id

All visitor page and view events, the base "event" to which all other events are linked

Product Interaction and Sales

product

view_id, product_id

Views where products were displayed, interacted with, or purchased

Segment Membership

segment

view_id,segmentId

Views that happened on or after a visitor entered a segment

Experience

experience

view_id, experienceId, goalId

- Views that happened on or after a visitor saw an experience

* If you wish to work with just the views that had the experience delivered on them, use is_post_experience_view to filter rows that are false

Transactions

transaction

transaction_id

Details every transaction

Sessions

session

session_id

Details every session for users

Entrances

entrance

entrance_id

Details every entrance for users

Goal Achieved

goal_achieved_views

view_id,goalId

- Contains all views after the goal was achieved

* If is_post_goal_achieved_view is FALSE, goal was achieved on the current view_id and if TRUE the goal was achieved previously

Attribution

attribution

Session_id, entrance_id

Entrances which took place before the visitor completed a transaction

Visitor pulse

visitor_pulse

View_id, question_id

Details visitor survey results

Travel model

travel
Name Contents

package_item

Similar to the Product table offered for retail schemas, this includes details on viewed & purchased package items such as a flight or hotel

eGaming model

gaming