Web analytics began as a technical curiosity and became the backbone of product decision-making. If you don't understand where the data comes from, you can't trust what it tells you.
Web analytics did not start with fancy dashboards or SaaS tools. It began with IT technicians maintaining server logs — raw files tracking every visitor's interaction with a website. This early data collection was rudimentary but foundational. Understanding this origin is critical because the actual job of web analytics is to turn noise into insight — to know who your users are, what they do, and how to improve their experience.
Today, countless Indian startups and enterprises rely on web analytics. But most product managers don't know how these numbers are generated or what assumptions underlie them. That gap leads to misinterpretation and wasted effort. The actual job is to understand the metrics at their core, so you can make confident product decisions.
The origins of web analytics: from server logs to actionable insights
Web analytics traces its roots to the earliest days of the Internet. Just after the birth of the web, IT teams began maintaining server log files. These logs recorded every request made to the server, capturing parameters such as:
- The visitor’s IP address
- The browser identifier (which browser and version)
- The operating system identifier
- The referrer URL (the website or page that led the user to the current page)
These logs were essentially the web’s raw heartbeat.
People started writing scripts to parse these server logs — extracting useful data to understand visitor behavior. This was tedious and technical work, but it laid the groundwork for modern analytics. As Talvinder explains, “Just after the birth of the Internet, IT technicians started maintaining server logs. People began developing scripts to extract relevant data from the server log files in order to compile useful information. In this way, web analytics came to life.”
Over time, these raw logs evolved into structured data systems and eventually into the web analytics tools we use today — including Google Analytics, Adobe Analytics, and others.
Why web analytics matters for product managers
The actual job of web analytics is to provide insight into visitor behavior so you can optimize your product. You want to know:
- Who is visiting your website or app?
- What paths do they take?
- Where do they drop off?
- Which features or pages drive conversions?
- How different segments of users behave differently?
This data enables you to make informed decisions about product development, marketing, and operations.
Talvinder puts it simply: “Web analytics provides business intelligence along with the context of customer segmentation, trends, and product development. It helps you decide which product areas to invest in, which features to improve, and which user groups to focus on.”
Without web analytics, you are flying blind. You guess, you hope, you argue — but you don’t have evidence.
Key concepts: web metrics, clickstream, and sessions
Before diving into tools, you must understand the basic concepts web analytics tracks.
-
Web metrics are measurable parameters reflecting activities on your website. Examples include pageviews, number of unique visitors, bounce rate, session duration, button clicks, and downloads.
-
Clickstream data records the sequence of actions a user takes on your site — every page viewed, every button clicked, every scroll event. It is the story of the user’s journey.
-
Sessions define a period of interaction between a visitor’s browser and your web server. Typically, a session expires after 30 minutes of inactivity. If the user returns after that, it starts a new session.
Talvinder explains: “Session is the period of interaction between a visitor’s browser and a particular web server. The rules are out there as to what will be called a session, what will not be called a session. Typically, an inactivity of 30 minutes is considered a session.”
Understanding sessions is crucial because many metrics — like bounce rate or conversions — are calculated per session.
Metrics and dimensions: the building blocks of web analytics reports
Most web analytics tools, including Google Analytics, organize data into metrics and dimensions. These are not interchangeable.
-
Metrics are numerical measurements — counts or ratios. For example: number of visits, pageviews, average session duration, bounce rate.
-
Dimensions are categorical attributes that describe the data — non-numerical labels like country, device type, browser, or traffic source.
Talvinder details:
“Metrics will always be expressed in the form of a number. Metrics are standalone entities. When you look at a metric in a standalone fashion it provides you with information about site-wide performance. Metrics form the columns of a report.”
“Dimensions are non-numerical data fields. Unlike metrics, dimensions are not standalone entities; they provide context when coupled with metrics. Dimensions can be used to segment a metric.”
For example, total pageviews (metric) segmented by country (dimension) tells you which countries generate the most traffic.
Knowing this distinction helps you ask better questions. Don’t just look at “visits” — ask “visits by device type” or “pageviews by referral source.”
How Google Analytics works under the hood
Google Analytics is the most widely used web analytics tool globally and in India. Its origins trace back to a company called Urchin, acquired by Google in 2005. Google Analytics then revolutionized web analytics by providing an easy-to-use interface to analyze complex visitor data.
At a high level, Google Analytics works like this:
- You embed a small JavaScript tracking code on your website.
- When a user visits, this code executes and collects data about the visit — page URL, timestamp, browser, device, referral, and more.
- The code sets a first-party cookie in the user’s browser to uniquely identify the visitor.
- This data is sent securely to Google servers, where it is aggregated and processed.
- You access reports via the Google Analytics web interface, which visualizes the processed data.
Talvinder explains:
“Google Analytics uses first party cookies to uniquely identify individual visitors. The tracking code gets initiated by a JavaScript snippet. If you inspect any website using Google Analytics, you will find this code. The data is then sent to secure Google servers, aggregated, and shown on the interface.”
Understanding this pipeline is important because it explains some quirks:
- If users block cookies, analytics data may be incomplete.
- Tracking is limited to pages with the code embedded.
- Data processing may have latency.
Defining and tracking goals: measuring success
A goal in web analytics is any activity on your website that is important to business success. For example, a visitor submitting an order, signing up for a newsletter, or reaching a thank-you page.
Google Analytics lets you define goals explicitly. Each time a visitor meets the criteria, a goal conversion is recorded. Note that during a single session, a goal can only be counted once.
Talvinder notes:
“A goal can be any activity that is important to the success of your business. For simplicity, a web page displaying a confirmation for submitting an order could act as a goal. Each time a visitor meets that criteria, a goal is recorded.”
Goals allow you to measure the effectiveness of your product features or marketing campaigns. For example, you can track how many users completed onboarding or made a purchase.
From raw data to actionable decisions
The real power of web analytics is not in collecting data, but in analyzing it to improve your product.
Talvinder advises:
“Web analytics is actionable, unlike web reporting. It helps you make informed decisions about changing your online strategy.”
For instance, if you see a high bounce rate on your pricing page, it might indicate confusion or misalignment. You can then run experiments to improve clarity or test different offers.
Similarly, segmentation can reveal that users from certain regions have lower conversion rates, prompting localization efforts.
Modern analytics beyond server logs
While server logs laid the foundation, modern analytics tools have expanded capabilities:
- Event tracking: capturing specific user actions like button clicks or video plays.
- Funnel analysis: understanding drop-off points in multi-step processes.
- Cohort analysis: tracking groups of users over time.
- User profiling: combining behavior with demographics or CRM data.
Talvinder mentions:
“Google Analytics has evolved much — but the core remains the same: recording clicks and taps, storing events, and letting you see what happened.”
Other tools like Mixpanel focus more on user profile driven analytics, tracking how individual users flow through the system rather than just aggregate clicks.
Indian context and practical advice
In India, many product teams rely heavily on Google Analytics because it is free for startups and widely supported. Talvinder recommends:
- Take Google’s official Analytics course — it is beginner-friendly and sufficient for most PMs.
- Understand the difference between metrics and dimensions to ask better questions.
- Use goals to measure meaningful user actions.
- Remember the data is only as good as your tracking implementation and cookie policies.
- Combine analytics with qualitative user research for a fuller picture.
Field exercise: explore your product’s web analytics
Take 10-15 minutes to open Google Analytics (or any web analytics tool you have access to) for a product or website you care about.
- Identify three key metrics you want to understand (e.g., sessions, bounce rate, goal conversions).
- Pick one dimension to segment each metric (e.g., country, device, traffic source).
- Look for patterns or anomalies. Where do users drop off? Which segments perform better?
- Write down one hypothesis about how you might improve the product based on this data.
This hands-on practice will help you connect theory with real-world data.
Test yourself: The analytics setup dilemma
You are the PM at a growing Indian e-commerce startup based in Bangalore. The marketing team asks you to set up Google Analytics goals to track the checkout funnel. The engineering team says they can implement event tracking, but it will take 3 weeks. The CEO wants to see funnel conversion metrics in 1 week for an upcoming board meeting.
The call: How do you prioritize the analytics work, and what do you communicate to the CEO and engineering?
Your reasoning:
Where to go next
- Master user behavior analysis: User Behavior Analytics
- Learn event-based analytics for product growth: Event Analytics
- Understand metrics and KPIs for product success: Metrics and KPIs
- Explore qualitative research methods: User Research Methods
- Get certified in Google Analytics: Google Analytics Academy (recommended by Talvinder)
/* End of lesson */