Web Analytics Strategy: The Measurement Plan Most Teams Skip
Your analytics setup can tell you how many people visited your website last month. It can show which campaigns brought them there. But ask whether those visitors came from companies you actually want to sell to, and suddenly nobody has a clear answer. Over time, different people have added tracking events and created reports without agreeing on what the business needs to know. The result is plenty of data, but not enough of it drives your business forward.
Web Analytics Strategy: The Measurement Plan Most Teams Skip
A web analytics strategy is the decision about which questions your site data has to answer, written down before anything is instrumented.
Build a measurement plan that connects your business goals to the metrics that matter, setting out what to track and what to leave out.
Assign someone to maintain this setup and establish a schedule for reviewing the results. This guide explains how to do it, including a measurement plan you can adapt to your website in around a fortnight.
What a web analytics strategy actually is
A web analytics strategy is the set of questions your business needs its website data to answer. Your measurement plan then establishes how you'll answer each question. Implementation puts the necessary tracking in place. Most teams have only the implementation stage, without the strategy or measurement plan. They have the tracking in place. They can measure website activity and produce reports. But they lack an agreed process for using that information to make decisions. So the data is abundant and mostly unused.
A website analytics strategy, or digital analytics strategy, gives you that direction. You can assess your own setup by checking which elements you already have. If tracking is working but nobody can explain which business questions it answers, the strategy and measurement plan need attention. For more on these fundamentals, see our guide to web analytics.
Step 1: The measurement plan
Start by agreeing on your business goals and the KPIs you'll use to measure progress. Your goals establish what the business wants to achieve, while the questions you ask determine how you'll know if you're getting there. Each KPI gives you a number that helps answer one of those questions.
Think about what your marketing team needs to know. Is your content reaching the companies you sell to? Which channels produce sales opportunities? Where do buyers drop out of the evaluation process? And are potential customers coming back to your website? Write these questions down before deciding which metrics to collect. They'll form the basis of your analytics measurement plan.
The table below shows how to connect each question to a metric and the decision it should inform, along with the process to get there. Use it as a starting point for your web analytics process.
Pay special attention to the final columns. The reporting source tells you where to find the answer, while the named owner takes responsibility for reviewing it. If you can't identify where a number will come from, resolve that gap before approving the plan. The final column is where the real magic happens (and what most teams leave out). What would make us act? Every question should have a clear condition that prompts someone to make a decision. Otherwise, you risk collecting information that nobody uses.
Keep your first measurement plan to six to ten rows. That should be enough to focus on the questions that matter to your business. Resist the temptation to add more questions for future use. If you can't explain why you need to measure something now, leave it out.
For agencies, include the company-level rows in the first version of each client's plan. They establish how the agency's work will be assessed, alongside the other agreed measures.
Step 2: What to track and what to skip
When implementing website analytics, track what your measurement plan needs and leave everything else out. Every event should help answer an agreed question. Adding events without a clear purpose creates extra work and makes it harder to know which figures to trust.
Use your measurement plan to decide which website actions need tracking. Focus on events that show how visitors interact with important pages and whether they complete the actions you've defined as goals, such as filling in a form or visiting a demo page. The table below will help you decide what to include and what to leave out. Use it as your go-to tracking specification.
Track
Why
Skip
Why
Key conversions and their type
Measures agreed website goals, such as form fills or demo-page visits
Duplicate events with different names
Creates conflicting figures for the same action
Form starts and completions
Shows where visitors abandon forms
Micro-events nobody has queried
Adds data that nobody uses
Engaged views of high-intent pages
Measures activity on pages important to the evaluation process
Scroll depth on every page
Collects unnecessary detail from pages outside the plan
Outbound clicks to pricing or documentation
Shows when visitors follow links to important resources
Vanity custom dimensions
Complicates reporting without answering a useful question
UTM-tagged campaign entries
Helps distinguish traffic from different campaigns
Events added for one campaign and never removed
Keeps collecting data after the campaign has ended
Consent state
Helps explain gaps in the data collected
Tracking on staging or test sites
Mixes test activity into live figures
Once you've decided what needs tracking, identify which tools will provide the information. Events and key events are recorded in Google Analytics 4, while Google Tag Manager manages how tracking is deployed and changed. Google Search Console provides information about how visitors find your website through search, including the queries they use. Each tool has a defined role in your measurement plan. You should also document which tool supplies each metric so everyone knows where to find the figures.
UTM discipline is key. Agree on one naming convention for your utm parameters and make sure everyone follows it. If different teams use different names for the same campaign or channel, your reports will split related traffic across separate categories. That makes it difficult to compare campaign performance or understand which sources bring visitors to your website. Write down the naming rules and apply them whenever someone launches a campaign. Fixing inconsistent names later won't repair the historical data you've already collected.
Consent choices also affect how much website activity you can measure. Decide how your team will record consent state and how you'll report the gaps it creates. For example, if visitors decline tracking, some activity may be missing from your reports. Your team needs to know this when interpreting the figures, especially when comparing different periods. Document how you'll account for these gaps so nobody mistakes incomplete measurement for a change in website performance. Whenever your consent banner or its settings change, note the date, because the numbers after it aren't comparable with the numbers before.
Step 3: Governance
Start with a naming convention for your tracking events and parameters. Everyone should use the same names for the same actions, following rules that are written down and accessible. This prevents different teams from introducing their own variations whenever they add tracking.
Next, appoint one person to own the tracking setup. Others can make changes, but the owner should approve them and check that they follow the measurement plan. That person should also resolve any disagreements about how the data is collected or reported.
Keep a change log so you can trace any changes to your tracking setup. Record each update and the reason behind it, along with who approved the change. Add each change as an annotation in Google Analytics 4 on the day it went live, so anyone reading a chart later sees why the line moved. If your figures suddenly look different, you'll have a record to help you find out why.
Document how every KPI is measured. For example, agree on how each KPI is calculated and which reporting period to use, so two people can't produce different figures for the same metric. A shared web analytics glossary will help everyone use the same terminology. Keep these rules in a shared governance document so everyone involved in tracking knows where to find them.
Governance keeps your tracking consistent as campaigns change and new people get involved. Most guides give it relatively little attention, and it's easy for teams to treat it as optional. If you’ve been in B2B for a while, you’ll know that it’s easy for a setup without a named owner to drift back to its old broken ways within a couple of quarters. With a named owner and written rules, your team can keep the tracking setup working as intended, even as campaigns and responsibilities change.
Step 4: The review loop
Your web analytics process needs a regular review schedule, so your team knows when to examine the results and when to reconsider the plan itself. Across the year, these loops will move at different speeds to make sure you’re always covered. Put these reviews in the calendar and assign an owner to each one. You'll then have a regular schedule for keeping your measurement plan aligned with what the business needs to know.
Every month, start with a quick health check: compare one number in Google Analytics 4 with the same number in a second source, such as form submissions in your CRM. If they've moved apart, fix the tracking before you read anything else. Then compare your results against the measurement plan. Check whether any figures have reached the thresholds you've agreed on and decide what action to take. Use a web analytics report to keep track of the findings.
Every quarter, revisit the questions themselves. This is the review that deserves the most attention, as your marketing priorities may have changed since you wrote the plan. A measurement plan based on last year’s strategy is worse than no plan at all. For example, if you're now focused on reaching a smaller group of target companies, questions based on growing overall traffic may no longer be useful. Use our guide to website kpis to help set targets for the revised plan.
Once a year, audit your tracking against the measurement plan. Check for events that are no longer needed and measurements that may be missing. Make sure the setup still collects the information your team relies on.
Where analytics strategies fall apart
Choosing an analytics tool before deciding what you need to measure is a common mistake. You can end up with a sophisticated tracking setup that produces impressive reports but tells you very little about how your marketing is performing. You end up measuring whatever the tool makes available, regardless of whether the figures help your business make decisions.
Another mistake is tracking everything "in case we need it later." Every new campaign brings more events, and nobody wants to remove anything in case it proves useful. Before long, the team is spending more time sorting through data than using it. If an event has no purpose in your measurement plan, it's probably unnecessary.
Ownership is another weak spot. Without someone in charge, the tracking setup can quickly become a free-for-all. People make changes without checking how they'll affect existing reports. Mistakes go unnoticed, and the team ends up wasting time trying to work out which numbers it can trust.
There's also the measurement plan that nobody revisits. Marketing goals change, but the team carries on measuring what mattered a year ago. The reports may still work perfectly, but the information they provide no longer helps anyone decide what to do next.
A measurement plan built entirely around sessions and conversions will struggle to answer questions about the companies visiting your website. Adding those questions later means revisiting the plan and potentially changing what you track. In B2B marketing, you need to know how many companies you're attracting and whether they're the ones you want to reach. That's why the first three rows in our Step 1 table measure company activity, alongside the usual website metrics.
There's another reason to get this right early. Tracking only starts collecting company data once the script is installed. If you add company-level measurement six months into your strategy, you'll have no earlier figures to compare against. Take the ICP ratio trigger in our table. You need three months of data before you can spot a drop against that average. Start tracking on day one, and you'll have a baseline for your first quarterly review.
In Leadfeeder, the Web Insights reports provide the numbers for those rows. The Traffic sources report shows how many identified companies came from each source and how many fit your ideal customer profile. The ICP ratio is the share of identified companies that fit your ideal customer profile. The Pages report shows how many companies viewed each page, including how many were returning. The Firmographics report groups company counts by segment, including ICP segments and a Non-ICP row. These reports also include average Intent Score. None of them lists companies by name. When your sales team needs to know which companies visited, it can use Web Visitors to identify website visitors by company name. The numbers from Google Analytics 4 and Leadfeeder will differ because GA4 counts sessions and users, while Leadfeeder counts companies. Both answer their own measurement questions. Install the tracking script when you approve your plan so you'll have company data ready for the first review.
Within the broader practice of website intelligence, reverse IP lookup matches an IP address against an IP-to-company database to identify the organization behind a website visit. It cannot identify the individual who was browsing. You can read more about reverse ip lookup in this article.
Frequently asked questions
What is a web analytics strategy?
A web analytics strategy defines the business questions your website data needs to answer. It establishes what you want to learn about your marketing performance before you decide what to measure. The strategy guides your measurement plan, which then determines the tracking you need to collect the right information.
What is a measurement plan?
A measurement plan is a document that connects your business questions to the data needed to answer them. It identifies which metrics to use and where to find them, along with who is responsible for reviewing the results. It also specifies what should trigger action. See the table in Step 1 for an example.
How many events should a website track?
Track as many events as your measurement plan requires. Each event should answer a specific question, so there's no fixed number that works for every website. Start with six to ten rows in your measurement plan, then identify the events needed to support them. Remove any tracking that serves no clear purpose.
Who should own web analytics in a B2B company?
One person should take overall responsibility for web analytics, including maintaining the tracking setup and approving changes. Other team members can manage individual metrics or produce reports, but the named owner makes sure everyone follows the measurement plan. This prevents confusion over who is responsible when something goes wrong.
How long does a measurement plan take to build?
Allow around a fortnight to create your first measurement plan. Most of that time will go into agreeing which business questions you need to answer and who should own each one. Follow the process in Step 1 to create a plan your team can start using.
Hana Banacka leads Web & Creative at Leadfeeder, where she focuses on improving website performance and optimizing the digital buyer journey. With more than 10 years of experience in B2B SaaS marketing, she specializes in conversion optimization, experimentation frameworks, and data-driven website strategy.
Hana has led global CRO programs, managed cross-functional web teams, and implemented testing strategies that significantly improve funnel performance. Her experience optimizing complex B2B websites informs her perspective on how companies can reduce friction in the buying journey and turn website visitors into qualified leads