How to Track Phone Calls and Form Leads in GA4 for Local Businesses (2027)

Learn how to track tel: phone calls and form leads in GA4 using Google Tag Manager, generate_lead parameters, and Once per session key event counting.

As seen in

  • Fox News
  • ABC News
  • CBS
  • NBC
  • Associated Press
  • USA Today
  • Bloomberg
  • HuffPost
Otto the beaver next to the Google Analytics logo
On this page6

To track phone calls and form leads in GA4 in 2027, do not rely on raw Enhanced Measurement alone: automatic click events only fire on outbound domains, and form_submit fires on every form across your site. Instead, create a Google Tag Manager Just Links trigger where Click URL starts with tel: for phone calls, send Google's recommended generate_lead event (or filter form_submit by form_name in Admin > Data Display > Events) for forms, mark both under Key events with Once per session counting, and verify the events in Realtime.

Why GA4 Enhanced Measurement misses phone calls and overcounts form leads

If you turned on GA4 Enhanced Measurement and still cannot see phone calls or real form leads in reports, the default setup is likely the reason—not a broken tag.

Enhanced Measurement measures outbound clicks through the click event only when a visitor clicks a link leading away from your current domain to an external website, according to Google Analytics Help. A click-to-call link uses the tel: protocol in an <a> element rather than an https URL to another site. Because a tel: link opens the visitor's phone dialer rather than an external web domain, GA4 ignores it completely.

Form tracking fails in the opposite direction: it overcounts. The automatic form_submit event fires whenever any form on your site submits, as documented in Google Analytics Help. That includes internal search bars, footer newsletter fields, and filter inputs—any <form> submit on the page. If you toggle raw form_submit on as a key event, your reporting treats an internal site search or a newsletter signup as a paid lead.

Reviewing raw numbers in Otto Website Analytics and weekly GA4 briefings requires accurate event boundaries. The table below contrasts default Enhanced Measurement behavior with properly configured key events.

Measurement TypeRaw Enhanced Measurement BehaviorScoped Event / GTM Key Event Behavior
Phone calls (tel: links)Ignored. Outbound click tracking only triggers when leaving for an external web domain (Google Analytics Help).Recorded as click_to_call via a GTM Just Links trigger matching tel:.
Site search formsFired as form_submit. Inaccurately counts search queries as conversions.Excluded by targeting specific form IDs or custom generate_lead tags.
Footer newsletter signupsFired as generic form_submit alongside quote forms.Separated by form_name or tagged as distinct newsletter events.
Contact or booking formsFired as generic form_submit without revenue or lead-source parameters.Recorded as generate_lead with value, currency, and lead_source (Google for Developers).
Conversion countingCounts every single action during a visit (Once per event).Counted Once per session to prevent duplicate refreshes from inflating counts (Google Analytics Help).

Step 1: Track tel: phone call clicks in Google Tag Manager (Just Links trigger)

Because Enhanced Measurement ignores tel: links, capture click-to-call interactions using Google Tag Manager (GTM).

First, ensure your site code wraps phone numbers in proper anchor tags. A number written as plain text cannot trigger a browser dialer. If you use the Otto AI Website Manager for draft-first WordPress and GitHub pull request updates, your phone numbers can be formatted inside drafts for your review before going live ``.

Follow these steps in Google Tag Manager:

  1. Enable Click Variables: Open your GTM container. Navigate to Variables > Built-In Variables > Configure. Ensure Click URL, Click Text, and Click Classes are checked, as described in Google Tag Manager Help.
  2. Create the Trigger: Go to Triggers > New. Name the trigger Click - Tel Links.
  3. Select Trigger Type: Under Trigger Configuration, select Click - Just Links, as detailed in Google Tag Manager Help.
  4. Configure Trigger Filters: Set the trigger to fire on Some Link Clicks. In the dropdown conditions, choose:
  • Click URL
  • starts with
  • tel:
  1. Create the GA4 Event Tag: Navigate to Tags > New. Name the tag GA4 Event - Phone Click. Under Tag Configuration, select Google Analytics: GA4 Event. Select your GA4 Measurement ID variable.
  2. Set Event Name and Parameters: Set Event Name to click_to_call. Under Event Parameters, add:
  • Parameter: phone_number | Value: the built-in Click URL variable
  • Parameter: link_text | Value: the built-in Click Text variable
  1. Attach Trigger and Save: Assign your Click - Tel Links trigger to this tag. Save the tag and submit the GTM container version.

