Google Analytics

Some current GA4 Standard property limits include:

Most normal business websites will not approach many of these limits.

The 14-month retention limit matters more for businesses that want long-term user-level analysis.

Create a Google Analytics account and a GA4 property for the website or application.

Then create a data stream for:

• Web

• iOS

• Android

A normal website uses a Web data stream.

Google provides a Measurement ID associated with the web stream.

It normally begins with:

G-

The tag can be installed through:

• A CMS integration

• Google Tag Manager

• Manual website code

Platforms such as Shopify, Wix, Squarespace, WordPress tools, and other supported systems may provide a field for the Google tag ID.

For a custom Website, the Google tag can also be installed directly in the site's code.

Visit the website after installation and open the Realtime report.

Confirm that Analytics receives:

• A user

• Page views

• Expected events

Google states that initial data collection can take up to approximately 30 minutes to begin.

Do this verification immediately instead of discovering weeks later that tracking was broken.

Do not begin by creating dozens of custom events.

Start with a few actions directly connected to the business.

Examples:

Ecommerce:

• view_item

• add_to_cart

• begin_checkout

• purchase

Lead generation:

• generate_lead

• Form completion

• Account signup

• Booking completion

Content:

• Newsletter signup

• Subscription

• Important outbound click

An event that matters to the business can be marked as a key event.

For example:

generate_lead → Key event

or:

purchase → Key event

Key events make it easier to evaluate which traffic sources and campaigns lead to meaningful outcomes.

GA4 uses events as the foundation of measurement.

Some events are collected automatically.

Enhanced Measurement can also collect interactions such as:

• Page views

• Scrolls

• Outbound clicks

• Site search

• Video engagement

• File downloads

Other business-specific events may need to be configured.

Google provides recommended event names for common activities.

Use recommended events where possible instead of inventing custom names for common actions.

For example, prefer:

generate_lead

rather than:

form_finished_123

when the first accurately describes the action.

Standardized events work better with Google's existing reporting and integrations.

Parameters add context to an event.

For example:

purchase

might include information about:

• Transaction ID

• Value

• Currency

• Products

A click event might include details about:

• Link URL

• Button

• Page

• Content

Think of an event as what happened and parameters as details about what happened.

GA4 separates important Analytics events from advertising conversions.

The current model can be summarized as:

Event → Key Event → Google Ads Conversion

An event can be marked as a key event when it represents an important business action.

If that action should also be used for Google Ads campaign measurement or bidding, a conversion can be created from the key event.

Do not mark every interaction as a key event.

A scroll is usually less valuable than:

• Purchase

• Subscription

• Qualified lead

• Trial signup

Email / Social / Campaign → UTM link → Landing page → User action → Key event

Add UTM parameters to external campaign links so Analytics can identify where traffic originated.

Important parameters include:

• utm_source

• utm_medium

• utm_campaign

For example:

utm_source=newsletter

utm_medium=email

utm_campaign=summer_sale

Google recommends consistently using source, medium, and campaign.

The main failure point is inconsistent naming.

For example:

facebook

Facebook

fb

can create fragmented reporting for what was intended to be one source.

Choose a naming convention and keep it consistent.

Search or ad → Landing page → Form submission → generate_lead → Key event

Instead of optimizing around pageviews, measure completed leads.

You can then compare:

• Organic search

• Paid search

• Social

• Referral traffic

• Email

based on actual lead generation.

This is especially useful for service businesses such as Freelancing and consulting.

Product view → Add to cart → Checkout → Purchase

An ecommerce store can compare how many users reach each stage.

For example:

1,000 product viewers
→ 100 add to cart
→ 60 begin checkout
→ 40 purchases

This immediately shows that improving product-to-cart conversion could have more impact than simply increasing traffic.

Stores built around platforms such as WooCommerce can use Analytics alongside native store reporting.

Tracking more events does not automatically produce better analytics.

Begin with questions such as:

• Did the visitor purchase?

• Did they register?

• Did they become a lead?

• Did they subscribe?

Then collect the events required to answer those questions.

Google maintains standardized recommended events for activities such as:

• Login

• Signup

• Lead generation

• Ecommerce

• Purchases

Use these when they match the action.

Custom events are useful when the interaction genuinely has no appropriate standard event.

UTM values are case-sensitive.

For example:

utm_source=linkedin

and:

utm_source=LinkedIn

can appear separately.

A simple convention might be:

• Lowercase values

• Stable source names

• Standard medium names

• Human-readable campaign names

Document the convention before several people begin creating campaign URLs.

UTM parameters are intended for identifying external campaign traffic.

Using them on links between pages of your own website can overwrite acquisition information and make attribution harder to interpret.

Use normal internal links for site navigation.

Use:

• Realtime

• DebugView

to confirm that important events actually fire.

Test the complete user journey.

For example:

