Analytics Setup Checklist for Lead Generation Websites That Actually Generate Enquiries

Most lead generation websites have analytics installed, but many are missing the events and conversions that actually tell you whether the site is working. A visitor form submission, a phone number click, a quote request sent, a chatbot conversation started — those are the moments that matter for a business website. If your analytics is not tracking them, you are flying blind while paying for traffic.

What makes lead generation website analytics different from standard analytics

Standard page view analytics tells you how many people visited a page. That is useful, but for a lead generation website it is not enough. The real question is whether visitors complete the specific actions that generate business enquiries. Without those events configured, you cannot tell which pages produce leads, which traffic sources convert, or where visitors drop off before submitting a form.

A lead generation website needs analytics that answers three questions: where traffic comes from, what visitors do on the site, and which actions count as valuable outcomes. Getting those three things right means you can make informed decisions about marketing spend, page design, and where to focus improvement work.

Google Analytics 4: the foundation for most UK business websites

Google Analytics 4 is the current version of Google's analytics platform. If your site still uses Universal Analytics, that setup stopped processing new data in mid-2024. For any UK business website still running Universal Analytics, migrating to GA4 should be the first priority in any analytics review.

GA4 works differently from its predecessor. It tracks events by default rather than sessions, which makes it more flexible for measuring specific interactions on a lead generation site. However, the default configuration is designed for general informational sites, not conversion-focused business websites. The setup needs tailoring.

Essential GA4 configuration steps

The GA4 configuration assistant runs when you create a new property, but several settings need manual adjustment for lead generation sites. Here is what to check and change.

Enable enhanced measurement. GA4's enhanced measurement settings track file downloads, outbound links, site search, and video engagement automatically. For a lead generation site, these additional signals add context about how visitors interact with downloadable resources like brochures, price lists, or case studies. Check the enhanced measurement settings in your GA4 admin panel under Data Display, then Properties, then Data Streams, then your website stream.

Configure conversion events. GA4 lets you mark any event as a conversion. This is how you tell the system which actions matter for your business. A conversion event might be a form submission, a phone click, or a chatbot interaction. You mark events as conversions in the Configure, then Conversions section of GA4. Do not rely on the default goal completions alone — configure events that reflect your actual lead generation actions.

Set up audience lists. GA4 can build audiences based on user behaviour. For a lead generation site, useful audiences might include visitors who viewed your contact page but did not submit a form, or visitors who downloaded a resource. These audiences can then be used in remarketing campaigns through Google Ads if you run paid traffic.

Link Google Ads if applicable. If you use Google Ads to drive traffic to your lead generation site, linking the accounts lets GA4 pull in campaign cost data and attribute conversions correctly. This connection is made in GA4 Admin under Product Links, then Google Ads Links.

Verifying your GA4 installation

Before assuming GA4 is working correctly, verify the data collection. The GA4 DebugView in the Configure section shows real-time events from your browser when debug mode is active. Install the GA4 DebugView browser extension, visit your site, and check that events appear in the DebugView. If they do not, the tracking code may not be installed correctly or may be blocked by a consent management platform that has not yet been configured.

Google Search Console: the search performance side of the picture

GA4 tells you what happens after visitors arrive. Google Search Console tells you how people found your site in search results in the first place. Together they give you the full picture of search-driven lead generation performance.

Search Console needs verification before it provides data. The most reliable method for most websites is adding a DNS TXT record to your domain, which confirms ownership without depending on site code that might change during development or migrations. If you have access to your domain's DNS settings, the TXT record verification method is worth using over the HTML file or tag alternatives.

Once verified, focus on three areas in Search Console:

• Performance report: Shows which queries bring traffic, average position, click-through rate, and total clicks. For lead generation sites, check whether your highest-traffic queries match the pages designed to convert visitors into leads.
• Index coverage: Shows which pages Google has crawled and indexed. Missing pages are invisible to search. If your lead generation forms or contact pages are not indexed, they cannot attract organic traffic.
• Core Web Vitals: Shows performance metrics that Google uses as ranking signals. Slow page load times directly affect both rankings and bounce rates on lead generation pages. If you are seeing poor Core Web Vitals scores, a CDN setup for business websites can often improve load times across the board.

Tracking the conversions that matter for your business

