Self Serve First Party Imports

The self-service first party import file feature empowers customers to bring offline user data into Salesforce Audience Studio to contribute to a more comprehensive view of their customer. Offline data can include CRM data, data from other technology partners like Email marketing tools, and consent data from a CMP.

With this feature customers can surface a dashboard overview of the offline data connectors. Highlights of the feature include:

  • Self-serve first party data import of user attributes, page attributes, transaction data, platform segments, consent data (capabilities may vary by Audience Studio Edition).
  • Ability to import data keyed off of different identifiers - Salesforce Audience Studio ID (KUID), Mobile Device ID (MAID), Hashed Email, First-Party ID and Other (capabilities may vary by Audience Studio Edition).
    • If First-Party ID (or specified bridgekey within First-Party ID selection) does not appear for you, please reach out to the Support team.
    • Hashed Email should only be used for HEM-based ingestion or HEM Onboarding
    • Other should only be used for OTT IDs, not a First-Party ID
  • In addition to Audience Studio format, enhancement to support CSV files, including flexibility in selecting the separators.
  • A dashboard view showcasing summary status of all offline data connectors.
  • The ability to surface detailed information on a specific connector, including number of records imported, validated, matched and consented.

How To Use the Self-Service First Party Import File Feature

Before getting started, please review the Data Ingestion Spec as a template for file imports into Audience Studio.

In the main menu of the UI, navigate to Manage > Data Capture Sources.

If you are importing offline data files, select the Offline Files header to view the Connector Dashboard. Here, you will see a summary for configured data connectors, including:

  • Data type (user, page, transaction, platform or consent data)
  • Received records (# lines in the file)
  • Available records (records Audience Studio has received consent for)

*Consent imports should be uploaded at least 1 day prior to the import file.

Here, you can start a new connector for a new import or select an existing active or inactive connector under the Offline Files source. You can also disable a connector from this screen to stop an existing import.

Click into an offline data connector for a more detailed view, including:

  • Received records: Number of lines in the imported files
  • Valid Records: Number of lines that were imported with no errors
  • Matched Records: Records that have been matched with a KUID
  • Available Records: Records that we have received consent for
  • A graph visual of the metrics
  • Metrics for previous imports
Please note, if your import is keyed off of an identifier other than KUIDs or MAIDs (e.g. a Bridge Key**) in your instance, the Matched Records count may appear significantly higher than Received Records and Valid Records count. A Matched Records count includes the multiple KUIDs that are tied to your first party ID in the import.
** A Bridge Key is an identifier to tie one or more KUIDs to devices. Look at User Identifier Definition for more information.

How To Create a New Connector

  1. In the Data Capture Sources dashboard, select New Connector under the Offline Files source.
  2. Enter a name for your connector in the top left of the screen.
  3. Select the Data Type that will be uploaded via this connector. Click Next.
  4. Select the Identifier Type, or the ID associated with the connector. Note: Salesforce Audience Studio only supports a single ID per file; users cannot have multiple ID types in the same file. Click Next.
  5. Select the Data Refresh Handling setting to specify how new files should be processed. Click Next. There are two options for the data refresh setting:
    1. Append: Files will be imported incrementally (each new file be added to existing imported files). This option also requires a look back window to be specified in order to define how far back the system should look for files (when the users expire). For example, if you enter a look back window of 30 days, the system will only look for the last 30 days of files, no further.
    2. Overwrite: Each new file will be a full refresh of the data so all users will be updated. (Note: This setting requires a look back of 0 days.)
  6. Enter the File Location. The file location must be within your pre-provisioned S3 bucket. While there is flexibility in the subfolder name and the number of subfolders, there must be one subfolder in the pre-defined data format (manually type "YYYY-MM-DD" as a placeholder) so the system can identify when a new file is available on a given day in the S3 bucket. Click Next.
  7. Select the File Compression Type. Click Next.
  8. Select the File Format. You can choose between the proprietary Krux format or CSV formats. Click Next.
  9. For CSV format, specify the Delimiter if it differs from the predefined delimiter. Enter the attributes from the file(For e.g: name for Segment ID column) and Click Next.
  10. Enter one row below for each column in the imported file. First, enter the attribute name as it should display in the Segment Builder. Then, enter the attribute type (identifier, user attribute or ignore to disregard the field). Ensure that the rows are entered in the same order as the columns in your offline file. Click Next.
  11. Click Create Connector. You will be brought to the Connector Summary where your new connector will appear. Note, imports run once per day. As such, your connector summary will populate the following day after it is created.
  12. When you're ready to import a file, add the file to the S3 bucket with the date folder in the YYYY-MM-DD format. Audience Studio will look for today's date minus one day.
Have more questions? Submit a request


Please sign in to leave a comment.