Track additional data about user actions

Use event attributes to track additional data points about your events. For example, your article_read event tag might include a section attribute.

Event attributes are details that describe the action taking place. Attributes are passed as key/value pairs that are contextual to the specific event being tagged. For example, a Product View event could have attributes tracking the product category, whether it was shared, how long the user spent viewing it, and anything else that helps you understand user behavior.

When tagging an app, you can think about events and attributes in terms of an English sentence. If you want to tag a user action or “verb,” then it's probably an event: Article Read, Game Played, Logged In. If you want to tag something that describes an action or “adjective,” then it's likely an attribute: Article ABC, Level 4, Via Facebook.

You can send attributes to Localytics as either strings or numbers. If you send raw numbers, Localytics will automatically bucket the numbers into equally-sized groups to be viewed in the Dashboard. You can then filter numeric attribute reports by greater than, greater than or equal to, between, less than, less than or equal to, and equal to any particular value. Numeric attributes have additional metrics in the Dashboard, including Average Value, Total Value, Maximum Value, and Minimum Value. You can then break the numeric attribute out by any other built-in dimension, custom dimension, or attribute.

Numeric attribute data can have a maximum of 13 digits before the decimal and up to 5 digits after. Negative numbers are permitted, so the range available is -9,999,999,999,999.99999–9,999,999,999,999.99999.

Learn about numeric event attributes in the Dashboard.

Note: For Roku, you may need to keep a session alive. This method is automatically called on TagEvent and TagScreen. Depending on usage, you can call this method in event loops.

m.LL.KeepSessionAlive()

Best Practices

Each event can have up to 50 event attributes. Event occurrences may be split or filtered by attributes, which makes them very powerful. To get the most value out of attributes, we recommend the following:

Attributes should be named with lower case naming so they are not confused with events
Attributes are stored as strings and are displayed in charts. For best results, maintain less than 100 attribute values.
Continuous or infinitely distributed values, such as file sizes, available memory, or time in milliseconds should be rounded or bucketed.
Never record binary values in an attribute. Consider an "is logged in" attribute. If the values "yes" and "no" are recorded then when trial accounts are added the values become "yes", "no" and "trial" which can be confusing. Instead, name the attribute "login state" with initial values "logged in" and "not logged in."
It is possible for different occurrences of the same event to have different attributes. For example a network event may have a "result" attribute which is usually "ok" but when it is "error" a "network error" attribute may also be present.
If you find the same attribute appearing in all of your events, promote that attribute to a custom dimension.
Ensure default values are specified for attributes. If an event is uploaded to Localytics with no value for an attribute, it will show as [Unspecified] in the dashboard and affect reporting.