Schema for session data tables collected with the OWOX BI algorithm ("owoxbi_sessions")

The session number of this user over the last six months. If it is the first session, then this field is set to 1. Learn more

The total number of new users in the session. If this is the first visit, this value is 1, otherwise null

A URL address of the first hit in the session without any query parameters such as UTM tags. This field helps unite the same landing pages from the sessions with different sources.

The type of the user's device:
-tv;
- game console;
- robot;
- set-top box;
- robot mobile;
- unknown;
- hacker;
- virtual reality;
- anonymizer
Full list and definitions

The Default Channel Group associated with an end user's session.

This field is null for now.

This section will contain information about the Google Ads click info if there is any associated with this session.

This field is null for now.

Shows where was placed the Google Ads advertisement that started the session.

This field is null for now.

The network (Content, Search, Search partners, etc.) used to deliver the ads.

This field is null for now.

Currently unavailable. The match type (Phrase, Exact, Broad, etc.) applied for users' search term. Ads on the content network are identified as "Content network".

This field is null for now.

Specifies the Google Ads Id

Specifies the Google Display Ads Id

Possible values: null, true.

The field is assigned true if the source of the session was Direct, e.g.:

• a user typed a website URL into a browser;
• a user came to a website via a bookmark. 

Note:

If a user first arrives on a website through the paid traffic source, leaves opened a page, and returns to the same page when the first session has timed out, then a new session will start. And the trafficSource.isTrueDirect field will be true for this new session.

The total sessions cost is attributed evenly between sessions according to the UTM tags 'source', 'medium', 'campaign', 'keyword', and 'content' if the tags perfectly match in all sessions.

The value from the adCost field will also be assigned to the attributedAdCost field for these sessions. See the example

When one or more tags are unknown, the total session cost is attributed evenly between the sessions according to the known tags. 

If some value has already been assigned to such sessions (for example, by assigning a value from the adCost field), the new value will be added to the existing one. See the example

This section contains any user-level or session-level custom dimensions that are set for a session. This is a repeated field and has an entry for each dimension that is set.

This field is null for now.

The index of the custom dimension.

This field is null for now.

The value of the custom dimension.

This field is null for now.

The time on the server according to the time zone when the hit occurred (in seconds).

Note:

If hits.queueTime not empty, then hits.time will contain the result of calculating the formula: (hits.timestamp - hits.queueTime) / 1000 in seconds.

For example, if you send hits from the call tracking system, then hits.queueTime will save the time in the queue, and hits.timestamp will save the time when the operator accepted the call. Therefore hits.time will get the time when the user made a call (calculated by the formula).

Page Group XX
Contains nested fields with content group on a property

STRING

Product Action
Can be one of: detail, click, add, remove, checkout, checkout_option, purchase, refund.

Also, this field can take the same value as the promotionActionInfo field.

This section is populated for all hits containing product scope Custom Dimensions

The product scope Custom Dimensions index

The product scope Custom Dimensions value

This section is populated for all hits containing product scope Custom Metrics

The product scope Custom Metrics index

The product scope Custom Metrics value

This section contains all user timing variables.

The fields are automatically filled in for the hit types 'timing' and 'adtiming'.

For easier reporting purposes, this is used to categorize all user timing variables into logical groups.

The field is automatically filled in for the hit types 'timing' and 'adtiming'.

Used to add flexibility to visualize user timings in the reports.

The field is automatically filled in for the hit types 'timing' and 'adtiming'.

The name of the resource's action being tracked.

The field is automatically filled in for the hit types 'timing' and 'adtiming'.

Total number of milliseconds for user timing.

The field is automatically filled in for the hit types 'timing' and 'adtiming'.

Total time (in milliseconds), from pageview initiation (e.g., a click on a page link) to page load completion in the browser, the pages in the sample set take to load.

The field is automatically filled in for the hit types 'timing' and 'adtiming'.

The total time (in milliseconds) all samples spent in DNS lookup for this page.

The field is automatically filled in for the hit types 'timing' and 'adtiming'.

The total time (in milliseconds) to download this page among all samples.

The field is automatically filled in for the hit types 'timing' and 'adtiming'.

The total time (in milliseconds) all samples spent in redirects before fetching this page. If there are no redirects, this is 0.

The field is automatically filled in for the hit types 'timing' and 'adtiming'.

Total time (in milliseconds) all samples spent in establishing a TCP connection to this page.

The field is automatically filled in for the hit types 'timing' and 'adtiming'.

The total time (in milliseconds) the site's server takes to respond to users' requests for all samples; this includes the network time from users' locations to the server.

The field is automatically filled in for the hit types 'timing' and 'adtiming'.

The time (in milliseconds), including the network time from users' locations to the site's server, the browser takes to parse the document (DOMInteractive). At this time, users can interact with the Document Object Model even though it is not fully loaded.

The field is automatically filled in for the hit types 'timing' and 'adtiming'.

The time (in milliseconds), including the network time from users' locations to the site's server, the browser takes to parse the document and execute deferred and parser-inserted scripts (DOMContentLoaded). When parsing of the document is finished, the Document Object Model (DOM) is ready, but the referenced style sheets, images, and subframes may not be finished loading. This is often the starting point of Javascript framework execution, e.g., JQuery's onready() callback.

The field is automatically filled in for the hit types 'timing' and 'adtiming'.

This section contains any hit-level custom dimensions. This is a repeated field and has an entry for each dimension that is set.

The index of the custom dimension

The value of the custom dimension