ForHosting KIT · Developer Utilities

KPI gap to target calculator

The KPI gap to target calculator turns two values into a clear measure of what separates current performance from the stated goal.

● BetaFree · in your browser

Run — free How it works & API

Use it from WebAPIEmailTelegramApp soon

Enter the current KPI and target to receive the absolute difference and, when requested, that difference as a percentage of the target. It works for revenue, conversion, service, production, quality, and other numeric indicators without assuming a particular unit or business model.

Read the absolute gap in the KPI's own unit

The absolute gap is the magnitude of the difference between the current value and the target value. The calculator subtracts one from the other and uses the absolute result, so the output is never negative. If current monthly recurring revenue is 72 and the target is 90, the absolute gap is 18 in the same unit used for those inputs. If performance has already passed the target, the result still shows the distance between the two values rather than labeling it as a shortfall. That distinction matters when this calculation feeds a dashboard: the number measures separation, while the surrounding report should state whether the current value is above or below target. Keep both inputs in the same unit and scale. Do not compare a percentage expressed as 0.72 with a target expressed as 90, or dollars with thousands of dollars. Consistent inputs make the returned gap directly usable in forecasts, scorecards, alerts, and progress reviews.

Understand the percentage gap calculation

When percentage output is enabled, the calculator divides the absolute gap by the absolute target value and multiplies the result by 100. Using the earlier values, 18 divided by 90 produces a percentage gap of 20 percent. Referencing the target makes KPIs with different scales easier to compare: a gap of 10 may be minor against a target of 1,000 but substantial against a target of 25. The denominator uses the target's magnitude, so a negative target still produces a nonnegative percentage that represents distance relative to target size. A zero target cannot serve as a denominator. For that reason, requesting a percentage with a zero target returns an input error instead of infinity or a misleading placeholder. If the absolute difference alone is meaningful for a zero-target KPI, disable percentage output. The response will then omit the percentage field and return the absolute gap normally, keeping the result explicit and machine-friendly.

Use the result consistently in reporting workflows

Define the KPI, measurement period, unit, and target before calculating the gap. A weekly current value should be compared with a weekly target, and a net percentage should use the same representation on both sides. The result is deterministic, which makes it suitable for scheduled reporting, spreadsheet replacements, data pipelines, and automated checks. Store the two source values beside the calculated output so reviewers can reproduce the result and understand later target changes. Because the calculation reports magnitude, add a separate status rule when direction matters. For a KPI where higher is better, compare current with target to label the position as below, met, or exceeded; for a KPI where lower is better, reverse that business rule. Avoid interpreting the percentage gap as percentage growth required when compounding, rate changes, or nonlinear relationships are involved. It is a direct relative difference from the target, useful for a concise snapshot, not a forecast of the actions needed to close the gap.

What you can do with it

Track sales performance

Compare current revenue, bookings, or units sold with the period target and publish a consistent gap metric.

Monitor operational service levels

Measure how far a response-time, throughput, or quality KPI sits from its agreed numeric target.

Standardize executive scorecards

Calculate comparable percentage gaps for KPIs that use different units and scales while retaining each absolute difference.

FAQ

How is the absolute gap calculated?

It is the absolute value of target_value minus current_value, so the result is always zero or positive.

How is the percentage gap calculated?

The absolute gap is divided by the absolute target value and multiplied by 100.

What happens when the target is zero?

A zero target causes an input error when percentage output is requested because division by zero is undefined. Disable percentage output to calculate only the absolute gap.

Does the result say whether performance is above or below target?

No. This calculator returns the magnitude of the gap. Compare the current and target values separately when your reporting needs a direction or status label.

Can I use negative KPI values?

Yes. Both inputs may be negative finite numbers. The percentage uses the absolute target magnitude as its denominator.

What does an API calculation cost?

Each API request costs $0.002. The same deterministic calculation is also available in the browser.

For developers — API access

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

API endpoint

POSThttps://api.kit.forhosting.com/biz/kpi-target-gap-calc

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.

Call it from your stack

curl -X POST https://api.kit.forhosting.com/biz/kpi-target-gap-calc \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"current_value":72,"target_value":90}'

const res = await fetch("https://api.kit.forhosting.com/biz/kpi-target-gap-calc", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.KIT_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "current_value": 72,
    "target_value": 90
  })
});
const { task_id } = await res.json();

import os, requests

res = requests.post(
    "https://api.kit.forhosting.com/biz/kpi-target-gap-calc",
    headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
    json={
    "current_value": 72,
    "target_value": 90
},
)
task_id = res.json()["task_id"]

<?php
$res = file_get_contents("https://api.kit.forhosting.com/biz/kpi-target-gap-calc", false, stream_context_create([
  "http" => [
    "method"  => "POST",
    "header"  => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
    "content" => '{"current_value":72,"target_value":90}',
  ],
]));
$task = json_decode($res, true);

body := bytes.NewBufferString(`{"current_value":72,"target_value":90}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/biz/kpi-target-gap-calc", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)

Example request

{
  "current_value": 72,
  "target_value": 90
}

Example response

{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "biz.kpi_target_gap_calc",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Pricing

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

Errors

HTTP	Code	Meaning
`401`	`unauthorized`	Missing or invalid API key.
`402`	`insufficient_balance`	Your balance doesn't cover the task price.
`404`	`unknown_type`	That task type doesn't exist.
`429`	`rate_limited`	Too many requests. Use the webhook instead of polling.

Read the full KIT documentation →