Your site gets visitors, but which actions actually matter? Page views alone do not tell you whether people sign up, contact you, download a guide or click an affiliate link. Google Analytics 4 (GA4) records every interaction as an event, and you can mark the important ones as key events, the conversions you care about. This guide shows you how to set up custom event tracking step by step, whether you have a developer or not.
How GA4 Thinks About Data
Unlike older versions of Google Analytics, GA4 is built entirely on events. A page view is an event. A click, a scroll, a file download and a form submission are events too. Some events are collected automatically, some come from enhanced measurement, and some you create yourself.
Google renamed "conversions" to key events in 2024. A key event is simply an event that you flag as important to your business.
Step 1: Decide What Counts as a Win
Before you touch any settings, list the actions that create value for your business. Examples:
- Contact form submitted.
- Newsletter signup.
- Phone number or email link clicked.
- Affiliate or outbound link clicked.
- File or guide downloaded.
- Purchase or booking completed.
Choose a handful. Tracking everything creates noise.
Step 2: Check What GA4 Already Collects
Open your GA4 property and go to Admin, then Data Streams, and select your web stream. Make sure Enhanced measurement is on. It automatically records page views, scrolls, outbound clicks, site search, video engagement and file downloads. Many goals can be tracked without writing any code.
Step 3: Choose How to Create Custom Events
You have three practical routes.
Option A: Create events inside GA4
In Admin, go to Events and choose Create event. You can build a new event from an existing one by setting conditions. For example, if a thank-you page loads after a form submission, create an event named `generate_lead` when the page path contains `/thank-you`. This needs no code.
Option B: Use Google Tag Manager
Google Tag Manager lets you trigger events from clicks, form submissions and other interactions without editing your site every time.
- Create a GA4 Event tag in Tag Manager.
- Name the event, such as `newsletter_signup`.
- Set a trigger, such as a click on a specific button, or a form submission.
- Add parameters if useful, such as the button text or the page URL.
- Test in preview mode, then publish.
Option C: Add code with gtag
If you can edit your site's code, you can send an event directly:
`gtag('event', 'newsletter_signup', { method: 'footer_form' });`
Use this for precise tracking, and ask a developer if you are unsure.
Step 4: Name Events Clearly
Use lowercase letters and underscores, and be consistent. Google recommends using its suggested event names where they fit, such as `generate_lead`, `sign_up` and `purchase`, because they unlock built-in reports. Avoid personal information in event names or parameters, such as email addresses, to stay compliant with privacy rules and Google's policies.
Step 5: Test Before You Trust the Data
Use DebugView in GA4 to watch events arrive as you perform actions on your site. Combine it with Tag Manager's preview mode. Confirm that:
- Each action fires the event once, not twice.
- The event name and parameters are correct.
- The event shows up in the Realtime report.
Step 6: Mark Key Events
After events have appeared in your property, go to Admin, then Events, and toggle the star to mark an event as a key event. Choose only events that represent real business value, such as leads and purchases. Give GA4 up to a day to start showing the data in reports.
Step 7: Register Custom Parameters if Needed
If you send extra details, such as the form name, register them as custom dimensions under Admin so they appear in reports. Plan these carefully, because there are limits on how many you can register.
Step 8: Build Useful Reports
Check Reports, then Engagement, then Events to see counts. Use Explore to build funnels, such as visitors to pricing to contact form. Compare key events by traffic source to see which channels bring real results, not just clicks.
Common Problems and Fixes
- Events fire twice: check whether both a Tag Manager tag and a hard-coded tag exist.
- No data in reports: wait a day, and confirm that the stream's measurement ID matches your tag.
- Spam or internal traffic: filter your own visits using internal traffic rules.
- Consent rules: in regions with strict privacy laws, set up consent mode and a cookie banner before collecting data.
Action Checklist
- List the three to five actions that matter most.
- Confirm that Enhanced measurement is on.
- Create each event in GA4 or Tag Manager.
- Use clear, lowercase event names.
- Test every event in DebugView.
- Mark the right events as key events.
- Register any custom parameters you need.
- Set up consent and privacy settings.
- Review key events by source every month.
Prices and features were checked in October 2026 and can change. Confirm current details on each provider's website before you buy.
