A goal is an action worth counting: a signup, a checkout started, a pricing page reached. The Goals card shows how many people completed each one and what share of your visitors that is.
The five ways to record one
Press Add a goal on the Goals card and you are offered five. They differ in where the goal is recorded from, not in what you get — every one of them lands on the same card and filters the dashboard the same way.
Which one to pick
Work down this list and stop at the first that fits.
| If the action… | Use | Why |
| ends on a page of its own | From a page visit | No deploy, and it counts backwards |
| is a button or link click | On a click | One attribute, no JavaScript |
| happens in your app's code | From your code | You choose the exact moment |
| happens with nobody on the site | From your server | The browser cannot report it |
| is worth a known amount | With a money value | Values need an API key |
Only the first counts your existing history. The other four begin at the moment you add them — an unmarked button's clicks from last month are gone for good.
You can mix them. A goal recorded from your code and a goal made from a page rule sit on the same card and behave identically once saved. Which method you used is a setup detail, not something a reader has to keep in mind.
The two numbers
Each goal shows people and, beneath it, completions when the two differ.
They differ for real reasons: the same person can trigger a goal twice — opening a second account, retrying a payment that failed. Showing only people would tell someone expecting nine signups that there were eight; showing only completions would suggest nine different people.
The main number is people, because "how many signed up" is what is being asked.
Filtering by a goal
Click a goal to filter the whole dashboard to the visitors who completed it — their countries, their browsers, the pages they saw. It is the fastest way to answer "where do the people who actually convert come from".
The funnel
Next to the goals list is a Funnel tab: how many visitors made it through a sequence of steps, and where they dropped.
You define the steps. Open the Funnel tab and choose New funnel: give it a name, then add between two and seven steps in the order a visitor takes them. Each step is one of three things — visited a page (exactly, starting with, or containing a path), completed a goal, or made a payment. Pick how long a visitor has to finish, from an hour to 90 days; someone who sees pricing today and pays next week still counts if the window covers it.
Save more than one and a picker appears in the tab header. Edit changes the selected funnel; deleting one removes the definition and nothing else.
Until you save a funnel, the tab shows a guess built from a page view and your two most-completed goals, and says so — two popular goals are not a sequence. Defining your own replaces the guess.
Two things worth knowing before reading it:
The steps are ordered, and the same visit must do them in order. Someone who signed up without seeing the pricing page is not counted at that step.
It follows the filters above it. Filter to organic search and the funnel redraws for those visitors only — which is usually the point, since drop-off differs sharply by channel.
Click any step to see its breakdown: which channels, pages and countries made it that far.
Goal parameters
If your code sends properties with a goal, clicking that goal opens them.
window.truestat("signup", { plan: "pro", billing: "yearly" })The panel groups conversions by each property value, so you see that yearly signups outnumber monthly ones three to one, or that one plan converts far more often than another.
Properties come from your own code — page-rule goals have none, since there is nothing to attach. See Custom events for what a property may contain.
Naming rules
Names use lowercase letters, numbers, and _, -, : only, up to 64
characters. signup, lead_won and checkout:started all work; Sign Up does
not.
The same rule applies to all five methods, so a goal that starts as a page rule can later move into your code without being renamed.
A name can only be used once per site. If a rule and a code-based goal shared a name, the card could not tell you which one it was counting.
Some names are reserved for the events the billing integration writes. See reserved names for the list.