10Reports
Goals, funnels and paths
Goals by page URL and by event, automatic goals, funnels of up to 10 steps and user paths by page and category — how Gauss counts them.
Goals show how many visits ended with the action you care about, funnels show at which step people drop off, and paths show how they move around the site. This page explains how Gauss counts all three.
The dashboard is in closed beta. You can apply on beta application.
Goals
A goal is what counts as a conversion. There are two kinds:
| Kind | Example | What counts |
|---|---|---|
| Page visit by pattern | /thanks* | A view of /thanks, /thanks/pro and any page whose path starts with /thanks |
| Event | form_submit with the condition form_id = callback | Submitting the callback form, but not other forms |
The event can be automatic (see What's tracked automatically) or your own:
gauss('event', 'generate_lead', { form_id: 'callback' });How to send your own events — Custom events.
A visit converts when it contains a goal. Conversion rate = visits with the goal ÷ all visits (the same as session conversion rate in GA4). Conversion rate by visitors is shown as well.
Automatic goals
When a site is created, these events are already enabled as goals, with nothing to set up:
| Event | What it is |
|---|---|
form_submit | any form submitted on the site |
contact_click | a click on a phone, email, WhatsApp or Telegram link |
generate_lead | a lead tagged by the site |
sign_up | a sign-up tagged by the site |
purchase | a purchase tagged by the site |
The tracker sends form_submit and contact_click on its own. generate_lead, sign_up and purchase appear once the site starts sending them. You can turn off goals you don't need in the site settings.
Goal value
A conversion can have a money value: from value and currency in the event itself, or a default from the goal settings (for example, a lead = $40). A repeated purchase with the same transaction_id within 48 hours does not double revenue. More — Conversions and e-commerce.
Funnels
Coming soon. Funnels are planned for the dashboard. Below is how they will be counted.
A funnel has up to 10 steps, where each step is a goal or a page. For example: catalog → product page → cart → purchase.
- The funnel window is set in its settings: within one visit, or within the visitor's day.
- Each step shows how many people reached it, their share and how many dropped off.
- Steps must be completed in order; other pages can come in between.
Coming soon. Automatic funnels: Gauss will suggest funnels for a goal based on the most frequent paths that lead to it, and you can save the one you like.
User paths
The report shows where people go from the entry page, or how they arrived at a selected page or goal.
- Nodes are pages or page categories. At the category level a path looks like “Home → Blog → Article → Product”.
- Repeats are collapsed: five articles in a row become one “Article” node, and its label shows how many pages were viewed in it on average. You can turn collapsing off, and then every view is a separate step.
- Nodes expand: a click shows exactly which pages are inside, with pageviews and visits, and lets you continue the path from one selected page only.
- Each step shows the most frequent transitions (5 by default) with the number and share of visits; the rest go to “Other” and “Exit”.
To separate the article list from the articles themselves, set two category rules: one for the section page (“Blog”) and one for the pages inside it (“Article”). How to set this up — Page categories.
Limits
- Within one day only. Paths are built from visits, and funnels work within a visit or a day. The visitor identifier changes every day, so someone who comes back tomorrow is a different visitor. The dashboard shows a hint next to these reports.
- A conversion belongs to the visit where it happened. A lead left three days after an ad click is credited to that visit's channel, often “Direct”. To link a CRM deal to the lead, use offline events.
- Retention. Paths and funnels are calculated from raw events and are available within your site's raw data retention period. Event goals and their value are also in daily summaries kept for 25 months.
- Day boundaries follow the site's time zone, see Metrics.