Course Preview

Google Analytics and Product Analytics Fundamentals

Google Analytics and product analytics turn website and app interactions into event data that supports questions about acquisition, conversion, engagement, and retention. The work includes planning events, collecting them responsibly, validating the data, and interpreting reports without confusing measurement with proof of causation.

itData engineering and analytics | OpenSkills.info

Course pathWalk it in order

Look it upDip in anytime

Go furtherLeaves this page

Don't Panic — Google Analytics and Product Analytics Fundamentals

Google Analytics is a tool for recording what people do on your website or app. Product analytics is the wider practice of turning that behavioral data into decisions about acquisition, adoption, conversion, and retention. The tool is the easier part. The practice is what takes work.

Before GA4 existed, analytics was built around sessions and pageviews. You counted visits, measured bounce rate, and called it a day. GA4 replaced that with an event-based model — every interaction is an event with a name and parameters, and you assemble meaning by combining them. This is more flexible, but it also means you are responsible for defining what your events actually mean. GA4 will not do that for you.

The idea that makes everything else work is the event contract. An event name says what happened. Parameters add context. Scope determines whether a field applies to an event, a session, or a user. If you get these right, the analysis follows. If you get them wrong, you get dashboards that load on time and show numbers that mean nothing.

The surprise for most people is how much can go wrong between "the tag fired" and "the data is correct." GA4 will accept events with missing or incorrect parameters without throwing an error. A purchase event can silently lose its transaction_id or currency field and you will not find out until someone compares GA4 revenue to your backend and the numbers do not match. The tag works. The dashboard loads. The data is wrong.

Identity is the other quiet problem. GA4 joins activity using a browser client ID, an app-instance ID, or an authenticated User-ID. Cookie deletion, consent denial, multiple devices, and shared computers all break the join. Treat every user count as a measurement definition, not a census of people.

Sessions add a time boundary. GA4 starts a session when a page is viewed and no session is active, and ends it after thirty minutes of inactivity. A long task may span sessions. A short session may contain many events. Use sessions for visit-shaped questions; use user-scoped sequences for behavior that crosses visits.

Attribution assigns credit to touchpoints. It does not prove that a channel caused the outcome. When the question is causal — did this campaign drive incremental revenue — you need a controlled experiment, not an attribution report. Confusing the two is one of the most expensive mistakes in product analytics.

For your next step, the Reference tab walks you from foundational documentation through the platform decision path. The Landscape tab shows you the market around GA4 so you can see what else exists. And if you skipped here from the title, go back to the intro — the five-layer model it describes is the mental map that holds everything else in place.

Where this skill leads

Relevant careers

See how this topic contributes to broader role-level skill maps.

Data Analystspecialization

Sources