Adobe Analytics

vvivek4ever · 5/20/25

Hi everyone,

Our organization captures Adobe Analytics data across three different digital touchpoints - mobile app, website, and certain embedded webviews that users may access post-login. A typical user journey can span across these environments. For instance:

A user may start on the mobile app, then navigate to a web page via an in-app link.
Or they might begin on the website, log in, and then transition to a post-login experience hosted within a separate platform (captured as a different feed).

Each of these streams is tracked independently, with their own unique hit identifiers and collection logic.

My question:
What are the best practices for stitching together a single user session that spans across these different platforms/feeds in Adobe Analytics?

Are there any recommended identifiers we should rely on for stitching?
How do we ensure continuity of session data across app-to-web or web-to-platform transitions?
Are there any implementation patterns or processing techniques that have worked well for others in similar cross-platform setups?

Any advice or shared experience would be greatly appreciated!

Thanks in advance!

Jennifer_Dungan · 5/23/25

If you don't have CJA device stitching... there is also the "cross domain" solution...

When going between sites, you can use an analytics plugin to append ECID information as a query parameter to the next site... Adobe is supposed to read this value and use the passed ECID on the next site.

Similar, when dealing with apps, sadly, there is no web to app solution, but app to web there is a similar append ECID to the outgoing links / webviews inside the app that force the website to take on the ECID from the mobile app.

https://experienceleague.adobe.com/en/docs/id-service/using/id-service-api/methods/appendvisitorid

https://experienceleague.adobe.com/en/docs/experience-platform/web-sdk/identity/id-sharing

View solution in original post

Imbalakumar · 5/20/25

Hi @vvivek4ever I do encountered similar challenges in the past.

Adobe came up with the solution Customer Journey Analytics with one or combination of a common identifier to stitch a user or member journey to understand the patterns.

Also if you have webSDK implementations and also if those are streaming to Adobe Experience Platform, you can find the events across cross device and cross platform engagements.

So you need the below licenses to address these challenges,

1. Customer Journey Analytics (CJA) - this will stich all the customer journey from multiple sources, cross device, cross platform etc

2. webSDK implementation

3. RT-CDP - may be a good to have platform

Thanks,

Bala

Regards,

Bala

nitesh__anwani · 5/20/25

Hi @vvivek4ever ,

I believe you may be looking to achieve one of the following two objectives:

1. Stitching the user profile within a single app session
In this case, you want to maintain the same identifier across both native app screens and embedded WebViews. If that's what you're trying to do, the solution is straightforward—you just need to append the Visitor ID to the WebView’s page load URL. You can find the relevant documentation here:
Adobe Mobile SDK: appendVisitorInfoForURL

2. Stitching the user profile across devices and sessions across all digital properties
Here, the goal is to link a user's journey across platforms—for example, when a user is logged in on your desktop website and also logged in through the mobile app, you want to unify that entire experience under a single profile. For this use case, you’ll likely need to explore Cross-Device Analytics (CDA).

While I’m not entirely certain, I believe CDA may come with additional costs and typically requires setup support from Adobe’s engineering team. They will configure a virtual report suite linked to your CDA-enabled global report suite. Here are the relevant resources: