Session collection based on OWOX BI Sessionization Algorithm

This is a new option in OWOX BI Pipeline, allowing you to automatically collect session data from your website in Google BigQuery without having to depend on the sessionization algorithm in Google Analytics.

Below, we describe the logic behind the new data collection feature, and take a detailed look at how OWOX BI computes sessions.

Session Expiration

A session is closed and a new session begins:

  • at the end of each day (12 AM) in the linked Google Analytics view timezone.
  • when a user returns to your website via another campaign source.
  • after a predefined period of inactivity (the default timeout of 30 minutes can be changed in the OWOX BI interface).

Filters and Exceptions

  • Sessions will contain raw unfiltered data. That's why we recommend that you select an unfiltered Google Analytics view when setting up data collection in Google BigQuery.
  • By default, your domain is automatically added to the referral exclusion list: as a result traffic from subdomains won't appear in the reports.

Identifying traffic sources

The new sessionization algorithm in OWOX BI Pipeline: Google Analytics to Google BigQuery attributes sessions to traffic sources using the Last Click attribution model. This means that, the sessions are always attributed to the last  traffic source that brought a user to the website. In this case, direct traffic is not overridden with the previous source.

With that said, by default Google Analytics attributes sessions to traffic sources using the Last Non-Direct Click attribution model. This means that direct traffic is ignored, and the session is attributed to the previous non-direct traffic source.

AdWords auto-tagging

In the cases of AdWords auto-tagging, the trafficSource.* fields, providing information about the traffic source from which the session originated, are retrieved from AdWords data tables uploaded to Google BigQuery using the Adwords API.

There are several ways to set up automatic uploads of AdWords reporting data into Google BigQuery. For more information about how to collect AdWords data in BigQuery, please refer to our Help Center.

Please note: Make sure you have configured automatic uploads of AdWords data into Google BigQuery. Otherwise the auto-tagging won't be available.

Data collection and update times in the Google Analytics view time zone

Type of data When the data appears in session data tables in Google BigQuery

Sessions computed on the basis of hit data tables

Within the following day after the start of hit data collection.

Cost data (adCost, attributedAdCost). This includes all advertising cost data imported into Google Analytics.

Within 9 hours on the following day. A repeated update may occur within 24 hours.

trafficSource.* data, retrieved from AdWords data tables in Google BigQuery. This data is required to obtain information about traffic sources for AdWords campaigns in the case of auto-tagging (GCLID values). More information about using AdWords data in session data tables can be found in our documentation.

Geo data

 

Fully consistent session data tables become available within the following day after the start of hit data collection.

Please note: the service is currently in Alpha. During the Alpha testing phase, there's no SLA on the time it takes to compute the tables.

Data collection limits:

  • The maximum of 6,000 hits can be collected per clientID per day.
  • The maximum hit size is 512 kB.

Please note: During the Alpha, when you create a new Google Analytics to Google BigQuery pipeline, both sessionization algorithms will be working simultaneously.

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.