What Are the Key Points of the MoEngage Data Tracking Policy?

This article explains the key points of the MoEngage data tracking policy. These policies help you make the necessary adjustments during the initial implementation stages.

​

Instructions

1. MoEngage accepts the following datatypes for attributes:
   • Integer, Float, Double, Long, Boolean, String, Datetime, Array<Long>, Array<Int>, Array<Double>, Array<Short>, Array<Float>, Array<String>, Object, Array of Objects.
2. Each array element can be a maximum of 512 characters, with up to 50 elements in each array.
3. Attribute values sent as dictionary data types will be rejected.
4. For attributes of the datetime data type,
   • When sending data through MoEngage Data APIs, use the ISO 8601 date format (for example, 2020-05-31T16:33:35Z).
   • When sending data through SDK, use the SDK’s date functions.
5. If an attribute value is a URL and exceeds the 512-character limit, it will be rejected to prevent issues with image and URL personalization.
6. Arrays must be homogeneous (all values in an array must be of the same datatype). Data typecasting is supported at the array level.
7. Event names used with periods create an additional space. For example, event.name will be ingested as event. Name (with a space). It is recommended to use “_” (hyphens) instead of ”.” (period).
8. You can create up to 100 unique event attributes for a single event.
9. The following table lists the limit values for events and attribute names:

   Key	Character Limit	Limit Breach Handling
   Event name length	200	Store the first 200 characters only.
   User attribute name length	200	Store the first 200 characters only.
   User attribute value length	512	Store the first 512 characters only.
   Event attribute name length	200	Store the first 200 characters only.
   Event attribute value length	512	Store the first 512 characters only.

For more information, read Data Tracking Policies.