What events should a SaaS site actually track?

If you are looking at your analytics and wondering what should I track in analytics for my SaaS site, you need to step away from default reports. Most SaaS startups fall into the pageview trap. They look at traffic charts, celebrate daily active user spikes, and track general page visits, but they remain blind to where users are actually falling out of the conversion funnel.

Pageviews are a vanity metric. Knowing that ten thousand people visited your homepage does not help you grow. You need to know how many of those visitors went to the pricing page, how many started the signup flow, where they dropped out, and what specific action marked the transition from visitor to activated user.

To build an analytics setup that actually drives product and marketing decisions, you must define and instrument a tight set of custom events. These events should map to the logical stages of your buyer's journey.

The SaaS funnel: mapping events to actions

A healthy B2B SaaS tracking plan does not track everything. Instead, it focuses on high-intent actions that represent clear steps toward subscription revenue.

I group these events into four distinct funnel stages: Awareness, Consideration, Acquisition, and Activation.

1. Awareness: tracking entry and intent

At the top of the funnel, you want to identify visitors who show more than passing interest.

• Event name: view_item (for key resources) or standard page views on high-value educational content.
• What to track: Do not just track that they landed on your blog. Track when they download a whitepaper, view a case study, or watch an embedded feature tour video.
• Why it matters: This helps you separate casual search visitors from high-intent readers who are actively researching a solution to their problem.

2. Consideration: pricing and feature research

The moment a user looks at your pricing or compares your plan features, they have entered the consideration phase. This is the highest-value traffic on your marketing site.

• Event name: view_pricing
• What to track: Trigger this event when a user loads the pricing page. If your page uses toggle tabs (such as monthly vs. yearly billing), send a custom event parameter like billing_toggle: yearly when they interact with it.
• Why it matters: Users who view your pricing page are highly qualified. If you run retargeting ads, this is the audience you want to target. If your pricing page has high traffic but low signups, you know you have a positioning or price-structure issue, not a traffic issue.

3. Acquisition: signup and demo initiation

Acquisition events measure the actual transition from visitor to lead or user. You need to track both the start and the completion of these flows.

• Event name: signup_started and signup_completed
• What to track: Trigger signup_started the moment a user clicks a "Start Trial" button or enters their email in the first field of the registration form. Trigger signup_completed when the backend database confirms their account has been created.
• Why it matters: This allows you to measure your signup flow abandonment rate. If 500 people start the signup process but only 100 complete it, your onboarding form has too much friction.

For enterprise-focused SaaS sites that do not offer self-service signups, replace or supplement these with demo-tracking events:

• Event name: demo_requested
• What to track: Trigger this event when a user successfully submits the demo request form or books a slot on your embedded calendar scheduler.

4. Activation: tracking the "Aha!" moment

Many SaaS founders stop tracking once the user enters the app. This is a mistake. A signup who never uses the product is worthless. You must track the specific event that indicates a user has realized the value of your tool.

This is the activation event, and it is unique to every product:

• For a project management tool, it might be project_created.
• For an invoicing app, it might be first_invoice_sent.
• For a CRM, it might be contact_imported.

Because these events happen inside the application, you should send them to GA4 via server-side API calls once the database registers the action. Linking this product-usage data back to the original marketing source tells you not just which channels drive cheap signups, but which channels drive long-term, active customers.

The power of custom event parameters

An event name alone is only half the story. To get actionable insights, you must pass metadata alongside the event. These are called custom parameters in GA4.

When tracking a signup_completed event, you should pass parameters like:

• plan_type (e.g., starter, professional, enterprise)
• billing_interval (e.g., monthly, annual)
• company_size (if captured on your signup form)

Passing these parameters allows you to build reports that show you which marketing campaigns are driving high-value annual subscriptions versus low-yield monthly trials. Without parameters, you are optimizing your marketing blind.

Keeping your tracking plan clean

A common trap is GTM bloat: tracking every single button hover, scroll percentage, and footer link click. This clutters your GTM container, slows down your site load times, and degrades your frontend performance metrics like INP.

Rule of thumb: if a metric will not change a business decision, do not track it. You do not need to know how many people clicked the "About" link in your footer if that data does not help you improve conversion rates. Focus your energy on the core funnel steps: pricing views, signup starts, signup completions, and activation actions.

If you are struggling to identify your key funnel metrics, or if your current SaaS analytics setup is filled with noisy, unorganized event tags, a clean analytics setup and funnel audit can clarify your tracking. Instrument the steps that actually map to your revenue, and ignore the rest.