← All free tools

SaaS event tracking-plan generator

Choose your signup flow and activation milestone. Export a practical event plan as CSV or JSON. No signup required.

1 · Describe your flow

Start with an outcome.

Choose how someone joins and the first action that delivers value. This creates a vendor-neutral plan, not tracking code.

Count the outcome, not the redirect.

A CTA click, a created account, and a confirmed trial answer different questions. Keep them separate.

2 · Take your plan

6 events, each with a purpose.

Export definitions, suggested properties, and checks. Adapt these names to your analytics provider. Configure consent, supported events, and deduplication in your own implementation.

No signup required. Entries stay in this tab; reloading clears them.

Turn a defined outcome into a VisitLift goal

Your event specification

No form contents, emails, passwords, tokens, or complete URLs with query strings belong in these suggested properties.

1

landing_viewed

Browser

A visible public landing page is viewed. Reuse a supported automatic pageview rather than sending a duplicate.

Suggested properties: path_without_query, campaign_name

Verify it

Navigate once and check one accepted pageview. Do not send form fields or complete query strings.

2

signup_cta_clicked

Browser

A visitor selects the signup CTA. This measures intent, not an account or trial.

Suggested properties: safe_cta_label, path_without_query

Verify it

Click once and confirm the intent event without an account-created event.

3

signup_started

Browser

The visitor begins the email and password signup flow. Opening a form or provider is not signup completion.

Suggested properties: signup_flow

Verify it

Begin then abandon signup; only the start event should be accepted.

4

account_created

Server

Your application confirms a new account through email and password. Existing-account logins and failed attempts are excluded.

Suggested properties: event_id, signup_flow

Verify it

Test failure, new signup, retry, and existing login. Only the new durable account counts once.

5

first_project_created

Server

The account creates its first durable project. A retry must not create another first-project event.

Suggested properties: event_id, project_type

Verify it

Create a project, retry the request, and confirm one first-project event is accepted.

6

trial_started

Server / billing confirmation

The billing provider confirms an active trial and the required payment-method setup. A return-page visit alone is insufficient.

Suggested properties: event_id, plan_id, trial_type

Verify it

Verify a confirmed start once; failed or abandoned trial setup must not count.

Build a plan before adding more events

Use the exported plan as a specification for your team. Suggested property names are not a claim that every analytics provider accepts them. An event is only useful after you implement it with the right consent and identity boundaries, verify an accepted record, and connect it to a decision.

What events should your SaaS actually track? →

Where do my entries go?

The tool processes entries in this browser tab. Entries are not uploaded or placed in a share-link URL. Download only when you want to save an export, and avoid entering personal information or secrets. Reloading clears the entries. VisitLift’s page measurement is described in our privacy policy.

Looking for another resource? Try the UTM builder and checker or the funnel calculator.