# RTB 2.0:  6% to 800% More Claimed Calls from the Same Traffic

## Why this matters

The RTB market has changed. Publishers ping more buyers, expect answers faster, and send their calls to whoever answers first with a good bid. A bid that arrives late, or a buyer that wasn't pinged in time, means a call you never see.

RTB 2.0 is our answer to that. Customers already on RTB 2.0 are seeing anywhere from **6% more claimed calls up to 8x more**, from the same campaigns and the same traffic.

## What's new

RTB 2.0 is a rebuild of how Retreaver answers RTB pings. It applies to campaigns that receive RTB inbound pings.

- **Faster responses.** Retreaver was already fast, and RTB 2.0 answers faster still.
- **Much more capacity.** RTB 2.0 can receive and send far more pings at the same time, so busy hours no longer slow your answers down.
- **Smarter pinging of your buyers.** RTB 2.0 is more careful about which buyers it pings and when, so more pings come back with a buyer ready to take the call.
- **Many improvements you won't see directly.** RTB 2.0 also changes a lot behind the scenes that isn't visible in the dashboard, and all of it goes toward answering more pings with a buyer who can take the call.
- **RTB 1.0 vs RTB 2.0 results.** You can compare your claimed and expired pings on RTB 1.0 with those on RTB 2.0, and see the difference for your own campaigns.

RTB 2.0 also includes new routing features:

- **Speed routing.** Answer the publisher as soon as the first buyer can take the call, instead of waiting for the slowest buyer.
- **Instant routing.** Answer the publisher straight from your routing settings, without waiting on buyer webhooks during the ping.
- **Better inbound and outbound limits.** More control over how many pings you receive from publishers and how many you send to your buyers.

You don't need these features to see the improvement. Customers moved to RTB 2.0 without changing anything report much better results.

A common misconception is that Ping Shield limits your RTB. Ping Shield is a spam filter you can turn on to control the pings your campaigns receive. It limits a publisher by claims: they can send as many pings as they like as long as calls keep coming. A publisher that sends pings but no calls, or uses a platform that sends dummy pings for them, uses up your capacity, and Ping Shield lets you limit them if you choose. Together with the new limits on postback keys and webhooks, it gives you the control to answer every publisher and buyer request you want to answer.

## What doesn't change

Nothing changes on your side. All the changes are internal.

- No API changes.
- No endpoint changes. Publishers keep pinging the same URLs.
- Your campaigns, buyers, and routing settings stay as they are.

## Will it help every campaign?

Not every campaign. Some campaigns are set up in a way that RTB 2.0 can't improve. If you want to know whether yours is one of them, we will look at it with you.

## What are the results?

RTB 2.0 helps a lot of campaigns, though not all of them. Some campaigns report 6% more claimed calls, some 30%, and some 800%. These numbers come from a 50/50 split of the same traffic, so the comparison is fair.

Here are results from three customers:

### Company 1 - 8x

RTB1.0
![image](/media/08/08f6d6ec79e106b2322d0cec4b4cd460578518c2d13a398d680e6ea9f2f85652.png)

RTB2.0
![image](/media/b7/b7f67a39c8ec2a7bddffefacc413894622ef9540bbeb026ba4ba1924d3fa9add.png)

### Company 2 - 60%

RTB1.0
![image](/media/35/35637fc52096eabae58fd81669990e69ab8f53de5938328a602e9ede96e00630.png)

RTB2.0
![image](/media/d0/d05929e051f4b60ffb5e6826a374d8bbc6e0ccefb67cf14e9d8c1687636651c7.png)

### Company 3 - 6%, which is about 1,000 more claimed calls

```
    "rtb1_results": {
      "claimed": {
        "resolutions_count": 16886.0,
      },
    },
    "rtb2_results": {
      "claimed": {
        "resolutions_count": 17954.0,
      },
    }
```

## Results depend on your campaigns

RTB 2.0 can't improve every campaign, and results depend on how a campaign is set up. We will work with you to find the right configuration for yours. You can also start by asking the [Retreaver MCP](/guides/install-mcp-server) how to improve a campaign.

## Getting RTB 2.0

Most companies are being moved to RTB 2.0 right now. If you're not sure whether your campaigns are on RTB 2.0, or you'd like to be moved, [request RTB 2.0](/rtb2) or use the form below.

We're also happy to go through your RTB 1.0 and RTB 2.0 results with you, and talk through speed routing, instant routing, and limits for your campaigns.

:::contact-support{kind="rtb2"}
Tell us which account to move, and we'll set it up with you.
:::

## Testimonials

Feel like we should add some

![Screenshot 2026 11 17 at 15.36.19](/media/d7/d7630ccb37c8f09118df2ad3091b4197f6be76bfd5f57cfd4631c620f522dc74.png)

![Screenshot 2026 11 17 at 15.35.31](/media/cf/cf76767046da552f70c1d7370c9b0573d3b9ce26c3ca5bc7320ede43ab7d154e.png)
