What is an event or key event in GA4, and what should I track?

Business Tech & Tools

What is an event or key event in GA4, and what should I track?

The short answer

In Google Analytics 4, an event is a measured interaction, such as viewing a page, clicking a link, submitting a form, or completing a purchase. A key event is an event you mark as especially important to the business.

Track actions that answer a decision you genuinely need to make. For a small service business, that may be a successful inquiry, booked consultation, and purchase. Do not turn every scroll and button click into a key event. If everything is important, the report cannot tell you what success means.

Begin with the customer commitment

Write the clearest action that moves the business forward. It should represent something the visitor actually completed, not merely started.

Business Strong key-event candidate Useful supporting event
Consultant Confirmed consultation booking Viewed service or booking page
Local service Successfully submitted qualified estimate request Clicked phone or directions link
Ecommerce shop Completed purchase with transaction data Added item to cart or began checkout
Membership Completed paid sign-up Viewed plans or started registration
Newsletter-led business Confirmed subscription Viewed sign-up form
Digital product Completed purchase or activated access Viewed sales page or checkout

Google defines a key event as an event that measures an action important to business success. Once marked, it can appear in reports used to evaluate performance across channels.

Choose one primary key event per main customer journey, then add only the supporting events needed to diagnose where people stop. A five-step funnel is often more useful than fifty unrelated clicks.

Use the right event before inventing a new one

GA4 collects some events automatically and can measure certain interactions through Enhanced Measurement. Google's event setup guide explains that events measure interactions such as page loads, link clicks, and purchases. Google also publishes names and parameters for recommended events, including lead and ecommerce actions.

Use an established event name when it accurately describes the action. That makes reports and integrations easier to understand. Create a custom event only when an automatic or recommended event does not fit.

Event names should describe what happened, not where the current button happens to sit. generate_lead can survive a design change. blue_button_click becomes nonsense when the designer turns the button green.

Write a measurement card for each important action

Before anyone changes a tag, complete this small card:

  • Business question: Which source produces completed consultations?
  • Event: The existing or proposed event name.
  • Exact trigger: Confirmation page loads after a valid booking, not when the booking button is clicked.
  • Useful parameters: Service type, location, or non-sensitive form type.
  • Key event: Yes or no.
  • Owner: Who checks that it still works.
  • Test: The steps and expected result for one test completion.

The trigger is where many reports go wrong. A button click does not prove a form was accepted. A checkout start is not revenue. A thank-you page that can be refreshed may count more than once. Choose the latest reliable success signal your system can provide.

Keep personal information out of events

Do not send a person's name, email address, phone number, full address, password, payment details, medical information, or other sensitive data in event names, page URLs, or parameters. Inspect confirmation-page URLs too. A form can accidentally place an email address in the URL and pass it to measurement tools.

Analytics and consent obligations vary by jurisdiction, audience, data use, and industry. Configure your privacy and consent process for the laws that apply to you, and obtain qualified local guidance when the answer is not clear.

Test the entire action, not only the tag

Complete one controlled test from the landing page through confirmation. Use Tag Assistant or DebugView to see whether the event fires once with the correct name and safe parameters. Then confirm that it appears in Realtime and later in the appropriate standard report.

Test failure cases as well. Submit an incomplete form or abandon checkout and make sure the success event does not fire. Try a repeat page refresh. Verify that a test purchase uses the platform's supported test mode and cannot create a real fulfillment or accounting problem.

Record the test date, event owner, trigger, and expected count. Recheck after form, theme, checkout, consent, or tag changes.

Read the event with a business denominator

“We recorded 40 leads” is incomplete. Compare the result with qualified visits, source, cost, and later sales.

If 400 qualified sessions produce 20 valid inquiries, the session-to-inquiry rate is 5 percent. If only two become customers, investigate qualification and sales follow-up before celebrating more form submissions. The key event makes a useful milestone visible. It does not replace judgment or revenue records.

Start with a small measurement plan you trust. Three accurate events are far more helpful than a sparkling dashboard built on double counts and hopeful button clicks.

Sources and further reading

A free next step

You don't have to build this alone

Bring your questions, share what you're working on, and meet other women building businesses from home. It is free to join.

Join Our Community Free

Related Questions

← All questions