Attributes
In addition of setting a custom user ID, an email address or overriding the language/region, you can assign attributes to your users, allowing you to improve your orchestrations targeting.

IMPORTANT - User IDs must be managed using our custom user ID implementation. - Email address must be managed using our email subscription implementation. - Region/language data must be managed using our custom region/language implementation. - Never use an existing tagging plan. Read our guide on custom data before tagging your app. - Newly tracked attributes are hidden by default. You will need to manually display them from the dashboard settings > "Custom data" tab.
Managing attributes
Before we get started on how to implement attributes, here are some rules you should know.
Naming
Attribute names are strings. They should be made of letters, numbers or underscores ([a-z0-9_]) and can't be longer than 30 characters (e.g. has_premium).
Values
Values must be any of the following types:
String, must not be longer than 64 characters and can be empty. For better results, you should make them upper/lowercase and trim the whitespaces.
Number
Boolean
Date, Since timezones are not supported, this will typically represent UTC dates.
URL, Must not be longer than 2048 characters and must follow the format
scheme://[authority][path][?query][#fragment]
.Array<String>, not longer than 25 items, only values of type String and must respect the string attribute limitations.
Methods
The profile attribute API is pretty straightforward:
You might be tempted to write helpers or loops that open and save many transactions in a row, with each transaction only doing one operation. Doing so prevents Batch from optimizing disk usage and network roundtrips, which impact your user's data plan and battery life. Please try to batch as many operations as you can in a single transaction.
Reading attributes and tag collections
Since Batch SDK v2, updating the user's data also update the profile's data to be accessible from your project scope. This mean the following APIs only read local data related to your installation and NOT to your profile.
You may also have noticed that APIs to set Tags or Tag Collections have been removed and replaced by array attributes. These methods are backward-compatible and array attributes are converted into tag collections to not break your implementation.
Reading attributes
Reading tag collections
Clearing installation data
Installation data can be cleared as following:
Last updated
Was this helpful?