Add MTU calculation during profile merge content #5898
Merged
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.
… is exceeded.
Proposed changes
How does profile creation affect MTUs, particularly in scenarios where the profile is not merged with the parent profile due to exceeding the merge limit?
The Monthly Tracked Users (MTUs) count is determined by the number of unique user IDs and anonymous IDs that Segment processes, regardless of how these profiles are later managed in Unify & Engage. This count is taken as events are sent to Segment, before they reach Unify & Engage. Therefore, the creation of new profiles or the merging of profiles in Unify does not affect the MTU count. The MTU count would only increase if new unique user IDs or anonymous IDs are sent to Segment.
Merge timing
Related issues (optional)