Configure multi‑step RTB formulas

Location: Targets/RTBs → Create RTB Formula
​Last Updated: September 15, 2026

---

Overview

Use more than one HTTP request on a single RTB formula when the buyer needs a ping first, then a post (confirm) that reuses values from the ping. One formula runs several request steps in order; map fields from an earlier step (for example a bid id or token) into the next step’s URL, headers, or body.

This is not a substitute for an RTB group. Comparing several buyers still means several formulas in a group. Multi‑step is chained HTTP on one formula.

---

How multi‑step runs

Within one RTB formula, you can define step‑based logic that executes sequentially:

• Ping then post — Step 1 is a lightweight ping. Step 2 posts or confirms using mapped fields from step 1.

• Map Response Fields to Tags — After you Send a test and get a response, map fields. Those tags are available on later steps.

• Continue on Failure — On a non‑last step, if this is on, a failed step does not stop the rest of the formula. Off (default) stops the formula at that step.

• Payout and duration — Come from the parsed winning response (phone or SIP, payout, duration) — not a separate payout editor on each step.

---

Winning Step (RTB groups only)

Turn on Enable Winning Step only when this formula sits in an RTB group. That extra step runs after this formula wins the group auction (for example a confirm/post to the buyer). It does not run if the formula is used alone, outside a group.

---

Logging & resilience

Multi‑step RTBs include built‑in observability and fault tolerance:

• Expanded logging — Step‑level responses are recorded to support debugging and analysis.

• Continue on Failure — Enables a multi‑step RTB to proceed to the next step even if the current step fails (non‑last steps only).

• Backward compatibility — Single‑step RTB formulas continue to work unchanged.

---

Why this matters

Previously, implementing layered bidding logic required creating and maintaining multiple formulas — increasing complexity and reducing visibility.

With multi‑step RTBs, you can manage advanced bidding strategies in one place, which helps you:

• Optimize call routing dynamically using performance data

• Run A/B variations across buyer tiers or targeting strategies

• Improve payout control without duplicating campaigns

• Reduce configuration overhead and routing errors

---

Example use cases

• Two-Step Bid Logic
  Send a ping to gather bids, then send the full payload only to the selected bidder.

• Map values between steps
  Map bid_id or token from Step 1’s response into Step 2’s URL, headers, or body.

• Conditional Fallback
  Automatically redirect traffic if response thresholds aren’t met.

---

Get started

1) Open or create an RTB formula

Navigate to Targets/RTBs → Create RTB Formula, then create a new formula or open an existing one.

---

2) Add steps in sequence

For each step, define:

• Request URL

• HTTP method

• Headers and parameters

Click Send to test a step. Unresolved caller/ZIP/state fields prompt for a test value — do not bake a test ANI into the saved formula.

---

3) Map Response Fields to Tags

• Enable Map Response Fields to Tags

• Click a response field to create a mapping

• Mapped variables become available in all subsequent steps

---

4) Chain steps together

• Add a new step

• Copy the previous step’s URL if needed

• Use Edit → Add Parameter to inject mapped variables into the request

---

5) Define the Winning Step (RTB groups only)

If the RTB is used in an RTB group, select which step determines the winning route, and enable Winning Step for the confirm/post request that should run only after this formula wins the group auction.

---

6) Save & deploy

Once saved, the RTB will automatically process multi‑step logic during execution.

---

Example flow

• Step 1: Call a “ping” endpoint → returns BID_ID

• Step 2: Call a “pong” endpoint using BID_ID → returns payout and duration

Moja automatically maps the results into your RTB routing and billing flow.