What are lists? 

Lists are a tool to manage a specific collection of accounts or contacts to target in your experiences. Lists can be reused across a variety of experiences and over time. For instance, you may create a target account list, a new business account list, a target account list, and more.  

Types of lists

There are two types of lists within Mutiny.

Contact Lists

Create a list of people. Best for contact level personalization and 1-1 distribution (email, inmail, etc.).

Account Lists

Create a list of companies. Best for account level personalization and broad distribution (inbound, landing page, etc.).

There are three ways to build a list within Mutiny. 

Define a list from existing data

Mutiny combines all existing data from your integrations (Salesforce, Hubspot, etc.) and past CSV uploads, so you can define a comprehensive target account list. 

Note: to use this option, you must have at least one data source for your Accounts, for example past CSV uploads, Hubspot, Salesforce, etc.

Upload a list from CSV

Upload a CSV list of accounts and any additional, relevant data that is not already available within Mutiny (e.g., Industry, Current Customer vs. Prospect, etc.).

Import Salesforce Campaign Members

Import Salesforce campaign members as the source of your list. Note: If you are creating an account based list and your campaign includes accounts and contacts or leads, the contacts and leads will be ignored.

Dynamic vs. Static Lists

Dynamic

Dynamic lists will automatically update over time. Records will be added or removed from the list as the source properties change. Lists defined from existing data or imported Salesforce campaign members can be dynamic. 

Static

Static lists do not update. A static list's members represent a snapshot in time of the list. All list types can be static. 

Define a list from existing data

Step 1 – Add filters

To define a list, you must add at least one filter. You can choose to filter accounts by any property that has been imported into Mutiny. These properties will have been imported through a data integration (i.e. Salesforce, Hubspot, or Segment), the Mutiny script, or a previous CSV upload.

Note: lists currently have a maximum size of 10,000 members; you will not be able to create a List unless the filters you have defined match fewer than 10,000 accounts.

Step 2 – Name, choose if dynamic or static, and save

The final step is to name the list and choose the list type (Dynamic or Static). Dynamic Lists are designed to automatically update over time as account properties change while Static Lists represent a point in time snapshot of the accounts that matched the defined filters.

Uploading Lists using CSV files

Click the Upload a list option.

Step 1 – Upload your CSV

Example CSV format

CSV uploads for accoun lists must have a “Domain” column. CSV uploads for contact lists must have an "Email" column. The “Domain” column is used as a unique identifier for an account and must be a valid link to the account’s website. The "email" column is used as a unique identifier for a conatact and must be a valid email.

A CSV upload may also include extra columns (such as a cleaned up Company Name, industry, title, or any other data for use in personalization) that will be merged into the account record.

Warning: Mutiny will store CSV data for future use across the app. Fields (i.e. CSV columns) that have the same name as an existing field in Mutiny will be overwritten. For example, if you sync an "Account Owner" field from Salesforce and have an "Account Owner" field in this CSV, Mutiny will use the CSV value going forward. We do not recommend overwriting any fields that are dynamic and are already syncing from the source of truth (e.g. Salesforce, Hubspot, Marketo, etc.).

Step 3 – Name and save

The final step is to name and save the list. The CSV will be processed asynchronously so you might notice a delay depending on the size of the upload or if you navigate away from the page quickly.

Importing Lists from Salesforce

Click the Import from Salesforce option.

Step 1 – Find your Salesforce Campaign

You can locate your Salesforce Campaign by name. The Salesforce Campaign should contain at least one relevant member.

Step 2 – Select refresh frequency and save

The final step is to choose a refresh frequency. This is the rate at which Mutiny will attempt to refresh list members if the Salesforce Campaign members happen to change (i.e. an account is added or removed from the Salesforce Campaign). The list members can also be refreshed manually from the list details page.

Managing your Lists

Finding your List

Navigate to the lists overview table by clicking the Lists button in the navigation bar.

You can search for a list by name in the lists overview table. Click the table row to access the List details page.

On this page you’ll find the list members and links to any experiences targeting the list.

You can search for list members, download your list in CSV format, and edit which columns to show in the table.

Making changes to your list

Renaming a list

To rename your list click Edit list > Rename.

Updating list members

To make changes to the filters for a dynamic list click Edit list > Update members.

Note: It is not possible to add members to or remove members from a static list

If the list was created from a Salesforce Campaign you can click Edit list > Edit in Salesforce to make changes to the list members directly in Salesforce.

Cleaning account properties

Example CSV upload for data cleanup

To cleanup properties for members in your list click Cleanup properties and upload a CSV with the desired changes. You can use this feature to fill in blank properties, override existing property values, and add new properties to the accounts in your list.

Warning: Mutiny will store CSV data for future use across the app. Fields (i.e. CSV columns) that have the same name as an existing field in Mutiny will be overwritten. For example, if you sync an "Account Owner" field from Salesforce and have an "Account Owner" field in this CSV, Mutiny will use the CSV value going forward. We do not recommend overwriting any fields that are dynamic and are already syncing from the source of truth (e.g. Salesforce, Hubspot, Marketo, etc.).