Skip to main content

Multi-Step RTB Target Configuration

D
Written by Denise Abdullah
Updated over 2 months ago

NEW FEATURE RELEASE: Multi-Step RTB Target Configuration
Location: Targets/RTBs -> RTBs

Overview
The Multi-Step RTB release enables chained bidding sequences—where multiple API requests can occur in order, and each step can use results from previous ones.
It allows flexible “ping-pong” auctions and real-time validation flows, so you can confirm winners or apply advanced decision logic before routing.What’s New
You can now define step-based logic within a single RTB target:

  • Ping-Then-Full Flow: Configure an initial limited “ping” call, then follow with the complete payload once a winning route is determined.

  • Step-Chained Evaluation: Define multiple steps inside an RTB target that execute in sequence.

  • Automatic Variable Chaining: Fields returned in one step (like BID_ID or SESSION_TOKEN) are automatically available in subsequent steps.

  • Per-Step Logic: Assign different payout, duration, or priority rules to each step.

  • RTB Target-Group Behavior: The winning step concept applies when the target is used inside an RTB Target Group only (the selected step determines the effective route for that group). runOnRTBGroupWin setting triggers a post-auction call once a winning route is selected.

  • Expanded Logging: Step responses are recorded to aid troubleshooting and analysis. Built-in resilience using continueOnFailure, ensuring the auction continues even if an intermediate step fails.

  • Backward Compatible: Single-step targets continue to work unchanged.

Why This Matters
Previously, advertisers had to create separate RTBs to simulate multi-layer logic, which complicated setup and reduced transparency.
Now, you can manage complex bidding strategies in one place — cutting down configuration time and minimizing routing errors.
Multi-step RTBs make it easier to:

  • Optimize call routing dynamically based on performance metrics.

  • Run A/B variations between buyer groups or targeting tiers.

  • Improve payout control without duplicating campaigns.

Example Use Cases

  • Two-Step Bid Logic: Send an initial ping to gather responses, then post the complete payload only to the selected bidder.

  • Dynamic Testing: Send the same call through multiple targets and route to whichever performs best.

  • Conditional Fallback: Automatically redirect to alternate buyers when response thresholds aren’t met.

  • Tiered Bidding: Create priority-based sequences for premium vs. secondary routes.

Did this answer your question?