Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Delivery API - SDID - Supplemental Data Id

Avatar

Level 1

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

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

@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 

 

View solution in original post

0 Replies

Avatar

Correct answer by
Employee Advisor

@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 

 

Avatar

Community Advisor

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:

  1. supplementalDataId - The ID that is utilized to stitch between Adobe Analytics and Adobe Target
  2. trackingServer - The Adobe Analaytics Server In order for Adobe Target and Adobe Analytics to correctly stitch the data together, the same supplementalDataId need to be passed to both Adobe Target and Adobe Analytics.

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. 

  

Avatar

Level 3

abu_shafi_0-1633562389366.png

I believe this diagram will help you understand the end to end process

 

Thanks

Abu

Avatar

Level 1

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?

 

 

Avatar

Level 1

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.