Customer Attributes

An Analytics FAQ for customer attributes, and how to run the Customer Attributes report.

Reports> Visitor Profile > Customer Attributes

If you capture enterprise customer data in a customer relationship management (CRM) database, you can upload the data into a customer attribute data source in the Experience Cloud. After the data is uploaded, you can run the Customer Attributes report in Reports & Analytics.

See Customer Attributes in Experience Cloud help for information about uploading customer attribute data.

Customer Attributes and Reporting Metrics in Analytics

After you upload customer attributes and validate the schema (in the Experience Cloud), the system creates metrics based on the friendly names (like age or gender) that you map to the attribute strings and integers. These metrics appear in Visitor Profile > Customer Attributes reports.

For example:

Visitor Profile > Customer Attributes > Age

Example - Age Metrics

If you specify a string as age, the system creates the following metrics and dimensions:

  • Age dimension: Lets you run a report based on the Age attribute.
  • Age metric: A metric you can add to a report, such as a Unique Visitors report.
  • Count of Age metric: Lets you understand, for example, if visitors specified an age value on a form.

Because metrics are sums in a report table, you should create a calculated metric that tells you the average age. The formula for this metric is Age / Count of Age.

FAQ - Customer Attributes in Analytics

Question Answer

Why is it preferable to use the Experience Cloud ID service to set the Customer ID instead of populating the Customer ID in a prop or eVar?

Using the Experience Cloud ID service offers a number of benefits:

  • If you do not set the Customer ID with the Experience Cloud ID service, the customer records are available only to Adobe Analytics. If you want to use the customer records for real-time targeting, you must use the Experience Cloud ID service.
  • Using the Experience Cloud ID service to set the Customer ID reduces the time it takes to synchronize IDs with the Experience Cloud. If you put the Customer ID in a prop or eVar, the Customer IDs are sent to the Experience Cloud via back-end server synchronization that occurs in batches. The Experience Cloud ID service synchronizes the Customer ID with the Experience Cloud immediately.
  • Using the Experience Cloud ID service instead of a prop or eVar frees up that prop or eVar for other uses.

If I am already storing a customer ID in a prop or eVar, why would I use this new functionality instead of classifying my prop or eVar with CRM attributes?

Props and eVars are subject to Uniques Exceeded limitations. Using this functionality you can bring in attribute data for an unlimited number of customer IDs. Also, using the prop/eVar approach limits the CRM information to Analytics.

How will my CRM attributes appear in Adobe Analytics?

CRM attributes will be manifest in Analysis Workspace, Reports & Analytics, Ad Hoc Analysis, the reporting API, and Report Builder. Text attributes will appear as reports/dimensions. Numeric attributes will appear as both dimensions and metrics.

Will the CRM data be available in Data Warehouse and in Data Feeds?

The CRM data is not currently available in Data Warehouse or Analytics Data Feed.