You can track phone calls in Google Analytics 4 in two ways: count clicks on your phone number with Google Tag Manager, or send real calls to GA4 as events from call tracking software. Method 1 is free, but it measures the click, not whether a call happened, how long it lasted or how it ended. Method 2 fires GA4 events on real calls, with the source, campaign, duration and outcome of each one. Use method 1 if you have no call tracking platform, and method 2 when you need real attribution and a clean signal for Google Ads bidding.

Before you set anything up, decide what you want to measure: taps on your phone number, or real calls with their source. The two need different setups, and this guide walks through both.

See the Google Analytics integration in Nimbata for what method 2 looks like end to end.

How GA4 treats phone calls

GA4 is event-based. A page view, a scroll, a purchase and a phone call are all events, and every event carries parameters. So tracking calls comes down to one decision: which event name you send, and which parameters you attach to it.

GA4 ignores your custom parameters in reports until you register them as custom dimensions (text values, like call outcome) or custom metrics (numbers, like call duration). This is the most common reason for “my events are firing but I don’t see the data”.

Two ways to track calls in GA4

Method 1: GA4 + Google Tag Manager Method 2: Call tracking software
What you measure Clicks on tel: links, mostly taps on mobile Real inbound calls, with duration, outcome and attribution
Captures desktop calls No. Desktop visitors usually dial the number by hand Yes. The call itself is the event
Captures call outcome No. GTM doesn’t know if the call connected or led to a sale Yes: connected, qualified, converted, missed, voicemail
Attribution Page and UTMs from the URL. GCLID only if Google Ads auto-tagging is on and the visitor consented to ad_storage The same, plus a GCLID kept for the whole visit and the call outcome tied to the same visitor
Cost Free Subscription (Nimbata, CallRail, CTM, etc.)
Setup time 30 to 60 minutes 10 minutes: paste two credentials, place a test call
Signal for Smart Bidding Weak. A click on the phone link is a noisy proxy Strong. You can fire the bidding event only on qualified calls

Many setups use both: method 1 as a tap-intent signal, method 2 as the source of truth for conversions.

Method 1: Track clicks on your phone number with Google Tag Manager

This method uses only Google’s tools: GA4 and Google Tag Manager. GTM sends a GA4 event each time someone clicks a tel: link on your site.

Phase 1: Inside Google Tag Manager

Step 1: Create a click trigger for tel: links.

GTM → Triggers → New → Trigger type: Just Links. Configure:

  • This trigger fires on: Some Link Clicks
  • Fire on: Click URL starts with tel:

Save it with an obvious name, like “Click - tel link”.

Step 2: Create a GA4 Event tag.

GTM → Tags → New → Google Analytics: GA4 Event. Configure:

  • Measurement ID: your G-XXXXXXXXXX
  • Event name: phone_link_click
  • Parameters: one row each in the Event Parameters table, as below
  • Trigger: the click trigger from step 1
Parameter Value
phone_number {{Click URL}}
page_location {{Page URL}}
page_title {{Page Title}}
device_category {{Device Category}}

Device Category requires a Built-In variable. Enable it under Variables → Built-In Variables → Device Category in GTM.

Step 3: Keep the GCLID and UTMs across pages.

Google Ads auto-tagging puts the GCLID in the URL the visitor lands on, and UTMs cover other sources. By the time the visitor clicks the phone number on another page, those parameters are gone from the URL, and the event lands as (direct)/(none) in GA4.

To fix it, add a small DataLayer push on page load that reads ?gclid, ?gbraid, ?wbraid and ?utm_* from the landing URL and stores them in a cookie. Then create GTM User-Defined Variables that read those cookies, and add them to the parameter list of the tag from step 2. Without this step, method 1 tells you little about paid traffic.

Phase 2: Inside GA4

Step 4: Register the parameters.

Register phone_number, page_location, device_category and your GCLID and UTM parameters as event-scoped custom dimensions in GA4 Admin → Custom Definitions.

Step 5: Mark the event as a key event.

Admin → Events → toggle phone_link_click. The event then appears in conversion reports next to your form fills. GA4 renamed conversions to “key events” in early 2024, and the mechanic is the same.

What method 1 counts: clicks, not calls

Put plainly, phone_link_click counts clicks on the number. It does not count phone calls. GTM sees the click and nothing after it.

What click tracking misses:

  • Desktop callers who type the number by hand.
  • Callers who tap a Google Business Profile listing or a Google Ads call extension.
  • Whether the click became a connected call, a wrong number, a hangup, a voicemail or a 20-minute qualified conversation.
  • Different outcomes. Every click is the same event.

