Conversion goals

A goal marks a conversion that matters to you — a key page reached, a named action taken, or revenue earned — and tracks how often it happens. Unlike funnels, which measure an ordered journey, a goal measures a single outcome.

Goal types

Each goal carries a type and a value.

Type	Value	Counts
`pageview`	a page path (e.g. `/thank-you`)	each visitor who views the matching page
`event`	an event name (e.g. `Signup`)	each visitor who fires the matching named event
`revenue`	an event name (e.g. `purchase`)	conversions and the revenue attached to that event

pageview: the value is a path. The path field suggests known pages as you type — drawn from your site’s sitemap.xml and the pages Takt has already seen — but you can always type any path freely.
event: the value is the exact name of a named event.
revenue: like an event goal, but Takt also sums the revenue amounts sent with the event. You pick the display currency; amounts are reported per currency.

Revenue goals read the `revenue` field of your events. Send it from the tracker, e.g. takt('purchase', { revenue: { amount: 49, currency: 'EUR' } }).

Creating a goal

Open your site, then the Goals tab.
Pick the type (pageview, event or revenue).
Enter the value — a page path or an event name. For a revenue goal, also pick the currency.
Save.

Reading conversions

A goal report respects the period selected on the dashboard and shows, for each goal:

Visitors: unique visitors who triggered the goal at least once.
Conversions: total number of conversions.
Conversion rate: converted visitors as a share of all visitors over the period.
Revenue: for revenue goals, the total per currency.

Retroactive by design

Goals are computed at query time from events already collected. Creating a goal immediately shows its history over the chosen period: no change to the tracking script is required, and you can add or remove goals at any time without losing data.

API

Goals are manageable through the REST API. Operations require an API key carrying the right scope — goals:read for reads, goals:write for writes.

Method	Route	Scope
`GET`	`/orgs/{org}/sites/{domain}/goals`	`goals:read`
`POST`	`/orgs/{org}/sites/{domain}/goals`	`goals:write`
`DELETE`	`/orgs/{org}/sites/{domain}/goals/{id}`	`goals:write`
`GET`	`/sites/{domain}/stats/goals`	`goals:read`

The report endpoint (/stats/goals) accepts the same period parameters as the other statistics endpoints.

What’s next

Events & payload — how pageviews and named events (and revenue) are defined.
Conversion funnels — measure an ordered multi-step journey.
API reference — key authentication and scopes.
See the goals demo — goals on a real dataset, no account needed.