Profile Fields

Overview

Profile fields define the data you keep about each registered user, such as their name, country, newsletter choices or the answers they give in forms. UniSignIn comes with common fields built in, and you can add your own.

Manage fields in Data Management > User Data > Data Schema.

Add a custom field

  1. Click New and give the field a Field Name, the label your team sees.
  2. Set the Field ID, the key used in forms, exports and integrations. Use lowercase letters, numbers and underscores, e.g. newsletter_weekly.
  3. Choose the Data Type (text, number, date, yes/no and so on) and the UI Type used when the field appears in a form.
  4. Turn on Is required in Form if readers must fill it in.
  5. Save the field.

Custom fields can be collected with Data Form and other experiences, and used as rules in Segments.

Fields found in profile data

Profile data you send through the JavaScript API is only used in segments and filters once it has a field. The Custom tab lists values that profiles send but that have no field yet, with how many profiles have each. Click Add field to create the field with its ID and type filled in. Values saved before the field existed are used again the next time each profile is sent.

Dictionaries

A dictionary is a list of values and the names shown for them, such as gb and United Kingdom. When you create or edit one in Data Dictionary, click Paste values to add many at once: one pair per line, the value then the name, separated by a comma.

Email subscription status

If a yes/no field records whether a reader subscribes to one of your newsletters, turn on Email subscription status for that field.

Readers with any of these fields set to yes count as email subscribers in the Audience Overview, including the Email subscribers card and the email opportunities. Each registered reader also gets an Email subscriber field you can use in Segments.

Fields written by an Email Subscription experience count automatically. Mark the fields that come from registration forms, imports or integrations yourself.

Email bounced and Spam complaint

Each registered reader has two yes/no fields about their email address:

  • Email bounced: yes when the address is suppressed because an email to it bounced.
  • Spam complaint: yes when the address is suppressed because the reader marked an email as spam.

Both are cleared when you remove the address on the Suppressed tab. Use them in Segments, for example to leave these readers out of a campaign. See Email.

Stay ahead in first-party data

Identity, consent, audience, and subscription insights for publishers. A few emails a month, no spam.

By subscribing you agree to our privacy policy.