Goals
Goals turn a page visit or a custom event into a conversion definition, authored in Settings and read on the Goals report, evaluated fresh against your events every time you open it.
Goals turn a page visit or a custom event into a conversion you can track. Define a goal once, on a single site, and the Goals report counts how many sessions on that site complete it for any period you choose.
Goals are a two-surface workflow: you author goal definitions in Settings, and you read their conversions on the Goals report. The two surfaces stay in sync automatically; nothing needs to be republished or refreshed between them.
Defining a goal
Open the Goals settings page and choose New goal. Every goal needs:
- Name - a short label shown on the Goals report.
- Site - the site this goal is evaluated against. A goal always belongs to exactly one site, and the site cannot be changed later; delete and recreate the goal to move it.
- Type - Page visit or Custom event.
A Page visit goal matches either an exact path (for example /thank-you, matched exactly, with no trailing-slash normalization) or a path prefix (matches that path and anything beneath it). A Custom event goal matches events fired by window.pulse.track("event_name", { ...props }) on your site, by event name.
Both types can carry an optional value per conversion, in CAD or USD. Give a goal a value to see booked value totalled on the Goals report; leave it blank for a goal you only want to count, not price.
Reading conversions
The Goals report lists every goal as a tile: the conversion count for the selected period, the conversion rate, the number of converted sessions, and, when a goal carries a value, its booked value. Until your workspace has at least one goal, the report shows an empty state prompting you to define your first one.
Goals evaluate at read time
No conversion is stored anywhere. Each time you open the Goals report, it scans every event on the goal's site for the selected period once, and checks that single set of rows against every goal's rule.
Conversion counts follow the same sampling convention as the rest of Web analytics: a sampled event counts as 10 toward the total. Converted sessions and converted visitors are always counted directly and never weighted, and the conversion rate is converted sessions divided by all sessions seen on that site in the period.
Where goals plug into other reports
Goals are the one definition that other reports read from, rather than defining conversions of their own:
- Paid campaigns omits its conversion tiles entirely until your workspace has at least one active goal, then attributes conversions to whichever ad platform sent the visitor. See Reports.
- A journey in Marketing can exit a contact when a goal condition is met. That exit condition needs a goal to already exist, so define the goal here first if you are setting one up for a journey.
Updated