Creating an audience on same attribute | Community
Skip to main content
S
SubeAEP
Level 2
January 13, 2025
Solved

Creating an audience on same attribute

  • January 13, 2025
  • 2 replies
  • 1103 views

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!

Best answer by PratheepArunRaj

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

 

2 replies

PratheepArunRaj
Community Advisor and Adobe Champion
PratheepArunRajCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
January 14, 2025

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

 

Thank You, Pratheep Arun Raj B (Arun) | Xerago | Terryn Winter Analytics
    S
    SubeAEPAuthor
    Level 2
    January 15, 2025

    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
      Community Advisor and Adobe Champion
      PratheepArunRajCommunity Advisor and Adobe Champion
      Community Advisor and Adobe Champion
      January 15, 2025

      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

       

      Thank You, Pratheep Arun Raj B (Arun) | Xerago | Terryn Winter Analytics
        RiteshY18
        Community Advisor
        RiteshY18Community Advisor
        Community Advisor
        January 15, 2025

        @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 

          S
          SubeAEPAuthor
          Level 2
          January 15, 2025

          Hi @riteshy18 , 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. 

            RiteshY18
            Community Advisor
            RiteshY18Community Advisor
            Community Advisor
            January 29, 2025

            @subeaep in this you should have something to check status of prior versus current in your XDM , I believe that is not exit 

            option could be 

            - use profile service to update as mentioned in prior comment 

            - create a new schema class for account as look entity with status or value as needed to validate current and historical value .. 

            Terms & ConditionsAccessibility statement

            Loading footer...