Submit form → Confirm generate_lead → Verify parameter → Check key event

Do this before running a major advertising campaign.

GA4 Standard properties support up to 30 key events.

More importantly, excessive key events make business reporting noisy.

Reserve them for actions that represent meaningful outcomes.

Realtime data can appear within minutes.

Standard property intraday processing typically takes around:

2–6 hours

Some daily processing can take longer.

Do not assume missing data from the last few minutes means tracking failed.

Analytics can compare traffic and outcomes across channels such as:

• Organic search

• Paid search

• Email

• Social

• Referral traffic

• Direct visits

This helps businesses allocate marketing effort based on outcomes rather than traffic alone.

Google Analytics shows what users do after reaching the website.

Search-performance tools show how people discovered the site.

Together they help answer:

Search query → Landing page → Engagement → Key event

For an SEO strategy, traffic growth matters less if the visitors never complete useful actions.

Stores can analyze:

• Product views

• Add-to-cart behavior

• Checkout activity

• Purchases

• Revenue

• Acquisition channels

This helps identify whether the primary problem is traffic, product-page conversion, checkout abandonment, or customer acquisition.

A SaaS business might measure:

Visitor → Signup → Trial → Subscription

GA4 can provide acquisition and behavioral measurement, while the product's own database should normally remain the source of truth for billing and account status.

Linking Google Ads and Analytics can connect advertising traffic with on-site behavior and key events.

Important business events can also be used to create Google Ads conversions.

This is useful when optimizing campaigns toward:

• Purchases

• Leads

• Registrations

rather than clicks alone.

Analytics can be linked with Search Console.

The integration can provide reports combining organic-search information with website behavior.

This helps connect:

Search visibility → Click → Landing page → User behavior

GA4 can export data to BigQuery for deeper analysis.

This becomes useful when businesses need:

• Raw event-level analysis

• Custom reporting

• Data warehouse integration

• Joining Analytics with business databases

Most small websites do not need BigQuery immediately.

Start with standard reports and Explorations.

Google Tag Manager can manage Analytics and other marketing tags without manually changing application code for every tracking adjustment.

It becomes especially useful when a business needs:

• Custom events

• Multiple marketing pixels

• More complex triggers

• Centralized tag management

Explorations allow more flexible analysis than standard reports.

Useful examples include:

• Funnel exploration

• Path exploration

• Segment comparisons

• User behavior analysis

A funnel might show:

Product page → Cart → Checkout → Purchase

This makes drop-off easier to identify.

Standard GA4 properties can encounter sampling in Explorations when ad-hoc queries process more than 10 million events.

For normal small websites, this is rarely the first limitation encountered.

Custom dimensions allow event parameters or user properties to become available for reporting.

Do not create them for every possible parameter.

Standard properties currently allow:

• 50 event-scoped custom dimensions

• 25 user-scoped custom dimensions

Use them for dimensions you expect to analyze repeatedly.

Google Analytics should not normally be the authoritative source for:

• Bank revenue

• Subscription status

• Inventory

• Taxes

• Accounting

Tracking can be affected by:

• Consent choices

• Browser restrictions

• Ad blockers

• Tag failures

• Network problems

Use the business database or payment platform as the source of truth for financial transactions.

A sophisticated dashboard built on incorrect events is still incorrect.

Common problems include:

• Duplicate tags

• Purchase events firing twice

• Forms triggering before successful submission

• Missing cross-domain tracking

• Inconsistent UTM naming

Validate data collection before making important decisions from it.

GA4 Standard user-level and event-level data retention used by certain analyses can be configured up to 14 months.

Businesses needing longer historical analysis may need:

• BigQuery exports

• Their own data warehouse

• Analytics 360

Plan this before historical data becomes unavailable.

Installing Google Analytics does not remove the website owner's responsibility for privacy and consent requirements.

Applicable requirements depend on:

• Jurisdiction

• Data collected

• Advertising features

• Consent setup

Configure tracking according to the business's legal and privacy requirements.

Yes. Standard Google Analytics 4 properties are provided without charge.

Google Analytics 360 is the premium enterprise version.

GA4 is the current generation of Google Analytics.

It uses an event-based measurement model for websites and applications.

Universal Analytics stopped processing new data for standard properties in 2023.

Start with actions tied directly to the business, such as:

• Purchases

• Leads

• Signups

• Subscriptions

Avoid creating unnecessary events before the important measurement is working.

A key event is an Analytics event marked as particularly important to the success of the business.

For example, purchase or generate_lead can be treated as key events.

Not necessarily for a simple website.

A direct Google tag or CMS integration can be enough.

Google Tag Manager becomes more useful when managing multiple tags, custom triggers, advertising pixels, or more complex event tracking.

It is useful for marketing and behavioral analysis, but it should not replace your payment processor, ecommerce database, or accounting system as the authoritative record of revenue.