Setting same SDID for all Target calls on page

Avatar

Avatar
Validate 10
Level 3
philipk92120636
Level 3

Likes

14 likes

Total Posts

91 posts

Correct reply

8 solutions
Top badges earned
Validate 10
Validate 1
Contributor
Give Back 3
Give Back
View profile

Avatar
Validate 10
Level 3
philipk92120636
Level 3

Likes

14 likes

Total Posts

91 posts

Correct reply

8 solutions
Top badges earned
Validate 10
Validate 1
Contributor
Give Back 3
Give Back
View profile
philipk92120636
Level 3

27-02-2020

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.

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 10
Level 3
philipk92120636
Level 3

Likes

14 likes

Total Posts

91 posts

Correct reply

8 solutions
Top badges earned
Validate 10
Validate 1
Contributor
Give Back 3
Give Back
View profile

Avatar
Validate 10
Level 3
philipk92120636
Level 3

Likes

14 likes

Total Posts

91 posts

Correct reply

8 solutions
Top badges earned
Validate 10
Validate 1
Contributor
Give Back 3
Give Back
View profile
philipk92120636
Level 3

14-05-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
        }
      }
   }
})

 

Answers (2)

Answers (2)

Avatar

Avatar
Validate 1000
Community Manager
jantzen_belliston-Adobe
Community Manager

Likes

339 likes

Total Posts

2,338 posts

Correct reply

819 solutions
Top badges earned
Validate 1000
Springboard
Validate 500
Validate 250
Validate 100
View profile

Avatar
Validate 1000
Community Manager
jantzen_belliston-Adobe
Community Manager

Likes

339 likes

Total Posts

2,338 posts

Correct reply

819 solutions
Top badges earned
Validate 1000
Springboard
Validate 500
Validate 250
Validate 100
View profile
jantzen_belliston-Adobe
Community Manager

27-03-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

Avatar

Avatar
Establish
Level 2
Haran_Huang
Level 2

Likes

17 likes

Total Posts

54 posts

Correct reply

6 solutions
Top badges earned
Establish
Validate 1
Boost 5
Boost 3
Boost 10
View profile

Avatar
Establish
Level 2
Haran_Huang
Level 2

Likes

17 likes

Total Posts

54 posts

Correct reply

6 solutions
Top badges earned
Establish
Validate 1
Boost 5
Boost 3
Boost 10
View profile
Haran_Huang
Level 2

27-02-2020

Experience Cloud Visitor ID service lets you identify users across Experience Cloud solutions.