🐞 fix(profile): Reverting to the most recent profile as primary source of truth#105
Merged
Charles Hudson (phobetron) merged 1 commit intoJan 7, 2026
Conversation
Charles Hudson (phobetron)
requested review from
Maroun (maroun9t) and
Maximilian Rauh (maxrawlinger)
as code owners
David Nalchevanidze (nalchevanidze)
approved these changes
Jan 7, 2026
Charles Hudson (phobetron)
deleted the
NT-1769_reverting-id-source-precedence
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
After talking with Matty, we may need to talk over some of the pitfalls of the order of precedence with anonymous/profile IDs. It seems that the change to the cookie domain may have fixed the previous E2E implementation issues (if CI passes here) so we could at least revert to the precedence that is closer to what is currently implemented in
experience.js.[NT-1769]