since ‎19-12-2020
‎13-01-2021
kaiomo
Level 1
Re: supplementalDataId Different For Each Adobe Target Re...
Avatar

kaiomo

kaiomo
- Adobe Target
@shelly-goelThank you for the links. After a bit more searching of the documentation: to solve this, when using getOffers I had to set the consumerId key to a unique value (it was defaulting to 'undefined' even if I was request regional mboxes). That value is used to determine whether the API should generate a new SDID or if it reuses the SDID already available on the page.

Views

222

Likes

0

Replies

0
Re: supplementalDataId Different For Each Adobe Target Re...
Avatar

kaiomo

kaiomo
- Adobe Target
Thank you @shelly-goel Just tried with a local mbox and a new sdid is being generated. Would also rather avoid using logging:client_side It seems the sdid is decided by a function called getSupplementalDataID - and there are two in circulation at any one time (stored in visitor._supplementalDataIDCurrent or visitor._supplementalDataIDLast). If I override those values I can force my getOffers request to use the sdid of my choosing (the same one that was used for pageLoad and Adobe Analytics page ...

Views

274

Like

1

Replies

2
supplementalDataId Different For Each Adobe Target Request
Avatar

kaiomo

kaiomo
- Adobe Target
Hello, We have a activity only for visitors with a particular profile parameter. But this data point does not exist until several seconds after the page has fully loaded. This means the first pageLoad request made to Adobe Target (at.js 2.x) is missing these parameters - and the visitor fails to qualify for the test. We have some code that will scrape the DOM for all the necessary data points, so we want to make a second request to the Adobe Target servers. This time with all the parameters in o...

Views

385

Like

1

Replies

4
Likes from