> For the complete documentation index, see [llms.txt](https://docs.roivenue.com/roivenue-resources/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roivenue.com/roivenue-resources/roivenue-training/roivenue-app/reports/targets.md).

# Targets

Targets let you set goals for any metric and track them over time. Each target shows period by period whether results are good, within tolerance or off target.

Targets turn your business goals into numbers you can track. Set a target for a metric, for example Cost, Net Revenue or ROAS, define what counts as good and what is still acceptable, and Roivenue colours every period by how close you are. You can create as many targets as you need, for the whole account or for selected sites and dimension values.

The page has two parts:

1. **Target cards:** one card for each target, with the target value, the actual value and a chart by period.
2. **Target settings:** the form where you create or edit a target.

To open the page, go to **Reports → Targets** in the left navigation. The attribution model and the date range at the top of the page apply to all cards.

***

### How to read a target card

<figure><img src="https://4279879158-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MGvvrlVUvq4TNL0oYP6%2Fuploads%2Fncm5i5WXUmMfW2V0kdFM%2F01-target-card.png?alt=media&amp;token=6fc55515-cb51-4b08-9d6f-56c20d0f2588" alt=""><figcaption></figcaption></figure>

1. **Target name and menu:** the ⋮ menu has **Edit**, **Download**, **Add to Dashboard** and **Delete**.
2. **Target and actual value** for the selected date range. The bold value on the right is the target, the value below it is the actual result. Metrics that add up, such as Cost or Net Revenue, show **Global Target Sum**. Ratios, such as ROAS or Cost per Conversion, show **Average Target**.
3. **Bars:** the actual value in each period, coloured by the result:
   * **Green:** good.
   * **Orange:** within the tolerance zone.
   * **Red:** off target.
   * **Blue:** no target is set for the period.
4. **Target line:** the target value in each period.

The bars follow the granularity of the date range. With a weekly date range, you see one bar per week, even when you entered the target by month. See FAQ 1.

***

### How to create a target

Click **Add New Target** at the top of the page. To change an existing target, choose **Edit** in the card menu. Both open the same form.

<figure><img src="https://4279879158-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MGvvrlVUvq4TNL0oYP6%2Fuploads%2FlWCox7n9w9RnTDRollpb%2F02-edit-target.png?alt=media&amp;token=2d87d976-e9d2-4541-8172-088044db768e" alt=""><figcaption></figcaption></figure>

1. **Name, Measure and Currency:** a short name for the card, the metric you track and the currency of the target values.
2. **Sites:** the sites the target applies to.
3. **Scope target to specific dimension values:** keep **Global** for the whole site, or choose a dimension and its values, for example one platform or one campaign.
4. **Type of Target, Tolerance Zone and Data Input Periods:** how Roivenue evaluates the result, how you define the tolerance and whether you enter targets per day, week or month. See the tables below.
5. **Maximum Acceptable Deviation:** how far from the target the result can be and still count as tolerable, in % of the target. Used with **Percentage From Target Value**.
6. **Target values:** enter the target for each period in the **Good** row. Roivenue calculates the **Bad** boundary from the tolerance. Use **Previous Period** and **Next Period** to move in time.
7. **Save** the target.

#### Type of Target

| Type                 | Use it for                                                       | How Roivenue evaluates the result                                                                                        |
| -------------------- | ---------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| **Higher is Better** | Revenue, conversions, ROAS                                       | Above the target is good. Between the bad boundary and the target is tolerable. Below the bad boundary is bad.           |
| **Lower is Better**  | Cost, Cost per Conversion                                        | At or below the target is good. Above the target but below the bad boundary is tolerable. Above the bad boundary is bad. |
| **Closer is Better** | Metrics that should stay in a range, for example a planned spend | Inside the range is good. Outside the range is bad.                                                                      |

#### Tolerance Zone

| Option                           | What it does                                                                             |
| -------------------------------- | ---------------------------------------------------------------------------------------- |
| **Percentage From Target Value** | The bad boundary is a percentage of the target, set in **Maximum Acceptable Deviation**. |
| **Absolute Value**               | The bad boundary is a fixed amount away from the target.                                 |
| **Manually Added Value**         | You enter the bad boundary yourself for each period.                                     |

{% hint style="info" %}
**Example:** Global Cost, **Lower is Better**, **Percentage From Target Value** with 120%. The target for January 2026 is EUR 13,333. Cost up to EUR 13,333 is good, cost up to EUR 15,999.60 is tolerable, and higher cost is bad.
{% endhint %}

**Data Input Periods** decides whether you enter the target per **Daily**, **Weekly** or **Monthly** period. Choose the period you plan in, for example monthly budgets.

***

### How to use targets on a dashboard

Choose **Add to Dashboard** in the card menu to add the target as a widget. On the dashboard, you can move and resize it with the other widgets. The widget keeps the target's settings. To change them, edit the target on the Targets page. Click the widget's name on the dashboard to get there.

If you delete a target, its dashboard widgets show that the target has been deleted.

***

#### FAQ

<details>

<summary>1. If I set a monthly target, does Roivenue compare weeks and days with it too?</summary>

Yes. Roivenue divides the monthly or weekly target by the number of days and uses this daily value for any period. A week then gets seven daily values, and a date range that covers part of a month gets only the days in the range.

</details>

<details>

<summary>2. Can I reorder targets on the Targets page?</summary>

No. Add the targets to a dashboard, where you can reorder and resize them freely. See [Dashboard](https://docs.roivenue.com/roivenue-resources/roivenue-training/roivenue-app/dashboard).

</details>

<details>

<summary>3. Why is a bar blue?</summary>

There is no target value for that period. Edit the target and fill in the period in the **Good** row.

</details>

<details>

<summary>4. Why is a high ROAS shown in red?</summary>

The target probably uses **Closer is Better**. Then any result outside the range is bad, also a result that is better than planned. Use **Higher is Better** if more is always better for you.

</details>

<details>

<summary>5. Does the attribution model change the result?</summary>

Yes, for metrics that depend on attribution, such as Net Revenue, Conversions or ROAS. The cards use the attribution model selected at the top of the page. Cost does not depend on attribution.

</details>

<details>

<summary>6. Why can't I edit a target widget on my dashboard?</summary>

Dashboard widgets show the original target. Click the widget's name to open the Targets page and edit the target there. The change shows in all widgets of that target.

</details>

<details>

<summary>7. Why can't I find a dimension when I scope a target?</summary>

Some dimensions are hidden in Targets. Go to **Data → Dimensions**, open the settings of the dimension and check whether **Hide in Targets** is on.

</details>