Next, register your parameters in GA4. In GA4, go to Admin > Data Display > Custom definitions > Custom dimensions > Create custom dimension. Set the Dimension name to Phone Number, scope to Event, and Event parameter to phone_number. This allows you to report on which specific phone number was tapped across your headers, footers, and landing pages.

Step 2: Track form leads with generate_lead (GA4 Create event vs. GTM Form Submission)

To avoid overcounting search bars and newsletter inputs, track only dedicated lead forms. You have three primary methods.

Method A: GA4 scoped event in the admin interface

If your site already fires form_submit cleanly and your lead form has a unique HTML name or ID attribute, isolate it inside GA4 without editing site code.

Under Admin > Data Display > Events, click Create event, as guided by Google Analytics Help. Set Custom event name to generate_lead. Under Matching conditions, enter two rules:

  • event_name equals form_submit
  • form_name equals contact_form (or match form_id equals main-lead-form)

Save the configuration. GA4 now records a clean generate_lead event whenever that specific form submits, ignoring site search bars.

Method B: GTM Form Submission trigger with validation

For sites where multiple forms share scripts, use a GTM Form Submission trigger:

  1. In GTM, go to Triggers > New and select Form Submission, as documented in Google Tag Manager Help.
  2. Check Wait for Tags and check Check Validation, as explained in Google Tag Manager Help. Wait for Tags delays the form submission until tags that depend on this trigger have fired or the timeout you set in GTM elapses. Check Validation fires the trigger only if the form is successfully sent rather than whenever a user attempts to submit.
  3. Under This trigger fires on, choose Some Forms and set Form ID equals contact-quote-form.
  4. Create a new GA4 Event Tag named GA4 Event - Generate Lead. Set the event name to generate_lead.

Google for Developers specifies generate_lead as the standard event for form submissions and inbound quotes, supporting parameters such as value, currency, and downstream pipeline events like qualify_lead and working_lead.

In your tag's Event Parameters, add:

  • currency: USD
  • value: 50 (use an estimated lead value based on your historical close rates)
  • lead_source: contact_page
gtag("event", "generate_lead", {
  currency: "USD",
  value: 50,
  lead_source: "contact_page"
});

Attach the form trigger, save, and publish.

Method C: Confirmation page view trigger

If your form redirects to a dedicated URL (for example, /thank-you or /consultation-confirmed), create a trigger fired on Page View where Page Path equals /thank-you. Attach a GA4 Event tag firing generate_lead. This usually fires only after a successful redirect, so submit attempts that never reach the confirmation page are less likely to count as leads. Keep the thank-you URL unique to completed lead forms—not a page visitors can load without submitting.

Step 3: Mark events as Key Events, set Once per session counting, and verify in Realtime

Once your click_to_call and generate_lead events fire, configure them as key events in GA4.

Mark as Key Events

  1. Navigate to Admin > Data Display > Events.
  2. Locate click_to_call and generate_lead in your existing event table.
  3. Toggle the switch under Mark as key event to active for both.
  4. If an event has not fired yet, go to Admin > Data Display > Key events, click New key event, type the exact event name, and click Save.

Change counting method to Once per session

By default, GA4 counts key events using Once per event (Recommended), which counts every time the event fires in a visit, according to Google Analytics Help.

For local service businesses, a visitor who refreshes a confirmation page or taps a phone number three times during a single call should count as one lead. In Admin > Data Display > Key events, click the three-dot menu next to click_to_call and select Change counting method, as outlined in Google Analytics Help. Select Once per session (Legacy). Repeat this for generate_lead.

