Via API, send a .csv file to Adobe Target with visitor profile updates for many visitors. Each visitor profile can be updated with multiple in-page profile attributes in one call.
This option is similar to Customer Attributes with a few differences:
mbox3rdPartyID: plus sign (+) and forward slash (/).
The .csv file must refer to each visitor via his or her Target PCID or mboxThirdPartyId . The Experience Cloud ID (ECID) is not supported. All profile attributes/values are created and updated via the API. Format details are available in the API documentation.
Your CRM or other internal system stores valuable data about your visitors that you want to consistently update into Target, without exposing the profile data in your page implementation.
No limit on the number of profile attributes.
Profile attributes sent via the site can be updated via the API and vice versa.
The size of the batch file must be less than 50 MB. In addition, the total number of rows should not exceed 500,000 rows per upload.
There is no limit on the number or rows you can upload over a period of 24 hours in subsequent batches. However, the ingestion process might be throttled during business hours to ensure that other processes run efficiently.
Consecutive V2 batch update calls without mbox calls in between for the same thirdPartyIds override the properties updated in the first batch update call.
See Updating Profiles.