Measure Signup Completion

Use a signup funnel to distinguish people reaching a registration page from visits that complete registration. A click on a signup button does not establish that an account was created.

Collect the confirmed outcome

Send sign_up after your application confirms a successful registration. Use a consistent method value when it is useful to inspect the event:

hrd.track("sign_up", { method: "email" });

Call the tracker after it is available. Send permitted identity separately through Identify Visitors; do not put an email address in the event name or page URL. The method parameter provides event context and is not automatically a funnel breakdown dimension.

Define the journey

Create a funnel using your actual routes. For example:

1. Path /pricing.
2. Path /signup.
3. Event sign_up.

If visitors can sign up without seeing pricing, create a second definition beginning at /signup for that question. The longer definition measures a particular path; it is not the total number of all successful registrations.

Read progression and traffic separately

Use supported device or channel breakdowns to compare the ordered journey. Inspect a sample event and its session to check that the implementation matches the funnel definition.

Choose sign_up in Acquisition's conversion configuration when you want campaign-credit analysis. Add it to Key Events when it should also count toward engaged sessions. These are separate choices.

For a different outcome such as a demo request, follow Measure Lead Generation. Use device conversion comparisons when the signup journey differs across screen contexts.