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
We will not be adding these metrics to Data Warehouse at this time. I'm
closing this status as declined at this time, as this request is very
old. If you continue to have a business need for this feature, please
post a new item.
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:
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 device-centric view of the world
to a person-centric view. Cross-Device Analytics provides the data,
capabilities and tools to help the enterprise understand the customer’s
multi-device usage and the ...
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.)...