Skip to content

Commit a575491

Browse files
Update faqs.md
Added the Faq to unify section and added some clarity
1 parent aced868 commit a575491

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

src/unify/faqs.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -54,6 +54,9 @@ No. As the Identity Graph uses ExternalIDs, they remain for the lifetime of the
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/).
5656

57+
## Can I remove a trait from a User profile?
58+
To remove a trait from a user profile, you can send in an identify event with null as the value for the trait in the traits object from one of the connected sources. E.g. `"traits": {"trait1": null, ..}, ...`. Note that sending in an empty string (i.e. `"traits": {"trait2": "", ..}, ...` will update the trait to be an 'empty' string, and will not remove the trait from the user profile.
59+
5760
### How does profile creation affect MTUs, particularly where a profile isn't merged with the parent profile due to exceeding the merge limit?
5861
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.
5962

0 commit comments

Comments
 (0)