Cross-device behavior export
Cross-device behavior export
This is for:
DeveloperIn this article, we’ll introduce you to our cross-device behavior export and how you can use it to get an insight into transaction and conversion data for users across multiple devices.
Reporting detail
This export type provides insight into the transaction and conversion data for users across multiple devices over a date range and will be of most use to analysts and marketers interested in how user behavior differs across devices.
As with all Qubit exports, you can specify the level of reporting detail to get a much greater understanding of reportables and focus on the details you’re really interested in.
For this export type, you can select:
-
A date range to include only data covering a defined period of time
-
Exclusion dates to exclude particular days or a period of time from the data
-
Dimensions which allow you to decide how to break down the data
-
Metrics that allow you to choose which metrics to include in the data
Logic
-
When applying the date range filter, we take the date when the transaction was carried out
-
The transaction date is based on
meta_recordDate
, which is in the timezone configured for the property -
The device type is taken from session data. Where there are duplicate events for the same users’s session, we take the first value in ascending alphabetical order
-
User email and Id are taken from the user event (for example,
ecUser
,egUser
,trUser
). If email and Id are emitted in view, events, such asecView
, we can also get the data from this event -
Only users with a non-null email address or user Id are included
-
Only users that have transacted in the date range are included
-
User email and Id data is only extracted from those events in the specified date range
-
In the unlikely event that multiple emails or user Ids are associated with the same logged-in user the first time the experience was seen in the date range, we take the first values in ascending alphabetical order
Note
Duplicate session events typically account for less than 1% of all session events. |
Dimensions, metrics, and output
Dimensions
Name | Description | Output |
---|---|---|
Device Type |
The user’s device type |
deviceType |
Metrics
Name | Description | Output |
---|---|---|
Conversions |
Total number of conversions carried out by the visitor |
conversions |
Total Order Value (Conversions) |
- Sum of all conversion amounts for the user- Reported with currency field |
totalOrderValueConversions |
Output
Additional fields not included in the dimensions and metrics tables above:
Field | Description |
---|---|
userId |
Unique ID that identifies a user |
userEmail |
User email of the user |