Digital marketing course (GA4, GTM)

A dimension that comes from UTM parameters (utm_campaign) in your URLs. It identifies which marketing campaign a visit is associated with. Example: If you tag a link as ?utm_campaign=spring_sale, GA4 will report “spring_sale” under Campaign Name. Visual: In Acquisition reports, you can add “Campaign” as a dimension.

Query parameters you append to URLs (like utm_source, utm_medium, utm_campaign) to track marketing efforts. They tell GA4 where the traffic came from. Example: A URL like example.com?utm_source=facebook&utm_medium=post&utm_campaign=promo uses campaign tags. Visual: You set these tags manually when creating links (no GA interface for tag creation, but you see them in report dimensions).

An audit log in GA4 that records changes made in the property or account. It shows who changed settings and what was changed (e.g. creating events, changing admin settings). Visual: Access this under Admin > Change History, where you can filter by date or user.

Predefined groupings of traffic sources into channels (like Organic Search, Paid Search, Email, Social). GA4 automatically sorts source/medium combinations into channels. Example: “google/cpc” might be grouped under “Paid Search.” Visual: In reports, channel groupings often appear as rows or segments (e.g. in Acquisition > Traffic Acquisition).

A unique, random identifier that GA4 assigns to each device or browser to distinguish users anonymously. Stored in cookies, it lets GA4 see the same visitor returning. Visual: Though not shown in standard UI, Client IDs can be seen if you inspect cookies or use debugging tools.

Groups of users who share a common event date (e.g. acquisition date) for cohort analysis. GA4’s Cohort reports let you analyze how the behavior of these groups changes over time. Example: You might create a cohort of users whose first session was in January to see how many returned in February. Visual: In Explore, the Cohort Exploration template uses cohorts to build retention tables.

A feature (for gtag.js installations) that lets you link new or existing GA4 properties without adding new code. It automatically shares tagging across properties. Visual: This is configured under Admin > Property > Connected site tags.

A GA4 feature that adjusts data collection based on user consent for cookies. It allows Google tags to adjust behavior (collecting modeled data when full consent is not given). Example: If a user declines analytics cookies, Consent Mode may use anonymous pings instead of cookies. Visual: There’s no UI report for Consent Mode, but it’s implemented via your site’s tag code.

Signals used by GA4 and Google’s Consent Mode to transmit a user’s cookie consent status (granted or denied for analytics, ads, etc.). These signals help GA4 know whether it can collect personal data. Visual: Seen under advanced settings; mainly a developer/implementation detail (e.g., default or granted status for ad_storage or analytics_storage).

A way to categorize pages or screens into logical groups for reporting. You send a content_group parameter with events to group content (like news categories, product categories). Example: You might tag all blog pages as “Blog” and all product pages as “Product” in content groups. Visual: In reports, you can use the Content Group dimension to compare metrics by these categories.