Understanding Lytics / Product Documentation / 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, by default, returned by the Lytics JavaScript tag 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 Lytics customers up to a variety of use cases only limited by your own data and creativity. Many of our customers have leveraged this whitelisting technique 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 relate to their last visit.

How do I whitelist fields?

At the moment whitelisting is managed by Lytics Customer Support. This ensures the safety and integrity of customers data. Simply speak with your customer rep and they can help you surface whichever fields are necessary via our JavaScript tag.

How do I access whitelisted fields?

Whitelisted field are returned along side the current membership of Lytics Audiences via our JavaScript tag. We have some basic documentation related to receiving data from our tag. Specifically you will want to look at Getting the User’s Profile and Create a Callback.

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 whitelisted 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": [
    "all",
    "potential_buyers",
    "high_momentum"
  ]
}

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