Analyze

Analyze is where behaviour becomes a number you can act on. Monitor shows you what happened; Analyze shows you the pattern across everyone it happened to.

Two halves#

Behavior holds the analysis primitives: events, the event debugger, funnels, retention, flows, segments, cohorts and groups. For web apps it adds form analytics, scroll and attention maps, CTA comparison, exit intent, and the Web Vitals → revenue view.

Visualize is where findings get saved and shared: heatmaps, dashboards and reports.

Start with the event debugger#

Before trusting any funnel, confirm the events underneath it are arriving with the properties you expect. The Event Debugger shows the raw stream for a device in near real time, and it is the fastest way to distinguish "users are not converting" from "the conversion event is not firing".

Most surprising analytics results are instrumentation problems, and every hour spent on a funnel built over a broken event is wasted.

Segments, cohorts and audiences#

Three words that get used interchangeably and should not be:

Segments and cohorts also appear under People, where they are managed as audience objects rather than analysis filters.

Related#

• Events SDK guide — designing a schema that survives contact with a funnel.

Behavior#

Visualize#