How to Use Goals in statpx: Track Conversions and Revenue Per Visit

A Goal in statpx is the simplest way to answer "did this visit accomplish something valuable?" Instead of staring at pageviews, Goals let you define exactly what a conversion means for your site — reaching a URL, or firing a custom event — and then statpx quietly counts, rates, and prices every one of them for you. This guide walks through setting up both types of goals on the Goals page and reading the numbers that come back.

What a Goal Tracks

Every goal in statpx has a type: url or event. A URL goal fires whenever a visitor lands on a matching path — a thank-you page, a pricing page, a signup-confirmed screen. An event goal fires whenever your site calls the _st('event', ...) tracker function with a matching name, so it can capture actions that never generate a page load at all, like a button click inside a single-page app.

Each goal also has a match mode that controls how the value is compared: exact, contains, starts, or regex. A regex match mode is useful when your thank-you URL includes a dynamic order ID, e.g. /order/\d+/complete.

Creating a URL Goal

On the Goals page, choose type URL, give the goal a name like "Signup Complete," and set the match value to the path you want to track, such as /signup/thank-you. Pick contains if the path might carry query parameters, or exact if it never will. Save, and statpx starts counting every session that hits that path as a conversion — no code changes required.

Creating an Event Goal

Event goals need one extra step: firing the event from your site. Add this call wherever the action happens — after a form submits successfully, when a modal confirms a booking, or inside a checkout success callback:

Then on the Goals page, choose type Event and set the match value to signup_complete (the event name, the second argument to _st). Every time that event fires, it counts toward the goal — regardless of which page the visitor was on.

Reading Conversion Rate and Revenue

Once a goal has traffic, its row on the Goals page shows the conversion rate: conversions divided by total sessions in the selected range. This is the number to watch after any change to your funnel, pricing page, or CTA copy — it tells you whether the change moved the needle, independent of whether overall traffic went up or down.

If the goal represents something with a dollar value — a subscription, a booked demo, a completed purchase — set value per conversion when you create the goal (a plain number like 29.99). statpx then multiplies that value by the conversion count and shows total attributed revenue for the goal alongside the conversion rate, so you can compare goals not just by volume but by the money each one is worth.

For a deeper look at what conversion rate means across your whole site (not just one goal), see our guide on conversion rate analytics. And if you want a walkthrough of the Goals form field-by-field, our earlier post on setting up conversion goals in statpx covers the UI in more depth.

The Bottom Line

Goals turn a vague question — "is the site working?" — into a specific, measurable one: what percentage of sessions reach this exact outcome, and what is that outcome worth? Start with one or two goals that map to your most important actions, add value_per_conversion wherever there's real revenue behind the action, and let the conversion rate column tell you whether every change you ship is actually helping.