Runs in your browser. Nothing you enter is uploaded or stored.
To name GA4 events correctly, type what happens on your site in plain words into the free GA4 Event Name Generator above, such as “User clicks the WhatsApp button” or “Visitor submits the contact form”. It returns a valid event name for each line, up to 200 at once. Where Google already has a name, it uses the recommended or enhanced-measurement event (generate_lead, sign_up, file_download), and it suggests parameters for each. It also checks names you already use against GA4’s rules and reserved names, and gives you the gtag.js and Google Tag Manager code plus a tracking plan you can export.
Last updated: 6 November 2026. Written by Saad Raza.
Key takeaways
- GA4 event names can be up to 40 characters, must start with a letter, and may use only letters, numbers and underscores.
- Names are case-sensitive, so “Form_Submit” and “form_submit” become two separate events. Use lower case snake_case everywhere.
- Some names are reserved for events GA4 collects itself, such as first_visit, session_start and user_engagement. Sending them yourself causes errors or double counting.
- Use Google’s recommended event names where one fits. Reports, conversions and future features recognise them; custom names need custom dimensions to report their parameters.
Why event names matter
In GA4, everything is an event: page views, scrolls, clicks, form submissions and purchases. Names are permanent in your reports. Once data has been collected under a messy name, you cannot rename it in past data, only create a new one going forward. A small site often ends up with “whatsapp”, “WhatsApp Click”, “click_whatsapp” and “wa_button” all tracking the same action because different people set them up. A clear naming convention, written down as a tracking plan, prevents that. My guide to using Google Analytics for SEO insights explains how events turn into the reports you actually use.
How to use the GA4 Event Name Generator
- List every action you want to track, one per line, in plain language. Mention the object (WhatsApp, phone, form, PDF) and the action (click, submit, download, open).
- To audit existing names, paste them as they are, such as
Book_Appointment_Click. Lines that already look like event names are validated and corrected rather than renamed. - Run the generator and review the table: the event name, whether it is a Google recommended, enhanced-measurement or custom event, suggested parameters, and any problems.
- Copy the example gtag.js or dataLayer code and adapt it in your theme or Google Tag Manager.
- Export the tracking plan CSV and keep it as the single list everyone uses.
The rules the generator checks
| Rule | Limit or requirement |
|---|---|
| Event name length | 40 characters or fewer |
| First character | A letter |
| Allowed characters | Letters, numbers and underscores only; no spaces or hyphens |
| Case | Case-sensitive; lower case recommended |
| Reserved names | Automatically collected events such as first_visit, session_start, user_engagement, first_open and app_update |
| Reserved prefixes | _, firebase_, ga_, google_ and gtag. |
| Parameters | Names up to 40 characters, values up to 100 characters, up to 25 parameters per event |
Across the whole list, the generator also warns when two lines would produce the same name, or names that differ only by case, so you can merge them or tell them apart with a parameter.
A worked example
The example lists ten actions for a small business site. The generator matched five to Google’s recommended or enhanced-measurement events, named four custom events, and flagged one problem:
- “Visitor submits the contact form” became generate_lead, Google’s recommended lead event, with form_name, value and currency as parameters.
- “Someone downloads the price list PDF” became file_download, which GA4 sends automatically when enhanced measurement is on.
- “User signs up for the newsletter” became sign_up with method set to “newsletter”.
- “Customer adds a product to the cart” became add_to_cart, and “User plays the intro video” became video_start.
- “User clicks the WhatsApp button on a product page” became the custom event whatsapp_click; “Visitor clicks the phone number in the header” became phone_click; “Visitor opens the size guide popup” became size_guide_open; and “Book Appointment Click” became appointment_click.
- “first_visit” was flagged as a reserved name that GA4 already collects automatically.
For the first event, the tool writes gtag('event', 'whatsapp_click', { link_url: "...", link_text: "..." }); and the equivalent dataLayer.push for Tag Manager.
Setting the events up
- Turn on enhanced measurement first. It already tracks scrolls, outbound clicks, site search, video engagement, file downloads and form interactions, so do not duplicate those.
- Use Tag Manager for clicks. A click trigger on the WhatsApp or phone link sends the event without editing theme code.
- Register parameters. For custom events, create a custom dimension in GA4 for each parameter you want in reports, or the values stay hidden.
- Mark key events. Mark generate_lead, whatsapp_click or phone_click as key events (formerly conversions) so they count in acquisition reports.
- Tag campaigns consistently. Events show what people did; UTM tags show where they came from. Build those in bulk with the UTM bulk builder.
For WhatsApp click tracking in particular, the WhatsApp link generator builds the link, and my article on the wa.me link format covers pre-filled messages. To see how AI assistants send visitors, read AI referral traffic in GA4. To put a value on what the tracked leads bring in, use the SEO ROI calculator.
Limits
The generator reads descriptions with simple language rules, so it works best with short, concrete sentences in English. Always check the suggested name makes sense to your team. Recommended event matching covers the most common web events, not every industry list Google publishes (games, travel and others have their own). The reserved-name list covers GA4’s documented automatic events for web and apps. The generator does not create the events in your GA4 property; you still add the code or tags. Everything runs in your browser.
Questions about the GA4 Event Name Generator
What is the naming convention for GA4 events?
Google uses lower case snake_case, such as generate_lead and add_to_cart. Follow the same pattern for custom events, usually object then action: whatsapp_click, quote_request_submit.
Can I use spaces or hyphens in event names?
No. Only letters, numbers and underscores are allowed, and the name must start with a letter. Spaces and hyphens are replaced with underscores.
Should I use a recommended event or a custom event?
Use a recommended event whenever one fits, such as generate_lead for a lead form. Google’s reports understand it and it needs less setup. Use custom events for actions specific to your site.
How many custom events can I have?
There is no hard limit on distinct event names for web data streams, but each event can carry up to 25 parameters, and reporting custom parameters uses your custom dimension quota. Keep the list focused on actions you will act on.
Can I rename an event later?
You can modify incoming events in the GA4 admin to rename them from now on, but past data keeps the old name. Getting names right at the start saves confusion.
If you want GA4 tracking planned around your business goals, see my SEO services, or ask for a free audit. You can also browse the other free marketing and analytics tools.
Request received
Thank you! Saad will contact you within the next 24 hours.
Keep an eye on your phone and inbox.
