Conversion tracking for websites and SaaS

Conversion tracking measures whether visitors complete a useful action: creating an account, requesting a demo or reaching a confirmation page. A pageview tells you someone arrived. A conversion goal tells you whether they took the next step.

In Yaap, create a goal from an exact page path or a custom event name. For example, match /thanks for a completed form or a signup event after account creation succeeds. Choose a confirmed outcome instead of a button click that might fail.

You can add up to three property conditions. A goal for signup with plan = "pro" counts only matching events with that value. Names, paths and values are exact and case-sensitive, so agree on a naming convention before instrumenting your website.

A funnel follows an ordered sequence. For a SaaS product, start with a pricing pageview, then a signup event, then an activation event. Yaap lets you choose the identity scope and completion window so the report reflects the journey you intend to measure.

Each step needs a later event. One event cannot satisfy two repeated steps. If 100 identified entrants reach pricing and 20 complete the full sequence, that funnel has a 20% completion rate. Those figures are an example, not a Yaap customer benchmark.

Use the drop-off between steps to choose what to investigate. A large gap between signup and activation might call for clearer onboarding. Check that the activation event actually fires before treating the gap as a product problem.

Goal completions count matching events, including repeated and anonymous events. Converted sessions count distinct identified sessions with a matching event. These answer different questions: how often an action happened, and how many sessions included that action.

Session conversion divides converted sessions by identified sessions with activity matching the report range and dimensions. Anonymous completions do not create identified sessions. When there are no identified sessions, the rate is unavailable.

Compare sources, campaigns and landing pages using consistent date ranges and filters. Keep changes to tracking mode and goal definitions in mind when comparing periods; changes in measurement can look like changes in visitor behavior.

Install the browser tracker or npm client, send a confirmed custom event and inspect it in Events. Then create a goal and walk through the journey yourself. The custom events guide covers event names and properties.

Use the goals and funnels guide to configure matching, identity scope and completion windows. Editing a definition recalculates retained history; it cannot recover raw events deleted by your retention policy.

Ordered funnels require identified activity. If your site uses anonymous collection, start with event counts and goal completions, and review the collection controls before enabling identifiers. For confirmed purchases and refunds, connect revenue attribution rather than relying on a browser purchase event.

Start a 14-day hosted trial with no credit card, or follow the documentation to run Yaap in your own Cloudflare account.

Start your free trial