Track the Actions That Matter: Calls, Directions and Bookings

Someone searches for a dinner spot on a Friday afternoon. They land on a restaurant’s website, look at the menu for a minute, tap the reservation button and finish booking on OpenTable. Someone else looks up a dental practice, taps the phone number and books a cleaning with the front desk. A third person taps for directions and drives over.

All three are exactly what the business wanted, and in a typical analytics report all three look like short visits that ended without a conversion. Nobody filled out a form. The report shows pageviews and time on site, and the owner is left wondering what the ad budget actually bought.

The visits that matter end in a tap

For restaurants, medical and dental practices, salons and most local services, the form is not the main way customers reach you. They call. They ask for directions. They click out to a booking system, whether that is OpenTable, Resy, a scheduling tool or a patient portal. Each of those actions happens in a fraction of a second and then the visitor is gone, into their phone app, their maps app or someone else’s website.

If your measurement only counts form submissions, it misses most of what your website does. And general numbers like pageviews, bounce rate or time on site do not help much either. A person who found your number in five seconds and called had a great visit. In most reports it looks like a poor one.

Name each action you care about

Google Analytics 4 records events, and you can define your own. The useful approach is to give each guest action its own clearly named event, so you can see each one separately:

• A reservation click, when someone taps through to your booking system
• A phone call tap, when someone taps a phone number on a phone
• A directions tap, when someone taps your address or a get-directions button
• A form lead, when a contact or inquiry form is submitted

Then mark the ones that represent real business as key events in GA4. Key events are what GA4 treats as outcomes, and they are what you want front and center in reports rather than buried among every scroll and click.

One practical detail: a new event will not appear in GA4’s key event settings until it has fired at least once. After setup, tap each button yourself on the live site, wait for the events to show up, and then mark them.

Connect them to your ads

If you run Google Ads, send the same actions to Google Ads as conversions. That does two things.

First, it lets the ad platform optimize toward what you actually care about. Automated bidding learns from conversions, and if the only conversion it can see is a form that few people fill out, it has very little to learn from. Give it calls, reservations and directions requests, and it can start finding more people who do those things.

Second, it changes the question you can answer. Instead of cost per click, you can read cost per call, cost per reservation and cost per directions request. Those are numbers an owner can make decisions with. A campaign with expensive clicks can still be a good one if those clicks turn into booked tables.

If the ads are sending people to the wrong page in the first place, that is its own problem. We covered it in Where Your Ad Clicks Should Land.

The details that decide whether the numbers are right

Tracking these actions is not complicated, but a few details decide whether the numbers mean anything:

• Record the tap before the visitor leaves. When someone taps a phone number or a booking link, the phone app or the booking site opens right away. If the event is not sent first, it can be lost along with the page. The tracking code has to send the event and then hand off, every time.
• Match the names exactly. Event names are case sensitive. If the site sends one spelling and your dashboard, key event settings or ad conversion setup expects another, those clicks quietly show up as nothing. Write the names down once and copy them everywhere.
• Only measure the real domain. Preview links, staging copies and test versions of your site should never send analytics. Otherwise every test click your web team makes lands in your reports. With Google Ads conversion tags it is worse: the bidding system learns from those fake conversions and starts optimizing your budget toward clicks that were never customers.
• Test it on a phone. Phone taps and directions taps behave differently on a phone than on a laptop. Check them where your customers actually use them.

We also check that the visitor arrives with their campaign tags intact, since a broken redirect can strip them before any of this runs. That is the subject of The Redirect That Quietly Erases Your Ad Tracking.

Read the numbers honestly

Each action tells you something different, and it is worth being clear about what.

A completed form or a call is a real contact. A reservation click means someone started booking; your booking system can tell you how many finished. A directions tap is intent, not a guaranteed visit. Some people tap and change their minds, and some arrive without ever tapping. Read directions as a trend over weeks: if they rise when a campaign runs and fall when it stops, that is a meaningful signal even if you cannot count every person who walked in.

The point is not a perfect count. It is having numbers that move with the things that pay your bills, so that when you change an ad, a page or a budget, you can see what happened.

Getting it set up

If your reports are full of pageviews and short on calls, bookings and directions, the measurement is the place to start. Our data and analytics team can set up and test the events, the key events and the ad conversions so the numbers you read reflect the customers you actually got.