August 27, 2018 — OWOX BI Pipeline. New fields in the "owoxbi_sessions" tables

Starting August 25, 2018, session data tables "owoxbi_sessions" collected with the OWOX BI algorithm will get fields from the hit data tables ("streaming"). Now you don't need additional JOIN functions to add these fields from hit data.

These fields, however, will not appear in the "session_streaming" tables being collected based on Google Analytics data.

Note:The fields with custom dimensions and metrics don't have level scopes as they do in Google Analytics (hit-level scope, session-level scope). They are being collected on hit level only. The session-level fields are not being filled in yet.

The field in the "streaming" tables The new field in the "owoxbi_sessions" tables Data type Description
device.ip device.ip STRING IP Override
User IP address
device.userAgent device.userAgent STRING User Agent Override
The User Agent of the browser
device.language device.language STRING Language
Language in the ISO-639 format
queueTime hits.queueTime INTEGER Queue Time
Used to collect offline / latent hits
customGroups hits.contentGroups RECORD  
customGroups.index hits.contentGroups.index INTEGER Page Group XX
The content group index on a property
customGroups.value hits.contentGroups.value STRING Page Group XX
The content group on a property
customDimensions hits.customDimensions RECORD Custom Dimension XX
This section contains any hit-level custom dimensions. This is a repeated field and has an entry for each dimension that is set.
customDimensions.index hits.customDimensions.index INTEGER Custom dimension index
customDimensions.value hits.customDimensions.value STRING Custom dimension value
customMetrics hits.customMetrics RECORD Custom Metric XX
This section contains any hit-level custom metrics. This is a repeated field and has an entry for each metric that is set.
customMetrics.index hits.customMetrics.index INTEGER Custom metric index
customMetrics.value hits.customMetrics.value STRING Custom metric value

 

We've also added fields from the "session_streaming", which were previously absent in the "owoxbi_sessions" tables. This will help you seamlessly move to the "owoxbi_sessions" by preserving the queries you use for the "session_streaming" tables.

A field from "session_streaming" added to "owoxbi_sessions" Data type Description
newVisits INTEGER Currently gets only the 'null' values. The correct values will appear with the upcoming updates.
totals RECORD Analog to the totalsStreaming field
totals.hits INTEGER Analog to the totalsStreaming.hits field. The field values may differ from the values in the "session_streaming" tables
totals.events INTEGER Analog to thetotalsStreaming.events field. The field values may differ from the values in the "session_streaming" tables
totals.transactions INTEGER Analog to thetotalsStreaming.transactions field. The field values may differ from the values in the "session_streaming" tables
totals.pageviews INTEGER Analog to the totalsStreaming.pageviews field. The field values may differ from the values in the "session_streaming" tables
totals.screenviews INTEGER Analog to the Streaming.screenview field. The field values may differ from the values in the "session_streaming" tables
totals.isInteraction BOOLEAN Analog to the totalsStreaming.isInteraction field. The field values may differ from the values in the "session_streaming" tables
totals.visits INTEGER For the sessions with interactions, the value equals 1 (isInteraction = true). Otherwise – 0.
The field values may differ from the values in the "session_streaming" tables
hits.pagePath STRING Analog to the hits.page.pagePath field
hits.pageType STRING Analog to the hits.page.pageType field
hits.eCommerceActionType STRING Analog to the hits.eCommerceAction.action_type field
hits.contentGroups RECORD Analog to the hits.customGroups field
hits.contentGroups.index INTEGER Analog to the hits.customGroups.index field
hits.contentGroups.value STRING Analog to the hits.customGroups.value field
hits.product.productListName STRING Currently gets only the 'null' values. The correct values will appear with the upcoming updates.
hits.product.localProductPrice FLOAT Currently gets only the 'null' values. The correct values will appear with the upcoming updates.

 

Reminding that these fields will appear un the "owoxbi_sessions" tables starting August 28, 2018 (for August, 27 data tables).

The updated data schema is here.

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

0 Comments

Please sign in to leave a comment.