Delivery API - SDID - Supplemental Data Id | Adobe Higher Education
Skip to main content
N
NikitaVerkhoshintcev
October 4, 2021
解決済み

Delivery API - SDID - Supplemental Data Id

  • October 4, 2021
  • 2 の返信
  • 5946 ビュー

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

    このトピックへの返信は締め切られました。
    ベストアンサー Gaurav_Singh_02

    @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 

     

    2 の返信

    G
    Adobe Employee
    Gaurav_Singh_02Adobe Employee回答
    Adobe Employee
    October 5, 2021

    @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 

     

      Gokul_Agiwal
      Community Advisor
      Gokul_AgiwalCommunity Advisor
      Community Advisor
      October 6, 2021

      Hey Hi @gaurav_singh_02 

      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. 

        

        A
        AbuSh1
        Level 4
        October 6, 2021

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

         

        Thanks

        Abu

          A
          Arsène
          Level 2
          December 20, 2022

          hello @nikitaverkhoshintcev  @user94030 @gaurav_singh_02 @abush1 @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
          }
        ]
      }
    }'


           

          契約条件Accessibility statement

          Loading footer...