Adobe Target

Michael_Soprano · 5/5/25

Is it batch or streaming? Is there any workflow how to make that connection?

VikasOhlan · 5/5/25

Hi @Michael_Soprano,

The Adobe Target Bulk Profile Update API is a batch API. You upload a bulk file (less than 50 MB and up to 500,000 rows per upload) containing multiple user profile updates in one go. Changes made using this API will typically be reflected in Target within an hour, but may take up to 24 hours in some cases.

The workflow looks something like this:

Prepare your data: Use a flat file format, such as CSV or JSON, where each record represents a user. Ensure that each record includes an identifier (e.g., mbox3rdPartyId) and key-value pairs of profile attributes.
Prepare an HTTP POST request to the endpoint: http://CLIENTCODE.tt.omtrdc.net/m2/CLIENTCODE/v2/profile/batchUpdate
Set the Content-Type to application/x-www-form-urlencoded and upload the batch file
Adobe Target processes the batch and updates user profiles as specified in your file. Once processed, the uploaded profile attributes become available in Adobe Target for segmentation and personalization.

Regards,
Vikas Ohlan
LinkedIn Profile

Michael_Soprano · 5/7/25

Do you know if there is a way to secure in some way that endpoint, some authentication or whatever?

VikasOhlan · 5/7/25

Hi @Michael_Soprano ,

Yes, you can secure the Bulk Profile Update API endpoint by enabling authentication through the Adobe Target Admin interface. By default, the API is an HTTP endpoint that, if not configured for authentication, may accept unauthenticated uploads. However, for security, Adobe too recommends setting up authentication token for all profile update API calls.

To enable it in Target UI,

Go to Administration > Implementation in the Target UI.
Under Profile API, toggle the "Require Authentication" setting to enabled.
After enabling authentication, click "Generate New Profile Authentication Token" in the Profile API settings (You must have the Admin role or at least Approver rights in Target to generate this token).
Add an "Authorization" header with the value Bearer {token} to your API requests.

Regards,
Vikas Ohlan
LinkedIn Profile