Measurement guide 03
For every phone number, form, and booking button, check two things: what analytics recorded, and what actually arrived. Test each path, keep taps separate from real calls and bookings, and confirm who follows up. If you use call tracking, keep your main number consistent on your Google Business Profile and check recording-consent rules first.
← All measurement and analytics guidanceMap the path
Choose the trigger
Confirm receipt
Test failures
Match the records
Why this matters
A person can tap your phone number and hang up, submit a form that shows an error, or open a scheduler without booking. Those actions show interest, but they are not a conversation, a delivered inquiry, or a confirmed appointment. Lumping them into one lead total hides the exact point where a customer was lost.
Use two checks for each path: what analytics saw, and what the phone, inbox, or scheduler received. Then name who follows up. A simple test sheet with times, expected events, what arrived, and pass or fail makes both tracking faults and customer-service gaps visible.
Responsible practices
Track a phone-link tap with a clear event name such as phone_click. Then test the actual number on a real phone. With staff aware, check who answers, voicemail, and after-hours handling. If a call-tracking service reports connected calls, keep those counts separate from taps and from staff-qualified inquiries.
Call-tracking services can show different numbers to website visitors from different sources. Keep your main local number on your Google Business Profile and in directories, so your name, address, and phone (NAP) match everywhere. Google asks for a number under your direct control that connects to your business, and allows additional numbers. Read its current guidelines before putting a tracking number on the profile.
Many call-tracking tools can record calls. Federal law allows recording when one party consents, but several states require every party's consent. A recorded notice at the start of each call is one way to inform callers. Confirm with a qualified attorney for your situation before turning recording on, and limit who can listen to recordings.
Google's recommended event for a submitted inquiry is generate_lead. Fire it when the form system accepts the submission, not when someone clicks the button. Then confirm the message reached the inbox. Test invalid entries, repeated clicks, and reloading the thank-you page; none should create a second success event.
Ask whether your scheduler supports GA4 and a completed-booking event. Cross-domain tracking needs the same GA4 tag on both sites; test that the _gl link parameter survives redirects. If the tool cannot report completions, call the website event booking_outbound and take confirmed appointments from the scheduler's own records.
Hypothetical example: a report shows 18 form-success events, while the form service has 12 accepted requests. Testing shows six thank-you page reloads created extra events. Of the 12 requests, two were staff tests and one was spam, leaving nine real inquiries. Fix the trigger, and note the overcount for the affected dates.
Contact-path test
Make one test-sheet row per phone number, form, and booking button, including mobile-only buttons.
For each row, note the page, the event, where the message should arrive, and who follows up.
Agree a test window with staff and use clearly labeled, non-customer test details.
Tap each phone link on a phone, place the test call, and check routing and voicemail.
Submit each form once, confirm one success event, and find the message in the real inbox.
Try invalid entries, repeat clicks, and thank-you page reloads, and confirm none adds a success event.
Make a test booking in an agreed slot, check the confirmation and staff notice, then cancel it.
Avoid these failures
Collection, attribution, qualification, bookings, costs, and revenue depend on technical, customer, operational, and platform factors outside any provider's control. Results are not guaranteed.
Questions business owners ask
It can record a phone-link tap, but not whether the call connected. Confirmed calls come from your phone system or a call-tracking service. Many people also dial the number by hand, which creates no website event at all.
Only if testing shows it matches accepted submissions on your actual forms. It often fires on attempts too. Test successful, invalid, and repeated submissions before using it in a lead report.
Report the booking-link click as a handoff, and take confirmed appointments from the provider's records. Keep the two numbers separate and note that some bookings come from elsewhere.
Analytics misses visitors who decline cookies or block tracking. Your inbox includes phone bookings entered by staff, spam, and repeats. Compare the same dates and definitions, check a sample, and keep unmatched records visible.
Primary guidance
Follow the inquiry all the way through