Great questions. (1) The best way to configure the implementation so that CDA will stitch the app hits with the in-app browser hits is to ensure the same user ID is stored in whatever prop or eVar you are using for field-based stitching. (The same user ID should be stored in the prop or eVar in both the app hits and the in-app browser hits.) (2) CDA stitched data is exposed through a special type of virtual report suite. In that virtual report suite there is no longer a unique visitors metric. I...

Hi and thank you for your feedback. CDA can use one of 3 different options for figuring out how to group devices together into people: Adobe Co-op Adobe private graph Field-based stitching I believe field-based stitching best meets the needs you are describing. Field-based stitching requires that you store a user ID of some sort (typically a hashed user identifier) in a prop or eVar when the user is known (typically when they are logged in.) If the login occurs on multiple devices/cookies/browse...

Cross-Device Analytics in EMEA will follow soon after the device graph is available in EMEA. Current timing (subject to change) is mid-2020.

Thanks for this feedback. I'll definitely pass this along to the Private Graph team. At a high level though, the Private Graph implementation is almost exactly the same as Co-op Graph: Both Private Graph and Co-op Graph require that you are implemented for Experience Cloud ID (ECID.)Both Private Graph and Co-op Graph require that you do ID syncing with the graph. See these links:Calling Visitor ID service: https://docs.adobe.com/content/help/en/id-service/using/id-service-api/methods/setcustomer...

This idea hasn't been updated in a while, but I thought I'd let you know we are actively working on a cross-device stitching capability that is far more robust than using s.visitorID. It is feature that leverages an integration between Adobe Analytics and the device graph (Co-op or private graph.)To that end, I wanted to ask a follow up question. Do you store a hashed user id in a prop or eVar? In particular, do you store an ID in a prop or eVar once the user is known (via login or other means.)...