Way more sessions and people in CJA than visits and visitors in Analytics

[JacobBa6]

I currently have Adobe Analytics and Adobe Customer Journey Analytics implemented through a dual tagging approach. Analytics through the adobe analytics extension and CJA through the Web SDK. Data collection has been running for a few days, and I'm surprised to see that there are nearly twice as many people in CJA as there are unique visitors in Analytics.

There is only one dataset in the CJA connection, which is coming from the WebSDK. It has the the connection has the identity map default settings as the person ID. I didn't mess with this at all.

I am also capturing ECID separately in schema using:
if(typeof Visitor=="function")
{
var visitor = Visitor.getInstance('ADOBE ORG ID@AdobeOrg');
return visitor.getMarketingCloudVisitorID();
}
else return '';
to do so

I have roughly twice the people in CJA as I do Unique Visitors in Adobe Analytics. and I am trying to troubleshoot why

AA: 

CJA:

If i break down by Person ID in CJA - person ID and people match 1:1 but if i break personID down by the ECID i am capturing through data collection I am getting several ECIDs per personID.

I'm really trying to get to the bottom of why sessions and people are so inflated in CJA and I'm not sure where to go from here.

[JacobBa6]

the method i was using to capture ecid is incorrect - more geared towards Adobe Analytics - i changed it to the method using xdm and data prep mapping rules. not sure how that will impact people and sessions but that's why i was getting two different ECIDs, most like.

[AnkitJasani29]

Hi @JacobBa6 ,

In CJA, Sessions and People are derived from datasets, where identity stitching can link multiple profiles and sessions using various identity types like email, ECID, CRM ID, etc. This allows for cross-device and cross-channel unification. However, this can inflate session and person counts if identities aren't stitched properly, or if the identity graph contains fragmented identities.

In AA, Visits and Visitors are tracked using the ECID, which is cookie-based and limited to a specific browser and device, resulting in a more siloed user profile.

Reference: 

https://experienceleague.adobe.com/en/docs/analytics/components/metrics/unique-visitors

https://experienceleague.adobe.com/en/docs/id-service/using/home

[JacobBa6]

There is only one dataset in the connection, and it is using clickstream data from the Web SDK, so there is no identity stitching taking place.

[AnkitJasani29]

Hi @JacobBa6 ,

By default, AA defines a session (visit) to end after 30 minutes of inactivity. This means if a user is inactive for 30 minutes, a new session will start upon their next interaction. Reference: https://experienceleague.adobe.com/en/docs/analytics/components/metrics/visits

In CJA, session timeout settings are configurable within each data view. If you haven't explicitly set this, it might differ from AA's default. Reference: https://experienceleague.adobe.com/en/docs/analytics-platform/using/cja-dataviews/session-settings

Adjusting the session timeout in CJA to match AA's 30-minute default can help align session and visitor metrics across both platforms.

[Supriya_Savre]

Hi @JacobBa6,

Did the shared solution help you out? Please let us know if you need more information. Otherwise kindly consider marking the most suitable answer as ‘correct’.

If you've discovered a solution yourself, we would appreciate it if you could share it with the community.

[JacobBa6]

the session timeout in CJA already matches the 30 minute session timeout in AA