How to Track Website Calls, Forms and Enquiries in GA4

If a business receives leads by phone, contact form, WhatsApp and bookings, counting only website visits gives an incomplete picture.

A useful lead-tracking setup connects three layers:

  1. Website action: what the visitor did.
  2. Successful enquiry: whether the action created a real lead.
  3. Business outcome: whether the lead was qualified, quoted and won.

Google Analytics 4 (GA4) can measure website events, but it should not be treated as the final source of truth for every offline conversation. Your CRM, call records, inbox or booking system should confirm the real outcome.

What should a small business track?

Lead typeWebsite signalStronger confirmation
Contact formSuccessful submit / thank-you pageStored submission or CRM lead
PhoneClick on a tel: linkCall-tracking record or phone system
WhatsAppWhatsApp link clickActual message/conversation
BookingBooking completion eventBooking system record
EcommercePurchase eventOrder/payment system

Before adding tags, decide what counts as a real conversion. The conversion audit checklist explains why measurement should come before design changes.

Start with a measurement plan

Write a simple table before opening GA4 or Google Tag Manager.

ActionValue to businessHow verifiedWhere reported
Form submissionLeadDatabase/CRM/emailGA4 + CRM
Phone clickLead intentCall recordGA4 + call tracking
WhatsApp clickLead intentMessage receivedGA4 + messaging record
Appointment bookedQualified actionBooking recordGA4 + booking system

This prevents every click from being labelled “conversion” without context.

GA4 events vs key events

GA4 records interactions as events.

A business can then mark the most important actions as key events so they appear clearly in performance reporting.

Examples might include:

  • successful lead form submission;
  • completed booking;
  • purchase;
  • qualified phone event where appropriate.

Do not mark every menu click, scroll and phone-number view as a key event. Keep key events aligned with meaningful business actions.

Track form submissions with the success state, not only the button

A submit-button click is weak evidence.

The user might click and receive:

  • validation error;
  • server error;
  • spam rejection;
  • payment failure;
  • no response at all.

Track a successful state instead.

Method 1: thank-you page tracking

A dedicated thank-you page is often the easiest setup when the form redirects only after a valid submission.

Example flow:

  1. Visitor submits form.
  2. Server accepts the enquiry.
  3. Visitor is sent to /thank-you/.
  4. GA4 records the thank-you page/event.
  5. The event is marked as a key event where appropriate.

This approach is easy to test and separates success from a button click.

Make sure the thank-you URL cannot be treated as proof of a new lead simply because somebody refreshed it repeatedly.

Method 2: track the form’s success event

Many modern forms use JavaScript and do not reload the page.

In that case, track the event that fires when the form reports a successful submission.

This may be configured through:

  • the form plugin;
  • Google Tag Manager;
  • a data-layer event;
  • custom JavaScript supplied by the form platform.

Test the event in debug/realtime tools before trusting it.

GA4 enhanced measurement and form events

GA4 enhanced measurement can detect some form interactions automatically, including form starts and submissions on supported implementations.

Do not assume automatic detection is complete.

JavaScript-heavy forms, embedded forms, iframes and custom implementations may behave differently. Submit a test enquiry and verify the event.

Then run the operational checks in our contact form testing guide so analytics success matches business receipt.

Use a sensible event name

Keep event names consistent and understandable.

Possible naming approaches:

  • generate_lead for a successful lead;
  • contact_form_submit for a specific form success;
  • phone_click for tap-to-call intent;
  • whatsapp_click for messaging intent;
  • booking_complete for a finished booking.

Choose a naming convention once and document it.

Track phone clicks separately from real phone calls

A tel: click is useful to measure because it shows intent.

It does not prove:

  • the visitor completed the call;
  • somebody answered;
  • the call lasted long enough to be meaningful;
  • the caller was a qualified customer.

For businesses where phone leads are important, call-tracking software or a suitable phone system can add stronger evidence.