Form submissions are the most obvious conversion for most lead generation sites, but they are not the only one worth tracking. A complete analytics setup captures multiple interaction types that signal intent.

Form submission tracking

GA4 does not automatically track every form submission as an event. Most forms on business websites — contact forms, quote request forms, booking forms — need custom event configuration. This depends on how the form is built.

For WordPress sites using a contact form plugin, the plugin may have built-in GA4 integration or a dedicated integration addon. For custom PHP forms, tracking typically requires adding JavaScript event listeners that fire a GA4 event when the form submits successfully. Here is a simplified example of what that JavaScript looks like:

document.querySelector('form.contact-form').addEventListener('submit', function() {
  gtag('event', 'generate_lead', {
    'event_category': 'Form',
    'event_label': 'Contact Form Submission'
  });
});

This fires a generate_lead event in GA4 when the form submits. You then mark that event as a conversion in GA4 settings so it appears in your conversion reports. The same pattern applies to any form — adjust the selector and event label for each form type.

If your form redirects to a thank-you page after submission, an alternative approach is to trigger the event on the thank-you page load. This is often more reliable because it fires only after the server has processed the form successfully, rather than risking the event firing if the user navigates away before the submission completes.

Phone number clicks and tap-to-call tracking

Many lead generation sites display a phone number with a tel: link. When a mobile visitor taps that number, their phone dials automatically. That interaction is a conversion signal — it shows intent and urgency. GA4 does not track these clicks by default.

Track phone link clicks by adding an event listener to all tel: links on the page:

document.querySelectorAll('a[href^="tel:"]').forEach(function(link) {
  link.addEventListener('click', function() {
    gtag('event', 'phone_click', {
      'event_category': 'Contact',
      'event_label': 'Tap to Call'
    });
  });
});

Mark the phone_click event as a conversion in GA4 to include it in your conversion reporting. This gives you visibility into how many mobile visitors are calling directly from the site.

Chat and chatbot interactions

If your site uses a live chat widget or an automated chatbot, track when visitors start conversations. This data helps you understand how many people engage with support before submitting a form, and whether chat is replacing or supplementing form submissions. AI chatbots for business websites have specific tracking requirements depending on the platform you use, so check your provider's documentation for event integration options.

Email link clicks

Similar to phone links, email mailto: links should be tracked. If visitors prefer to email rather than use a form, that interaction is worth recording. Use the same pattern as phone link tracking but with an href^="mailto:"] selector.

Tracking traffic sources correctly

Understanding where your leads come from requires correct UTM parameter usage and attribution configuration. If UTM parameters are missing or inconsistent, your source data will be unreliable.

Use UTM parameters consistently on every campaign link. A typical structure looks like this:

https://example.com/contact?utm_source=google&utm_medium=cpc&utm_campaign=uk-services-q1

The three core parameters are utm_source (where the traffic originates, such as google, newsletter, or linkedin), utm_medium (the marketing type, such as cpc, email, or social), and utm_campaign (the specific campaign name). Keep naming conventions consistent across your team so reports are readable.

For lead generation sites that also receive organic traffic, the organic source appears automatically in GA4 without UTM parameters. Search Console shows which queries drive that traffic. Combined with your campaign UTM data, you get a complete picture of which channels produce leads.

WordPress-specific analytics setup considerations

WordPress sites often accumulate multiple analytics plugins over time. Having more than one analytics plugin active creates duplicate data, distorts session counts, and makes debugging difficult. If your WordPress site has multiple analytics plugins installed, deactivate the duplicates and keep one primary method of GA4 tracking.

Many WordPress sites use cookie consent plugins to meet UK GDPR requirements. Cookie consent plugins can block analytics until the visitor accepts tracking cookies. Test your form tracking and conversion events after implementing cookie consent to confirm they fire correctly for visitors who accept cookies. Visitors who reject cookies should not generate conversion data from tracking pixels, but the page views themselves can still be recorded in a privacy-respecting way.

If your WordPress site uses a page builder, check that the builder is not injecting its own analytics scripts that conflict with your GA4 setup. A technical SEO audit checklist for service business websites covers these kinds of integration conflicts and how to identify them during a site review.

Custom PHP website analytics considerations

