How to build a conversion funnel on your website

Pageviews tell you people arrived. They do not tell you where they left.

A visitor can open /pricing, skip the signup button, and never join the list. Those are three different steps. A funnel counts how many people reach each one, in order.

Sitebase’s Funnels page is that report. You name the steps. It computes from events you already have.

Sitebase is in private beta. Public signup isn’t open. These steps are for accounts with access.

Get the events in first

A funnel has no snippet of its own. It reads the same events as the Events page.

Put the site snippet on every public page so pageviews land. The attribute is data-sitebase-site, not data-sitebase-widget.

<script
  async
  crossorigin="anonymous"
  src="https://sitebase.dev/embed.js"
  data-sitebase-site="YOUR_SITE_KEY"
></script>

Replace YOUR_SITE_KEY with the website key from your dashboard. A feature embed on the same page also starts the tracker. You still want the site snippet on pages that have no feature.

The tracker ignores localhost and file: pages. Publish first, then walk the path yourself.

You also need the middle click. If the pricing button is not a Sitebase form, mark it:

<a href="/waitlist" data-sitebase-event="signup_click">Join the waiting list</a>

A waiting list submit already writes waitlist_signup. Do not add a custom event on that form.

Confirm the names on Events before you build the funnel. How to track custom events covers that install.

Enable Funnels

Add your website in Sitebase. On the Features to start with step, keep Funnels checked under Data. It is on by default.

If the site already exists, use + Add more and enable Funnels.

Open Funnels in the sidebar, right after Events. Until you create one, the page shows the create form and the how-to. There is no Setup tab.

Create a signup funnel

Name it Signup funnel.

Add three steps, in order:

1. Page visited: /pricing
2. Event: signup_click
3. Event: waitlist_signup

A Page visited step matches one exact path. /pricing does not match /pricing/. An Event step matches that name exactly. You can mix both types in the same funnel.

You need at least 2 steps. You can add up to 8 with + Add step.

Click Create funnel. Sitebase recalculates from events you already stored. You can define it today and read yesterday, as long as those events are still inside the 6-month detail window.

Read where people drop off

After the first funnel exists, Data is the default tab. Docs keeps the how-to.

Each row is a step. The first bar is full width. Later bars shrink with the visitor count. The first step is labeled Viewed /pricing. Event steps keep the event name.

Under each step after the first you see conversion from the previous step, how many visitors dropped, and conversion from the start. The header shows how many visitors entered and what share completed.

The range tabs are 7 days, 30 days, and 6 months. The default is 30 days.

If the first step is empty, the path or event name is wrong, or nobody hit that step in the range. Open Events and copy the name exactly.

Counting is per visitor. A person counts for step 2 only after step 1, and for step 3 only after both. The steps can sit hours apart inside the range. They do not need to happen in the same visit.

Visitor ids rotate every day. A path that spans two days counts as two visitors. That is the same cookieless design as Analytics.

Change the question

Edit the steps when the flow changes. Save changes recomputes the same stored events. Delete removes the definition. The events stay.

Add another funnel with + if you later want a contact path, such as /contact then contact_message.

For the reports around pageviews, see the analytics guide. For install detail, see the funnels documentation.