---
title: "ROI"
description: "Translate an app's protection activity into an estimated return on your DoveRunner investment."
---
> For the complete documentation index, see [llms.txt](https://docs.doverunner.com/llms.txt).

**ROI** turns the hacking attempts DoveRunner blocked for one app into an estimated money value and sets it against what you spent on protecting that app. The console describes it as *Translate protection activity into the return on your investment, per app and platform.*

Open **Mobile App Security → Analytics → ROI**.

**Available only for eligible accounts:** 
ROI is shown only to accounts enabled for Access Signals. For other accounts the **ROI** tab is hidden, and opening the page directly shows *ROI is not yet available for your account.* To enable it, contact the [Help Center](https://support.doverunner.com).


## Filters

| Filter | Description |
| :----- | :---------- |
| **Application** | Search or select the app. Nothing is shown until an app is selected. |
| **Platform** | **Android** or **iOS**. When you switch platform, the app stays selected if an app with the same name exists on the other platform. |
| **Period** | **Last 3 Months** (default), **Last 6 Months**, **Last 9 Months**, **Last 12 Months**, or **Custom**. |

A preset covers whole calendar months: **Last 3 Months** is the current month plus the two months before it, not a rolling 90 days. **Custom** opens **From** and **To** month pickers limited to the last 12 months; click **Apply** to use the range, or **Simple timeframes** to go back to the presets.

Your app, platform, and period are remembered in the browser, so the page reopens on the same selection.

**Note:** 
ROI figures are calculated from **Release**-mode data. Builds sealed in Test mode are not included.


## Return on investment

The banner at the top shows two headline figures:

| Figure | How it is calculated |
| :----- | :------------------- |
| **Return on investment** | **Potential savings** ÷ **Total spend**, rounded to a whole number and shown as a multiplier (for example `12x`). |
| **Net value (savings - spend)** | **Potential savings** − **Total spend**, shown in US dollars. It never goes below $0. |

Both show a dash (`–`) when there is no spend record for the app in the selected period, so the page doesn't report an unknown spend as $0.

## Summary tiles

| Tile | Shows |
| :--- | :---- |
| **Active devices protected** | *Peak monthly active devices in period* — the highest monthly active device count in the selected period. |
| **Hacking Attempts Blocked** | All hacking attempts blocked in the period. The line beneath gives how many of them were high-severity (*N high-severity attempts prevented*). |
| **Potential savings** | *Estimated loss avoided* — see [How potential savings is calculated](#how-potential-savings-is-calculated). |
| **Total spend** | *Your AppSealing investment* — the billed usage for this app and platform over the period. Shows `$ –` when no spend record is found. |
| **Service Reliability** | The live DoveRunner service status badge from [status.doverunner.com](https://status.doverunner.com). |

## Hacking Attempts Blocked chart

A bar chart of the period's blocked attempts. Use **Break down by** to change the grouping:

| Option | Bars |
| :----- | :--- |
| **Month** | One bar per month in the period. |
| **Country** | The eight countries with the most attempts; the rest are combined into **Other**. |
| **Hacking Type** | One bar per threat type, split into **High severity** and **Other**. Click either legend item to show only that part; click it again to show both. |
| **OS Version** | The eight OS versions with the most attempts; the rest are combined into **Other**. |

## How potential savings is calculated

The info box at the bottom of the page explains the formula:

**Potential savings = high-severity attempts prevented × $30** (an estimated average loss per incident).

The console counts these threat types as high-severity, because a successful attempt of this kind is the most likely to cause a financial loss:

- Repackaged application
- Code modification
- Detour security module
- Dynamic memory cracking
- Bypass security module

All other threat types count toward **Hacking Attempts Blocked**, but not toward potential savings.

**Caution:** 
Potential savings, net value, and return on investment are estimates that illustrate value. They are not booked savings.