You can use a Flow visualization with the Mobile Device Type dimension.
Using Mobile Device Type as illustrated above allows you to see how people move between mobile device types and desktop device types. However you may want to distinguish desktop browsers from mobile browsers. One way to do this is to create an eVar that records whether the experience occurred on a desktop browser, mobile browser, or mobile app. Then create a Flow diagram as described above, using your “experience” eVar rather than the Mobile Device Type dimension. This provides a slightly different view on cross-device behavior.
Adobe keeps device stitching data for approximately 30 days. If a device is intitially not identified but is later identified within 30 days, CDA goes back and restates that device as belonging to identified person up to 30 days in the past. If some of a user’s unidentified behavior falls outside the 30-day lookback window, that portion of the user’s journey is not stitched.
Adobe treats timestamped hits as if they were received at the time of the timestamp, not when Adobe received the hit. Timestamped hits older than 1 month are never stitched since they are outside the range Adobe uses for stitching.
Using a custom visitor ID is a legacy method to connect users across devices. With a custom visitor ID, you use the
visitorID variable to explicitly set the ID that is used for visitor logic. The
visitorID variable overrides any cookie-based IDs that are present.
Custom visitor IDs have several undesirable side effects that CDA overcomes or minimizes. For example, the custom visitor ID methodology has no replay capabilities. If a user authenticates in the middle of a visit, the first part of the visit associates with a different visitor ID than the latter part of the visit. The separate visitor IDs results in visit and visitor inflation. CDA restates historical data so unaunthenticated hits belong to the correct person.
Customers already using Custom Visitor ID can upgrade to CDA without any implementation changes. The
visitorID variable is still used in the source report suite. However, CDA ignores the
visitorID variable in the virtual report suite if a user authenticates.
In some situations it is possible that multiple people log in from the same device. Examples include a shared device at home, shared PCs in a library, or a kiosk in a retail outlet.
In some situations, an individual user can associate with a large number of ECIDs. This can occur if the individual uses a lot of browsers or apps, and can be exacerbated if they frequently clear cookies or use the browser’s private or incognito browsing mode.
The People metric is similar to the Unique Visitors metric in that it reports on the number of unique individuals. However, when using Cross-Device Analytics, unique visitors are combined when they are otherwise recorded as two separate unique visitors outside of CDA. The ‘People’ metric replaces the ‘Unique Visitors’ metric when Cross-Device Analytics is enabled. A new metric, Unique Devices, is available that is approximately equal to Unique Visitors outside of Cross-Device Analytics.
These two metrics are roughly equivalent to each other.
Yes. Analysis Workspace uses the 2.0 API to request data from Adobe’s servers, and you can view API calls Adobe uses to make your own reports:
Yes. If an individual sends hits from two separate devices within your virtual report suite’s visit timeout (30 minutes by default), they are stitched into the same visit.
Both of these identifiers are calculated by Adobe at the time the report is run, also known as Report-time processing. The nature of Report-time processing means that it is not compatible with Data Warehouse, data feeds, or other export features that Adobe offers.
If you would like to switch CDA identifying methods, talk to your organization’s Account Manager. The Account Manager can provision your report suite to the desired method to identify people. Historical stitched data from the previous method is lost.
CDA pulls eVar dimension items before they are optimized for reporting. You do not need to worry about unique limits for the purposes of CDA. However, if you tried using that prop/eVar in a Workspace project, you can still see the (Low-traffic) dimension item.