Goals

A goal is a specific outcome you want to measure: a signup, checkout, paid upgrade, or a reader reaching the bottom of an article. Statable counts every completion and shows a conversion rate against sessions, broken down by every dashboard dimension.

Three goal types

1. Pageview goal

Fires when a visitor loads a URL matching a path you specify. Three operators:

Equal: exact path match. /thank-you matches /thank-you and nothing else.
Begins With: prefix match. /checkout/ matches /checkout/cart, /checkout/payment, /checkout/complete.
Contains: substring match. success matches /order/success, /signup-success, /payment-success-page.

Pageview goals need no code changes, just the path:

Type:     Pageview
Operator: Equal
Path:     /thank-you

Use them for confirmation pages, milestone screens, and any URL that already exists as a side-effect of the action.

2. Custom event goal

Fires every time a custom event with the matching name is recorded. The event must already be firing on your site. Statable doesn't auto-create events from goal definitions.

<button data-statable-event="Sign Up">Sign up now</button>

Type:  Custom Event
Event: Sign Up

Custom event goals fit when the action has no dedicated URL: modal submissions, in-app interactions, anything fired with window.statable.t().

3. Scroll depth goal

Fires when a visitor scrolls past a percentage threshold on any page in the session. Threshold is a 0–100% slider:

Type:      Scroll Depth
Threshold: 75%

Scroll goals work well for content sites. A 75% scroll on a long-form article is a much stronger engagement signal than a pageview alone.

Creating a goal

Go to Site settings → Goals.
Click Create Goal.
Pick a type: Pageview, Custom Event, or Scroll Depth.
Fill in the type-specific fields (path + operator, event name, or threshold).
Optionally rename the goal. Leaving the name blank auto-generates one from your inputs (Pageview equal /thank-you, Event Sign Up, Scroll 75%).
Save.

Create goal screen

The goal starts counting from the moment you save it. Historical data is not backfilled. Visits before the goal existed don't retroactively become conversions.

Editing and deleting

From Site settings → Goals, every goal has Edit and Delete:

Edit changes the goal definition going forward. Existing conversion data stays. New criteria apply from the save timestamp.
Delete removes the goal and its historical stats. No soft-delete. Check no dashboards or reports depend on it first.

If criteria change significantly (e.g. switching from Equal /thank-you to Begins With /checkout/), it's usually cleaner to create a new goal and delete the old. That avoids mixing two definitions into one stream.

Naming conventions

Auto-generated names are descriptive but verbose. For dashboards you check daily, override them with short, action-oriented names:

Auto-generated	Better
`Pageview equal /thank-you`	`Newsletter Signup`
`Event Sign Up`	`Account Created`
`Scroll 75%`	`Article Read`
`Pageview begin /checkout/`	`Checkout Started`

A consistent style (past tense, capitalized, no jargon) pays off when you have a dozen goals and need to scan the report quickly.

Next: read the data

Once a goal is firing, head to Conversion tracking to see how it surfaces in the dashboard, how to filter sessions by completion, and how to compare conversion rates across channels.

Ready to take control of your web analytics? Try Statable free for 30 days — no credit card required, full feature access, GDPR-compliant by default. Start your free trial or view a live demo.