Skip to content

Commit a01cde3

Browse files
authored
Merge pull request #5898 from segmentio/Panandhan22-patch-3
Add MTU calculation during profile merge content
2 parents 85c49df + 3375c4b commit a01cde3

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 where a profile isn't merged with the parent profile due to exceeding the merge limit?
58+
Segment determines the Monthly Tracked Users (MTUs) count by the number of unique user IDs and anonymous IDs processed, regardless of how you manage these profiles in Unify and Engage. This count is taken as events are sent to Segment, before they reach Unify and Engage. Therefore, the creation of new profiles or the merging of profiles in Unify doesn't affect the MTU count. The MTU count only increases when you send new unique user or anonymous IDs to Segment.
59+

0 commit comments

Comments
 (0)