Metrics are the numbers that tell you if your product is moving towards its goal or drifting away. Dimensions give those numbers meaning.
Google Analytics is one of the most important tools in your product analytics toolkit. The actual job is to turn raw data into insights that guide product decisions. Without a clear understanding of how analytics reports are structured and what the numbers mean, you risk chasing vanity metrics or missing critical user behaviors.
The trap is treating metrics as standalone absolutes without context, or confusing data reporting with actionable insights. This lesson teaches you the foundational concepts of metrics, dimensions, and goals in Google Analytics — the building blocks for meaningful analysis.
Metrics and dimensions are the pillars of Google Analytics reports
Google Analytics organizes data around two fundamental concepts: metrics and dimensions.
Metrics are numerical measures of user interactions on your website. They always appear as numbers and represent quantities or rates. For example, visits, pageviews, and bounce rate are common metrics.
Dimensions are non-numerical attributes that add context to metrics. They describe characteristics of users, sessions, or actions that help segment and interpret the numbers. Examples include the browser type, device category, or geographic location.
The actual job is this: metrics tell you what happened; dimensions tell you who, where, or how.
Metrics form the columns of Google Analytics reports; dimensions form the rows. When you combine them, you get meaningful insights.
For example, a report might show the number of visits (metric) segmented by device type (dimension). This tells you not just how many visits you had, but how many came from mobile versus desktop.
Dimensions are not standalone entities. Looking at a dimension like "Chrome browser" in isolation doesn’t mean much. But when you see that Chrome users had 10,000 visits, that is actionable.
Dimensions can be used to segment metrics, revealing patterns hidden in aggregate numbers.
In practice, you will use dimensions to filter or segment your metrics. For instance:
- How many visits came from Bangalore versus Mumbai?
- Which pages have the highest bounce rate for first-time visitors?
- What is the average session duration on Android devices versus iOS?
This structure is critical to understand before you dive into Google Analytics dashboards.
Metrics are standalone numbers that quantify user behavior
A metric measures a specific user action or event. Metrics are always numerical and provide a direct quantification of user activity.
Some common metrics in Google Analytics include:
- Visits (Sessions): The total number of times users have interacted with your site during a time period.
- Pageviews: The total number of pages viewed.
- Bounce Rate: The percentage of sessions where users left after viewing only one page.
- Average Session Duration: How long users stay on your site on average.
- Goal Conversion Rate: The percentage of sessions that completed a defined goal.
Metrics can be viewed individually to get a high-level sense of site performance. For example, if your visits dropped 20% week-over-week, that signals a potential issue.
However, metrics alone are not enough. You must combine them with dimensions to understand why.
Dimensions provide context and segmentation to metrics
Dimensions are descriptive attributes that qualify your metrics. They answer questions like:
- Who are my users? (e.g., new vs returning, country, age group)
- How did they arrive? (e.g., referral source, campaign, device)
- What did they do? (e.g., page path, event category)
Dimensions are categorical data fields, not numbers. They are meaningless alone, but crucial when paired with metrics.
For example:
- 500 visits from Chrome users
- 300 sessions from organic search
- 1000 pageviews of the pricing page
Using dimensions, you can segment your metrics to identify trends and opportunities.
The trap is treating dimensions as standalone metrics or ignoring them altogether.
You will often want to slice your reports by dimensions to see how different user segments behave.
Filters refine your data for accurate analysis
Google Analytics offers filters to clean and segment your data sets. Filters help remove noise and focus on relevant subsets.
For example:
- Exclude internal traffic from your office IP addresses.
- Include only users from India.
- Filter sessions from a specific campaign.
Filters operate on dimensions and metrics to create precise views of your data.
In practice, filters help you avoid misleading conclusions by ensuring your data reflects real user behavior, not spam or bots.
Goals track the critical user actions that drive business success
A goal in Google Analytics is any user activity important to your business outcomes. It measures whether users complete key actions on your site.
Examples of goals include:
- Completing a purchase (order confirmation page)
- Submitting a lead form
- Registering for an event
- Viewing a key content page
Goals help you quantify the success of your product in driving desired user behaviors.
Each time a visitor meets the goal criteria, Google Analytics records a conversion. During a single session, a goal can only be counted once.
Goals are essential for turning raw traffic metrics into business insights. For example, it is not enough to know you had 10,000 visits. You want to know how many of those visits resulted in a purchase or signup.
In India, where cost sensitivity and conversion optimization are critical, measuring goals helps you improve ROI on your digital efforts.
Web analytics is actionable data, not just reporting
Just after the birth of the Internet, IT teams maintained server logs recording raw data such as:
- IP address of the visitor
- Browser and operating system identifiers
- Referrer URLs
Initially, these logs were cryptic and hard to interpret.
People developed scripts to extract useful information, leading to the birth of web analytics.
Unlike web reporting, which just dumps data, web analytics helps you make informed decisions about changing your online strategy.
The actual job is to use analytics data to answer:
- Which channels bring the most valuable users?
- Where are users dropping off in the funnel?
- What product features engage users best?
Google Analytics is a powerful tool for this purpose, but only if you understand its metrics, dimensions, and goals.
Understanding the historical context sharpens your perspective
India’s digital ecosystem is growing fast, but many product teams still treat analytics as a checkbox rather than a strategic asset.
The pattern is consistent: teams look at total pageviews or sessions and declare success or failure without digging deeper.
I have seen product managers at Indian startups confuse raw traffic numbers with product health.
For example, a spike in visits from a bot or a campaign click farm inflates metrics but does not create value.
Understanding the difference between metrics and dimensions, and using goals to track meaningful user actions, is the foundation of data-driven product management.
Common metrics and their Indian context applications
| Metric | What it measures | Example in Indian product context |
|---|---|---|
| Visits (Sessions) | Number of user sessions on your site | Number of visits to Razorpay’s payment gateway page |
| Pageviews | Number of pages viewed | Total pageviews on Meesho’s product listing pages |
| Bounce Rate | % of single-page sessions | Swiggy’s landing page bounce rate during a festival season |
| Goal Completions | Count of a specific action completion | Number of loan applications completed on a fintech site |
| Avg. Session Duration | Average time users spend per session | Average time users spend on PhonePe’s offers page |
Metrics should be interpreted in the Indian market context, where mobile users dominate, data costs matter, and user behavior varies widely by region.
How to use Google Analytics effectively as a PM
- Start with your business goals. Define what success looks like (e.g., increase signups by 10%).
- Set up relevant goals in GA. Track key user actions that align with your objectives.
- Use dimensions to segment your users. Analyze behavior by geography, device, traffic source.
- Look beyond vanity metrics. Don’t celebrate visits without conversions.
- Apply filters to clean your data. Remove internal traffic, spam, or irrelevant segments.
- Regularly review reports and dashboards. Make data-driven product decisions and test hypotheses.
Supporting media
Test yourself: Interpreting Google Analytics reports at an Indian fintech startup
You are a PM at a Series B fintech startup in Bangalore. Your marketing team reports a 15% increase in visits last month but a 10% drop in goal completions for loan applications. The bounce rate on the loan application page increased from 35% to 50%.
The call: What does this data tell you about user behavior? What actions would you recommend to the team?
Your reasoning:
Where to go next
- Understand how to frame product hypotheses with metrics: Metrics and KPIs
- Learn to segment users for deeper insights: User Segmentation Techniques
- Explore goal-setting frameworks for product success: OKRs for Product Teams
- Get hands-on with user research to complement analytics: User Research Methods
- Advance your skills in data visualization and dashboards: Data Storytelling for PMs