feat: include identity info in pseudo identity event payloads#95
Open
khushi1033 wants to merge 1 commit into
Open
feat: include identity info in pseudo identity event payloads#95khushi1033 wants to merge 1 commit into
khushi1033 wants to merge 1 commit into
Conversation
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
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.
Summary
Adds
user_identitiesanduser_attributesto individual identity event payloads (login,logout,modify_user,identify). Previously these fields were intentionally omitted from individual events since they exist onmparticle_batchin the metadata envelope. The requirement has changed and events need to carry this context individually for how they are consumed downstream.Both fields are placed inside
event.data(event-specific payload), following the GatewayTransactionEventcontract.user_attributesis snapshotted at callback time via the existinghandleIdentityCompleteordering, so each event reflects the user state at the moment of the identity transition.user_identitieshas the emailsha256 key remapping applied before being set on the event.Testing Plan
What has been tested
212/212 unit tests passing. Updated existing tests to assert
data.user_identitiesanddata.user_attributes. New tests added covering:Screenshots
Before

After
