Research paper · Conversion
Registration Conversion: Measuring Sign-Up Completion
Registration conversion is the share of landing visitors who complete an account sign-up. Measure it from a confirmed account record, not a button click, and read it inside one market and one intent group, because age rules and market limits lower it for good reasons.
Define the registration first
A registration on this site means a completed account sign-up that your system accepted. It is not a click on "Join," a form that was started, or a form that failed validation. Write that definition into the reporting notes so that product, marketing and compliance teams count the same thing.
Google Analytics' list of recommended events includes sign_up, described as "A user signs up for a new account," with an optional method parameter. Using the recommended name keeps reports and exports consistent. Send the event when your server confirms the account, either from the server itself or from the confirmation page that only loads after the account exists.
Record the steps inside the form
A single rate cannot tell you where people stop. Record a small set of custom events for the form itself:
- Form viewed. The registration form rendered on screen.
- Form started. The first field received input.
- Validation error. A field failed, with the field name but never the value typed.
- Submitted. The form was sent to the server.
- Registered. The sign_up event, sent once the account exists.
Google Analytics' funnel exploration can turn these into a report. You can define up to 10 steps, and you choose between an open funnel, where "users can enter the funnel in any step," and a closed funnel, where "users must enter the funnel in the first step." A closed funnel suits registration, because a sign-up without a form view usually signals a tracking gap. The funnel tracking guide walks through the setup.
Read the rate inside its context
In the site's default model, 18% of landing visits become registrations. That number is an illustrative input, not a measurement. Your own rate depends heavily on which pages people land on, which markets they come from and how many arrive already intending to join. Compare a page with itself over time, or compare pages within one intent group, rather than comparing the site against a figure from somewhere else.
| Check | What it rules out |
|---|---|
| Landing page mix | More explainer traffic, which converts lower by design |
| Market mix | More visits from markets you cannot serve |
| Consent and tags | A change in what analytics can count |
| Form step events | A step that started failing, such as an address lookup |
| Release log | A product change on the day the rate moved |
To see how a change in this rate carries through to first deposits, enter it in the registration-to-FTD calculator.
What lowers the rate for good reasons
Some steps exist to stop the wrong people from registering, and a lower rate is the point:
- Age and identity. In Great Britain, remote operators must complete verification of name, address and date of birth "before allowing that customer to gamble," a rule in force since May 7, 2019. The verification paper covers how that stage is measured.
- Market restrictions. Visitors from places where the product is not licensed should be turned away before the form.
- Marketing preferences. Since May 1, 2025, Gambling Commission rules give customers of remote operators more control over the direct marketing they receive, by product type and by channel. Pre-ticked boxes that inflate consent counts work against that intent.
- Harm monitoring. The Commission's customer interaction rules require remote operators to monitor activity from account opening to identify harm or potential harm. Registration is where that monitoring starts, not a hurdle in front of it.
Practices to avoid
Do not hide terms behind extra clicks, add countdown timers, or show offers in markets where they are not allowed. Do not test form variants that remove age or market checks. These raise the number in the short term and create regulatory risk, and they say nothing true about whether your content serves the people who arrive.
Limits of this paper
This paper describes measurement. It does not give target rates, and it uses no operator data. Rules are summarized as published on the dates in the sources; check current requirements with counsel for each market.
Questions
Should registrations be counted in the browser or on the server?
On the server, or on a page that only loads after the server has created the account. Browser clicks overcount, because they include failed and abandoned submissions.
Do social sign-in methods need their own rate?
Record the method parameter on sign_up so you can split the rate by method, but report one registration total so the funnel stays additive.
Is a high registration rate always good?
No. If it rises after a change that weakened age, market or consent checks, it is a compliance problem, not a gain.
Sources
Each source was read on October 27, 2026. How we choose sources is set out on the sources and reading list page.
- Google Analytics developer documentation, Recommended events, last updated May 29, 2026.
- Google Analytics Help, [GA4] Funnel exploration, no date shown.
- Gambling Commission, New age and identity verification rules: changes to the LCCP from Tuesday 7 May, published May 3, 2019, updated August 27, 2021.
- Gambling Commission, Summary: improving customer choice on direct marketing, published May 1, 2024, updated August 1, 2025.
- Gambling Commission, LCCP social responsibility code provision 3.4.3: remote customer interaction, no date shown.