Why Is the New Data Type Not Reflecting in Data Management?

​

Problem

The Data management section does not reflect newly updated data types for user or event attributes. Segmentation still uses the old data type.

​

Solution

Perform the following steps:

1. Update the data type: Go to Settings > Data management, edit the user or event attributes and update the desired new data type.
2. Send test values: Update the attribute values for a specific test user to send sample values with the new data type to a test user profile.
3. Verify reflection: After MoEngage processes values in the new data type, the updated type will be reflected in the Data management dashboard, as well as in Segmentation and throughout the system.

​

Why Segmentation Returns Fewer Users After the Change

Because the existing data keeps its original data type, the attribute holds a mix of both types. A query evaluates the attribute as one data type at a time, so a segment or analysis filtered on the new data type matches only the values ingested since the change. The count is low, or zero, until enough new data arrives — this is the usual reason a segment count appears to drop straight after a data type change. To match the full history while both data types are present, add one condition per data type and combine them with OR — the attribute as the new type for recent values, OR the attribute as the previous type for older values. Relative date operators, such as “in the last 7 days”, work only on the Date data type, so the condition covering String-stored values needs an absolute value or range. Where the full history has to be matched with relative dates, re-ingest the historical values in the new data type instead. For the complete behavior and its effect on value suggestions, see Set Allowed Data types.