Possible sources of offer request parameters

[Alexander_Prikhodko]

I need help to understand how Target determines what parameters to include in the /mbox/json request when getting offers. The exact issue I have seems to be caused by some legacy from people who don't work at the company anymore and left no documentation, so it's quite puzzling.

When I check the request in the browser's debugger, I can see:

• parameters added out of the box, like screenHeight or mboxTime
• parameters added by our custom code
• a few more that come from elsewhere

The ones from the last part are definitely not out of the box (their names refer to some of our internal processes), but they are not mentioned in our custom code. Where else can they come from?

Our at.js version is 1.8.2.

[Alexander_Prikhodko · Accepted solution]

I have found the additional source of parameters. They are configured inside Adobe Launch rules, the way it's described at https://experienceleague.adobe.com/docs/platform-learn/implement-in-websites/implement-solutions/tar... in "Add parameters" section.