When Localytics reports “[Unspecified]” in the dashboard for a specific Event Attribute, it means Localytics has received a NULL value for that Event Attribute. In other words, when the Event was triggered, no known value had been assigned for that Attribute in your app. We report this as “[Unspecified]” to distinguish from cases where a customer might prefer to deliberately pass the value of “NULL”.
We recommend your developers provide a default value for the Event Attribute such as “No Value Set or N/A” and then, when the value that you’d like to assign becomes known, you overwrite with the known value.
If you’re expecting a known value and seeing “[Unspecified]” it is likely that your developers instrumented the Event differently than expected or intended. In these cases, we advise that your developers review the instrumentation and perform quality control to ensure that they have sequenced code correctly and considered all possible behavioral paths.
Another potential scenario is when an Event attribute is newly implemented. For example, consider a scenario in which your app started tracking a new attribute as of a new app version released yesterday. If you were then looking at historical data prior to that date (eg. the last 7 days), the dashboard would be looking for a value for that attribute for the entire time range; however, those values would inherently not be available because they weren’t collected during most of that time, so they would be reported as Unspecified.