Create a Customer Attribute source and upload the data file

Create a .csv.

Sample enterprise customer data file:

Before continuing, review the important information in Data File Requirements, before you upload the file.

Create a Customer Attribute source and upload the data, described below.

In the Experience Cloud, select the Menu icon.

Under Experience Platform, select People > Customer Attributes.

The Customer Attributes page is where you can manage and edit existing attribute data sources.

Select New.

On the Edit Customer Attribute Source page, configure the following fields:

• Name: A friendly name for the data attribute source. For Adobe Target, attribute names cannot include spaces. If an attribute with a space is passed, Target ignores it. Other characters not supported include: < , >, ', ".

• Description: (Optional) A description of the data attribute source.

• Alias ID: Represents a source of Customer Attribute data, such as a specific CRM system. Alias ID is a unique ID that is used in your Customer Attribute Source code. The ID should be unique, lowercase, with no spaces. The value that is entered in the Alias ID field for a Customer Attribute source in Experience Cloud should match the values that are being passed in from the implementation (whether via Platform Data Collection or JavaScript of the Mobile SDK.)

  The Alias ID corresponds to certain areas where you set additional Customer ID values. For example:

  • Dynamic tag management: The Alias ID corresponds to the Integration Code value under Customer Settings, in the Experience Cloud ID Service tool.

  • Visitor API: The Alias ID corresponds to the additional Customer IDs that you can associate with each visitor.

    For example, “crm_id” in:

    code language-none
    "crm_id":"67312378756723456"

  • iOS: The Alias ID corresponds to “idType” in visitorSyncIdentifiers:identifiers.

    For example:

    [ADBMobile visitorSyncIdentifiers:@{@<"idType":@"idValue"}];

  • Android™: The Alias ID corresponds to “idType” in syncIdentifiers.

    For example:

    identifiers.put("idType", "idValue");

    See Leveraging multiple data sources for additional information about data processing regarding the Alias ID field and Customer IDs.

• File Upload: You can drag-and-drop the .csv data file, or upload the data via FTP. (Using FTP also requires a .fin file.) See Upload the Data via FTP.

  note important
  IMPORTANT
  Specific data file requirements exist. See Data File Requirements for more information.

  After uploading the file, table data is displayed under the File Upload heading on this page. You can validate the schema, configure subscriptions, or set up the FTP.

  File upload graphic

  

• Unique Customer ID: Displays how many unique IDs you have uploaded to this attribute source.

• Customer-Provided IDs Aliased to Experience Cloud Visitor IDs: Displays how many IDs have been aliased to Experience Cloud Visitor IDs.

• Customer-Provided IDs with High Alias Counts: Displays the count of customer-provided IDs with 500 or more aliased Experience Cloud Visitor IDs. These customer-provided IDs most likely do not represent individuals but rather some sort of shared login. The system distributes the attributes associated with these IDs to the 500 most recent aliased Experience Cloud Visitor IDs, until the alias count reaches 10,000. Then, the system invalidates the customer-provided ID and no longer distributes associated attributes.