Adding a timestamp to streamed profile data | Adobe Higher Education
Skip to main content
O
Olivier_Blonste
Level 2
February 2, 2024
Besvarat

Adding a timestamp to streamed profile data

  • February 2, 2024
  • 2 svar
  • 1393 visningar

We're sending Profile data to an AEP Profile dataset.
We're using the AEP HTTP API to stream this data to the Profile dataset.
Profile datasets do not require a timestamp, as opposed to event datasets.
However, could we add a timestamp and ensure that the AEP will ingest our payloads based on the timestamp?
We're running into issues where payloads get ingested in the wrong order.

Thank you!

    Det här ämnet har stängts för svar.
    Bästa svar av Manoj_Kumar

    Hello @olivier_blonste 

    Consent should be overwritten when changed.

    I am assuming, you are saving behaviour as an event. In this case, the timestamp attribute can be used.

     

     

    2 svar

    arpan-garg
    Community Advisor
    arpan-gargCommunity Advisor
    Community Advisor
    February 3, 2024

    Hi @olivier_blonste - Whats the usecase behind this? You want to have the profile with the latest timestamp in the profile store?

     

    Thanks

      O
      Olivier_BlonsteSkribent
      Level 2
      February 4, 2024

      Hi @arpan-garg ,

      It's "consent" data sent every time a user toggles the switch. We noticed that some users "like" to toggle that switch back and forth very quickly and sometimes several times in a row.
      As you said, we would like RTCP to have the latest user's selection, "on" or "off", whatever was the last option selected by the user.
      Because of this issue, as you can imagine, we will end up running some marketing activities to users that they did not opt-in for...or vice versa, which could lead to Legal issues.

      Thank you!

        Manoj_Kumar
        Community Advisor
        Manoj_KumarCommunity AdvisorSvar
        Community Advisor
        February 5, 2024

        Hello @olivier_blonste 

        Consent should be overwritten when changed.

        I am assuming, you are saving behaviour as an event. In this case, the timestamp attribute can be used.

         

         

        Manoj  | https://themartech.pro
          NimashaJain
          Adobe Employee
          NimashaJainAdobe Employee
          Adobe Employee
          February 5, 2024

          @olivier_blonste Did you find the suggested solutions helpful? It would be great if you can  mark the answer as correct for posterity. If you have found out solution yourself, share it with wider audience in the community.

          Villkor och bestämmelserAccessibility statement

          Loading footer...