A goal names one business outcome and gives it one daily series: completions, converters, and a conversion rate, drawn on the Goals screen and served by the API like any other report. It is configuration, not code: you create one on Settings, Goals, and the matching starts from there.

Three kinds

Kind	Counts	Typical use
Event	Every custom event with exactly the name you set	Signups, contact forms, trials started. See custom events
Page	Every pageview of the path you set, spelled the way the collector spells a path: trailing slash off and percent-encoding decoded, so /thank-you/ is saved and shown as /thank-you and matches	A thank-you page, a confirmation step, a pricing view
Order	Every accepted commerce order that is not a refund	Purchases, with no match value to configure

An event goal will not accept pageview or pageleave as its name: page outcomes have their own kind, and pageleave is a measurement signal rather than an outcome.

What a goal reports

Event and page goals report daily completions and exact daily converters, and the conversion rate divides those converters by the day's visitors with a pageview. An order goal counts sales as completions, zero-value orders included. A refund reduces net revenue but never subtracts a completion. Order goals carry no converter count or rate, because the commerce contract deliberately carries no visitor identity to count converters with.

Event values and order revenue stay grouped by currency. Kehai never adds unlike currencies and never infers an exchange rate. An amount without a currency stays a bare number.

Set a target, get pacing

A target turns a goal into the weekly question: are we going to hit the number. It names the goal, the measure, completions or revenue in one currency, the period, a month or a quarter cut in your site's own time zone, the amount, and the expected shape, straight-line or seasonal. The amount is a whole number of completions, or an amount of money, and at most a billion. One target per goal, measure, and period. Setting another for the same period replaces it.

With a target set, Overview shows pacing beside the goal and the Goals screen shows the run rate you need against the run rate you have, in plain status bands. Pacing is arithmetic against your own number, so it works from the first week. The modeled projection beside it belongs to the forecast module and its own rules.

Imported history joins the same goal

If you migrated from GA4, Plausible, or Umami, an imported outcome can be mapped onto a goal you already have. It becomes that goal's history, read through the same fields as every other day, with its origin labeled on the row. Imported days are never restated as Kehai's own measurements.