3/13/2023 0 Comments Universal database table address![]() The type of device (Mobile, Tablet, Desktop). This captures the initial dimensions of the viewport in pixels and is formatted as width x height, for example, 1920x960. The browser used (e.g., "Chrome" or "Firefox"). This section contains information about the user devices. The Default Channel Group associated with an end user's session for this View. Could be the name of the search engine, the referring hostname, or a value of the utm_source URL parameter.Įngagement type, either "Socially Engaged" or "Not Socially Engaged". (The host name of the referrer is in trafficSource.source.) If dium is "referral", then this is set to the path of the referrer. Could be "organic", "cpc", "referral", or the value of the utm_medium URL parameter. Can be set by the utm_term URL parameter. The keyword of the traffic source, usually set when the dium is "organic" or "cpc". ![]() True if the source of the session was Direct (meaning the user typed the name of your website URL into the browser or came to your site via a bookmark), This field will also be true if 2 successive but distinct sessions have exactly the same campaign details. Value of the utm_id campaign tracking parameter, used for manual campaign tracking. Usually set by the utm_campaign URL parameter. Remarketing list ID (if any) in Google Ads, derived from matching_criteria in click record. There are multiple types of targeting criteria, but should have only one value for each criterion. Google Ads targeting criteria for a click. Analytics uses the last non-direct click model. This section contains information about the Google Ads click info if there is any associated with this session. Can be set by the utm_content URL parameter. This section contains information about the Traffic Source from which the session originated. The value is null if there are no interaction events in the session. This value is 1 for sessions with interaction events. The number of sessions (for convenience). Total number of unique screenviews within the session. Total number of ecommerce transactions within the session. Use "totals.totalTransactionRevenue" instead (see above). Total transaction revenue, expressed as the value passed to Analytics multiplied by 10^6 (e.g., 2.40 would be given as 2400000). Total time of the session expressed in seconds. A value of 0 indicates that Session Quality is not calculated for the selected time range. A value closer to 1 indicates a low session quality, or far from transacting, while a value closer to 100 indicates a high session quality, or very close to transacting. Total number of screenviews within the session.Īn estimate of how close a particular session was to transacting, ranging from 1 to 100, calculated for each session. Total number of pageviews within the session. If this is the first visit, this value is 1, otherwise it is null. Total number of new users in session (for convenience). For a bounced session, the value is 1, otherwise it is null. This section contains aggregate values across the session. The date of the session in YYYYMMDD format. For a completely unique ID, you should use a combination of fullVisitorId and visitId. This is part of the value usually stored as the _utmb cookie. If this is the first session, then this is set to 1.Īn identifier for this session. Unhashed version of the Client ID for a given user associated with any given visit/session. In BigQuery, some columns may have nested fields and messages within them. The columns within the export are listed below. RowsĮach row within a table corresponds to a session in Analytics 360. You may notice differences between intraday and daily data based on active user sessions that cross the time boundary of last intraday import. If an intraday-table write fails, then the previous day's intraday table is preserved.ĭata for the current day is not final until the daily import is complete. ![]() For the current day, until the first intraday import, there is no intraday table. When the daily import is complete, the intraday table from the previous day is deleted. During the same day, each import of intraday data overwrites the previous import in the same table. Intraday tables have the format "ga_sessions_intraday_YYYYMMDD". Intraday data is imported at least three times a day. Daily tables have the format "ga_sessions_YYYYMMDD". Within each dataset, a table is imported for each day of export. Datasetsįor each Analytics view that is enabled for BigQuery integration, a dataset is added using the view ID as the name. This article explains the format and schema of the data that is imported into BigQuery. This feature is not governed by a service-level agreement (SLA).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |