Measure website conversions after launch: which goals, events and dashboards to set up

Measuring website conversions does not start after launch, it starts before. First you decide which actions count as a lead for you, then you tag those actions as measurable events, and you prepare one dashboard that you open every week. Skip that before go-live and you lose the data from exactly the weeks in which you would have spotted the most mistakes. In this article you will learn which conversion goals to pick, how to set them up as events in GA4, how to factor in lead quality, and which dashboards you will actually use.

This is precisely the work that belongs to a conversion-focused website: a new site is only finished once you can see whether it delivers leads. If you are still choosing between a replatform, a redesign or a full rebuild, make that call first, because it partly determines what your measurement setup looks like. For the bigger picture, start with the B2B website guide, because measurement is the keystone of that entire process.

Why should you start measuring from day one?

Because data you do not collect is gone for good. An analytics platform only measures from the moment the tag is running, so every day without a correct measurement setup is a hole in your numbers that you cannot fill in later.

The first weeks after launch are exactly the most valuable. That is when you see where visitors drop off, which pages nobody reaches, and whether your forms work at all. A common mistake is that companies plan the measurement setup as the last chore after launch, which means they go into the busiest introduction period blind. So prepare your tags, events and goals in the staging environment and test them before the site goes public.

Also decide straight away who looks at the data and how often. A dashboard nobody opens is just as useless as no dashboard. Agree that someone reviews the key numbers weekly, so a broken form gets noticed within days instead of at the quarterly report. Measurement is only one part of what continues after launch, by the way; see the broader overview of what website maintenance involves.

Which conversion goals should you set?

The actions that are worth money, not the actions that are easy to count. In B2B it almost always comes down to requests: a completed contact form, a quote or demo request, a whitepaper downloaded behind a form, or a phone call from the site.

A useful approach is to split your goals into two layers:

• Primary conversions: the actions that directly produce a lead. A submitted contact form, a requested quote, a booked intake call. These are the numbers you steer your site on.
• Secondary or micro conversions: signals that someone is on their way to a request. Think of a click on a phone number, a view of the pricing page, or starting (but not finishing) a form. These tell you where visitors get stuck.

Keep the number of primary goals small. If everything is a conversion, nothing is. Tie this to the principle of one clear primary action per page, as described in a B2B website that generates leads. Measure ten things at once and at the end of the month you still will not know whether your site works.

How do you set up GA4 events in practice?

In GA4 everything is an event, and you mark the important events as key events. Since March 2024, what used to be a conversion in Google Analytics is called a key event. The term conversion is now reserved for measuring and optimising your Google Ads campaigns. Existing conversions were migrated automatically, so nothing changes about the measurement logic itself, only the name.

In practice it works like this:

1. Define your events. For a submitted form you create an event such as generate_lead or a custom name like form_submit. GA4 picks up some actions automatically through enhanced measurement, but a real form submission is usually something you tag yourself, preferably on the confirmation (the thank-you page or the success message after sending), not on the click. That way you only count requests that genuinely came through.
2. Mark them as a key event. In GA4 you flip the toggle for the events that matter. Only then do they count as key events in your reports.
3. Use Google Tag Manager as an intermediate layer. With a tag manager you manage your tags without having to change code every time, and you can trigger cleanly on a form submission or a click on a phone link.

Test every event before you go live. Use GA4’s realtime mode or DebugView and fill in your own form to see whether the event comes through. A form that works in the browser but fires no event is a leak you would otherwise only discover weeks later. Also make sure you do not pollute the measurement: exclude your own traffic and known bots, otherwise test visits colour your numbers.

How do you measure lead quality and not just volume?

By connecting your web numbers to what happens after the request. A hundred form submissions sounds great, but if sales discards ninety of them because they are not a fit, you have a measurement problem dressed up as a success. So steer on leads that can become customers, not on the number of fields filled in.

That calls for a feedback loop between your website and your CRM or sales process. Agree which statuses a lead moves through, for example new, qualified and customer, and look per channel or per landing page at what share actually becomes qualified. That is how you discover that the page with the most requests does not always deliver the best leads.

A practical tip: keep your forms short and let sales qualify during the conversation. That usually produces more usable requests than a long form that scares people away, as we explain in form conversion optimisation. Then measure not only how many people submit the form, but also how many start and drop out, because that is where your biggest gain sits. The same logic applies to your contact page: measure whether visitors get there and whether they take the step. Also see how an FAQ section removes doubts right before the CTA, because you often solve those drop-off points by answering objections on the page itself.

Which dashboards do you need?

One overview that you open every week, not five reports nobody reads. The goal of a dashboard is that you can see in thirty seconds whether things are going well, and that a deviation stands out immediately.

Keep it simple and put at least these numbers together:

• Requests per week: your primary key events, with the trend compared to previous weeks.
• Conversion rate per important page: visitors divided by requests on your service pages, landing pages and contact page.
• Source of your leads: which channel (organic, ads, direct, referral) brings your best requests.
• Drop-off points: where in your form or funnel visitors disappear.

GA4 has built-in reports, but for a readable overview you often connect your data to a free visualisation tool such as Looker Studio. That lets you build one page that colleagues without analytics knowledge understand too. More important than the tool is the agreement behind it: who looks when, and what is the action if a number drops. A dashboard only becomes valuable once a conversation follows.

The short summary

Measuring conversions on your website is not a separate step after launch, it is part of the build. Decide before go-live which actions are leads, tag them as key events in GA4, test whether they really come through, and connect the numbers to lead quality instead of to raw volume. Then set up one weekly dashboard and agree who steers on it. That way you know from day one whether your new site does what it was built for: turning visitors into customers.

Want a website that delivers measurable leads and whose measurement setup is right from the very first day? Book your free intake and we will look at your goals and your measurement plan together.