Events and goals

Custom events

The script exposes one global function. Call it where something actually happened: after a form submission succeeded, not after the button was clicked.

metuno('signup', { plan: 'pro' })

The name is yours to choose, but it stays with you for a long time, so pick it once and stick to it. Names written consistently, always lower case and without spaces for instance, save later tidying of a report in which Signup and signup are two separate rows.

Properties

The second argument is an object with extra dimensions for the event. We store them as a pair of arrays: keys and values. They suit whatever splits an event into a few kinds: the chosen plan, the type of form, the variant of a test.

Goals

A goal is a page path or an event name that counts as success. You add it in the panel, in the Conversions view. An asterisk in a path means any continuation, so /thank-you* also covers /thank-you/for-your-order.

Goal matching is computed when the report is read, not when the event is stored. That has one practical consequence worth coming here for: a goal you add today covers the entire history you already have. You do not wait a week for the first numbers.

A conversion counts per visit, not per event. One visit with three hits on the thank you page is one conversion, which keeps the conversion rate a fraction of visits and unable to exceed one hundred percent.

Funnels

A funnel is several goals placed in order. The panel shows how many visits reached each step and where most of them drop out. The steps need not follow one another directly: what counts is their order within a single visit, not whether other pageviews happened in between.

A funnel longer than four or five steps rarely says anything two shorter ones do not. At ten steps the first bar is so tall that the rest is invisible, and the conclusion concerns one transition anyway.