Human Readable Names (Import / Export) Tool


This documentation will cover off on how to use the import/export UI in the Salesforce DMP. You can find the tool by clicking "Manage → Upload / Export" in the UI.

Workflow & Expected Outcomes

When used correctly,  this tool will help you assign a different name for an attribute value for the following attribute types:

  • Page Attributes
  • Media Attributes

Please note that this product is NOT intended to allow you to upload NEW attribute values. The general workflow for updating the name that is seen in the UI is as follows:

  1. Export name mappings for a specific attribute
  2. Update attribute name mappings
  3. Upload updated name mappings
Timing Considerations

Once you have uploaded the file you should expect to see a status update within 5 minutes of the upload. Additionally, the system will ALWAYS use the most recent information it receives. For example, if you upload mappings for the same IDs twice in the same day, the UI will reflect the most recent upload submitted. Once the process is finished you can expect to see values updated in the Segment Builder immediately, while Campaign Performance reports will update next day.

API Integrations

Some attribute value names are updated using an API. For example, DCM has an API that is available to update names for some media attributes (eg. campaign ID). For customers that are using this tool in conjunction with an API it is important to understand that the system always shows the most recent mapping it receives (regardless of if that comes from the UI or the API). For example, if you have a campaign ID (123) with a mapping of "Campaign 6" that came from the API at 8AM, but changed it to "Campaign Six" using the UI at 9AM, the UI would show "Campaign Six" starting at 9AM. However, because the API is queried every single day, the value would return to "Campaign 6" the next day.

It is not recommended to use this UI to update IDs that are being addressed through API integrations.

Upload Steps:

1.  Export Attributes

It is best to start an update by exporting all the attribute values that exist for an attribute.

Within Salesforce DMP, navigate to Export → Export Type → Attribute Name.  In the Upload & Export Tool screen, select Media Attribute as the Export Type.  In the Attribute Name field, select the attribute for the values you wish to export.

You may choose to export CSV or Excel format. Files must be uploaded as CSV, but Excel files may be modified and then saved as CSV format prior to uploading modifications.

2.  Update Attributes

Once you have exported your attributes you can use the downloaded file to make updates.

There are known issues with using Microsoft Excel's rich formats to make these updates. If using Microsoft Excel to modify a CSV file, the file format must be .csv and numeric values must be plain numbers with no commas or scientific notation.  The media attribute name column accepts unicode values and spaces.

Google Sheets may also be used to perform data updates.

Recommendations: Export via CSV if you plan to modify the file in plain text or you plan to import it to Google Sheets. If you plan to modify using Excel, export via Excel format.

Using Google Sheets to Modify CSV Export

Once you have a downloaded CSV file, import it into Google Sheets.

Within Google Sheets, navigate to File→ Import → Select File

You can make all updates to human readable names in Google sheets, and save the file as a CSV to import back into the UI.

Using Excel to Modify CSV Export

Open a new Microsoft Excel spreadsheet.

On the Data tab, in the Get External Data group, click From Text.

Browse for the csv file you want to import, select it and click the Import button (or simply double click the .csv file).

The Text Import Wizard will appear and you follow its steps. 

    • Step 1 Configurations:
      • File Type - Delimited
      • Start Import at row - 1
      • File Origin - 65001 : Unicode (UTF-8)
      • My data has headers - Yes
      •  Step 3 Configurations:
        • All columns - Text
      • Step 2 Configurations:
        • Delimiters - Comma
        • Treat consecutive delimiters as one - No
        • Text qualifier - None

Choose the destination for the imported data, either an existing or a new worksheet, and click OK to finish importing your CSV file to Excel.

Save your file as a CSV and upload it to the DMP UI.

Scientific Notation Issues

We have experienced cases in which the attribute value IDs are converted to scientific notation which ultimately does not successfully re-import into the DMP. To address these issues in Google Sheets you must convert the attribute value number format:

        1. Highlight Attribute Values → Format → Number→ More Formats → Custom Number Format
        2. Select 0 as the format and apply.

3.  Upload Attributes

  1. Three column headers in the following order and format: MEDIA_ATTRIBUTE_NAME, MEDIA_ATTRIBUTE_VALUE_CODE and MEDIA_ATTRIBUTE_VALUE_NAME. Any other order or more columns will result in an ingestion failure.
  2. Column MEDIA_ATTRIBUTE_NAME can be any one of the following values: Brand, Placement, Campaign, Site, Ad, Creative or ConfID. The value is case sensitive; all uppercase or all lowercase values will result in an ingestion status failure.
  3. If using a plain text file, column values should be encapsulated with (“ “) quotation marks.

Once prerequisites are met, upload updated document to the UI, and ensure it is a CSV file (save as CSV if using an alternative file type for editing). Within Salesforce DMP, navigate to Upload→ Upload Type → Attribute Name. Upon upload, go to Ingestion Status to review upload status. Reload page to see the status update. When upload status is a SUCCESS, attribute name update is complete for Segment Builder. Attribute name update for Campaign Performance reports will run overnight for viewing by next day.  

4.  Manage Status

All files that have been uploaded can be reviewed in the status screen, with all pertinent information about the ingestion.

        • Name - This name is the attribute type and attribute being updated.
        • Status - The status of the ingestion.
        • Uploaded User - The individual who uploaded the file
        • Status Last Updated - The date of the last action against the file.
        • Upload File - The file that was uploaded to the system.
        • Log File - The log of detailed processing results.


A file can have one of a few statuses:

        • In Progress - The data is being processed and has not yet finished.
        • Success - The processing has finished and every single record was successfully updated. Please note - records that were included in the file but have no change to the name will show as successful records. Updates will reflect immediately in Segment Builder and will update next day in Campaign Performance Reports.
        • Partial Success - A subset of the records failed to update for some reason.*
        • Failure - Unable to start or make updates.*

Upon Partial Success or Failure, the log file will detail number of records that failed, as well as individual line items not found.

Reasons for Partial Success or Failure:

        • Values of Attribute Type are not valid.
        • IDs in Attribute Code do not have IDs in SF DMP.
          • Data is not being captured for the campaign.
          • Campaigns may not be tagged.
        • Attribute Codes are in scientific notation.
        • Attribute Name has no value.
        • Header columns are out of order.
        • More columns in file than expected.
Log File

Downloading the log file will give you more detailed insight into the results of the file processing.

        • Number of Records Processed - The total number of records addressed by the job.
        • Number of Records Successfully Updated - The total number of records that were updated. If a record had no change it will still be counted as "updated".
        • Number of Records Failed to Update - The total number of records that were ignored due to errors.

Additionally, there is detailed information about which records failed and the reasons for failure.

      • Attribute Code Note Found - Only attribute values that already exist in the system get updated. If the value is not recognized, it triggers an error.
      • Incorrect Attribute Name - Only records that have the correct attribute name will be processed.
Have more questions? Submit a request


Article is closed for comments.