Goals & conversions
A goal turns a raw signal — a custom event or a pageview on a specific path — into a measured conversion, with a conversion rate and breakdowns by source, country, device and more.
Goals are created per site in the dashboard (your site → Goals). Each goal has a name, a type, and a matcher.
Goal types
There are two types.
Custom-event goals
Match a custom event by its exact name. Fire the event once from your code, then create a goal whose matcher is that name.
| Field | Value |
|---|---|
| Type | custom_event |
| Matcher | The event name, e.g. signup |
A session that fires window.satsu("signup") at least once counts as one
conversion.
Path goals
Match a pageview by its path — no code required. Useful for "reached the thank-you page" style goals.
| Field | Value |
|---|---|
| Type | path |
| Matcher | A path starting with /, e.g. /welcome |
Path matchers support a single trailing wildcard: /blog/* matches any path that
starts with /blog/. There are no other patterns — no regex, no mid-string
globs. A matcher without a * must match the path exactly.
How conversions are counted
- A conversion is a unique session that satisfies the goal at least once. Firing the same event twice in a session is still one conversion.
- The conversion rate is converting sessions ÷ total sessions in the selected period.
- Breakdowns attribute each converting session to its first-touch value — the source, campaign, country or device the session started with. This matches how channel attribution works elsewhere in Satsu.
Goals are evaluated at query time against your existing events. Creating a goal works retroactively: it measures conversions from data you've already collected, not just from the moment you add it.
Plan limits
The number of goals per site depends on your plan. When you hit the limit, upgrade for more (or unlimited on higher tiers). Deleting a goal frees a slot.
Next: What we track →