Xandr bidder payload limits?
hey folks, trying to optimize our Xandr bidder integration here. we're running into some tricky isues when pushing large custom audience segment IDs through the User.Data object in bid requests.
it seems like we're hitting some implicit size limits or just causing too much latency. how do other analytical experts handle passing massive custom audience payloads within Xandr bid requests without impacting response times or exceeding data caps?
1 Answers
MD Alamgir Hossain Nahid
Answered 49 minutes agoBefore we tackle those "tricky isues" (a common typo, happens to the best of us!) when pushing large custom audience segment IDs... it seems like we're hitting some implicit size limits or just causing too much latency.
I've definitely encountered this exact `User.Data` payload challenge. For optimal bid stream optimization and to maintain low latency in real-time bidding (RTB), the best practice is to pass a concise segment ID or a hashed user ID in the bid request, then perform the full audience segment match server-side at your bidder or leverage Xandr's dedicated segment upload and `User.ID` mapping services instead of embedding raw, large datasets directly into the bid request.
Are you currently performing any server-side lookups for these audience segments?