Custom-built websites written in PHP or other server-side languages give you full control over analytics implementation, but also require manual setup for everything. There is no plugin to install. The GA4 tracking code must be added to every page, typically in a shared header file that loads on every template.

For PHP sites with database-backed form handling, form submission tracking should be implemented at the server level where possible, rather than relying solely on client-side JavaScript. Server-side event tracking is more reliable because it cannot be blocked by browser extensions or affected by users navigating away before the page fully loads. GA4 supports server-side tagging through Google Tag Server, though the setup is more involved than standard JavaScript tracking.

If your PHP site uses sessions or cookies to track user state across pages, make sure the analytics implementation respects those same sessions and does not create separate anonymous users for each page view. Inconsistent user tracking inflates visitor counts and makes conversion rate calculations unreliable.

Common analytics setup mistakes on lead generation sites

Tracking forms but not failed submissions. If a form submission fails — server error, validation error, timeout — that is also a signal worth understanding. A high failure rate on quote request forms might indicate a technical problem that is costing you leads.

Ignoring duplicate analytics tools. If you have both GA4 and an older analytics platform running simultaneously, the data will conflict. Choose one primary platform and remove legacy tracking code.

Not filtering internal traffic. If you and your team regularly visit your own website, those visits contaminate your data. Create an internal traffic filter in GA4 using a custom dimension based on IP address or a browser cookie so internal visits are excluded from reports.

Missing thank-you page events. If your forms redirect to a thank-you page, and you only track the page view on that page without a conversion event, the conversion will not appear in GA4's conversion reports. Ensure every thank-you page fires a conversion event.

Not setting up cross-domain tracking. If your lead generation site sits on a different domain from your booking system, CRM, or quote builder tool, visitors clicking between them may be tracked as separate users. Cross-domain tracking links the user journey across both domains.

How to verify your analytics is working before launch

Before launching a new site or making significant changes to your analytics setup, run through a verification checklist. This prevents discovering tracking problems three months later when the data has already been lost.

1. Test every conversion path manually. Submit every form on the site. Click every phone and email link. Complete any quote or booking flow. Check GA4 DebugView after each action to confirm the events fire correctly.
2. Verify real-time data. Open your GA4 real-time report in one browser tab while testing in another. Confirm active users appear and that your test conversions show up in real-time.
3. Check across devices. Test on mobile and desktop. If you have a phone number, test from a mobile device to confirm tap-to-call tracking works.
4. Confirm UTM data flows. Click a UTM-tagged link to your site and verify the source, medium, and campaign data appears in your GA4 traffic acquisition reports within 24 to 48 hours.
5. Review goal completions in reports. After a few days of live traffic, check your conversion reports to confirm that actual business conversions are appearing, not just test data.

When to handle analytics setup yourself and when to ask for help

If you are comfortable adding tracking code to your site and reviewing GA4 settings, a DIY analytics setup is achievable for standard lead generation forms and page tracking. The GA4 interface has improved significantly and most core configuration tasks are documented by Google.

However, some situations benefit from professional help. Custom PHP websites where form tracking requires server-side implementation, multi-domain setups that need cross-domain linking, or sites with complex user journeys across multiple tools are more involved. If you have multiple analytics tools that are not agreeing with each other, a specialist can audit the data flow and identify where discrepancies originate.

Lead generation sites that depend heavily on organic search should also ensure their analytics setup integrates cleanly with their search visibility data. A technical SEO audit checklist for service business websites covers how analytics and search data work together to inform decisions about content and page performance.

What comes after the initial analytics setup

Setting up analytics is not a one-time task. Over time, your lead generation site will add new forms, new landing pages, new marketing campaigns, and new conversion paths. Each of these needs corresponding tracking. Build a habit of reviewing your conversion events whenever you launch a new page or form.

Schedule a regular analytics review — monthly or quarterly depending on traffic volume — to check that the data still reflects how your site actually works. Tracking decay is common. Plugin updates, theme changes, code deployments, and cookie consent updates can all break tracking without obvious symptoms until you notice a sudden drop in reported conversions.

If you are running paid traffic, your analytics data feeds directly into campaign optimisation. Without reliable conversion data, you risk spending budget on traffic that appears to convert but actually does not. The cost of bad data is often higher than the cost of getting the tracking right from the beginning.