GA4 Events Explained: The Complete List for Online Stores

1. What Are GA4 Events?

In GA4, an event represents an interaction or occurrence measured on a website or app. A page view, a product selection, a search, a checkout start, and a completed purchase can all be recorded as events.

Each event has a name and can include parameters that provide additional context. For example, a purchase event can contain a transaction ID, currency, total value, and an array of purchased items.

For example, when a customer adds a pair of shoes to a shopping cart, the website can send add_to_cart along with the item ID, product name, price, quantity, currency, and event value.

Correct event implementation matters because inaccurate or duplicated events can distort conversion funnels, product performance reports, and revenue analysis.

2. The Main Types of GA4 Events

GA4 events are commonly grouped into four categories. Understanding the differences helps determine which events require custom implementation and which may already be collected automatically.

3. The Complete GA4 E-Commerce Event List

The following reference covers the principal recommended e-commerce events and related interactions that an online store may want to measure. Use the search field and category filters to find an event.

Showing all events

This is a practical reference, not a claim that every event is automatically collected. Search tracking depends on the implementation. Product, cart, checkout, promotion, purchase, and refund events usually require an appropriate commerce integration or explicit configuration.

Which e-commerce events should you implement first?

If you are building analytics for a new online store, start with the events that measure the main conversion journey:

1. view_item to measure product detail views.
2. add_to_cart to measure shopping intent.
3. begin_checkout to measure checkout initiation.
4. purchase to measure completed transactions.

Then add view_item_list, select_item, view_cart, shipping and payment events, promotion events, and refund to build a more detailed view of customer behavior.

4. Other Useful GA4 Events for Online Stores

E-commerce events explain shopping activity, but general GA4 events help describe how users arrive at and interact with the website.

Event availability depends on the tag, platform, and configuration. For example, enhanced measurement can record some interactions automatically, while account creation and login usually need deliberate implementation.

5. Important GA4 E-Commerce Event Parameters

Event names describe what happened. Parameters explain the context. For e-commerce tracking, item and transaction parameters are especially important.

Use the parameter definitions in Google’s current GA4 documentation. In particular, ensure that value, item prices, taxes, shipping, discounts, and refunds are handled consistently with the store’s financial and reporting requirements.

6. How to Implement GA4 Events

Method 1: Use Google Tag Manager

Google Tag Manager lets you configure GA4 event tags, triggers, and variables without manually adding a separate tracking script for every interaction.

1. Install the GTM container on your website.
2. Configure the Google tag with the correct GA4 Measurement ID.
3. Make the store’s event data available through the data layer.
4. Create event triggers for the interactions you want to measure.
5. Configure GA4 event tags to pass the correct event parameters.
6. Test the setup in Preview mode before publishing.

Method 2: Use a platform integration

An integration or analytics plugin may automatically send some e-commerce events. Review the integration’s documentation and verify that it provides the events and parameters your store needs.

Avoid installing overlapping tracking solutions without checking whether they send the same events. Duplicate implementations can inflate counts and distort reports.

Method 3: Use a custom data layer

Developers can push event information to dataLayer when a real user interaction occurs. Google Tag Manager can then process those events and send them to GA4.

This approach offers flexibility, but requires careful implementation of product data, checkout transitions, transaction values, and duplicate-event prevention.

7. GA4 Event Code Examples for Online Stores

The following snippets demonstrate how a website can push recommended e-commerce events to the Google Tag Manager data layer. They are examples, not a complete plug-and-play tracking installation.

Example 1: Track an add-to-cart event

window.dataLayer = window.dataLayer || [];

window.dataLayer.push({
  event: "add_to_cart",
  ecommerce: {
    currency: "USD",
    value: 59.99,
    items: [
      {
        item_id: "SKU-1001",
        item_name: "Running Shoes",
        price: 59.99,
        quantity: 1
      }
    ]
  }
});

Trigger this event after the product has actually been added to the cart. Configure a corresponding GA4 event tag in GTM to send the event name and parameters.

Example 2: Track the start of checkout

window.dataLayer = window.dataLayer || [];

window.dataLayer.push({
  event: "begin_checkout",
  ecommerce: {
    currency: "USD",
    value: 119.98,
    items: [
      {
        item_id: "SKU-1001",
        item_name: "Running Shoes",
        price: 59.99,
        quantity: 2
      }
    ]
  }
});

Fire begin_checkout when the shopper starts the checkout process, not simply when a cart page is viewed.

Example 3: Track a completed purchase

window.dataLayer = window.dataLayer || [];

window.dataLayer.push({
  event: "purchase",
  ecommerce: {
    transaction_id: "ORDER-12345",
    value: 119.98,
    currency: "USD",
    shipping: 5.99,
    tax: 8.50,
    items: [
      {
        item_id: "SKU-1001",
        item_name: "Running Shoes",
        price: 59.99,
        quantity: 2
      }
    ]
  }
});

A production implementation must populate the event using real order data and Google’s recommended parameter definitions. This sample illustrates the structure and does not establish the correct revenue calculation for every business.

8. How to Test GA4 Events

Always validate event collection before using the data to make business decisions. An event can appear to fire while carrying incorrect values or missing product information.

1. Use GTM Preview: Confirm that the correct trigger and tag fire when the user performs an action.
2. Open GA4 DebugView: Inspect incoming events and their parameters during a supported debugging session.
3. Test a complete journey: View a product, add it to the cart, start checkout, and complete a test order when possible.
4. Verify transaction details: Check currency, value, item IDs, quantities, and transaction IDs.
5. Look for duplicates: Check whether plugins, direct tags, or GTM send the same event more than once.
6. Review reports: Allow time for standard reports to process data after confirming events are received.

Interactive GA4 event implementation checklist

9. Common GA4 Event Tracking Mistakes

Using custom event names unnecessarily

Replacing recommended events with custom names can make standard e-commerce reporting more difficult. Use the recommended event name when it accurately describes the interaction.

Sending incomplete item data

Events without reliable item identifiers, names, prices, or quantities may limit product-level analysis. Map the commerce platform’s product fields to the appropriate GA4 item parameters.

Firing events at the wrong time

An add_to_cart event should reflect a successful cart addition. A purchase event should reflect a confirmed transaction. Incorrect triggers can overstate customer intent or revenue.

Duplicating purchase events

Repeated confirmation-page visits, multiple tags, or duplicated integration logic can produce repeated purchase events. Review the entire tracking architecture and use reliable transaction identifiers.

Assuming all events are automatic

Installing the Google tag does not guarantee that all shopping, checkout, and transaction events are collected. Verify each required event in the actual implementation.

Ignoring consent and data quality

Consent configuration, ad blockers, browser restrictions, and implementation errors can affect the data received. Follow applicable privacy requirements and document known measurement limitations.

Conclusion: Build a Better GA4 Event Tracking Strategy

GA4 events provide the foundation for understanding how customers interact with an online store. From product discovery and shopping cart activity to checkout and completed transactions, the right events reveal where shoppers engage and where they leave the journey.

Start with the core e-commerce events, use Google’s recommended names and parameters, and validate every implementation. Expand your event coverage as your analytics requirements grow, while keeping the tracking setup accurate, privacy-conscious, and easy to maintain.

A well-implemented GA4 event strategy helps e-commerce businesses improve funnel analysis, understand product performance, measure marketing outcomes, and make better-informed decisions.