Custom Profiles

You can use Custom Profiles to collect additional information about your users. Custom Profiles are sent to Localytics via the Localytics SDK or the server-to-server API.

Use the Profiles API to send information from inside and outside your app to Localytics. Then, use the Custom Profiles you sent to target users for in-app and push messaging campaigns.

You send Profiles data to Localytics as a key/value pair. A key/value pair is a set of two linked items: a unique identifier, or key, and a value. For example, if you want to send information about users who are female, you could send Localytics a key/value pair that includes the key gender and the value female. If you want to send information about a user's age to Localytics, you could send the key age and the value 65.

You can send information like last in-store purchase or web article viewed, and then use that information to target users across all their interactions with your organization. For example, if your research shows that people of different genders prefer different types of information about weight loss, you could send in-app messages to users whose gender is male. If your research shows that people of different ages respond better to different types of push offers, you could send push messages to users whose age is greater than 40 and whose age is less than 65.

Localytics provides a simple REST API to store and retrieve Profiles information about your users. As a Localytics customer, your organization has access to a private Profiles database. Each app also comes with its own Profiles database. You should store organization-wide data that is useful to all apps, like demographic information, in your org database. Store app-specific data, like high scores or favorite teams, in your app databases.

Profiles attributes can be numeric integers or strings of 255 characters or less. Dates must be sent as strings in the format YYYY-MM-DD. Any data sent as strings must be in quotes. You can send groups of numbers, or arrays, but you must send all values when setting that profile attribute, as each set overwrites existing Profiles information.