Frequently asked questions, limitations, and best practices
FAQ and best practices for Customer Attributes in Analytics and Target.
Best practices and limitations
Guidance and limitations when using Customer Attributes.
Customer attribute subscription limitations
When you upgrade to Analytics Premium, there is a 24-hour delay before additional attributes are available. You may see an Attribute Subscription Max error issued during this delay.
Multiple logins on the same device
When using Customer Attributes to upload customer profiles into a data source, Adobe recommends against users sharing the same device (meaning, the same Experience Cloud ID). Doing so might cause the ECID service, which persists on the device, to link multiple users under the same Experience Cloud ID, causing unexpected results in Target. Note: For Mobile, the ECID is permanent after the Mobile app is installed, and you must reinstall the app to generate a new ECID. For Web, a new ECID is generated after the browser cookie is cleared.
Daily frequency upload limitation
Adobe recommends that you update Customer Attributes only once per day. You must wait at least 24 hours to upload another customer profile data file for the same set of profiles.
Custom Analytics ID ( s.visitorID )
Setting a customer ID using s.visitorID is a method of identifying users in Analytics. However, integrations in which Analytics data is exported or imported using the ID Service will not function when a visitor is identified using s.visitorID.
This includes, but is not limited to, shared Audiences, Analytics for Adobe Target (A4T), and Customer Attributes.
For these integrations, setting a custom Analytics ID is not supported.
Character length limitations in Analytics
When creating an Analytics subscription, field lengths for the uploaded files are truncated to 255.
FAQ about Customer Attributes
Can I receive notifications about upload status for Customer Attributes?
Yes. See Manage notifications .
What should I do to get started with Customer Attributes?
Note: An administrator's FAQ for implementing core services is available here .
How many Customer Attributes am I allowed to use?
You can upload hundreds of .csv columns to the customer attribute service. However, when configuring subscriptions and selecting attributes, the following limits apply (per report suite), depending on the solutions you own:
Is migrating to the Experience Cloud ID Service required?
Migration depends on the solutions you use.
Using the ID service enhances the functionality opens the doors to using the latest Experience Cloud functionality, including real-time audiences, the Adobe Target modernization, Analytics integration, and video heartbeat tracking.
For more details see Enable your solutions for core services .
** Note:** The Experience Cloud ID Service is the modernized implementation of what is formerly known as Analytics visitor ID service.
How does the customer attribute functionality relate to Adobe Audience Manager?
While Audience Manager can receive data to perform audience identification, it cannot perform analytics functionality that ties attributes to historical behavioral data or provide the reporting, analysis, and segmentation capabilities that are available in Adobe Analytics. People enables rich data from across solutions to be tied together and associated with a single ID for use across the Experience Cloud.
In Adobe Target, Customer Attributes appear as individual attributes that can be combined with other rules to build audiences. Audiences shared to the People service are full audiences that cannot be modified.
(Analytics only) How is this functionality different from what is provided in Analytics premium?
In the past, customers interested in combining customer attribute data with Analytics data have relied heavily on the data workbench tool for this functionality. Customer attributes exposes this functionality to a wider audience by providing Customer Attributes as dimensions and metrics in reports & analytics, ad hoc analysis, and report builder. Analytics Standard customers will have access to Customer Attributes, but with limited capabilities. The full capability is available to Analytics Premium customers.
(Adobe Target Only) Can I pre-load or upload data for customers that Adobe Target has never seen?
Yes. When the visitor makes their first request to Adobe Target, the system will fetch the existing information we have about them from Customer Attributes and use that data for targeting. Note: Retrieving this data can take up to 20 min from the visitor's first interaction with Adobe Target.
(Adobe Target Only) Can I create a super audience by combining customer attribute data with shared audience data?
No. Shared audience data is a completed audience.
(Adobe Target only) How does the Customer Attributes functionality compare to Adobe Target's bulk profile API?
The bulk profile API enables Adobe Target profiles to be updated directly via the API, either for an individual profile or in bulk. The capability is similar to Customer Attributes, with the following key differences:
(Adobe Target only) Does uploading data from Customer Attributes to Adobe Target extend the Adobe Target visitor's profile lifetime?
Yes. See Visitor Profile Lifetime in Adobe Target Help.
(Adobe Target only) Can I target on the data uploaded in Customer Attributes immediately after the visitor is identified by the customer ID?
Yes. On the server call to Adobe Target, which includes the mbox third-party ID, all customer attribute data will be available.
(Adobe Target only) What does the Sync Status column represent for files uploaded in customer attribute source?
The number of records published and synced by Adobe Target can be viewed by clicking the Sync Status icon against a specific attribute file. Sync % is a realtime metric that specifies the % of profiles that have been synced in Adobe Target.
Note: It may take up to 24 hours for attributes to sync with Adobe Target.
What do the file upload metrics represent in Customer Attributes Source?
You can check the status of attributes uploaded to Customer Attributes with the help of following metrics: