I went looking for my ad profile inside the bid request. It wasn't there.
When an ad is auctioned for you, a bid request goes out that describes you — segments, identity graphs, consent state, location precision. Buyers see that description for free, before anyone pays for anything. So I tried to read mine. One operator, one browser, my own data, everything public: genaforvena/self-adint , data CC0. The result is a negative for the naive form of that idea, and the…
In a recent report, a reporter delved into the bid request to find their ad profile but found none. The bid request, which describes users for ad auctions, contains segments, identity graphs, consent state, and location precision. However, the reporter discovered that the body of the request was often not retained, resulting in the loss of valuable information.
This failure mode, where a pipeline answers a different question than what was asked, highlights the importance of keeping the entire payload. The reporter also noted that some SSPs, such as ssp01.rambler.ru, truncate the request URL, cutting off important data. This truncation results in a misleading view of the ad stack, as the GET half is not a lesser half.
The report further reveals that some bid requests may carry no audience field at all, while others have filled audience slots. The most informative state is when the audience profile is present and empty, indicating that the browser has nothing to put in it. This finding sheds light on the fact that the identity and control of a person often travel through the publisher's own language rather than the bid request itself.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
