How to Track SaaS Signup Conversions (Without Counting Button Clicks)
A signup CTA click is not a new account. Track completed registrations, preserve acquisition context and investigate the steps between a visit and a real signup.
If your dashboard shows 1,000 visitors and 50 clicks on Sign up, you do not necessarily have 50 new users. A click expresses intent. A completed account creation is the outcome. Treating both as the same event makes conversion rates and acquisition decisions unreliable.
Define the outcome before adding events
Write down what counts as a successful signup for your product: an account created in your database, an email verified, or an onboarding flow completed. Pick one primary signup outcome and keep the earlier steps as diagnostic signals. A product can legitimately track all three, but it should never label them all as the same conversion.
- CTA click: someone explored the signup path, not proof of registration.
- Signup started: the registration form or OAuth flow began.
- Signup completed: the server or auth provider confirmed an account was created.
- Activated: the new user performed the first meaningful product action. Track this separately from signup.
Send the completed event only after success
For a browser flow, emit the completed event after the confirmed signup response or authenticated redirect. If signup is verified asynchronously, reconcile it against the authoritative backend event rather than assuming the click succeeded. Keep the exact event name consistent across pages and goal configuration.
window.pulse?.track('signup_completed', { method: 'google' });When measuring GA4 in parallel, its recommended account-registration event is sign_up. Pulse and GA4 do not automatically share event streams: configure the outcome in the system that actually receives it, or instrument both deliberately.
Connect signups to acquisition, not just page views
Once the event is reliable, inspect landing page and source together. Did a specific campaign create sessions that finished signup, or merely a spike in visitors? Compare sessions and completed signups for the same time window and attribution definition. Use a consistent denominator; a session-based conversion rate is not interchangeable with a user-based rate.
Diagnose the step that lost users
A short visit → signup started → signup completed funnel separates an acquisition-intent issue from form or authentication friction. If starts increase but completions do not, inspect errors and device-specific behavior before rewriting marketing copy. If almost nobody starts, examine the promise, landing page and CTA.
What Pulse contributes
Pulse ties a completed goal to the tracked session and its source. Use visitor journeys to inspect the pages and events preceding the outcome, then compare which traffic sources deliver completed registrations rather than clicks. For a launch, start with one honest signup goal; add extra goals only when they change a decision.
Sources and verification
Frequently asked questions
Should I track signup button clicks as conversions?
Keep clicks as diagnostic events. Use a confirmed account-creation event for the actual signup goal.
Can GA4 historical events automatically create Pulse signup events?
No. GA4-imported reporting and native Pulse tracker events are distinct; verify which dataset powers the conversion report before comparing totals.
Want to see your own traffic live?
Install Pulse for free and connect acquisition, conversion and revenue in one dashboard.
Start free