Set your first conversion goal in PureMetrix

Visitor numbers alone do not tell you whether your website works. A conversion goal answers a clear question: did the visitor do what you wanted, such as send an enquiry or buy something?

Pick one outcome

For example the thank-you page after a contact form, a demo request, a confirmed newsletter signup, or—for shops—a WooCommerce or Shopify purchase. Do not start with ten goals on day one.

Prefer thank-you URLs

Point your goal at a dedicated success page. Goals based on button clicks break easily when a theme, Shopify section, or React layout changes the page structure.

Set it up

Open your website in the PureMetrix dashboard and go to Site settings > Goals.
Click Add goal, choose Page visit, and give the goal a clear name, such as “Enquiry sent”.
Under Page path to match, enter the path of your thank-you page, starting with / (for example /thank-you).
Test it from a private browser window.
Check that one successful submission counts as exactly one conversion.

Forms and newsletters

Contact forms, newsletters. Wherever possible, count the confirmed state.

Shops

WooCommerce purchases can be recorded as server-side events; Shopify uses the custom pixel. You can still add page goals for other actions, such as reaching your contact page.

Read the rate

A conversion rate needs a clear basis (conversions divided by visitors). Definition. Break it down by landing page and campaign.

Pick one outcome that pays the bills

Your first goal should be tied to money or a sales conversation: purchase confirmation, a booked demo, or a serious contact enquiry—not “scrolled to 50%.” A PureMetrix page goal on a stable thank-you URL is more robust than button tracking that breaks with the next layout change.

Give the thank-you page a clear page title so future editors do not turn it into a marketing landing page. Set it to noindex if it should not appear in search results.

Validate before celebrating

Send one test while not logged in as excluded staff, check that the goal appears in the dashboard within minutes, then leave the definition alone for two weeks to collect a baseline. Changing goal URLs every week destroys your trend lines.

Examples by business type

Local service providers: thank-you page after the quote form. B2B software: confirmation of a booked demo. Publishers: confirmed newsletter signup. Shops: purchase via WooCommerce server event or Shopify pixel. Each fits neatly into a PureMetrix goal or shop event—no need for scroll-depth theatrics.

If marketing wants five goals in the first week, say no politely. Set up one, collect two weeks of data, then add a secondary small step that feeds your sales pipeline.

Goal hygiene checklist

A fixed URL, or a custom event sent only after the server has accepted the form.
noindex on the thank-you page if it should not appear in search.
UTM parameters kept through the redirect.
Staff excluded from tracking (WordPress roles, Shopify staff, or skip the snippet on admin hosts).
One named person responsible for the definition.

Change the goal URL only with a dated note in your team documentation. Silent changes break your history and restart debates about whether the numbers can be trusted.

Small steps that are worth measuring

Once your main goal is stable, add one smaller step that leads to it: viewing the pricing page, watching the demo video to the end, or downloading a PDF. Keep these secondary in your dashboards so teams do not optimise a soft signal that never turns into revenue.

PureMetrix page goals work well for small steps on your own domain. Thank-you pages hosted by third-party tools need a redirect back to your site first.

Design the thank-you experience

Thank-you pages should explain what happens next: what happens to the enquiry, when to expect a reply, and a link to further information or your shop. That reduces duplicate submissions. PureMetrix only needs the path to match—but a clear thank-you page also improves the experience for the person behind the goal.

Do not put a prominent button on the thank-you page that sends people straight back into the same form; it causes accidental double conversions and confused visitors.

If marketing insists on a pop-up message instead of a separate thank-you page, send the PureMetrix custom event only after the server has accepted the form, and note this exception in your documentation so future editors do not “simplify” it into a button-click tracker.

Sign-off

Get marketing and sales to confirm the goal definition in writing—path, exclusions, and what does not count. PureMetrix counts whatever you set up; clear agreement prevents renames mid-quarter that destroy your baselines.