DoubleVerify reported $42.3M of remaining performance obligations at 31 Dec 2025, up 35% from a year earlier. That is 0.1 years of trailing revenue already under contract.
Twelve-month book-to-bill: 1.01, i.e. 1.01 of new orders for every 1 of revenue recognised.
Backlog growth minus revenue growth: +21 points — orders are running ahead of revenue.
The latest filed figure is more than 200 days old.
DoubleVerify backlog history
Remaining performance obligations at each quarter end (bars) against trailing twelve-month revenue (line).
Amounts in USD. Source: SEC XBRL filings.
Quarter end
Backlog (RPO)
TTM revenue
Coverage
Customer prepayments
31 Dec 2025
$42.3M
$748M
0.1 yrs
n/a
31 Dec 2024
$31.3M
$657M
0.0 yrs
n/a
30 Sep 2024
$29.7M
$638M
0.0 yrs
n/a
30 Jun 2024
$16.9M
$613M
0.0 yrs
n/a
31 Mar 2024
$13.9M
$591M
0.0 yrs
n/a
31 Dec 2023
$10.9M
$572M
0.0 yrs
n/a
Questions
What is DoubleVerify's backlog?
DoubleVerify reported $42.3M of remaining performance obligations at 31 Dec 2025, up 35% from a year earlier. That is 0.1 years of trailing revenue already under contract.
About these numbers
Remaining performance obligations (RPO) are revenue a company has contracted but not yet recognised, as reported in its SEC filings (XBRL tag RevenueRemainingPerformanceObligation). Coverage = backlog ÷ trailing twelve-month revenue. Book-to-bill = (change in backlog + revenue) ÷ revenue. Conversion = revenue recognised ÷ the backlog at the start of each quarter, summed over four quarters. Counterparty values come from company filings and releases.