AEP - update profile attribute conditionally | Community
Skip to main content
G
GabrielaNa1
Level 3
February 10, 2025
Question

AEP - update profile attribute conditionally

  • February 10, 2025
  • 3 replies
  • 794 views

Hi 

I have a question about the possibility to update a certain profile attribute under some conditions.

Let's say I have a profile attribute called "Last Touchpoint". If the attribute is populated in the profile, I don't want to overwrite it with the value coming from a batch ingestion for a certain source. In other words, I want the value already in the profile to trump any value coming from a certain source, unless the attribute in the profile is empty, but the data source has value.

 

Can this be achieved? Any suggestions?
Thanks.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

3 replies

nnakirikanti
Community Advisor
nnakirikantiCommunity Advisor
Community Advisor
February 10, 2025

@gabrielana1 It would be ideal to fix source flows in such situations, any solution with datalake will be a stopgap solution and wont represent right timestamp for streaming data as it will be processed in batches from UPS to datalake. 

 

If you need any additional help with this, please let me know; if not, please mark this thread appropriately.

 

~cheers,

NN.

    G
    GabrielaNa1Author
    Level 3
    February 10, 2025

    Hi

     

    "It would be ideal to fix source flows in such situations" - not sure I understand what you mean by this. The source (a batch, not streaming in my case, but I don't think is relevant for my question) wouldn't know if the profile has value until the moment of fragment stitching, right? I do not care much here about the timestamp. All I care is to prioritize the value in the profile over anything that comes from this particular data source. Is this even possible?

    nnakirikanti
    Community Advisor
    nnakirikantiCommunity Advisor
    Community Advisor
    February 10, 2025

    @gabrielana1 I have interpreted your initial question in-correctly, prioritizing a value from a source is not feasible, you can prioritize a dataset data with dataset precedence. please check the link below.

     

    https://experienceleague.adobe.com/en/docs/experience-platform/profile/merge-policies/overview#dataset-precedence

     

    ~cheers,

    NN.

      Harveer_SinghGi1
      Community Advisor and Adobe Champion
      Harveer_SinghGi1Community Advisor and Adobe Champion
      Community Advisor and Adobe Champion
      February 11, 2025

      Hi @gabrielana1 ,

      I don't think what you are trying to achieve is possible, the best you can do is prepare your ingestion payload based on the value of the edge profile attribute for the identities you are sending and then ingest the modified payload. So these could be the steps,

      This is not something that I've tried so you can do a POC first if this is something that you think can serve your use case.

      Cheers!

        kautuk_sahni
        Community Manager
        kautuk_sahniCommunity Manager
        Community Manager
        February 17, 2025

        @gabrielana1 Did you find the suggestions helpful? Please let us know if you need more information. If a response worked, kindly mark it as correct for posterity; alternatively, if you found a solution yourself, we’d appreciate it if you could share it with the community. Thank you!

        Kautuk Sahni
        Terms & ConditionsAccessibility statement

        Loading footer...