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...
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-opAdobe private graphField-based stitching
I believe field-based stitching best meets the needs you are describing. Field-based stitching requires that ...
Hello and welcome!This forum is dedicated to discussion about Journey IQ: Cross-Device Analytics (CDA.) If you are a user of CDA, this is where you can:Ask questionsMake suggestions and provide feedbackCollaborate with othersCDA overviewJourney IQ: Cross-Device Analytics transforms Analytics from a ...
Hello, @web_analyst. As you noted, the IP obfuscation tool applies only from the time you enable obfuscation forward. Removing IP addresses historically requires an engagement with our Engineering Architects consulting team. Please contact your Account Manager (CSM) to coordinate with the Engineerin...
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...