Events
This route only includes events on the web platform. App and mini program analytics reuse the same page, with labels switched to users and screens.
ConsoleWeb analyticsEventsWhat the report shows
The cards are total events, distinct visitors who fired one, number of names, and interactive events. Interactive events are those whose names do not start with a double underscore. Outbound clicks, downloads, form submits, and 404s do start with a double underscore and are shown with readable labels.
The table has name, count, distinct visitors, times per visitor, share, and a 7-day trend. Above it, the five most frequent events are charted. Open a row for property keys and values. If the site has goals, a property value also shows a conversion rate whose denominator is visitors who had that value. Pageviews can be broken down by one property key as well.
How to use it
If there are no custom events yet, the page shows a snippet. Naming rules are in Custom events and Events & properties. For per-user averages, formulas, breakdowns, or a saved metric, open Event analysis.
Limits
This page lists names that have already been collected. It cannot edit definitions. Definitions, hiding, and blocking live with event definitions in all-platform analytics. See Event definitions. A high-cardinality property is a poor fit for a value-by-value table here.
FAQ
Do autocaptured clicks count as events? Outbound links, downloads, forms, and 404s do. Clicks on elements are in heatmaps and autocapture; they do not each become an event name. See Autocapture & definitions.
Goals
A goal only asks whether something happened. It does not require an order. To see how many people are lost between step one and step two, use Basic funnels, paths & retention.
ConsoleWeb analyticsGoalsWhat the report shows
The cards are total conversions, distinct people who converted, overall conversion rate, and revenue. Each goal is a row: type (page or event), match rule, conversions, distinct converters, conversion rate, change, and revenue. The rate’s denominator is distinct visitors in the range, not sessions. The overall rate is distinct visitors who completed at least one goal, divided by distinct visitors in the same range.
A page goal matches a path: exact, prefix, or wildcard. An event goal matches an event name. You can add a property condition, for example only when a property equals a given value. With Track revenue on, amounts are summed from the property name you enter.
The breakdown splits conversions by source, entry page, country, or device. The chart draws conversion count and rate together.
How to use it
Owners, admins, and analysts can create or edit goals. Viewers can only read. Start with one or two clear completions, then use the source breakdown to see which channels convert. If revenue and orders should come from the server, use business goals in Business goals. Do not estimate money from a page goal alone.
Limits
Disabled goals are left out of the totals. Wildcards are stars in the path or event name, not regular expressions. Property conditions are equality only. With no revenue property, revenue is 0.
FAQ
Does this match the conversion rate on the data report? Not directly. The data report’s rate is conversion count divided by sessions. See Web metric definitions.
Where do I see whether people who chatted convert more? Not on this page. The chat reports compare people who opened a conversation with people who did not. See Chat vs no-chat conversion.