Skip to content

Commit 3a5d4c9

Browse files
authored
MTU calculation during profile merge, especially when the merge limit is exceeded.
1 parent 5122dce commit 3a5d4c9

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

src/unify/faqs.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,4 +53,7 @@ No. As the Identity Graph uses ExternalIDs, they remain for the lifetime of the
5353

5454
### Can I delete specific events from a user profile in Unify?
5555
No. Alternatively, you may delete the entire user profile from Segment using a [GDPR deletion request](/docs/privacy/user-deletion-and-suppression/).
56-
56+
57+
### 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?
58+
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.
59+

0 commit comments

Comments
 (0)