Expand my Community achievements bar.

Profile Isn't Being Selected for All of It's Attributes

Avatar

Level 2

Complicated one so I will try and explain.  I have a core customer schema which has the primary identity representing an individual.  Each customer can have multiple accounts so there is another identity field on that schema Account ID.  There are several other schemas with account information, all of these have the Account ID as the primary identity on the schema and all use the same Account ID Identity Namespace.  Based on my understanding the various data on those tables make up the profile fragments that I can then use to create an audience, however when I try and build a rule it is not selecting the profile for all of the available values.

 

Ex. Customer X has Customer ID ABC on core customer schema he also has AccountID's 123, 456 and 789 on the same schema.  Account Info Schema has Account ID as the primary identity for that schema and Customer X has 3 rows, one for each account.  This schema has a field "Account Type" and each account has a different account type 123 - Personal, 456 - Business, 789 - Savings. 

 

When I create an audience my expectation would be that the Profile associated with ABC would get selected whether I I have an account type of Personal, Business or Savings, however I'm only seeing it for 1.  Any help appreciated.   

12 Replies

Avatar

Community Advisor

@DanSpigs1 I hope you've structured the data and established a relationship between core customer schema and account info schema. If so, when you create an audience with any account type personal/business/savings it should pull the customer ABC into the audience.

Screenshot 2025-03-27 at 11.51.44 PM.png

Thanks, Sathees

Avatar

Level 2

Hi SatheeskannaK,

 

I believe I have and I can see the linked identities on the profile.  Each schema has the associated ID's defined as identities with the corresponding identity namespaces.  What else should I be checking to confirm this is configured correctly?

 

DanSpigs1_0-1743167035629.png

 

Avatar

Community Advisor

@DanSpigs1 Your screenshot confirms that all of these different account id's are rolling up to 1 profile (customer id: 8888), considering Bpid is one of the namespace used as an identity. Ideally, if there is a defined relationship between the customer and the account information schema, it should link all different account types (personal, business, savings) back to customer ID 8888.

Thanks, Sathees

Avatar

Level 2

Thank you, what would be a reason it is not?  I'm creating an audience rule and it's only selecting for one value not all.  This data structure was changed recently, is there a possibility that this new relationship isn't being read correctly by the system? Any advice appreciated here.  Thanks.

Avatar

Community Advisor

Ok. After changing the structure, I hope you have followed the steps to reingest the historical data. You can validate the data in the datalake using query service. Remind me, if you create an audience which account type, it's not pulling the customer 8888 into the audience? and works with other account types.

Thanks, Sathees

Avatar

Level 2

I did reingest the data following the changes.  I was wondering if since previously we used different Identity's could there be an association that needs to be broken and reestablished?

 

To answer your question, I am using the Audience Creation, create a rule in the tool and even though there is a valid value in the condition it returns no profiles.  I can use the query editor and confirm that the data exists on the dataset, but it is not being properly stitched to the profile.

Avatar

Community Advisor

It's possible that a change of identity may be causing this problem to have an inconsistent state on a stitched profile. If you've followed all the steps after changing the structure and the profile is not stitched appropriately, I would suggest opening a support to look into the problem. At the end profile store data should reflect with the appropriate attributes and values. so that audience segmentation will reflect the profile count.

Thanks, Sathees

Avatar

Level 2

Thanks Sathees,

 

At this point with several revisions to the data structure we're going to do a sandbox reset on the Dev environment and rebuild.  Hopefully at that point you are correct, and we see everything coming in as expected.  Appreciate the help.

Avatar

Administrator

Hi @DanSpigs1,

Was the above approach helpful in resolving your issue? Do let us know.

Thanks!



Sukrity Wadhwa

Avatar

Level 2

Unfortunately the system is still not behaving as expected, I have opened a support ticket and I am working with Adobe to understand the issue.

Avatar

Administrator

Thanks @DanSpigs1 for sharing the update. Do share the final resolution with us once your issue is resolved. It would be helpful for other community members facing the same issue.



Sukrity Wadhwa

Avatar

Level 2

To elaborate, data is currently loaded like this 

Customer IDAccount ID
8888123
8888456
8888789
8888135

With account info as you've laid out.  Screenshot above shows the associated Identities on the profile.