mParticle imposes certain limits on incoming data in order to protect the performance of both the mParticle dashboard and your apps. This includes limits around the length of individual data points, such as event names, how fast mParticle can receive data, and how many unique data points a workspace or account can have.
The following table shows the limits for inbound batches.
Incoming Event Batches
| Resource | Limits | Details |
|---|---|---|
| Event name length | 256 characters | SDK will log an error and the event will not be uploaded. For S2S data, names exceeding the limit will be truncated. |
| Max unique attributes per event | 100 | SDK will log an error and upload the event with no attributes. |
| Event attribute name length | 256 characters | SDK will log an error and no attributes will be set for the event. S2S will truncate the attribute name. |
| Event attribute value length | 4096 characters | SDK will log an error and no attributes will be set for the event. |
| User attributes per event batch | 100 | SDK will allow only 100 attributes per user and will log an error you attempt to create additional attributes. |
| User attribute name length | 256 characters | SDK will log an error and no attributes will be set. |
| User attribute value length | 4096 characters | SDK will log an error and no attributes will be set. |
| User attribute list | 1000 Entries | SDK will log an error and no attributes will be set. |
| User attribute list entry length | 512 characters | SDK will log an error and no attributes will be set. |
For additional information on mParticle's service limits, please visit our docs site.