fix: ensure user attributes are applied before proceeding with Rokt execution#585
Merged
Mansi-mParticle merged 1 commit intodevelopmentfrom Jun 17, 2025
Merged
Conversation
b0b4ff0 to
41014f2
Compare
rmi22186
approved these changes
Jun 17, 2025
mparticle-automation
added a commit
that referenced
this pull request
Jun 17, 2025
Collaborator
|
🎉 This PR is included in version 5.69.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
Instructions
developmentSummary
It uses a callback with getUserAttributes to wait until the data is ready.
This helps avoid problems where Rokt tries to use user info before it's updated.
Testing Plan
Reference Issue (For mParticle employees only. Ignore if you are an outside contributor)