CX Enterprise atlas / Shared Services & Administration | Platform & administration
ProductGenerally available
Shared Services & AdministrationPlatform & administration
Also known as Customer Attributes, Experience Cloud Customer Attributes, Adobe Experience Cloud Customer Attributes, Customer Attributes core service, Customer Relationship Service
The CX Enterprise core service for bringing CRM data such as loyalty level, products owned or lifetime value into Analytics and Target. Customers upload CSV files to an attribute source keyed on their own customer ID; the service matches those IDs to Experience Cloud IDs through the customer IDs that sites and apps pass to the Visitor ID Service, then sends the subscribed attributes to Analytics report suites and Target profiles.
Adobe provisions Customer Attributes for Analytics customers; Target-only customers request core services from Customer Care. It appears as a product profile in Admin Console, and uploaders must be in the Customer Attributes group plus an Analytics or Target group. Target needs at.js (or mbox.js 58 or later).
Integrates with: Admin Console
Last checked 2026-09-30
Also known as Customer Attributes data sources
A named container for one CRM feed, with an alias ID and a namespace code. New, changed or deleted sources take about an hour before IDs start syncing.
Last checked 2026-09-30
Also known as Customer Attributes integration code
The unique lowercase key of a source. It must match the integration code of the customer ID set in the tags extension, in setCustomerIDs or in the mobile SDKs. A deleted source's alias ID cannot be reused because it is stored across several services.
Integrates with: Customer IDs and authentication states
Last checked 2026-09-30
Several sources can use the same customer ID if the site sets one customer ID per alias; each source has its own alias ID.
Last checked 2026-09-30
Also known as Customer Attributes data files
CSV files (optionally .gz or single-file .zip) whose first column is the unique customer ID and whose other columns are attributes; about 200 columns is the practical maximum and there is no row limit. The service is built for a few files a day: files within 30 minutes of the last batch go to a lower-priority queue, and Adobe recommends one update per day.
Last checked 2026-09-30
Uploading a file of less than 100 MB in the attribute source page; no .fin file is needed.
Last checked 2026-09-30
One FTP account per source on ftp.adobe.com, over FTP or SFTP (password or key). Each CSV needs a matching empty .fin file, which triggers pickup within a minute; uploads are 10 MB to 4 GB, one every half hour, in 40 GB of account space that the customer must clean up.
Last checked 2026-09-30
Counts of records, new and updated records, unique customer IDs, IDs aliased to ECIDs and IDs with high alias counts, plus CX Enterprise notifications about upload activity.
Last checked 2026-09-30
After the first upload each column is mapped to a type (string, integer or number), display name and description; the schema then validates later uploads. The display names become Analytics dimensions and metrics.
Last checked 2026-09-30
Deleting or replacing attributes by removing them from the subscriptions and uploading a file with the new fields; updating a validated schema deletes attributes.
Last checked 2026-09-30
Troubleshooting tool that shows, for one customer ID, its attributes and the ECIDs or Analytics visitor IDs aliased to it.
Last checked 2026-09-30
When a visitor signs in, the site or app sends the CRM ID with setCustomerIDs (or a prop or eVar), and the service aliases it to the visitor's ECID. A customer ID with 500 or more ECIDs is treated as a shared login: attributes go only to the 500 most recent ECIDs and the ID is invalidated at 10,000. Shared devices can link several people to one ECID.
Integrates with: Experience Cloud ID (ECID)
Last checked 2026-09-30
Attributes stay on the visitor's Analytics profile for its whole life, including visits before the first sign-in. Customers who tracked customer IDs in a prop or eVar can ask Support to send past logins to CX Enterprise.
Last checked 2026-09-30
A former method of backfilling ID syncs from Analytics Data Warehouse for customers without the Visitor ID Service, tied to the Analytics ID; no longer available since October 2022.
Replaced by Visitor ID Service for Analytics
Last checked 2026-09-30
Also known as Customer Attributes subscriptions
The settings that activate a source and choose which attributes flow to Analytics and Target. The number of attributes allowed depends on the licensed edition.
Last checked 2026-09-30
Sends attributes to up to 10 report suites per source for reporting and segmentation under Visitor Profile > Customer Attributes. Per report suite, Foundation allows 0 attributes, Select 3, Prime 15 and Ultimate 200 (legacy Standard 3 in total, Premium 200). Values are cut to 255 characters and do not appear in data feeds.
Integrates with: Analytics
Last checked 2026-09-30
Loads attributes, prefixed crs., into Target visitor profiles for audiences and activities, with up to 5 attributes on Target Standard and 200 on Premium. Profiles need an AUTHENTICATED customer ID; data can reach Target before a visitor's first visit, takes up to 24 hours to sync, and lives as long as the Target profile (14 days by default).
Integrates with: Visitor profiles
Last checked 2026-09-30
An Experience Platform source that ingests Customer Attributes data into Real-Time Customer Profile, auto-creating the schema and dataset; the first CSV column is mapped to the CORE namespace, so records join other profile data only when they can be matched to an ECID.
Integrates with: applications sources
Last checked 2026-09-30
Data subject requests and guidance on personal data in Customer Attributes.
Last checked 2026-09-30
Also known as Customer Attributes GDPR and CCPA support
Access and delete requests under GDPR, CCPA and similar laws, sent through Privacy Service with the product value CRS, the source's alias ID as namespace (type integrationCode) and the CRM ID.
Integrates with: Privacy Service
Last checked 2026-09-30
Adobe asks that directly identifying data such as email addresses be hashed before upload and prohibits sensitive data such as medical records, financial account details and data about minors.
Last checked 2026-09-30