Setting same SDID for all Target calls on page | Community
Skip to main content
P
philipk92120636
Level 4
February 27, 2020
Solved

Setting same SDID for all Target calls on page

  • February 27, 2020
  • 3 replies
  • 19833 views

Hi everyone!

We're migrating from DTM to Launch. I'm using the 'Adobe Target v2 - Add Params to Page Load Request' action in my Launch rule to add in profile and entity parameters. Previously we did this all in custom code so it's great being able to add these via the extension.

However, one thing I can't seem to set is the SDID value for A4T. On some pages we will have multiple Mboxes firing (as we will want to fire tests based on answers to particular questions, appearance of certain modals etc.), but in the Target requests the SDID values are different each time. How can I make it so that all Target requests on the same page have the same SDID? So far I've tried adding in the mboxMCSDID parameter to the parameters action and it didn't do anything. I also tried adding targetPageParamsAll to fire before the library loads and that didn't work either.

Any help would be greatly appreciated.

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by philipk92120636

    Achieved this using the adobe.target.getOffers() method in the at.js 2.0 API and a bit of custom code that resets the SDID to s.visitor._supplementalDataIDLast.

    In my rule in Launch, I have the custom code that resets the SDID followed by the below which uses the Target API to manually set the SDID:

     

    adobe.target.getOffers({ request: { "experienceCloud": { "analytics": { "supplementalDataId" : _satellite.getVar("sdid") // Data element containing last SDID value } } } })

     

    3 replies

    Haran_Huang
    Haran_Huang
    Level 4
    February 27, 2020
    Experience Cloud Visitor ID service lets you identify users across Experience Cloud solutions.
      P
      philipk92120636Author
      Level 4
      March 9, 2020
      I've tweaked it so that it goes Target - Target - Analytics but the SDID doesn't match up still.
        jantzen_b
        Adobe Employee
        jantzen_bAdobe Employee
        Adobe Employee
        March 27, 2020

        The SDID is used to connect the Analytics and Target hits together on the back end for the A4T integration. I'd suggest using the Experience Cloud ID Service to consistently identify users across your Adobe solutions as it was designed just for that purpose.

         

         

        "The way the out-of-the-box settings are configured for Target and Analytics integration from an implementation perspective is to use the SDID that is passed from the page to stitch the Target and Analytics request together on the backend automatically for you."

        https://docs.adobe.com/content/help/en/target/using/integrate/a4t/a4timplementation.html

          P
          philipk92120636Author
          Level 4
          March 27, 2020
          Hi Jantzen! Many thanks for the response. We do use the Experience Cloud ID Service and fire this on all pages before we load in Analytics or Target. What happens is when we have two Target calls on the same page (use case here is to update profile parameters based on a customer's action), the SDID of the second Target call doesn't match the Analytics call.
          P
          philipk92120636AuthorAccepted solution
          Level 4
          May 14, 2020

          Achieved this using the adobe.target.getOffers() method in the at.js 2.0 API and a bit of custom code that resets the SDID to s.visitor._supplementalDataIDLast.

          In my rule in Launch, I have the custom code that resets the SDID followed by the below which uses the Target API to manually set the SDID:

           

          adobe.target.getOffers({ request: { "experienceCloud": { "analytics": { "supplementalDataId" : _satellite.getVar("sdid") // Data element containing last SDID value } } } })

           

            A
            akma1991
            Level 2
            March 24, 2021

            How can you manually set the SDID if visitorapi.js and at.js are not fired from within a TMS?

            Terms & ConditionsAccessibility statement

            Loading footer...