Getting Started

In order to get started, there are a couple of pre-requisites to be aware of.


  • You must have an active Salesforce Audience Studio license
  • You must have Audience Studio OnBoarding included in your SOW

If you need to address any of the above, please contact your Salesforce Audience Studio account representative.


Account Setup

An I&I representative will work with you to setup your account:

  1. Account Creation - your DMZ account will be linked to your Audience Studio account to ensure all data gets sent to the right place.
  2. User Creation & Permissions - Please provide your I&I lead a document containing the following information for each user that should have access.
    1. Name
    2. Email Address
    3. Role
      1. User
      2. Admin
      3. Owner
  3. Notification Preference - indicate which users want to be notified of file status changes.
  4. Native Matching - Ensure you have accurately setup native matching for your account.


After you have been given access to the account you will receive an email with instructions on setting your password. If you do not receive anything, please check your spam folder, and then check with your Audience Studio account lead if you need further assistance.



There are three permission groups (roles) that users can fall into. As a rule of thumb, the majority of users should fall into the "user" group, a few should be "administrators", and a very select few of highly technical users should be "owners".


Account Permissions Overview:

Upload & View Files / Status (tick) (tick) (tick)
Manage Folders & Attributes (error) (tick) (tick)
Manage Access Keys (error) (error) (tick)


Onboarding Workflow

Once your account has been setup and you have access to the UI, you are ready to start using the product. The product is intended to be self service, but Salesforce resources are available to help address any questions you have.

The general workflow for onboarding a file follows a few main steps:

  1. File Creation - Client technical resources create a file that needs to be onboarded.
  2. File Specs Review - Audience Studio I&I (optional), client business stakeholders, and client technical resources align on the specs of the file (format, fields, data types etc.)
    1. Individuals who create the files should supply business owners and/or Audience Studio I&I team members with headers and data types for each field within the file. This will help ensure all things in the UI are setup correctly.
  3. Folder Creation - Create a folder where you will upload the data, and configure all the settings for how the system should handle the file (based on step 2). This can be done by technical or business users, but it must be done in the UI.
  4. Attribute Definition - Define what data is in the files you will upload and how you want them to appear in Audience Studio (based on step 2). This can be done by technical or business users, but it must be done in the UI.
  5. Test File Upload - Uploading a test file with 10k records is recommended as it will help surface any configuration errors that were not caught by automated QA.
  6. Final File Upload - Upload the files you want to onboard either using the UI, or directly to S3.


Quick Review of Routing

Once you have uploaded a file, the data will begin the onboarding process. Depending on how you set things up, the file will go through one or many of the following stages to find matches for users in the supplied file. This process is what we refer to as "routing".

  1. Native Matching - Match assets supplied by your 1st party footprint.
  2. Audience Studio Proprietary Matching - A collection of Audience Studio purchased assets with which matches can be made. 
  3. Vendor Matching - A collection of integrated partners with which Audience Studio works to onboard data.

The routing process is executed in the order above unless otherwise specified in the folder or organization configuration. 


All subsequent documentation will define in detail how to execute on the process defined above.

Have more questions? Submit a request


Article is closed for comments.