Skip to main content

Reusing Outbound RTB Buyer Responses with Per-Call Caching

Understand how Moja reuses a valid outbound RTB buyer response when the same step is evaluated again during rerouting, and how to verify cached usage.

E
Written by Eric Gardona

Location: Calls → Call details → Life Log / RTB tab; Inbound RTB → Requests → Steps

Use case: Reuse a valid outbound buyer response when the same RTB step is evaluated again during rerouting, without sending the buyer another HTTP request.

Overview

During a single call, Moja may evaluate an outbound RTB buyer more than once while searching for an eligible route. Per-call RTB response caching allows Moja to reuse a valid response from the earlier evaluation instead of sending the buyer a duplicate request.

This can reduce buyer-side request volume, avoid unnecessary duplicate pings, and shorten rerouting time.

How per-call RTB caching works

  1. Moja evaluates an outbound RTB step and sends an HTTP request to the buyer.

  2. The buyer returns a response, such as a valid bid and route.

  3. Moja stores the usable response in the current call session.

  4. If rerouting evaluates that RTB step again during the same call, Moja can reuse the cached response instead of sending another buyer request.

  5. The reused step is marked with a sky-blue Cache badge.

Example: the same buyer is evaluated twice

A routing plan is attempting to find an available buyer for one call:

  1. First evaluation: Moja sends an outbound RTB request to Buyer A. Buyer A returns a valid response.

  2. Routing continues and later reaches the same RTB step again while rerouting.

  3. Second evaluation: Moja reuses the valid response stored for this call instead of sending Buyer A a second HTTP request.

  4. The second RTB step displays the Cache badge, confirming that the response was reused.

What the cache does—and does not do

  • Per-call only: Cached responses belong to the current call session. They are not shared across different calls or callers.

  • Response reuse: The cache reuses an existing valid buyer response. It does not create a new bid or change the buyer response.

  • No duplicate buyer request: When a step is served from cache, Moja does not send a new HTTP request for that evaluation.

  • Validity still matters: Expired cache entries are not replayed. Bid expiration and TTL controls continue to protect routing from stale responses.

  • Automatic behavior: The cache is part of RTB routing behavior; the Cache badge provides visibility when reuse occurs.

How to confirm a response was reused

Open a call or inbound RTB request that contains RTB activity and review either:

  • Calls → Call details → Life Log / RTB tab

  • Inbound RTB → Requests → Steps

A step served from the per-call cache displays a sky-blue Cache badge. A step without that badge is not shown as having been served from cache.

Why this matters

  • Reduces unnecessary duplicate requests to buyer endpoints.

  • Avoids relying on the buyer platform to recognize and handle a repeated ping.

  • Improves visibility when troubleshooting multi-path or rerouting behavior.

  • Preserves the original valid response while its usable lifetime remains eligible.

Related guidance

Did this answer your question?