A form submission rarely shows the whole customer journey. Someone may search your site, tap your phone number, revisit a service page, then send an enquiry hours later.
GA4 enquiry tracking connects searches, phone taps, page visits and completed forms. It shows which pages, campaigns and contact routes lead to valuable website enquiries, rather than treating every action as the same outcome.
With a clearer view of each journey, your reporting can support better Web Design, Digital Marketing and follow-up decisions.
Key Takeaways
- Plan enquiry tracking around meaningful customer actions, distinguishing genuine outcomes from signals of interest such as form opens, phone taps and email clicks.
- Use Google Tag Manager and GA4 events such as
generate_lead,telephone_enquiry,email_enquiryandview_search_resultsto connect customer journeys with enquiry outcomes. - Fire completed-enquiry events only after a successful form submission or confirmed action, then test triggers and parameters in Tag Manager Preview and GA4 DebugView.
- Protect customer information by keeping personally identifiable and free-text enquiry data out of GA4, while reviewing consent settings for New Zealand visitors.
- Use Explore reports to compare enquiries with engaged sessions, search terms, landing pages, traffic sources and devices so website and marketing decisions reflect qualified outcomes.
Start with a useful measurement plan
Google Analytics 4 records interactions as events, unlike the session-based model used by Universal Analytics. That change is helpful, but only when your events reflect how people actually contact your business.
Before setting up tags, write down the actions that indicate real intent. Use engaged sessions as supporting context, not proof of an enquiry. A local Small Business might value quote requests and calls. A creative agency may care more about discovery-call bookings and project briefs.
Separate interest from completed enquiries
An interaction can show interest without becoming an enquiry. A visitor who opens a contact form has shown interest. Someone who reaches a genuine confirmation screen has completed an enquiry. Track both, but don’t treat them as equal.
generate_lead is a recommended GA4 event for completed leads. Telephone and email actions may need custom events, so keep those names separate.
Useful events could include:
| Customer action | Example event | Helpful parameters |
|---|---|---|
| Successful contact form | generate_lead (recommended event) | form_id, enquiry_type |
| Click-to-call link | telephone_enquiry (custom event name) | link_url, page_location |
| Email link click | email_enquiry (custom event name) | link_url, page_location |
| Site search results | view_search_results | search_term |
| Booking completed | generate_lead (recommended event) | enquiry_type, booking_service |
Use a consistent event name for the same outcome across the site. Otherwise, reports become a cupboard full of mismatched labels.
Define what a good enquiry means
Conversion Optimisation should focus on enquiry quality, not only volume. Ten spam submissions or unsuitable jobs don’t beat three enquiries that become profitable Clients. Define that profitable outcome before labelling the event as successful.
Ask the person handling new work to record whether an enquiry became a quote, consultation, booking or completed job. You can then compare GA4 activity with your CRM, inbox or job-management system.
Define the event that represents a completed enquiry. Mark it as a key event only after confirming it fires for a successful action, not every button tap.
This approach also keeps your Lead Generation reporting grounded in business outcomes.
Set up enquiry measurement with Google Tag Manager before building tags
A sound Google Analytics 4 setup starts with one Google tag sending data to the relevant GA4 web data stream. If you use Google Tag Manager, place the tag there and check that a CMS plugin, form plugin or old hard-coded tracking code isn’t sending a second page view.
Duplicate implementation can inflate users, sessions, event counts and enquiry totals. It also makes campaign reporting harder to trust.
Check your data stream and measurement settings
In your Google Analytics 4 property, go to Admin, open Data streams, and choose your web stream. Confirm that Enhanced Measurement is on, then use its settings icon to review the available options.
Google’s Enhanced Measurement event documentation explains which actions GA4 can collect without extra tagging. These can include outbound clicks, scrolls, form interactions and site search, depending on your configuration.
Enhanced Measurement can provide a useful baseline. However, it can’t determine whether a generic form is a newsletter sign-up, a job application or a quote request. Add your own event for the enquiry outcome that matters.
Choose event parameters that answer practical questions
These values add context to an action. For example, enquiry_type could contain quote_request, consultation or emergency_call. A form_id parameter distinguishes a footer form from a service-page form.
Google explains the role of GA4 event parameters. Keep these values focused. They mustn’t contain names, email addresses, phone numbers, free-text messages or other personally identifiable information.
Use page URLs, page titles, form names and broad service categories instead. Those details are enough to improve a Mobile Responsive contact journey without turning analytics into a customer database.
Site search tracking alongside contact actions
On-site search reveals intent that page views can hide. A search term such as “after-hours electrician”, “pricing” or “WordPress support” shows what visitors couldn’t immediately find.
This site search tracking supports SEO, website content and Digital Branding. It can show missing service pages, unclear navigation or wording that doesn’t match the language customers use.
Enable search tracking in Enhanced Measurement
Google Analytics 4 can automatically send the view_search_results event when users view search results. In prose, view search results describes the action, while view_search_results is the actual event name.
By default, it checks common query parameters such as q, s, search, query and keyword.
Open the Site search settings in your web data stream. Then run a real test search and inspect the search results page address. A URL such as /search/?q=roof+repair is straightforward because q holds the search term.
If your platform uses different query parameters, add the relevant name in the advanced Site search settings. GA4 should then pass the query as the search_term parameter.
The event fires when a search results page contains a recognised query. GA4 can then record a view search results event automatically.
GA4’s list of automatically collected events confirms that search data needs reporting setup before it’s broadly available in your analysis.
Compare search behaviour with engaged sessions to assess meaningful engagement, not completed enquiries.
When the term is not in the URL
Some search tools update results without changing the URL. Others put the term in a page path, an autocomplete widget or a JavaScript request. In those cases, Enhanced Measurement can’t reliably identify the search phrase.
Use Google Tag Manager to send a view_search_results event when the search results load. The best option is a developer-provided data layer value containing a clean search term. This is more dependable than scraping text from the page, which can break when the design changes.
If the search provider can’t expose a clean value in the data layer, use a custom JavaScript variable in the container as a fallback. However, a custom JavaScript variable is less reliable when rendered text changes. If a CMS or search provider has a native GA4 integration, check it first, as platforms vary widely and may need developer support.
Use Google Tag Manager for forms, phone and email
Google Tag Manager gives you control over which interactions count as enquiries. It is especially useful where forms submit through AJAX, show a popup confirmation or redirect to a thank-you page.
A reliable setup tracks success, not intent alone.
Send a form event after success
Start by identifying the form’s success signal. This might be a thank-you page, a visible confirmation message, a successful form callback or an event from the form provider.
Create a Google Tag Manager trigger for that success signal. Then create a GA4 Event tag with the event name generate_lead and add safe parameters such as form_id and enquiry_type.
Google lists generate_lead amongst its recommended GA4 events. Using recognised event names can make your data easier to understand across analytics and advertising tools.
Don’t fire generate_lead on a form’s submit button. A visitor may leave required fields blank, fail a spam check or lose connection before the form reaches your system.
Track telephone and email enquiries accurately
For telephone links, create a Just Links trigger that fires only when the URL begins with tel:. Send a custom event such as telephone_enquiry to record a telephone enquiry.
For email links, use the same principle with mailto: and an event such as email_enquiry to record an email enquiry. Add page_location automatically, then use a simple contact_method parameter for a combined contact-method report. Phone and email link clicks can use custom events, while generate_lead remains the recommended event for a confirmed form submission.
A telephone or email click indicates intent, not a completed conversation. It can still be a strong signal when a service page has a clear call-to-action. In a combined contact-method report, treat a telephone enquiry and email enquiry as intent signals, not confirmed conversations.
For service businesses, a fast page and tappable contact routes are part of conversion-focused web design, not finishing touches. Heroic’s approach to turning website traffic into enquiries connects the page, contact action and follow-up process.
Test events, key events and consent choices
Never publish tags and assume they work. Test the same journey a customer takes, on desktop and a real phone.
In Google Tag Manager, preview mode shows which triggers fire. Check that each action fires once. Duplicate tags can inflate enquiry totals and distort engaged sessions. They can also make engaged sessions appear higher than the real level. Google Analytics 4 DebugView then shows the events arriving in your property, often within seconds.
Validate the event details in DebugView
Open Google Analytics 4 DebugView and submit a test form. Look for generate_lead, then inspect its parameters. DebugView helps confirm the event and its parameters, rather than merely an inflated event count.
Repeat the process for a phone link, an email link and internal site search. Use DebugView to verify each event and its values.
For the view search results test, confirm that view_search_results includes the expected search_term. Try a valid two-word search, punctuation and a service-specific search term. A blank value or undefined points to a broken variable.
Once the event works, mark the completed enquiry event as a key event in GA4. GA4 currently uses key events in the interface, while marketers and older documentation may still refer to conversion events. Review the validated data in an exploration report.
Respect consent and protect enquiry data
If your site serves people in New Zealand, consider the Privacy Act 2020 and applicable consent and electronic-marketing obligations. Obtain current legal advice for your situation before relying on the setup.
Your consent banner should record choices and pass them to Google tags before analytics or advertising storage operates beyond the permissions granted.
Review your Consent Mode configuration whenever you add tags. This matters for Website Care & Maintenance, too, because a plugin update or new marketing tool can alter consent behaviour.
Keep free-text fields out of analytics. Someone may include health details, financial information, an address or a complaint in an enquiry message. GA4 is not the place to store it.
Build reports that improve marketing decisions
After clean data has accumulated, use Google Analytics 4’s Explore workspace to build an exploration report from validated events. Standard reports won’t automatically expose every parameter.
Add dimensions such as Event name, search_term, Landing page, Session source / medium and Device category in the exploration report.
For metrics, compare event count with engaged sessions and key events in the exploration report. Use the exploration report to review engaged sessions by Landing page and Session source / medium.
Then segment engaged sessions by Device category, comparing engaged sessions with enquiry outcomes by device. High engaged sessions with few enquiries require investigation, particularly when engaged sessions contain few key events. Check whether the event count reflects repeated clicks or genuine outcomes when engaged sessions are high, rather than treating them as leads.
Use custom filters to isolate validated outcomes, then filter for generate_lead, telephone_enquiry, email_enquiry or view_search_results. For wider dashboards, connect validated analytics data to Looker Studio.
Apply consistent UTM parameters to campaign links, then interpret them alongside Session source / medium, Landing page and Device category. UTM parameters can be lost through consent choices or redirects, so don’t treat them as person-level identifiers.
Register custom dimensions where needed
GA4 doesn’t automatically make every event parameter available in standard reports. Register event-scoped custom dimensions for parameters you need to analyse, such as enquiry_type, form_id and, where needed, search_term.
Google’s dimensions and metrics reference is a useful check before adding custom definitions.
Give each dimension a clear name and use one format. For example, don’t mix Quote Request, quote, and quote_request. Consistent values make filters and comparisons far more useful.
Find the gaps before changing the website
Use site search tracking to compare pages with high-volume search term data against enquiry actions. A search term with many searches but few enquiries may point to a missing page, unclear pricing or weak contact options.
Review the same report by device. If mobile visitors search and call less often than desktop visitors, test the form, phone button and page speed on actual handsets. Web Hosting, Web Development and content design all affect this path.
Agencies can use the same event framework across client sites without forcing every business into identical reporting. See how we collaborate with creative agencies when you need a technical partner for the build, tracking and ongoing support. Trades businesses can also find out more about how we work with tradies on websites and enquiry systems that reduce missed opportunities.
Frequently Asked Questions
What is GA4 enquiry tracking?
GA4 enquiry tracking records the actions that lead to customer contact, including completed forms, telephone clicks, email clicks and relevant site searches. It helps connect those actions with landing pages, campaigns and devices so you can assess which journeys produce valuable enquiries.
Should every form submission be tracked as generate_lead?
Use generate_lead for a confirmed lead, such as a form that has reached a genuine thank-you page or success message. Don’t trigger it from a submit-button click, because the visitor may not complete the form or the submission may fail.
How can I track telephone and email enquiries in GA4?
Use Google Tag Manager triggers for links beginning with tel: and mailto:, then send separate custom events such as telephone_enquiry and email_enquiry. These clicks show intent rather than a completed conversation, so review them alongside qualified enquiries and follow-up data.
How do I check that my enquiry events are working?
Use Google Tag Manager Preview to confirm that each trigger fires once, then inspect the event and its parameters in GA4 DebugView. Test forms, phone links, email links and site search on desktop and an actual mobile device before marking a completed enquiry as a key event.
Can GA4 store information from an enquiry form?
Don’t send names, email addresses, phone numbers, free-text messages or other personally identifiable information to GA4. Use safe values such as form_id, broad enquiry_type, page location and service categories, and review consent requirements under the New Zealand Privacy Act 2020.
Make every enquiry signal count
Completed forms, telephone taps, email clicks and the searches that came before them need to be read together. This gives you evidence for practical changes instead of guesses.
Treat a rise in enquiries as the start of the review, not the finish. Engaged sessions provide useful context, but qualified enquiries and quick follow-up show whether the website is helping the business grow. Use an exploration report to review these patterns and decide what to improve next.
