Read your analytics

Analytics lives on your event's own address — open Analytics in the sidebar and it takes you there.

What you get

Page views — visits to your public pages.

Registrations — how many completed.

Conversion rate — registrations as a share of views. The most useful single number you have.

30-day charts for registrations and page views.

Export summary CSV and Export detailed views CSV.

Reading the conversion rate

This is the number worth watching, because it separates two very different problems.

Low views, decent conversion — your page works, not enough people are seeing it. The problem is promotion.

High views, low conversion — plenty of interest, something on the page or in the form is losing them. The problem is your site.

Chasing more traffic when your conversion is broken is the most common wasted effort in event marketing.

If conversion is low

Work through the likely causes, in order of how often they are the culprit:

1. Register on your own phone, over mobile data. Most problems are visible within thirty seconds of doing this.
2. Count your form questions. Every one loses people. Remove anything you will not use — see Add a question.
3. Is the price visible before the form? People who discover the price at step three leave.
4. Is the register button obvious, near the top and again near the bottom?
5. How fast does the page load? Unoptimised images are the usual cause — see Add images to a section.

Reading the charts

Watch the shape, not the daily numbers.

Registrations for most events are flat in the middle and spike at deadlines — early-bird endings and the last week. If your middle is completely flat, price phases give you deadlines to create the spikes: see Set up early-bird pricing.

What happens next

Analytics covers your public pages. For attendees, orders and revenue, use the reports.

Common problems

Views but no registrations. See the conversion checklist above.

Numbers seem low. Analytics starts when your event goes live. A Draft event has no public traffic.

They do not match Google Analytics. Different tools count differently. Use one consistently rather than reconciling them.

A spike you cannot explain. Usually a share on social or a newsletter mention. The detailed views export may show where it came from.

You need per-ticket revenue. That is the Orders & revenue report, not analytics.