GA4 Key Events: The Exact Setup for Call, Form, and Chat Tracking

GA4 Key Events: The Exact Setup for Call, Form, and Chat Tracking

A configuration walkthrough for GA4 key events on a service business site — tagging call taps, form submits, and chat starts, then verifying in DebugView.

TL;DR: GA4 collects a lot by default and almost none of it tells you whether your website produced a lead. Three events do: call taps, form submissions, and chat starts. This is the configuration walkthrough — what to tag, how to mark it as a key event, and how to verify it’s actually firing before you trust a single report. For what the numbers mean once they’re flowing, see our guide to navigating Google Analytics.

Table of Contents

  • Events versus key events
  • The three events that matter
  • Tagging call taps
  • Tagging form submissions
  • Tagging chat starts
  • Marking them as key events
  • Verifying in DebugView
  • Building the one report you’ll use

Events Versus Key Events

GA4 renamed “conversions” to “key events” in 2024, and the distinction trips people up.

An event is anything GA4 records — page views, scrolls, clicks, file downloads. Dozens fire automatically and most are noise for a service business.

A key event is an event you’ve flagged as meaningful. Marking one is a single toggle, and it’s what promotes the event into the reports people actually look at.

The practical consequence: you can have call tracking firing perfectly and still see nothing useful, because the event was never marked as a key event. That’s the most common gap we find in contractor GA4 setups — the data is being collected and nobody surfaced it.

Want more customers from Google & AI search?

Get a free SEO audit of your site — see exactly what to fix first.

Get My Free Audit Book a Call

The Three Events That Matter

For a home service business, these three answer the only question that matters:

  1. call_tap — someone tapped your phone number
  2. form_submit — someone submitted a quote request
  3. chat_start — someone opened a chat conversation, if you run one

Everything else is supporting detail. If you configure nothing but these three, segmented by page, you’ll know more than most businesses know about their own websites.

Tagging Call Taps

A tap on a tel: link. Two approaches depending on your setup.

With Google Tag Manager (preferred):

  1. Enable the built-in Click trigger variables (Click URL in particular)
  2. Create a trigger: Click — Just Links, fire when Click URL contains tel:
  3. Create a GA4 Event tag using that trigger, event name call_tap
  4. Add parameters: page_location and link_url so you can segment by page and by which number was tapped
  5. Publish

Without GTM, a small script sends the event on any tel: click:

javascript
document.addEventListener('click', function (e) {
var a = e.target.closest('a[href^="tel:"]');
if (a && typeof gtag === 'function') {
gtag('event', 'call_tap', {
link_url: a.getAttribute('href'),
page_location: window.location.href
});
}
});

Prerequisite either way: your phone numbers must be real tel: links. If the number is plain text or an image, there’s nothing to track — fix that first.

Tagging Form Submissions

Forms are messier because plugins behave differently. Three approaches in order of reliability:

Thank-you page (most reliable). If submitting redirects to a confirmation URL, trigger on that page view. Simple and hard to break. If your form doesn’t redirect, consider making it — the confirmation page is good for users anyway.

Plugin-native events. Gravity Forms, WPForms, Contact Form 7, Elementor Forms and others push a JavaScript event or support a GTM integration. Check your plugin’s documentation for the exact event name; this is cleaner than DOM guessing.

GTM Form Submission trigger. Works, but unreliably with page builders that submit via AJAX. Test carefully rather than assuming.

Whichever you use, send form_submit with a parameter identifying which form — you want to distinguish your water damage page form from the general contact form.

Then verify the email actually arrives. Analytics tracking a submission tells you the JavaScript fired, not that the lead reached your inbox. Those are different failures and both happen. Submit a real test and confirm both.

Tagging Chat Starts

If you run chat, most vendors expose a JavaScript event or a GTM integration for conversation start. Fire chat_start on the visitor’s first message, not on the widget loading — widget loads are worthless as a metric.

