Skip to main content
Skip table of contents

How does a DSP receive Anonymised audiences at present

Assumptions:

  • An active deal has been curated in the SSP using the Anonymised segment and has been passed to the DSP or buyer seat.

  • SSP has parsed the segments in the bid request, matched and appended the corresponding deals to the bid request and forwarded it on to the DSP

  • QPS throttling and SSP traffic shaping have not omitted the majority of such traffic

Bid requests from SSPs other than Xandr

Bid requests will be received with the following objects present:

  1. ortb2.x.imps.pmp.deals array

  2. ortb2.x.user.data.segment array

  3. ortb2.x.user.data.ext.segtax = 1000

Bid requests from Xandr

Bid requests will be received with the following objects present:

  1. ortb2.x.imps.pmp.deals array

  2. ortb2.x.user.data.ext.segtax = 1000 [although this is not currently being passed as our RTD module has not been universally installed nor has Amazon TAM adjusted their HB to send segtax to Xandr]

Example SSP to DSP Bid Request

Click here to view

Potential Issues & Remedial Actions

  • Impression and User objects are unrelated

    • Get SSP to add segtax to deal object using deal extension object as part of their synchronisation activity.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.