Goals

A goal is what finishing looks like on your site. When a visit reaches one, it counts as completed: on the visit's page, in the funnel on Insights, and in the abandoned insight, which looks for agents that start a purchase or form and never finish.

The defaults

Until a project has goals, a visit is completed when it reaches a confirmation page: a path segment such as /thank-you, /thanks, /order-received, /order-confirmation, /confirmation, /success or /checkout/success. Your first goal replaces these, so if you want them too, add them as goals. Delete every goal and the defaults come back.

Pages and actions

• A page goal is a path. It's matched against the request's path alone, ignoring case, the query string and a trailing slash. It isn't percent-decoded, so write the path as it's requested, such as /caf%C3%A9. * stands for any characters, slashes included, up to 4 times in a goal. Up to 200 characters.
• An action goal is the name your code passes to track(), matched in full and ignoring case. Up to 100 characters.
• A blocked request or a server error never counts, even on a goal's path.

Managing goals

Owners and admins add and delete goals under Settings, Goals; everyone on the project sees them. A project can have up to 20 goals. Insights and each visit's page are worked out again with the new goals the next time someone opens them, so a new goal applies to the last two weeks there as well. The action counts on the overview are taken as events arrive, so counts from before a goal change stay as they were.

A goal is your own text, a path or an action name. It holds nothing about your visitors, so leave anything secret out of it.