Goals

Track conversions from page visits, custom events, and autocaptured interactions

Goals Dashboard

Goals let you define specific actions — from visiting a page to clicking a button — and measure how often your visitors complete them. Each goal tracks a conversion rate against total sessions, giving you a clear picture of how effectively your site drives key outcomes.

Creating a Goal

Click "Create Goal"

Every goal has:

Name (optional) — A friendly label like "Completed Checkout" or "Signed Up"
Type — Page, custom event, outbound link, button click, form submission, or copied text
Value — A required path or custom event name, or an optional pattern that narrows an autocaptured interaction

Choose a Goal Type

There are six goal types. Page and custom event goals require a value. For the four autocaptured interaction types, the pattern is optional—leave it empty to count every interaction of that type.

Page goals track when a user visits a URL matching a given path pattern.

The value must be a path starting with / (not a full URL)
Wildcards are supported:
- * matches a single path segment — /blog/* matches /blog/my-post
- ** matches multiple segments — /docs/** matches /docs/api/v2/intro

The form provides autocomplete suggestions based on actual paths seen on your site.

Custom event goals track when an event with a specific name is fired. The value is the event name (e.g., signup_clicked, purchase_completed).

Events must be tracked using the Rybbit tracking script. See Track Events for setup instructions.

Outbound link goals track clicks on links that lead away from your site.

Enter a destination URL pattern such as https://example.com/pricing or https://*.example.com/**
Leave the pattern empty to count clicks to any external URL

Outbound link tracking is enabled by default.

Button click goals track clicks on buttons, button/submit inputs, and elements with role="button".

Enter a visible button-text pattern such as Sign Up or Start * Trial
Leave the pattern empty to count any button click

Buttons that already use data-rybbit-event are recorded as custom events instead.

Form submit goals track submissions of HTML forms.

Enter a form name or ID pattern such as signup-form
The pattern can also match the form's action URL
Leave the pattern empty to count any form submission

Copy goals track text that visitors copy from your site.

Enter a copied-text pattern such as PROMO*
Leave the pattern empty to count any copied text

Autocaptured interaction patterns support wildcards: * matches one or more characters and ** also matches an empty value. The form suggests values already observed on your site.

Enable autocapture first

Button click, form interaction, and copy tracking are disabled by default. Enable the event types you want to use in the Tracking tab of your site settings. Only interactions collected after tracking is enabled can count toward a goal. See Autocapture for the properties collected with each type.

Add Property Filters (optional)

Property Filters

You can narrow a goal to only count conversions when specific properties match:

Page goals — Filter by URL parameters (e.g., only count visits where utm_source=adwords)
Custom event goals — Filter by event properties (e.g., only count events where plan=premium)
Autocaptured interaction goals — Filter by captured properties such as url, text, formName, formId, or formAction

Toggle Match specific URL parameters or Match specific event properties to add filters. You can add multiple filters per goal — all filters must match for a session to count as a conversion.

Goal Metrics

Each goal card displays:

Total Conversions — The number of distinct sessions that completed the goal
Conversion Rate — Conversions divided by total sessions in the selected time period, shown as a percentage with a visual progress bar

Goals respect the global date range and filters (country, device, browser, etc.) applied on the page.

Viewing Converted Sessions

Click a goal card to expand it and see the sessions that converted. Each session shows:

Entry and exit pages
Session duration
Location (country, region, city)
Device, browser, and OS
Referrer, channel, and UTM parameters
User ID (if identified)

Sessions are sorted by most recent first and paginated.

Related Documentation:

Autocapture — Configure automatically captured interactions
Track Events — Set up custom event tracking
Funnels — Analyze multi-step conversion paths