hi @broman__pl - If you use single-profile update API then the delay will remain same regardless the implementation approach. To make profile-updates much faster, solution is Server side delivery API as you mentioned. Server-side API implementation requires:
1. An execution environment which can make calls to API - there are SDKs for Java and NodeJS though you may use any other languages
2. Way to get Experience Cloud ID or PCID - the easiest way is to pass these from client-side to execution environment
3. Generate the session-id: You can either pass the session-id from client-side or generate your own following these guidelines:
4. Pass user data as mbox call - here's a code sample below:
5. In Adobe Target - you can use Profile Scripts to read the parameters and use in Audiences as per your use-cases.
var targetURL = 'https://<your-client-code>.tt.omtrdc.net/rest/v1/delivery?client=<your-client-code>&sessionId='+<session-id>;
var targetData = {
"context":{
"channel":"web"
},
"id": {
"marketingCloudVisitorId": <ECID>,
"tntId": <PCID>
},
"experienceCloud" : {
"analytics": {
"logging": "client_side"
}
},
"execute": {
"mboxes" : [
{
"name" : "<mbox-name>",
"index" : 1,
"parameters": {"param1":"value1"}
}
]
}
}
let targetHeaders = new Headers();
targetHeaders.append('Content-Type','application/json');
let targetRequest = new Request(targetURL, {
method: 'POST',
headers: targetHeaders,
mode: 'cors',
cache: 'default',
body: JSON.stringify(targetData)
});
fetch(targetRequest)
.then(response => {
if (!response.ok) {
throw new Error(`Network response was not ok. Status code: ${JSON.stringify(response)}.`);
}
return response.json();
})
.then(data => yourFunctionToProcessTargetResponse(data))
.catch(error => console.log("Error:" + error.message));
}