So treat this key event as a sign of intent in your GA4 reports. Do not use it as the bidding conversion in Google Ads: Smart Bidding would optimize toward more tel: clicks, not more revenue calls. When call quality starts to drive budget decisions, add method 2.

Method 2: Send real calls to GA4 with call tracking software

Call tracking software measures the actual call: who called, from where, when, for how long, and what happened.

It works with a unique tracking phone number swapped in by Dynamic Number Insertion (DNI). The visitor sees a number tied to their session and calls it. The platform ties the call back to the visit, the campaign and the original ad click, then sends the call to GA4 as an event through the Measurement Protocol.

The steps below use Nimbata. Phase 1 usually takes under 5 minutes. Phase 2 is where setups go wrong, so do it carefully.

Phase 1: Inside Nimbata

The integration is configured at the project level, so make sure you are in the right project first.

Step 1: Get your GA4 credentials.

In GA4, go to Admin → Data collection and modification → Data Streams → [your web stream] → Web Stream Details. You need two values from this page:

  • Measurement ID (format: G-XXXXXXXXXX), listed under Stream Details.
  • Measurement Protocol API secret, under Events → Measurement Protocol API secrets. Generate one if you don’t have it yet. Treat it as a credential: it has write access to your property.

Step 2: Connect Nimbata to GA4.

In Nimbata: Integrations → Google Analytics. Paste the Measurement ID and API secret. Save.

Step 3: Select the call events to send.

Nimbata can send several call events to GA4 from the same integration, each with its own name and parameters. Click on the tab and configure each event:

Google Analytics 4 (GA4) Call Events Configuration

  • Event name: a distinct name per row, so data does not overlap in GA4.
  • Event parameters: optionally attach extra parameters to each event (Start Time, Campaign, Recording Link, Call Outcome, Tracking Number and so on) by selecting them and assigning a name. They must be registered in phase 2 before they show in reports.

A single call_completed event treats a missed call, a hangup and a sale as the same thing. Most production setups send 3 or 4 events instead:

One call can fire several of these. They count as separate events in GA4, which is what you want: sales and marketing can each report on the event that matters to them.

Then create a simple workflow to set the firing condition for each event:

GA4 Call Tracking - Firing Conditions

  • Trigger condition: which calls fire this event. All Calls, Answered Calls, First-time Callers, calls that meet a duration threshold, or custom criteria configured in Nimbata workflows.

Step 4: Activate the integration.

Once credentials are saved and events are configured, Nimbata prompts you to create a workflow. Click Create new workflow and Nimbata sets up the automation for you. No GTM, no Zapier, no manual scripting.

Return to the Google Analytics integration page. You should see:

This integration is running in 1 workflow: Google Analytics (running)

Phase 1 is done. Place a test call now and it will arrive in GA4.

Phase 2: Inside GA4

Step 5: Verify in DebugView.

GA4 → Admin → DebugView. Place a test call. Within minutes you should see the call events you configured in step 3, with their parameters filled in.

If a parameter is empty in DebugView, it will be empty in your reports. Fix it before moving on, either in the Nimbata event configuration or by checking that Nimbata captures the parameter in the first place.

Step 6: Register parameters as custom dimensions and metrics.

Until you register a parameter, GA4 won’t show it anywhere: not in reports, Explorations, audiences or Looker Studio. Admin → Custom definitions → Custom dimensions / Custom metrics → Create. For each parameter you will filter or aggregate on:

  • Dimensions (text): tracking number name, call outcome, call disposition, source channel, brand name, campaign, GCLID, country.
  • Metrics (numeric): call duration, talk duration, call value, engagement_time_msec.
  • Scope: Event for almost everything. User scope only for per-visitor properties like “is repeat caller”.

GA4 limits standard properties to 50 event-scoped dimensions and 50 metrics, so register what you will use, not every parameter Nimbata sends.

Step 7: Mark your events as key events.

Admin → Events → toggle the events you want counted as conversions. Typically that is call_qualified, and optionally call_converted. Leave call_completed and call_missed unmarked: they are useful to look at, but they are not conversions.

Once marked, the event appears in conversion reports, can be imported into Google Ads as a conversion action, and shows as a conversion metric in Looker Studio.

Send only real leads to GA4

In Nimbata, integration triggers decide which calls are sent to each integration. You can filter by tag (only calls tagged “sale”), call duration (only calls longer than 90 seconds), value, or first-time callers, among others.