Skip this section entirely if you don’t run chat. Don’t configure events for things you don’t have.

Marking Them as Key Events

In GA4: Admin → Data display → Events. Find each event and toggle Mark as key event.

Two notes:

  • The event has to have fired at least once before it appears in the list. Trigger each one yourself first.
  • Marking a key event isn’t retroactive in every report, so do this at setup rather than months later.

Resist marking things like scroll or page_view as key events. It inflates your numbers and destroys the usefulness of the metric — if everything is a conversion, nothing is.

Verifying in DebugView

Never trust a configuration you haven’t watched fire. This is the step people skip and it’s why so many GA4 setups quietly report nothing.

  1. Open Admin → DebugView in GA4
  2. Enable debug mode — either GTM Preview mode, or the Google Analytics Debugger browser extension
  3. On your own site, do all three actions: tap the phone number, submit the form, start a chat
  4. Watch the events appear in DebugView in real time
  5. Click each one and confirm the parameters are populated — especially page location

If an event doesn’t appear, the tag or trigger is wrong. Fix it now, because a report built on a broken tag looks exactly like a report showing genuine zero.

Re-verify after any theme update, plugin update, or site redesign. Tracking breaks silently and the symptom is a slow unexplained decline in reported conversions.

Building the One Report You’ll Use

Once the three events fire, build a single exploration you’ll actually open:

  • Rows: Landing page
  • Values: Sessions, call_tap, form_submit, key events total
  • Filter: Organic search traffic
  • Date range: Last 90 days

That table tells you which pages produce leads, which get traffic but produce nothing, and where to spend your next content dollar. A service page with meaningful sessions and zero call taps has a conversion problem, not a traffic problem — and you can’t see that without this configuration.

One caution on interpretation: taps aren’t calls. Some taps get cancelled. Reconcile against your call tracking data to learn your own ratio, then treat taps as a reliable leading indicator.

Quick Recap

  • Events are collected; key events are surfaced. Marking the toggle is what makes them visible.
  • Configure three: call_tap, form_submit, chat_start.
  • Call taps require real tel: links — fix those before tagging anything.
  • Thank-you page triggers are the most reliable form tracking; plugin-native events are second.
  • Verify every event in DebugView before trusting a report, and re-verify after updates.
  • Build one exploration: landing page against sessions and key events, filtered to organic.

Frequently Asked Questions

Do I need Google Tag Manager?
No, but it makes this substantially easier and keeps tracking changes out of your theme files. For a site you’ll be editing over years, GTM is worth the setup.

Why do my GA4 numbers not match my call tracking?
They measure different things. GA4 counts taps on a link; call tracking counts connected calls. Expect a gap and learn your own ratio rather than trying to reconcile them exactly.

Should I import GA4 key events into Google Ads?
Yes, if you run paid search — that’s how smart bidding learns what a good outcome looks like. Import the lead events, not page views.

How long until data appears in standard reports?
DebugView is real time. Standard reports typically take 24–48 hours. Don’t panic on day one.

What if I inherited a GA4 property and don’t know what’s configured?
Open Admin → Events and look at what’s marked as a key event. If nothing is, or if page_view is, that’s your starting point.

Want more customers from Google & AI search?

Get a free SEO audit of your site — see exactly what to fix first.

Get My Free Audit Book a Call

Up next

SEO Analytics and Reporting Research Report: Measuring Success That Actually Drives Business Results

27 min read · This comprehensive research reveals that 91% of organizations report SEO positively impacts website performance, yet the traditional metrics we've relied on for decades are…

Want this done for you?

Scan your site. See the gaps. Decide with numbers.

  • Rankings, Google Business Profile and site-speed teardown
  • Report lands in your inbox in about a minute
  • No obligation · 4.9 from 67 Google reviews

Prefer a human? Book 20 minutes with Jeremy

Continue reading

Share this post

GA4 Key Events: The Exact Setup for Call, Form, and Chat Tracking