measuremy.site
measuremy.site / Blog

Map your site's funnel from first visit to signup

October 18, 2026 · 5 min read

Detailed close-up of a hand-drawn wireframe design on paper for a UX project.
Photo by picjumbo.com on Pexels

Start with the conversion action

Before mapping the top of the funnel, decide what a conversion means on your site. For a small site, conversion is usually one of a few actions: signup submitted, trial started, purchase completed, demo requested, contact form sent, email collected, first project created, or a file imported. Make each one a separate event. Do not treat a page view as conversion unless the page can only be reached after the action, and even then an event is cleaner.

Work backwards through consideration

Consideration is the messy middle. Visitors compare, read, return, and hesitate. On a small site, the most useful consideration signals are:

Map these as page paths and click events. For a product site, pricing and docs are stronger consideration signals than home page views. For a content site, repeated views of a guide may show consideration. For a GitHub README project, clicking from the README to the site and then viewing setup docs is a meaningful path.

Awareness is a source and landing page problem

Awareness is not just "people arrived." It is the combination of source and landing page. A visitor from a search result reading a specific blog post is a different awareness signal than a visitor from a newsletter landing on the homepage. Track awareness as a landing page plus source pair.

Useful awareness groups:

Tag campaign links with UTM parameters so later conversions can be credited to the right source. If your redirects strip UTM tags, fix that before the campaign starts. A clean landing page without UTM tags may still count as a visit, but it will be harder to connect to conversion.

Map stages to page paths and events

Create a simple mapping you can reuse in reports:

Do not force every page into a stage. Some pages, such as privacy policy or changelog, may not map cleanly. It is fine to leave them out of the funnel.

Build funnels from paths and events

Once the mapping exists, build three or four funnels that match real journeys. For a SaaS site:

For an event-driven product:

In measuremy.site, funnels can be built from page paths and events, and tracked campaign links can credit later traffic and signups. Use the smallest number of steps that still shows the decision point. A five-step funnel may look impressive, but on a low-traffic site it will be too thin to interpret.

Compare stage counts, not just total visits

A useful weekly check is:

Do not compare conversion to all visits if half the visits are to blog posts that were never intended to sell. Compare conversion to the audience that actually saw the product or pricing. That gives a clearer view of the bottom of the funnel.

Find the biggest drop-off first

Start with the largest gap between stages. If many visitors see pricing but few start signup, the issue is probably on the pricing or signup page. If many visitors land on a blog post but few reach pricing, the issue may be the call to action, the relevance of the post, or the source. If a campaign drives many landing page views but almost no consideration, the message may not match the ad or post.

Look at the path from the page before the drop-off to the next step. Check the page text, button position, loading speed, and whether the next step is obvious. Make one change and watch whether the gap narrows.

Do not rely on multi-day paths unless your analytics supports it

Some analytics methods count visitors without cookies and use an anonymous id that changes daily. In that setup, same-session paths are reliable, but a visitor who returns three days later may look like a new visitor. For cross-day behaviour, use tracked links and conversion events rather than assuming you can follow a person. UTM-tagged campaigns and signup events can still connect an early campaign touch to a later conversion without storing personal data. Check your own legal position if you need to retain longer-term behaviour.

Turn the mapping into a weekly report

A small-site funnel report can be a short list of stage counts and drop-offs. Keep it to one page. If you automate a weekly traffic report, include the funnel stage counts next to the raw pageviews. If a coding agent has access to the measuremy.site MCP server, ask it to read the stage counts and highlight the largest drop-off. That is usually more useful than another list of pageviews.

The point of mapping awareness, consideration and conversion is to stop reading total traffic as success. When each stage is tied to a page path or event, you can see where people lose interest, what content creates demand, and which sources bring visitors who actually move forward. Start with one conversion event, build one funnel, and improve the biggest gap before adding more reports.

See it on your own site

measuremy.site is cookieless analytics your coding agent can read. 30-day free trial, no card. Plans from $9/month.

Start free trial See the live demo

Add measuremy.site analytics to this project: connect the measuremy.site MCP server at https://a.measuremy.site/mcp for all my projects (claude mcp add --scope user; it signs in with OAuth, no key, and one sign-in covers every site), then tell me how to sign in. Details: measuremy.site/llms.txt

Free tools

All free tools

More from the blog