Google Analytics is a free web analytics service from Google that records how people arrive at a website or app and what they do there. The current version treats every interaction as an event, such as a page view, a click or a purchase, so a business can measure traffic, engagement and sales in one place.
An event-based model
Older web analytics counted mainly page views and sessions. The current generation of Google Analytics records almost everything as an event: a page loading, a scroll, a video starting, a product being added to a cart or an order being placed. Each event can carry extra details, called parameters, such as the product name, its category or its price.
This model makes websites and apps easier to compare, because a tap in an app and a click on a site are both events. It also means the quality of the data depends on which events a store chooses to send and how carefully it labels them.
Some events are collected automatically once the tag is installed, such as page views and first visits. Others, including most shopping actions, must be sent by the store or its platform integration. Knowing which is which prevents a common surprise: a report that shows plenty of visits but no revenue, because purchase events were never configured.
Key events and conversions
Not every event matters equally. A business marks the events that represent real progress, such as a completed purchase, a newsletter sign-up or a quote request, as the ones to watch. Recent versions of the interface call these key events, while earlier versions called them conversions. The idea is the same: a short list of actions that show the site is doing its job.
- A purchase event for a completed order
- A sign-up or account creation event
- A begin-checkout event to see how many shoppers reach payment
- A contact or quote request event for higher-priced items
Reports a store owner actually uses
Most stores rely on a handful of views. Acquisition reports show where visitors came from, such as search, ads, email or social posts. Engagement reports show which pages people view and how long they stay active. Monetization reports, when e-commerce events are set up, show revenue, items purchased and average order value.
The most useful insight usually comes from combining them. For example, a channel that sends many visitors but few purchases tells a different story from a smaller channel whose visitors buy often.
Segments and comparisons add depth. Splitting reports by device, country or new versus returning visitors often shows that an average hides two very different groups. A product page that converts well on desktop but poorly on mobile, for instance, needs a different fix from one that performs badly everywhere.
Reading price changes in your analytics
Analytics shows what happened on your own site, but not why. A drop in purchases on a product page might come from a slower page, a broken image or a competitor that cut its price that morning. Without a record of market prices, the last cause is easy to miss.
Take an assumed case. A shop sells a coffee grinder at 89 dollars. Over two weeks, product views stay near 1,000 per week, but purchases fall from 30 to 18. Nothing on the site changed. If a price history for the same grinder shows two rivals moving to 79 dollars on the day sales dropped, the analytics data now has an explanation, and the pricing team has a decision to make.
Setting up e-commerce tracking
- Install the tracking tag through your store platform’s built-in integration or a tag manager.
- Send standard e-commerce events, such as viewing an item, adding to cart, starting checkout and purchasing.
- Include the item price, quantity and currency with each event, so revenue figures are correct.
- Mark the purchase and other important actions as key events.
- Place a test order and confirm that it appears once, with the right value.
Platforms such as Shopify and WooCommerce offer ready-made connections, which reduce the work but still need a test order to confirm they report the right values.
Limits and common mistakes
Analytics figures are estimates, not a ledger. Visitors who block tracking or decline analytics cookies may not be counted, so totals in Google Analytics rarely match the orders in your store system exactly. Treat the store system as the record of sales and analytics as the record of behaviour.
- Counting the same purchase twice when a thank-you page is reloaded
- Sending prices without currency, which mixes values across markets
- Marking too many events as key events, so the important ones get lost
- Comparing periods without checking for promotions, holidays or competitor price moves
Making it part of pricing decisions
Before changing a price, note the date, the old price and the new price, and pick a few pages to watch. After the change, compare product views, add-to-cart rates and purchases for a period of similar length. Keep a note of competitor price moves during the same window, so a shift in demand is not credited to the wrong cause.
Over time, this habit turns analytics from a traffic counter into evidence about how your customers respond to price.
Be patient with small numbers. A product that sells five units a week cannot show a reliable change after three days, because ordinary variation is larger than the effect you are looking for. Wait for a full week or two, and compare the same weekdays, before deciding whether a new price helped or hurt.
Key takeaways
- Google Analytics records visits and actions on your site as events with optional details such as price.
- Key events are the few actions a business marks as important, such as purchases.
- Analytics explains what happened on your site, not what competitors did.
- Pair analytics with a record of market prices before judging a price change.
- Treat analytics totals as estimates and the store system as the record of sales.
Frequently asked questions
Is Google Analytics free?
The standard version is free to use for most websites and apps. Google also offers a paid enterprise edition with higher limits and support. Small and mid-sized stores usually find the free version sufficient.
What is the difference between an event and a key event?
An event is any interaction that analytics records, such as a page view or a click. A key event is an event the business has marked as important, such as a purchase. Earlier versions of the product called these conversions.
Why do analytics sales numbers differ from my store orders?
Some visitors block tracking or decline consent, and some events fail to send. Refunds and edited orders may also be handled differently. Use your store system as the source of truth for revenue.
Can Google Analytics show competitor prices?
No. It measures behaviour on your own site only. To understand whether a change in sales came from the market, you need a separate record of competitor prices over the same period.
Related terms
In BlackAha, Pricing Reports helps you analyze pricing and competition by category, brand and domain.