Creating an audience on same attribute

[SubeAEP]

Hi everyone,

I have a use case where some members' account types(account_type) have changed from Type A to Type B in the past. I managed to identify these members by using a self-join query in the query service on the member dataset, but I'm having trouble creating an audience based on this condition. Has anyone encountered a similar situation?

Could you share how I can create an audience segment for members whose account type has changed from Type A to Type B?

Any help or guidance would be greatly appreciated!

[PratheepArunRaj · Accepted solution]

Hello @SubeAEP ,

Is the Account Type (account_type) a field from Profile Schema?

If it is a Profile Schema, then I don't think it is possible to create a segmentation for it because only the latest value is stored in the Profile Store. Managing to identify the members using Query Service is fine because every change is logged (a profile copy at the time of change) into the Data Lake.

So, my understanding is that you need to add an attribute for the resultant profiles (from your query) and update them to Profile Store for segmentation.

If it is an Event Schema, we need to see the audience builder options and understand whether we can include the audience based on our use case.

Thank You, Pratheep Arun Raj B (Arun) | NextRow Digital | Terryn Winter Analytics

[SubeAEP]

Hi @PratheepArunRaj , thanks for your answer. Yes,its a profile data and we are trying to capture those members whose account_type attribute got changed from one to the other. I too believe that its not possible to achieve this by using segmentation service as the profile snapshot dataset only stores the updated values.

[PratheepArunRaj]

Hello @SubeAEP ,

The profile snapshot dataset does have all the changes because it was taken every day; however, it is not available for you as a profile attribute to include it for a segmentation (not profile enabled), i.e., the dataset is sitting only in the Data Lake.

Thank You, Pratheep Arun Raj B (Arun) | NextRow Digital | Terryn Winter Analytics

[Rite18]

@SubeAEP understanding is the same scenarios when account type was A and now the Type is B- Is that right?

if it is profile schema then the time-based/update record is not maintained.  

One option could be  to update the existing schema using the profile service considering u have detailed historical data when A did not exist 

[SubeAEP]

Hi @Rite18 , thanks for your reply. Yes, its a profile data and we are trying to capture those members whose account_type attribute got changed from one to the other.