Person ID missing in a new data view from an existing connection

[KarunaHa]

Field DescriptionWhat product are you using?What area of the product are you using?What are you trying to achieve?What’s the problem or error?What have you tried so far?Environment / VersionScreenshots / Videos / Logs / Code

Customer Journey Analytics

Data views

Stitching across data sets

I'm creating a new dataview from an existing connecting which has website, call centre, and summary data (this I've just added), also the stitched data between web & call centre but in the new dataview, I'm not getting the Person ID

checked identities are properly marked in schema & datasets. Also checked dataview to make sure all components are added.

[Elanchezhiyan_E]

@KarunaHaCorrect me if I'm wrong,

I guess you are adding an new summary dataset to the existing CJA connection which has Website data and Call Centre data. 

When you add an summary dataset to a connection, it would not ask for Person ID in summary dataset.

As you mentioned that the data has already been stitched between Website Data and Call Centre Data, you just need to group a summary dimension to a Event Dimension while configuring data views.

For more details just go through this tutorial, https://experienceleague.adobe.com/en/docs/customer-journey-analytics-learn/tutorials/data-views/cre...

Please let me know if you need further assistance.

[Jude_Felix]

Hi @KarunaHa, here are a few things you might check: 

1. Confirm that the Person ID field is included as a dimension in your data view. 

Even if it’s correctly set up in the schema and dataset, it still needs to be explicitly added as a component in the data view configuration. 

2. Check which dataset the Person ID is coming from. 

If you’re stitching across datasets (like web and call centre), sometimes the Person ID may be populated only in the stitched dataset and not in the summary or other datasets. Make sure the stitched dataset is actually added to your data view and the data view is using the right identity namespace. 

3. Verify that stitching completed successfully and the identity graph is working as expected. 

You can look in the Connections view and Identity Service diagnostics to check whether profiles are truly being stitched and whether the Person ID is linked. 

4. Try creating a very simple test data view that includes only the stitched dataset and the Person ID to see if it appears there. 

This can help isolate whether the issue is in the data view configuration or in the dataset itself. 

If after checking all of this the Person ID still doesn’t appear, it could be worth revalidating the datasets in the connection or checking if the identity namespace used for Person ID matches exactly between the datasets and the data view.