Guides / Analytics & Conversion Tools
Decision guide
Analytics & Conversion Tools
Analytics tells you what visitors do; conversion tools help more of them do what you want. This guide starts from the questions worth answering, maps them to the tool classes, and covers the privacy, performance and statistics traps that catch most small sites.
- Five situationsEach with a way into Solutions
- About 10 minutes11 sections, jump to any
- Informational guideNot personalised advice
The short answer
Choose tools by the question you need answered. Start with the closest situation.
You have a site but no clear picture of results
Set up one analytics tool, define two or three outcomes and check the numbers against real enquiries or orders.
You run campaigns and cannot tell what worked
Tag campaigns consistently and track the outcome, not just visits. Add tools only for specific questions.
You want more enquiries or sales from the same traffic
Look at where people leave and at your forms. Fix obvious problems before testing. Test only if you have enough traffic.
You handle visitors in regulated or privacy-sensitive markets
Check consent rules first, then choose tools and settings that fit, and mask sensitive fields.
Your pages are slow and full of scripts
Audit your tags, remove what nobody reads and load the rest carefully. Speed affects conversions.
The measurement funnel: from question to tool
Analytics tools answer questions. Start from the question, then choose the tool class that can answer it. Read across a row to see what to look at and which class of tool provides it.
Show the table
| Stage | The question | What to look at | Tool class |
|---|---|---|---|
| Acquire | Where do visitors come from, and which sources bring people who matter? | Visits and outcomes by source, medium and campaign | Web analytics; consistent campaign tagging |
| Engage | Do visitors find what they came for? | Pages viewed, time on page, searches on your site, where people leave | Web analytics; heatmaps and session tools, used sparingly |
| Convert | Do they complete the actions that pay for the site? | Form submissions, checkouts, sign-ups, and the steps in between | Analytics goals and funnels; form tools; landing-page tools |
| Retain | Do they come back or buy again? | Returning visitors, repeat purchases, email engagement | Analytics with CRM and email connections |
| Improve | Did a change help? | Before-and-after or controlled comparison of one outcome | A/B testing, only with enough traffic |
The tool classes
“Analytics and conversion” covers several jobs. They have different costs and different privacy consequences.
Show the table
| Class | What it does | Cost to consider | Watch for |
|---|---|---|---|
| Web and product analytics | Counts visits and actions and reports on behaviour | Set-up time and reporting habits | Definitions that differ between tools; data retention limits |
| Tag management | Loads and controls tracking scripts from one place | Governance; each tag adds weight | Unreviewed tags accumulating over years |
| Heatmaps and session tools | Show where people click, scroll and struggle | Extra scripts and stored behavioural data | Recording sensitive fields; consent and privacy duties |
| A/B and multivariate testing | Compares versions of a page or element | Traffic, time and statistical skill | Declaring winners too early |
| Form builders | Collects enquiries and orders | Spam handling, accessibility, storage of submissions | Where submitted data is stored and who can read it |
| Landing-page and funnel builders | Builds focused pages for a campaign or offer | Another platform to host and maintain | Lock-in of pages and forms; performance of the pages |
| Popups and on-site messages | Displays offers or prompts | Friction and performance | Annoying visitors; accessibility of overlays |
A measurement plan in six steps
- Write down the two or three outcomes that matter. Sales, enquiries, sign-ups, bookings.
- Define each one exactly. What counts as a conversion, and from which page or action.
- Tag your campaigns consistently. Agree naming once and keep to it.
- Install as little tracking as you need, through one place you control, and review it every quarter.
- Check the numbers against reality. Compare form counts with the enquiries you actually received.
- Decide what you will change, and by how much, before you look at the report.
Most sites need less than they install. The point is a decision, not a dashboard.
Where this shows up in Solutions
Privacy, consent and what visitors are told
Analytics and conversion tools usually read or store information on a visitor’s device, or collect data about behaviour. Rules differ by region, and they are changing.
- Consent. Many jurisdictions require consent before non-essential cookies and similar technologies are used, with an exception for those that are strictly necessary. The UK ICO’s guidance on storage and access technologies is one detailed example. Rules differ, so check what applies to the people who visit your site.
- Transparency. Notice is a common requirement; the UK ICO, for example, says organisations must tell people, clearly and comprehensively, about the technologies they use, including those set by third parties on linked pages.
- Sensitive data. Do not record what people type into forms or payment fields. Check that heatmap and recording tools mask them.
- Data location and retention. Read where the data is stored, how long it is kept, and who else can access it.
This guide is general information, not legal advice. Take qualified advice on the rules that apply to you, including the privacy and cookie rules of the countries your visitors are in.
Tracking has a performance cost
Every tag, pixel and widget is code that runs on your pages. web.dev’s guidance on third-party JavaScript says such scripts can significantly slow page loads, especially when loaded synchronously, and recommends loading them asynchronously with the async or defer attributes unless a script must run first, connecting early to important third-party origins, lazy-loading non-critical items, and choosing carefully how scripts are hosted.
The practical rule is simple: measure your page speed with and without your tags, and remove any tag whose report nobody reads. Speed affects the same conversions you are trying to measure. See the Hosting guide for how hosting relates to performance.
Forms, landing pages and funnels: three ways to capture a lead
The same enquiry can be captured in three different places. Which is best depends on who maintains it.
A form on your own site
A form built into your existing pages, using your CMS or a form tool.
Suits: most businesses with a working website
Trade-off: less design freedom; you own maintenance and spam handling.
A landing-page builder
Focused pages for a specific campaign, on a separate platform, often with built-in forms and testing.
Suits: teams running frequent campaigns who want speed
Trade-off: another platform to pay for and leave; pages and forms may not export cleanly.
A funnel platform
Connected pages for a multi-step journey, sometimes with payments and email.
Suits: sellers of a single offer with a defined journey
Trade-off: the widest lock-in; check what you can move and what you must rebuild.
Whichever you pick, forms need to be accessible. The W3C’s form tutorial covers the basics: connect every field to a label, group related controls with fieldset and legend, give clear instructions, validate input and tell users what went wrong and how to fix it, and break long forms into logical steps.
Where this shows up in Solutions
A/B testing: powerful, and easy to misuse
An A/B test is a randomised experiment comparing two variants of one thing and using statistical testing to see which performs better on a defined outcome such as sales or sign-ups. Descriptions of the method stress several limits:
- It needs a large enough sample to produce a reliable result, so low-traffic sites may wait a long time.
- Results must be tested to make sure the difference is real and repeatable, not chance.
- Poor design, such as stopping early or changing several things at once, leads to false conclusions.
If your site gets little traffic, better research often beats testing: talk to customers, read the questions they ask and fix the obvious problems first.
How analytics and conversion costs are structured
Prices change often, so this guide gives no figures. The structure is what lasts:
- Analytics is priced by events, visits or data volume, with retention and feature limits by plan. Some tools are free at small scale.
- Session and testing tools are priced by sessions or tested visitors.
- Form and landing-page tools are priced by pages, submissions or seats.
- Add-ons such as integrations, extra users and longer data retention.
- Your time. Set-up, tagging, checking and acting on the data.
Compare tools against the two or three outcomes you defined, not against feature lists.
Switching tools without losing your history
Historical data is the hardest thing to move, because different tools define visits and conversions differently.
- Export what you can from the old tool: reports, raw data and configuration such as goals and definitions.
- Run the new tool alongside the old for a full reporting cycle and compare the numbers, expecting differences.
- Document your definitions so later reports mean the same thing.
- Keep the old account read-only if the vendor allows it, until you no longer need the history.
- Remove the old tags once the switch is confirmed.
Common mistakes and warning signs
- Installing tracking without a question to answer.
- A tag manager full of tags nobody remembers adding.
- Recording sensitive form fields.
- Declaring an A/B test won after two days of traffic.
Show 4 more
- Comparing numbers between tools that define visits differently.
- Building landing pages on a platform you cannot leave.
- Ignoring what tracking does to page speed.
- Reports that nobody uses to make a decision.
Frequently asked questions
Do I need analytics on a small site?
You need to know whether the site is doing its job. A simple analytics tool and a clear outcome are usually enough. Add other tool classes only when a specific question needs them.
Which analytics tool is best?
There is no single best tool. The right one depends on your outcomes, your traffic, your privacy obligations and your team. Start from the question and the constraints, using the funnel above.
Do I need a cookie banner?
It depends on which technologies you use and where your visitors are. Many regulators, such as the UK ICO, require consent before non-exempt storage or access technologies. Check the rules for your audience, and take qualified advice.
Are heatmaps and session recordings worth it?
They can reveal usability problems, but they add scripts and store behavioural data. Use them for a defined question and switch them off afterwards, masking sensitive fields.
How much traffic do I need for A/B testing?
Enough that a difference can be told from chance, which depends on your baseline conversion rate and the size of change you expect. Small sites often cannot run reliable tests.
Should I build landing pages in a separate tool?
Only if the speed and testing features are worth the extra platform. Building them in your own CMS keeps everything in one place and easier to leave.
How often is this guide updated?
We review it when material information changes, and the review date is shown at the top. See How We Evaluate.
Ready to compare available providers?
This guide explains the decision. When you are ready to shortlist by business need, see Analytics & Conversion Tool Solutions.
Sources and method
Sources and how we work (5 sources)
This guide is based on public documentation, standards and published sources, and on general industry practice. Provider claims, public documentation, published sources and our own observations are kept distinct, and where we have directly tested or used something, we say so explicitly. This guide names no products as recommendations. Figures that change are dated where they appear. Sources used:
- web.dev: Efficiently load third-party JavaScript Performance impact of third-party scripts and how to reduce it.
- UK ICO: Guidance on the use of storage and access technologies Consent, the strictly necessary exception and transparency.
- Wikipedia: A/B testing Definition, sample size and statistical pitfalls.
- W3C Web Accessibility Initiative: Forms tutorial Labels, grouping, instructions and validation.
- web.dev: Web Vitals Why page speed affects the outcomes you measure.
Read How We Evaluate for our criteria and the limits of what we claim. If you spot an error or an omission, please email info@kybervega.com.