_id deduplication functionality for non profile enabled datasets | Community
Skip to main content
TylerKrause
Adobe Champion
TylerKrauseAdobe Champion
Adobe Champion
October 30, 2025
Solved

_id deduplication functionality for non profile enabled datasets

  • October 30, 2025
  • 1 reply
  • 146 views

Hey all! As I believe many of you know the functionality of _id deduplication is specific to Profile store ingestion. We're ingesting events for reporting and analysis off of one source that is profile enabled. We're using another that has additional specific parameters to power the actual transactional communication in AJO. The method of delivery of our source into AEP uses an 'At Least Once' connection so relying on idempotence of that source isn't possible. Outside of having a check for duplicate events in a Journey condition, does anyone have any thoughts on a solution for avoiding duplicate records flowing through the journey?

Best answer by bjoern__koth

Hi @tylerkrause 

different from profiles, events are immutable and cannot be updated.
If you feed in an event with the same _id, to my knowledge, it will still end up in the data lake but the added data wont be available in your profile.

 

 

1 reply

bjoern__koth
Community Advisor and Adobe Champion
bjoern__kothCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
November 1, 2025

Hi @tylerkrause 

different from profiles, events are immutable and cannot be updated.
If you feed in an event with the same _id, to my knowledge, it will still end up in the data lake but the added data wont be available in your profile.

 

 

Cheers from Switzerland!
    Terms & ConditionsAccessibility statement

    Loading footer...