The site can still record phone clicks in GA4, but report them as clicks unless you have a system that confirms the actual call.

How to track click-to-call in Google Tag Manager

A common setup is:

  1. Ensure phone links use tel:.
  2. Create a link-click trigger for URLs starting with tel:.
  3. Send a GA4 event such as phone_click.
  4. Include useful parameters such as page location where appropriate.
  5. Preview and test the tag.
  6. Publish only after confirming it fires once per intended click.

Then compare clicks with actual call records.

Track WhatsApp as intent, then confirm the message

WhatsApp links can be tracked as outbound/contact clicks.

But opening WhatsApp does not guarantee the visitor sends the message.

Report it separately:

  • WhatsApp click;
  • WhatsApp conversation received;
  • qualified WhatsApp lead;
  • sale from WhatsApp.

Our contact channel guide explains why these channels attract people at different stages of readiness.

Track booking completion, not calendar opening

A “Book Now” click is not a completed appointment.

Where your booking platform allows it, capture the final booking confirmation.

If the booking occurs on another domain or inside an embed, test whether attribution continues correctly.

Use UTMs for campaigns

UTM parameters help label campaign traffic consistently.

A useful campaign naming system can identify:

  • source;
  • medium;
  • campaign;
  • content/creative where needed.

Keep naming rules documented. “facebook”, “Facebook”, “fb” and “paid_social_fb” can fragment reporting if used randomly.

Do not add UTMs to normal internal links

UTMs are for campaign attribution, not ordinary internal navigation.

Adding them to internal links can overwrite or confuse the source of the session.

Use normal internal links and event tracking for on-site behaviour.

Connect website leads to CRM outcomes

GA4 tells you what happened on the website.

Your CRM or sales process should tell you:

  • was the lead genuine;
  • was it qualified;
  • was a quote sent;
  • was the job won;
  • what was the revenue;
  • why was it lost.

This is where marketing data becomes useful commercially.

Create one source of truth for lead status

Different systems can disagree.

For example:

  • GA4 shows 30 form submissions;
  • WordPress stores 28;
  • the inbox has 26;
  • the CRM has 24;
  • sales says 16 were genuine.

That discrepancy is valuable. It tells you where data or leads may be getting lost.

Choose the system that defines a real business lead, then use analytics to explain how people reached it.

Avoid double-counting conversions

Common duplicate patterns include:

  • form plugin sends an event and GTM sends another;
  • submit click and thank-you page are both counted as leads;
  • thank-you page refresh records another conversion;
  • phone click plus confirmed call are added together without distinction;
  • booking confirmation fires twice inside an embed.

Test every conversion path with a single known enquiry and compare systems.

Consent and privacy can affect measurement

Analytics and advertising tags should be configured consistently with your cookie/consent setup and the data you actually collect.

Expect reported website data to be incomplete when users do not consent to relevant tracking.

Do not “fix” that by bypassing user choices. Use business systems such as CRM and phone records alongside analytics to understand total lead volume.

Track pages that generate leads

Once conversion events work, look beyond channel totals.

Ask:

  • Which landing pages produce qualified leads?
  • Which service pages generate calls?
  • Which blog posts assist later conversions?
  • Which location pages generate real enquiries?
  • Which pages attract lots of traffic but almost no commercial action?

This helps decide where to improve content and internal links.

Do not confuse Search Console clicks with leads

Google Search Console measures search visibility and clicks from Google Search. It does not tell you whether those visitors became customers.

Our guide to impressions versus clicks helps interpret search performance. Use GA4 and business lead records for the next stage.

A simple lead-tracking dashboard

MetricWhy it matters
Relevant website visitsShows opportunity
Form successesShows submitted leads
Phone clicksShows call intent
Confirmed callsShows actual phone leads
WhatsApp clicksShows message intent
BookingsShows completed appointment actions
Qualified leadsShows commercial relevance
Sales wonShows business outcome

