SDK Bidding Process

The following diagram provides an overview of the SDK bidding process:

Bidding Process

1. Initiating the Bid Request: The Mediation SDK begins the process by requesting a unique identification token from the DT Exchange SDK, which is a key part of setting up the ad request.

2. Receiving a Security Token: The DT Exchange SDK provides the requested token back to the Mediation SDK to confirm its identity. For more information about generating a token, see Fetching the Ad for SDK Bidding (Android docs, iOS docs).

3. Forwarding the Token: The Mediation SDK sends this token to its server-side component, the Mediation Backend, which will handle the rest of the bid process.

4. Creating a Bid Request: The Mediation Backend creates and sends an OpenRTB bid request to the DT Exchange Backend. This request includes the security token and other relevant information for the ad placement. For more information, see Bid Request Specifications.

5. Running an Internal Auction: The DT Exchange Backend receives the bid request and runs an internal OpenRTB auction among its network of Demand-Side Platforms (DSPs) to find the best ad.

6. Sending the Winning Bid: After the auction concludes, the DT Exchange Backend sends the highest bid response, including the creative and price, back to the Mediation Backend. For more information, see Bid Response Specifications.

7. Conducting a Final Auction: The Mediation Backend then performs a secondary auction, comparing the winning bid from DT Exchange against bids from all other ad networks to find the overall best bid.

Alternative 1: DT Exchange Wins

1. Notifying of Win: If the DT Exchange bid wins the final auction, the Mediation Backend notifies the DT Exchange Backend with a win notification that includes details about the successful bid. For more information, see the seatbid.bid.nurl attribute in the Bid Response Specifications.

2. Preparing to Render: The Mediation Backend sends the winning ad creative from DT Exchange back to the DT Exchange SDK on the user's device, preparing it for display.

3. Confirming Impression: Once the ad is displayed to the user, the DT Exchange SDK notifies the Mediation SDK that an impression has occurred.

4. Logging the Impression: The Mediation SDK relays this impression notification to the Mediation Backend to log the event.

5. Sending a Billing Confirmation: The Mediation Backend sends a final billing notification to the DT Exchange Backend to complete the transaction for the winning ad impression. For more information, see the seatbid.bid.burl attribute in the Bid Response Specifications.

Alternative 2: DT Exchange Loses

1. Notifying of Loss: If another network's bid is higher, the Mediation Backend sends a loss notification to the DT Exchange Backend, informing it that its bid was not selected. For more information, see the seatbid.bid.lurl attribute in the Bid Response Specifications.