All of the subscribed customers and their information is stored here. There are four ways that you can filter people:

  • Properties

  • Events

  • Campaigns

  • Segments

Multiple filters can also be used simultaneously, regardless of what type of filter they are. For example, you can narrow down your audience by using two Property filters AND a Segment filter.) Once you’ve selected your filter parameters, you can compose a message directly from the audience you’ve narrowed down to. You can also export these results. Or save as a list or segment. You can apply lists or segments to campaigns later.


Clicking the user id will open the person's profile. The profile shows a summary of the following:

  • General info

  • Contact values with their status

  • Segments and Lists the person is a member of

  • An exact copy of each message the person has received

  • Journey

People can be manually unsubscribed using the option next to the relevant contact value.

Person Profile Photo Details

The way the profile avatar can be derived is by following the below instructions:

  • People can upload an attribute by name {{avatar_url}} to a given person’s profile to render images (or add as an explicit property using the interface).

  • Square images (aspect ratio 1:1) will render the best. Note that if {{avatar_url}} exists on a profile, the default behavior of lookup from gravatar is overridden.

Contact Preferences

Contact Preferences allow you to assign categories to contacts for specific types of mailings.

In the ZMP, a single person may have multiple email addresses or phone numbers. With Contact preferences, you can assign these categories so that you can use specific emails or phone numbers when messaging; for example, John uses john@zetaglobalemail.com for most emails but then uses johnbilling@zetaglobalemail.com for all billing emails.

Contact preferences allow you to ensure all billing messages goes to "johnbilling".

In order to apply these preferences to people, You will need to create “contact preferences” under Messaging within platform Settings:

  1. Create Contact Preferences in Settings: Settings → Messaging → Contact Preferences
    NOTE - 10 are allowed per account

  2. The following criteria will be present



Contact Type

The name by which you can select the contact preference for a campaign

Email Contact Property

The property you may import or write to that will save with this email contact.

Phone Contact Property

The property you may import or write to that will save with this phone contact

Another option is to Import Contact Preferences

  1. An example of a JSON Call - It should be a “preferences” array:

    {"user_id": "100","first_name": "john","contacts": [{"contact_type": "email","contact_value": "johndoee6001@zeta.com","subscription_status": "active","preferences": ["standard", "ohp", "jms"]},{"contact_type": "email","contact_value": "johndoe@zeta.com","subscription_status": "inactive","preferences": ["jms"]},]}

Info: Make sure at least one of the contacts has “standard” included in preferences, otherwise the user will only get the campaigns that have a preference selection.

When uploading a CSV, the pattern is to use “email_ohp”, “email_jms” etc., and supply the value of the email under that column.

During Campaign Setup

When setting up a campaign you will have a single option where the values will be the same as the Contact Type. Make sure the people are already created.

Open a specific campaign → Campaign Settings → Contact Preferences


The journey displays all relevant events the person has performed or that have happened to the user. This is useful for troubleshooting issues related to deliverability among others. This list is searchable using the search bar at the top of the journey. Further information about an event in the journey can be displayed by clicking on the event. All the information we have for a specific event will be revealed.


Information is stored for people as properties. Properties can be used for filtering, segment/list creation, and populated within the content.

There are two categories of properties:

  • Implicit

  • Explicit

Explicit Properties are what the client tells us. Examples would be the customer’s name or account id. Implicit Properties are what our system infers about a member. These properties show recent details of the customer including their last open timestamp, preferred browser, and last seen timestamp among others. Properties prefixed by “ns_” are derived from the most recent site activity as well as email opens and clicks.

Email Address Syntax Validation

Please see the details below for the default email address syntax validation

  1. One or more valid characters before '@'.

  2. A required '@' symbol.

  3. One or more valid characters after the '@'

  4. Valid special characters before the @ symbol include: .!#$%&'*+=?^_`{|}~-