Weekly lead tracking routine

  1. Check that key events are still firing.
  2. Submit one test form on the most important journey.
  3. Compare GA4 lead events with CRM/inbox totals.
  4. Compare phone clicks with call records if available.
  5. Review qualified leads by source and landing page.
  6. Investigate sudden drops before changing campaigns.

Common lead-tracking mistakes

  • counting contact-page views as conversions;
  • counting button clicks as completed forms;
  • not tracking phone-led customers;
  • treating WhatsApp opens as guaranteed leads;
  • using inconsistent UTM names;
  • double-counting form events;
  • never testing tags after website updates;
  • measuring lead volume but not lead quality;
  • making decisions from one analytics system without checking sales reality.

The goal is not perfect attribution

Small businesses rarely need an enterprise analytics project before they can make better decisions.

Start by accurately measuring the few actions that genuinely matter.

Then connect those actions to real enquiries and sales.

When the numbers are trustworthy, the business can decide whether it needs more traffic, a better service page, a shorter form, a different CTA or a faster response process.

Build a lead-quality feedback loop

Marketing should learn from sales outcomes.

At least once a month, compare sources and landing pages against:

  • qualified lead rate;
  • quote rate;
  • sale rate;
  • average value;
  • common disqualification reason.

If one campaign produces many events but almost no suitable customers, optimise for quality rather than celebrating the conversion count.

Record the first useful source without pretending attribution is perfect

Customers may visit several times, switch devices, call later or return through a brand search. No small-business setup will perfectly reconstruct every journey.

Use consistent UTMs, GA4, Search Console, call data and CRM notes to build a reasonable picture. Be clear about what the data can and cannot prove.

Use annotations or a change log

When leads move suddenly, check what changed.

Record dates for:

  • website redesigns;
  • form changes;
  • new campaigns;
  • tracking/tag changes;
  • pricing changes;
  • major Google updates where relevant;
  • sales-process changes.

A simple change log can prevent hours of guessing months later.

Lead-tracking QA checklist

CheckPass condition
FormOne real test submission creates one lead event and one business record
PhoneTap-to-call event fires once; actual calls are verified separately
WhatsAppClick event is distinct from conversation received
BookingCompletion, not calendar view, is counted
UTMsNaming follows one documented convention
CRMLead source and final outcome can be compared

Separate marketing attribution from operational truth

Analytics answers “what digital path did we observe?” Operations answers “did a real customer contact us and buy?”. Those questions overlap but are not identical.

Keep both views. Marketing can use GA4 and campaign data to optimise acquisition. The business should use CRM, booking, payment and phone records to confirm actual outcomes.

Test tracking after plugin, consent and template updates

Tags can stop firing after a form plugin update, consent-manager change, template rebuild or new booking provider. Add tracking QA to the same maintenance routine used for forms and checkout.

A monthly test lead with a clearly labelled test name is often enough to confirm the basic path from page to analytics to business system.

Keep a written tracking map

Document the event name, trigger, key-event status, destination system and person responsible for each lead type. This small record makes future troubleshooting much faster when a form, tag or integration changes.

Website lead tracking FAQs

Can GA4 track contact form submissions?

Yes, but automatic form tracking does not work perfectly for every implementation. Verify the event with a test submission and use a reliable success state such as a thank-you page or confirmed form event where needed.

Can GA4 track phone calls?

GA4 can easily track clicks on phone links. Confirming that a real call connected usually requires call-tracking software or phone-system data.

How do I track WhatsApp leads?

Track clicks on the WhatsApp link as lead intent, then compare them with actual messages and qualified conversations where your process allows.

Should I mark every contact event as a GA4 key event?

No. Reserve key events for meaningful actions. Keep lower-value interactions available as normal events.

What is the most important lead metric?

For most service businesses, qualified leads and sales matter more than raw clicks or form starts. Website events explain how those outcomes happened.

Share