Documentation / Product / Features / User Profiles

Whitelisting User Fields

As a matter of security, by default, Lytics never surfaces any of the user fields that are available on a user's profile outside of the Lytics Audiences they are currently a member of. This information is returned by the Lytics JavaScript tag by default in order to facilitate integrations with web personalization, Facebook, Google, etc. That said, any of the fields available on a user profile can be whitelisted, meaning they can be surfaced to the browser by the Lytics JavaScript tag in order to unlock various site personalization use cases.

What can I do with whitelisted fields?

Whitelisted user fields open up a variety of use cases only limited by your own data and creativity. This whitelisting technique is commonly leveraged to facilitate the pre-filling of forms, progressive profiling and a number of other custom, brand specific, use cases such as populating the item last added to cart or something related to a user's last visit.

How do I whitelist fields?

Fields can be whitelisted via the API section of your account settings. Simply visit<Your Lytics Account Number>/edit/api API Whitelist From here type in the name of the field you want to whitelist and click Add.

How do I access whitelisted fields?

Whitelisted field are returned alongside the current membership of Lytics Audiences via our JavaScript tag. For more information, visit the receiving data documentation. Specifically you will want to look at Getting the User’s Profile and Create a Callback sections.

These callbacks will return a data variable that contains an array of audiences as well as any additional whitelisted field data. For instance, if a customer was tracking the vehicles someone was looking to purchase, you might surface some of those fields and pre-fill some on-site searches for them.

By whitelisting the fields Last Make, Last Model, Last Color you might end up with a data value that looks something like this:

  "last_make": "audi",
  "last_model": "rx8",
  "last_color": "onyx",
  "segments": [

Looking for more? We have detailed documents on using this data with both our JavaScript tag and accessing entities from the server side of things.