Hello,
We are implementing the integration using the Target Delivery API and I need to send the Supplemental Data Id to ensure the integration with the Analytics.
I cannot find where the supplemental data id is coming from. As I understood, the SDID should be different for each request, is that correct?
How can I generate one before the request?
Thanks! Br, Nikita
Solved! Go to Solution.
@NikitaVerkhoshintcev The SDID parameter is generated in the ID services payload . You may refer to this document for more details : https://experienceleague.adobe.com/docs/id-service/using/implementation/ecid-a4t-target.html?lang=en
@NikitaVerkhoshintcev The SDID parameter is generated in the ID services payload . You may refer to this document for more details : https://experienceleague.adobe.com/docs/id-service/using/implementation/ecid-a4t-target.html?lang=en
Hey Hi @Gaurav_Singh
When we implement Adobe Target server-side through delivery APIs (rest API) how we can achieve A4T integration?
on the link https://developers.adobetarget.com/api/delivery-api/#section/Integration-with-Experience-Cloud it mentioned Adobe Target can automatically forward the analytics payload to Adobe Analytics via the server side if the following identifiers are provided:
but then there is no information how we can pass the SDID, how it's getting generated?
Do you have any tutorial / use case where it can shows how this is being done?
The link you posted is https://experienceleague.adobe.com/docs/id-service/using/implementation/ecid-a4t-target.html?lang=en is mixed server- and client-side implementations of Target, Analytics, and the ID service but what if we have to achieve A4T implementation both from server side.
Hi @Gaurav_Singh,
We have AEP Web SDK implementation where we are using Web SDK for ECID and Analytics Implementation. We are using Delivery APIs for Adobe Target. In this case, how can we achieve A4T integration? How do we get SDID here or is there any other alternative?
Views
Replies
Total Likes
@DisaRas you may refer to this document: https://experienceleague.adobe.com/docs/target/using/integrate/a4t/a4timplementation.html?lang=en.
Let me know if this helps.
Views
Replies
Total Likes
Hi @Gaurav_Singh,
The below article mentions about implementation steps for A4T in case of Web SDK or at.js implementation and not in case of mixed implementation as above where we are using ECID and Analytics (client-side) and Target (server-side)
https://experienceleague.adobe.com/docs/target/using/integrate/a4t/a4timplementation.html?lang=en.
So the primary questions are as follows -
a. How do we get SDID if we want a direct integration. Does alloy.js provide any endpoint for the same to query? Do note ECID is client-side so we are not explicitly calling any library here(for passing ecid value in our target request, we are picking amcv cookie value)
b. Data Insertion API - Given that we are using Analytics client-side, we cannot disable datastream configuration for Analytics so my understanding is we cannot use this method. Also the endpoint for this API is b/ss i.e Appmeasurement library so does this endpoint remain same even if we are using Web SDK.
Thanks for your help.
Views
Replies
Total Likes
hello @NikitaVerkhoshintcev @DisaRas @Gaurav_Singh @abu_shafi @Gokul_Agiwal
"the same supplementalDataId
need to be passed to both Adobe Target and Adobe Analytics."
where can I pass the supplementalDataId
into adobe analytics ... I mean via what ?
here in Delivery Api they do only one request to the delivery api
so is that request guarantee to deliver to adobe analytics ?
curl -X POST \
'https://demo.tt.omtrdc.net/rest/v1/delivery?client=demo&sessionId=d359234570e04f14e1faeeba02d6ab9914e' \
-H 'Content-Type: application/json' \
-H 'cache-control: no-cache' \
-d '{
"context": {
"channel": "web",
"browser" : {
"host" : "demo"
},
"address" : {
"url" : "http://demo.dev.tt-demo.com/demo/store/index.html"
},
"screen" : {
"width" : 1200,
"height": 1400
}
},
"id": {
"marketingCloudVisitorId": "2304820394812039"
},
"property" : {
"token": "08b62abd-c3e7-dfb2-da93-96b3aa724d81"
},
"experienceCloud": {
"analytics": {
"supplementalDataId" : "23423498732598234",
"trackingServer": "ags041.sc.omtrdc.net",
"logging": "server_side"
}
},
"execute": {
"mboxes" : [
{
"name" : "homepage",
"index" : 1
}
]
}
}'
Views
Replies
Total Likes
Views
Likes
Replies