Set up GA4 event tags in Google Tag Manager

#01When you need a GA4 Event tag

Enhanced measurement and the Google tag already collect page_view and optionally scrolls, outbound clicks, site search, video, file downloads and form interactions. You still need Event tags when:

• The business event is not covered (demo lead, pricing plan selected, chatbot qualified).
• You need ecommerce recommended events (lesson 14).
• You need parameters enhanced measurement does not send.
• Form interaction auto-events are noisy or incomplete for your SPA forms.

According to Google Tag Manager Help on setting up Analytics events, you create a GA4 Event tag, set the event name, optionally add parameters, and attach a trigger.

#02Build a generate_lead tag

Assume the site pushes generate_lead with lead_type and form_id.

1. Create Data Layer Variables dlv - lead_type and dlv - form_id (lesson 5).
2. Tags → New → Google Analytics: GA4 Event.
3. Measurement ID: your Constant, or select the configuration / Google tag your container uses (UI wording varies; follow the fields shown).
4. Event Name: generate_lead.
5. Event Parameters:

- lead_type = {{dlv - lead_type}} - form_id = {{dlv - form_id}}

1. Trigger: Custom Event generate_lead.
2. Name: GA4 Event - generate_lead.
3. Preview → submit a test lead → confirm the tag fired once on the generate_lead event.
4. In GA4 Admin → DebugView, confirm the event and parameters.
5. Publish with a clear version name.

#03Recommended vs custom event names

Prefer Google’s recommended names when the meaning matches: generate_lead, sign_up, login, search, select_content, and the ecommerce set. Recommended names unlock clearer reporting and integrations.

Custom names are fine when nothing fits (webinar_register, calculator_complete). Stay consistent and document them in the event dictionary.

Caveats. Renaming an event in GTM creates a new event in GA4; history does not merge. Mark the old event’s key-event status off after cutover.

#04Event Settings variables

If many GA4 Event tags share parameters (for example page_path, content_group, env), create a Google Tag: Event Settings variable with those pairs and reuse it. Less copy-paste, fewer mismatches.

#05Parameters and custom dimensions

Sending a parameter is not the same as seeing it in standard reports. In GA4, register event-scoped custom dimensions for parameters you need in Explorations and audiences. See GA4 custom dimensions and DebugView.

High-cardinality parameters (transaction IDs, timestamps) may be poor dimension choices; keep them for BigQuery export instead (GA4 BigQuery export).

#06Tag firing options

On the GA4 Event tag, open advanced settings when needed:

• Tag firing priority if order matters relative to other tags.
• Only fire tag in published containers during risky tests (use carefully).
• Consent requirements once Consent Mode is configured (lesson 12).

Avoid stacking conflicting Once per page / Once per event settings until you understand duplicates in Preview.

#07SPA and duplicate page_view

If you manually send page_view on History Change while automatic history page views are also on, you will double-count. Pick one approach. Document it in the container notes.

#08Worked example: Ledgerline generate_lead

Ledgerline is a fictional accounts-payable software company. Details are illustrative.

Ledgerline’s first GA4 Event tag used Event Name GenerateLead (PascalCase). DebugView showed it, but a teammate building an exploration filtered for generate_lead and saw nothing. They republished with the recommended snake_case name and updated the Ads import mapping the same day.

They also sent lead_type but forgot to register a custom dimension; weekly Looker dashboards could not break out demo vs webinar for two weeks. Registration fixed reporting going forward (historical UI breakdowns still limited).

Walkthrough

1. Confirm generate_lead appears in Preview Data Layer.
2. Build the GA4 Event tag as above.
3. Fire three successful tests and zero failed validation submits; tag should fire three times, not on failures.
4. Open GA4 DebugView on the same browser / debug device.
5. Register lead_type as an event-scoped custom dimension if you need it.
6. Compare event count to CRM creates for a day on staging.

#09Troubleshooting

#10Parameter design guidelines

Send parameters that change decisions:

• lead_type, plan, locale, template_id — useful.
• Entire form field dumps — harmful.
• Random timestamps as event params — usually noise.
• Page titles copied into every event — redundant with page_view.

Cardinality matters for custom dimensions. If a parameter can have tens of thousands of values (article IDs at news scale), prefer BigQuery over UI dimensions.

#11Reusing triggers across vendors

The same Custom Event generate_lead should fire GA4, Ads (if native), and Meta Lead tags. Do not create three different click triggers that almost match. One signal, many destinations — that is the point of GTM.

#12Validation against CRM

For a week after launch, compare daily generate_lead counts to CRM opportunities created by the web form. Investigate gaps over ~15% (directionally; consent and adblockers explain some loss). GTM cannot fix CRM routing bugs, but it can reveal them early.

#13Event naming anti-patterns

Avoid: Event1, click, button, conversion, goal, camelCase mixed with snake_case, spaces, and names over ~40 characters without reason. Prefer specific verbs: generate_lead, download_whitepaper, start_trial.

#14Debugging parameters that look "missing" in reports

If DebugView shows a parameter but standard reports do not, you likely did not register a custom dimension, or you are looking at a report that cannot break down by that scope. Free-form Explorations after registration are the usual fix (custom dimensions lesson).

#15Coordination with content and CRO

When CRO tools change button IDs weekly, click triggers rot. Give CRO a rule: primary conversion remains a data layer event; they may add extra cta_click probes but must not redefine generate_lead. Put that rule in the experimentation playbook.

#16Parameter registration workflow

After you ship a new event with custom parameters:

1. Confirm DebugView shows the parameters on a real hit.
2. In GA4 Admin, create custom dimensions (event-scoped) for each parameter you need in reports.
3. Wait for the dimension to become available (can take hours; do not panic at minute 10).
4. Build an Exploration that breaks down the event by the new dimension.
5. Document the dimension name next to the dictionary row so analysts stop inventing synonyms.

Without registration, parameters exist on the hit but stay invisible in most UI reports — a classic "GTM works, reports look empty" false alarm (custom dimensions lesson).

#17Volume and sampling awareness

High-traffic sites can flood GA4 with vanity click events. Keep interaction events purposeful. If you must measure every nav click for a redesign week, time-box the tags and pause them after the study. Permanent high-cardinality click spam makes Explorations slow and expensive for teams on BigQuery export too.

#18Try it yourself

Ship one GA4 Event tag for your primary lead event end-to-end: dictionary → push → tag → DebugView → custom dimension. Write the version description like a release note.

#19Quick quiz

1. Does creating a GA4 Event tag automatically make a key event?

Answer: No. Marking key events happens in GA4 Admin (lesson 8).

2. Why use recommended event names?

Answer: Better alignment with GA4 features, docs and import paths; consistent naming across teams.

3. Where should you QA first?

Answer: GTM Preview and GA4 DebugView, not the standard reports waiting room.

#20What should you check before the next lesson?

• At least one custom GA4 Event tag live or ready.
• DebugView proof saved.
• Parameters you need are registered or consciously deferred.

Previous: The data layer for marketers. Next: GA4 key events and Ads import. Or return to the GTM for Marketers track. Related: GA4 events and enhanced measurement, GA4 key events setup.

#21Common questions

Separate tag per event? Usually yes; reuse Event Settings for shared params.

Event name rules? snake_case, prefer recommended names, case-sensitive.

Where do events show first? DebugView and Realtime.