Maintenance
Analytics tools: what beginners should know in 2027
A practical 2027 guide to analytics tools: what beginners should know with current definitions, decisions, checks, and review steps.
Almost everything sold as analytics is doing one, two or three separate jobs: recording what happened, deciding what it means, and drawing it. The three have different costs, different lock-in and different ways of going wrong. A vendor strong in one is usually thin in another, and the demo is designed so you never find out which.
What to take away
- Work out which of the three layers a vendor actually owns. That single fact predicts the price shape and the failure mode.
- The number in a report is produced by four settings, not by the data: identity, attribution window, time boundary, and filtering.
- Presentation is the layer you look at and the layer that matters least. A charting product will not fix a collection problem.
Layer one: recording what happened
Collection is the part that decides what questions are answerable at all. Data arrives from a tag or SDK you install, a stream sent from your own servers, an API on someone else's platform, or a file somebody uploads. Each route has a different failure mode, and the routes are not interchangeable.
Two properties are worth more than any feature here. The first is what is structurally invisible. Nothing collected on your site can see a competitor's spend, a conversation that happened offline, or a person who declined tracking. Cross-device behaviour is invisible unless there is a login. A tool that appears to report on these is modeling them, and modeling belongs to the next layer.
The second is whether the record is replayable. If you can get the raw events back out and load them somewhere else, a change of vendor costs you effort. If you cannot, a change of vendor costs you your history, because the new tool starts from the day you install it. Whoever owns collection owns the switching cost, which is why collection is where the serious contracts live.
Layer two: deciding what it means
Between the events and the report sits a set of choices. Four of them move the numbers more than any feature comparison will.
Identity. What makes two visits the same person. Device, login, or a probabilistic match. Everything downstream inherits this rule, including your unique visitor count and your conversion rate.
Attribution. Which touch gets the credit, and over what window. Every tool ships with a default. The default is a decision made by the vendor, not a property of your campaign, and it is worth naming beside the number every time.
Time boundary. Which day a thing belongs to. Time zone, week start, and the exchange rate date for anything in another currency. Two tools with identical events and different boundaries will never agree on a Monday total.
Filtering. Bots, internal traffic, test orders, and thresholds that suppress rows below some size. Filtering rules differ by vendor and change without much announcement, so when a figure looks impossible, find out what is being removed before building a story on what is left.
Two tools reading the same events will disagree if any one of these four differs. That disagreement is the useful part of a comparison, not a defect in either product.
Layer three: drawing it
Dashboards, scheduled reports, client portals, and the export button. This is the layer that fills the demo, takes the largest share of the interface, and is the easiest of the three to replace. It is also the layer where a good product over a weak collection layer produces confident wrong answers faster than a spreadsheet would.
Judge it on one thing: can a person who did not build the report reproduce a number in it. If the only route back to a figure is asking the person who made the chart, the layer has failed at its actual job.
Reading which layers a vendor really owns
Vendors describe themselves generously. Their pricing and their setup requirements describe them honestly.
| What you observe | What it usually tells you |
|---|---|
| Setup is one script and nothing else | Collection, with modeling left at defaults |
| It wants access to your ad accounts, not your site | Platform reporting, aggregated from elsewhere |
| Event level rows cannot be exported | A presentation layer over somebody else's data |
| Price grows with tracked events or data volume | They are storing your raw record, so collection is the product |
| Price grows with seats or dashboards | Presentation is the product |
| Attribution models are named and switchable | Modeling is a real part of what you are buying |
| Historic figures change after a settings edit | Modeling happens at read time, so old reports are not fixed |
That last row deserves a test of its own. Change one setting, then reopen a report you exported last week. Whether the past moves tells you something no feature list will.
The agency problem
Buying for one brand is a different exercise from buying for a portfolio. Three things break first.
Access is borrowed and it ends. Your setup lives inside a property the client owns, and one day it does not. Find out what survives that: the tracking plan, the exported history, the report definitions, or nothing.
Templates have to travel. If a report has to be rebuilt by hand for each new account, the tool has quietly added a recurring cost to every win. Make the vendor apply a template to a fresh account during the evaluation.
Separation has to be real. A client should see their own data and nothing else, including the fact that other clients exist. Test this with two actual accounts.
Price shape is the last one, and it is where spiky agency volume bites. Work out which line grows when a campaign succeeds, then model the busiest month you have actually had rather than the average. The campaign side of the stack usually carries the same shape, so settle both in the same week.
What analytics cannot settle
Every honest measurement setup has a list of questions it cannot answer. Whether a campaign caused the sales, or the sales were coming anyway. What happened offline. What a competitor did. Anything before collection started. Anything a person declined to share.
Naming those limits in the report is what makes the rest of it credible. It also stops the slow drift where a plausible figure from an audience estimate gets treated as a measurement three slides later. The same discipline applies when the numbers come from a partner rather than your own stack, which is a standing issue for anyone working through an influencer agency on borrowed reporting. It applies twice over when the figures arrive as a screenshot from a creator's manager, since talent representation sits between you and the account the numbers came from.
Common questions
Do we need all three layers from one vendor?
No, and the buyers with the most reliable reporting usually do not. One tool for collection with real export, and whatever presentation suits the client, is a common and durable arrangement.
Two tools show different totals. Which one is right?
Probably both, about different questions. Compare the four settings above before comparing the numbers. If the settings match and the totals still differ, you have a collection problem worth chasing.
Is raw export worth paying for if nobody would use it?
Yes. It is the only way to check a tool against anything outside itself, and it is what keeps the decision reversible.
Where should a small team start?
With a written list of the questions clients actually ask at month end. Fit is measured against that list. Everything in this guide is downstream of it.