Product Enhancement: FIFO enforcement on Profile Ingestion | Community
Skip to main content
J
j_goetze_5000
Level 2
January 22, 2026

Product Enhancement: FIFO enforcement on Profile Ingestion

  • January 22, 2026
  • 3 replies
  • 78 views

When ingestion data via HTTP API to profile, FIFO is not guaranteed, resulting in potentially incorrect data being stored on the Profile. 
The enhancement request is to make this an optinal feature when creating a source connector or dataflow. It could be a toggle. The trade-off would be increased processing time, but I would rather have correct profile data a bit slower, than fast updates that taht eventually prove incorrect

    3 replies

    SG14_97
    SG14_97
    Level 3
    February 2, 2026

    ​@j_goetze_5000 This is very interesting quick question did you see this behavior in the UPS as well? in my experience I didn’t face this and updates were streamed to Profile within ~5/10 mins, or is it based on the micro batching in the data lake flows you noticed this.

    It should indeed be compliant with the recent updates only.  

    J
    j_goetze_5000Author
    Level 2
    February 18, 2026

    I did a test with ingesting via the HTTP API . Sent in 5 events with different values to be able to distinguish them. The last sent was NOT the one that persisted on profile, due to the async processing

      arpan-garg
      Community Advisor
      arpan-gargCommunity Advisor
      Community Advisor
      February 18, 2026

      Hi ​@j_goetze_5000  - I never noticed it , the profile in UPS is processed in the order of the requests, can you please tell me how you came to an understanding that FIFO is not guaranteed.

      J
      j_goetze_5000Author
      Level 2
      February 18, 2026

      ​@arpan-garg  The documentation states that ingestions via HTTP API is processed async, meaning that ingetions to profile (schema) has the potential to not (finish) processing in the same order as they are ingeted. Since profile does not have a required timestamp as experienceEvent does, at you cannot force one upon it. Say a user changes something on their account multiple times within seconds. Something that pertains to the same profile attribute. There is no guarantee their processing would be completed in the order they are happening. It might, but it also might not. 

      J
      j_goetze_5000Author
      Level 2
      February 18, 2026

      ​@Sga1 ​@arpan-garg 
      I think the reason this is not often registered, is that that is fairly rare that user behaviour happens that would cause it. However, in my business, it can and it does. If there is “sufficient” time between the ingested, it is unlikely that processing will not be completed in the correct order. However, if they happen within seconds, the risk is definitely present. 

      Terms & ConditionsAccessibility statement

      Loading footer...