Changes to the counting method apply to future key events only and will not apply to past data, as noted in Google Analytics Help.

Worked example: Local sports physical therapy clinic

Consider a hypothetical physical therapy clinic tracking patient inquiries to measure strategy for getting more patient bookings and calls from a clinic website. A mobile user lands on the sports injury rehabilitation page from a local search, clicks the header phone number, talks to the front desk, and later submits the intake form on the same page.

Under raw Enhanced Measurement, the phone click is never recorded, while the contact form records a generic form_submit mixed together with search bar queries.

Under this configured setup:

  • The phone tap fires click_to_call with the full tel: URL stored in the phone_number parameter.
  • The form fires generate_lead with value: 30.03, currency: USD, and lead_source: clinic_evaluation_form (Google for Developers).
  • With Once per session active, an accidental second tap on the phone number during the appointment discussion registers as one call conversion, not two (Google Analytics Help).

Verify in GA4 Realtime

Before trusting your data, verify both events:

  1. Open GA4 and go to Reports > Realtime.
  2. In a separate mobile browser or private window, load your website.
  3. Tap your phone link, then return to the site and complete a test form submission.
  4. Watch the Event Count by Event name card in the Realtime report, which shows events collected in the last 30 minutes (Google Analytics Help). After your test, click_to_call and generate_lead should appear there.
  5. Check the Key Events by Event Name card directly below it to confirm both are registering under your conversion counts.

How to audit GA4 phone and form leads alongside Search Console, paid ads, Shopify, and Google Sheets in Claude

Once your events fire, tracking data is only useful if you review it regularly against your marketing spend. Local operators often struggle to connect GA4 landing page leads with search rankings, ad spend, and CRM records.

Manually exporting 3,000-row CSV spreadsheets from Meta Ads, Google Ads, and GA4 to paste into AI tools is inefficient. Uploading a raw 3,000-row Ads Manager CSV into Claude can consume 40,000 to 80,000 tokens in a single turn, whereas querying aggregated metrics through Otto MCP cuts token usage by 80–90% ``.

You can connect Claude to Otto MCP using an HTTP server connection at https://otto.islaintel.com/api/mcp using a single organization bearer token prefixed otto_mcp__ `. Users do not paste GA4 keys, Meta tokens, or WordPress passwords into Claude; accounts connect once via OAuth, and credentials never leave Otto's server `.

From there, you can connect Google Analytics 4 (GA4) to Otto, connect Google Search Console to Otto, connect Google Sheets to Otto for live KPI reporting, and connect Shopify to Otto to audit performance `. Otto Webmaster connects 227 tools across 15 platforms to inspect site traffic, ad spend, search queries, and store metrics together `.

Guillermo Marti leads paid ads, SEO, and AI marketing workflows at IslaIntel `, while Enrique Vásquez oversees operations guides covering Shopify inventory and Google Sheets live KPI reporting `. Review your GA4 and paid media landing page dashboards using these four Claude prompts:

Prompt 1: Landing page phone call and lead audit

Query GA4 for the last 30 days. List my top 10 landing pages sorted by sessions. For each landing page, show the count of 'click_to_call' and 'generate_lead' key events alongside the calculated conversion rate. Highlight any high-traffic page converting below 2%.

Prompt 2: Cross-referencing Google Search Console rankings with GA4 leads

Query Google Search Console and GA4 for the last 28 days. Identify pages ranking in positions 4 through 10 that generate phone calls or form leads, and list the top search queries driving clicks to those pages so we can improve content relevance.

Prompt 3: Paid ad spend versus actual phone and form leads

Pull ad spend for the last 14 days from Google Ads and Meta Ads. Compare total campaign spend against GA4 key events (click_to_call and generate_lead) attributed to google / cpc and meta / cpc. Calculate my cost per lead for each channel.

Prompt 4: Reconciling GA4 leads with Google Sheets CRM records

