GA4 / GTM / Google Ads
GA4 and GTM lead tracking checklist before you spend on Google Ads
Before a service business increases ad spend, it should verify that forms, calls, email clicks, source attribution, and Google Ads conversion imports are working. Otherwise the account can optimize toward noisy traffic instead of real leads.
Quick answer: A basic lead tracking setup should include one GA4 web stream, one Google Tag Manager container, verified lead events, Google Ads conversion actions, clean UTM/source attribution, and a test record for every form or contact path. Google recommends the `generate_lead` event when a user submits a form or request for information.
1. Confirm what counts as a lead
Start by defining the action that creates business value. For a service business, the primary lead is usually a qualified form submission, consultation request, phone call, email click, or calendar booking. Do not treat every button click as a lead. Track secondary actions separately so reporting does not inflate performance.
- Primary lead: audit request, quote request, booking, or consultation form.
- Secondary intent: email click, phone click, pricing click, or service page CTA.
- Noise: scrolls, generic page views, or menu clicks.
2. Install one tracking method
Use either the Google tag directly or Google Tag Manager as the source that sends GA4 hits. During a migration, both snippets can exist on the site, but only one setup should send GA4 page views or conversion events. For businesses that will later add Google Ads, Meta Pixel, call tracking, or CRM events, GTM is usually easier to manage.
Google's GA4 setup docs recommend creating an Analytics account, property, and web data stream, then copying the Measurement ID that starts with `G-`. Search Console can also use Analytics for verification when the tracking code is already installed and accessible to the same Google account.
3. Verify the form event
For lead generation, the most important event is the one that fires when a real inquiry is sent. In GA4, use the recommended `generate_lead` event for form submissions or requests for information. Include helpful parameters such as lead source, service interest, and page location.
- Event name: `generate_lead`
- Useful parameters: `lead_source`, `service_name`, `page_location`, `value`, `currency`
- Verification: check GA4 Realtime and DebugView after submitting a test lead.
4. Import only qualified conversions into Google Ads
Once GA4 is receiving the lead event, connect Google Ads and import the right conversion. Be careful here: if every email click or half-completed form becomes a primary conversion, automated bidding can chase low-quality actions. Keep the strongest lead event as primary and use lower-intent actions as observation signals.
5. Test every path from mobile
Most tracking failures happen in small details: a mobile email link opens but does not fire an event, a form uses a different thank-you state, or a landing page has a duplicate tag. Test the site from a phone, submit one lead per page, and confirm that GA4 shows the source and page where the lead started.
6. Document the baseline before optimizing
Before changing campaigns or SEO pages, capture the current state: indexed pages, organic impressions, lead count, conversion rate, and the pages that generated inquiries. That makes future improvement visible and keeps the work tied to revenue instead of vanity metrics.
Sources and setup references
- Google Analytics Help: set up GA4 for a website
- Google Search Console Help: verify site ownership
- Google Developers: GA4 recommended events
Need this checked?
Send me your website, the lead action you care about, and whether you already have GA4, GTM, or Google Ads access. I will tell you what I would fix first.
Request Tracking Audit