Session-level attribution also depends on a pool of tracking numbers large enough for your traffic. If the pool is too small, two visitors get the same number and one visitor’s data is credited to the other. To size it, divide your peak hourly visitors by the sessions that fit in an hour (60 divided by the average session duration in minutes), then multiply by 1.3. See how to calculate the size of your call tracking number pool.

Use the call event in Google Ads

GA4 is your reporting layer, and bidding happens in Google Ads. To import the key event: Tools → Conversions → New conversion action → Import → Google Analytics 4 properties, then pick your call event (typically call_qualified). You can also send call conversions straight from Nimbata with Nimbata’s Google Ads integration, as explained in GCLID tracking for Google Ads.

If the data does not show up

Four things to check first:

  • No test call. GA4 won’t list an event for key event marking, custom dimensions or audiences until it has received it at least once.
  • Wrong Measurement ID or API secret. The Measurement Protocol does not report an error on a malformed request, so the event vanishes silently. Verify in DebugView.
  • Parameters not registered. The events fire, but GA4 does not show the parameters anywhere.
  • Event not marked as a key event. Without the toggle, the event is missing from conversion reports and can’t be imported to Google Ads.

Prefer a video walk-through? This tutorial shows how to set everything up and where to find your credentials.

FAQ: Google Analytics 4 call tracking

How long does it take for GA4 to show events?

Events in GA4 typically show up after a couple of minutes but may take up to 36 hours to show.

How do you track phone calls in GA4?

Two methods. Native (GA4 + Google Tag Manager): fire a GA4 event when someone clicks a tel: link on your site. Free, but it only measures clicks, not actual calls. With call tracking software: the platform measures real answered calls and fires GA4 events with full attribution and call outcome. Most professional setups use method 2 for real attribution and Smart Bidding optimization.

Can I track calls in GA4 without using a call tracking platform?

Yes, with method 1 in this guide. GTM fires a GA4 event on every click of a tel: link. You’ll see how many people tapped the phone number, broken down by source. You won’t see whether the call actually happened, how long it lasted, or how it ended.

What's the difference between phone_link_click and call_completed?

phone_link_click is fired when someone taps the phone number on your website. It is a click event. call_completed (or whatever name your call tracking platform uses) is fired after a real inbound phone call to your tracking number, with the actual call data attached. The click is intent; the call is the conversion.

Where can I see the source / medium of each call?

Click on Engagement - Conversions and locate the call conversion. Click on the conversion and set source or medium as the filter in the column.

I run Google Ads. Where can I see the campaign that generated each call?

Click on Engagement - Conversions and locate the call conversion. Click on the conversion and set campaign as the filter in the column.

Why do my call events come in as "direct" or "not set"?

GA4 is built on events, not sessions. Even though Nimbata sends the GA client ID, session ID, source, medium and campaign, Google may not match these in some cases. We recommend creating custom definitions, as shown in step 6 of method 2.

Can I attach a value to each call?

Yes. Create a custom metric first so Nimbata can pass the value along with the event. Step 6 of method 2 shows how.

What data does Nimbata send to GA4?

Always sent by default: client_id, page_location, source, medium, campaign, gclid, dclid, device, country, ua, session_id and engagement_time_msec. You can also send: Unique Call ID, Start Time, Tracking Number, Tracking Number Friendly Name, Destination Number, Destination Number Friendly Name, Configured Tracking Source, Call Duration, Talk Duration, Call Outcome, Call Disposition, Call Frequency, Brand Name, Digits Pressed by Caller, Digits Pressed by Destination, Tags, Value, Trigger Name, and any custom property you create in Nimbata.

What are custom definitions and why do I need them?

To view call information in GA4 you need to set up custom dimensions, custom metrics or both. When you create one, GA4 fills it with the value it collects from the matching event parameter or user property. For example, without a custom dimension for your Tracking Number Name event parameter, you won’t see the tracking number name in GA4 reports or be able to use it in audiences.

Takeaway: send real calls to GA4, not clicks

GA4 and Google Tag Manager on their own track clicks on tel: links. That is a useful, free signal, especially on mobile-heavy sites, but it is a click, not a call.

Call tracking software sends the real call to GA4, with its source, its outcome and an event you can hand to Google Ads. Start with method 1 if you are not ready for software, and add method 2 when call quality starts to drive budget decisions. To see which sources bring qualified calls, connect Nimbata to Google Analytics 4.