Skip to content

Guide 180 · Conversions · GA4 + Tag Manager

Key event for a phone-number click in GA4: the tel link, the click event, and the rate

Checked 11 November 2026 · Verification: key-event reference validated structurally (9 checks, all passed) · Steps traced to Analytics Help, read 11 November 2026 · 5-minute read

A tap on the phone number is the closest a website gets to a phone call, and it deserves a key event. The event is a click event on a tel: link, sent with a name the business recognizes, and marked in GA4. This guide builds it, checks it in DebugView, and works out the session key event rate for a week of taps.

Expected signal

After the steps, the phone_click key event appears under the Key events tab in Admin, and the standard reports show it within a day. The worked example below gives the count and the rate to expect.

Download the reference: the phone_click key-event reference (JSON) (673 bytes, MD5 559d92d28c1cbfb77f2277de36dd50e9). It holds the event name, the counting method, the worked-example figures recomputed for this guide, and the checkpoints that prove the key event is recording. The figures in the file are the same figures shown on this page.

What you need

  • Editor access or above at property level in GA4. Marking an event as a key event is a property setting, and the star in the Events table does not appear for a Viewer.
  • A phone number on the site as a link with a tel: address, such as tel:+16045550134. A number printed as plain text cannot be clicked and cannot fire an event.
  • Editor access in Tag Manager, to build the click trigger and the GA4 event tag, and Editor access or above in GA4, to mark the event.

The trace

  1. Check the number is a tel: link. The link must start with tel: followed by the number. A link that starts with https: or a span styled to look like a link will not match a tel: trigger, and no event will fire.
  2. Build the trigger in Tag Manager. In the workspace, go to Triggers, then New, and choose Click — All Elements. Set it to fire on Some Clicks, where Click URL starts with tel:. Name it Click — Phone link.
  3. Add a GA4 Event tag named phone_click. Go to Tags, then New, and choose the GA4 Event tag type. Set the Measurement ID to the property's ID and the Event Name to phone_click. Attach the phone-link trigger and save the tag.
  4. Check it in Preview, then publish. Click Preview, connect the site, and tap the phone number. The tag must appear under Tags Fired on the click event. Then click Submit, choose Publish and Create Version, and publish, because Preview alone reaches nobody.
  5. Confirm it in DebugView, then mark it in GA4. Open DebugView, tap the number, and watch phone_click arrive. Then open Admin, then Data display, then Events, and click the star on the phone_click row.
  6. Work out the session key event rate. In the worked example the week shows 1,900 sessions and 58 sessions with a phone_click key event, which is 58 / 1,900 = 3.05%. The 63 phone_click events came from 58 sessions, so 5 sessions tapped the number more than once.

Dead ends

DEAD END — A NUMBER THAT IS NOT A LINK. Plain text with a phone icon beside it looks clickable and is not. No link means no click event, no matter how the trigger is built. The fix is in the page, not in Tag Manager.

DEAD END — READING A TAP AS A COMPLETED CALL. A tap opens the phone app; it does not prove the call connected, lasted, or booked anything. Report it as interest, and never present the tap count as the call count.

DEAD END — A CLICK — JUST LINKS TRIGGER ON A BUTTON. If the phone number sits inside a button, the click lands on the button element, and a Just Links trigger can miss it. All Elements catches the click wherever it lands inside the link, which is why this guide uses it.

End state

The phone_click event is a key event, fired from a tel: link through Tag Manager. The week closes at 63 key events from 58 sessions, a session key event rate of 3.05%.

FigureValue
Sessions in the week1,900
phone_click events63
Sessions with a phone_click key event58
Session key event rate3.05%
Sessions that tapped more than once5

The rate is 58 / 1,900 = 3.05%, recomputed in Python 3 and rounded to two places. The repeat count is 63 − 58 = 5, because 63 events came from 58 sessions. The figures are a worked example, not a real property.

Sources

Checked 11 November 2026. The click paths above are the ones in Google's help and Tag Manager help pages, read 11 November 2026. The GA4 Event tag, the Click — All Elements trigger, Preview verification, publishing as a version, and marking in GA4 are as Google documents them. No step in this guide was run inside a live Tag Manager container or a live Analytics property, because both need a Google sign-in and this site does not sign in as anyone. The figures on this page are a worked example recomputed in Python 3 with decimal arithmetic, not numbers from a real property. Google moves menu items without warning; if a path on this page no longer matches, the linked help page is the current map.