Read the qualified consultations tab from my connected Google Sheets spreadsheet and compare it against GA4 generate_lead counts for this month. Show me the discrepancy between web form submissions and qualified consults logged by our front office.
Setup ApproachSetup FrictionToken Consumption in ClaudeCross-Channel ContextLanding Page Fixes
Manual CSV ExportsHigh. Requires pulling CSVs from GA4, Ads, and CRM weekly.40,000–80,000 tokens per prompt run ``.None. Data sits in isolated spreadsheets.Manual. You edit code and files yourself.
Ad-Only Connectors (e.g., Synter, Opteo)Medium. Connects ad channels to AI assistants ` `.Moderate API usage across ad metrics.Limited to paid advertising networks without site deploys ` `.None. Ad tools cannot edit CMS files ` `.
Otto MCP ConnectorLow. OAuth connection once, queried directly via Claude ` `.Cuts token usage by 80–90% via aggregated queries ``.Unifies GA4, Search Console, Google Ads, Meta Ads, Shopify, and Sheets ``.Direct. Drafts WordPress changes or opens GitHub pull requests ` `.

Read-only analytics guardrails, approval-gated website fixes, and Otto plans

Understanding where leads drop off is helpful only if you can fix the page. When ad traffic arrives on a landing page with a hidden phone number or a broken mobile layout, repairs should happen quickly.

Otto Webmaster is an AI digital webmaster built by IslaIntel in San Juan, Puerto Rico `. Otto is built for service businesses and small teams—including clinics, law firms, studios, cafés, agencies, gyms, and salons—that need their site, search, and ads kept current without hiring a full-time marketer or paying an agency retainer for routine work . He performs weekly execution including site updates, ad checks, SEO maintenance, and reporting, while strategy and approvals stay with you `.

Otto operates under strict read and write boundaries:

  • Read-Only Analytics Guardrails: In Otto MCP, Google Analytics 4, Google Search Console, YouTube, Google Sheets, and PageSpeed Insights are read-only with no spend or configuration changes. The built-in psi_analyze_url tool checks Core Web Vitals on your contact pages without requiring a separate Google API key.
  • Approval-Gated Website Edits: Otto is not a website builder; he works on the site you already have `. On GitHub, changes open as a pull request with a preview . On WordPress, where Otto provides 29 tools (15 read and 14 write), new content stays a draft until you publish it . Contact, checkout, and legal pages always require human approval `.
  • Approval-Gated Paid Ads: In Otto MCP, LinkedIn Ads campaigns and ad sets are created as DRAFT by default, activating requires explicit confirmation plus a reviewer, and zero-dollar budgets are rejected `. Meta Ads write operations also require reviewer or admin permissions . You can approve or reject changes directly from WhatsApp without logging into the web dashboard . Otto never guarantees Google Map Pack placement or search rankings, focusing instead on structuring websites, schema, and reviews cleanly `.

Otto offers transparent plan tiers:

  • Starter: $9.99/week or $29.99/month, paid in full. MCP only: reads every connected source in Claude, ChatGPT or Cursor and publishes posts to Instagram, Facebook Pages, LinkedIn and Google Business Profile. No scheduling, ad changes, image generation or site edits.
  • Pro: $199/mo, or $99/mo billed annually ($1,188/year), starting with $1 for 3 days. Adds the Otto app, website updates and SEO, ad changes, post scheduling, comment replies, image generation and team seats, with a homepage redesign included with the $1 trial. Otto generates automated weekly SEO reports that track rankings over time.
  • Enterprise: no published price; a call with the founder, for bigger businesses and agencies.
  • Honest Limitations: Ad changes, post scheduling and comment replies require Pro, while social posting works on every plan, and white-label agency portals are limited. Otto MCP connects to Claude, ChatGPT, Cursor, Claude Code, OpenClaw, and Hermes under the same plan boundaries without a separate MCP fee.

Fix your GA4 tracking first so your phone calls and form leads are measured accurately. Then start a $1 3-day Otto trial to connect your accounts, audit your pipeline, and put routine site fixes on draft-first approval.

Written by

Otto Team

Editorial & SEO Team at Otto

Practical website, SEO, paid ads, and analytics playbooks for small businesses from the Otto team.