SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site, support.twilio.com, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to help.twilio.com, where you can continue to find helpful Support articles, API docs, and Twilio blog content, and escalate your issues to our Support team. We encourage you to update your bookmarks and begin using the new site today for all your Twilio Support needs.

Segment MTU counting when anonymousId is an email address

Question

In Twilio Segment, if source events have no userId and use the user’s email address as anonymousId, will Segment Unify merge profiles and will this inflate MTU counts?

 

Product

Twilio Segment

 

Environment

Segment Console

 

Answer

Segment treats anonymousId as an identifier, not as an email trait. If multiple events use the same anonymousId value, those events can be associated with the same profile according to the workspace’s identity resolution settings.

MTU billing is not based on the number of profiles shown in Unify or Engage. Segment counts unique userId values, then adds unique anonymousId values that were not associated with a userId during the billing period. Repeated events with the same anonymousId should not each count as a separate MTU.

For the most reliable identity resolution and MTU behavior, sources should send a stable userId whenever possible.

 

Additional Information 

For additional details about MTU billing, throughput, and identity resolution, see the following Twilio Segment documentation:

Have more questions? Submit a request
Powered by Zendesk