GA4 conversion tracking starts with a clear definition of success. For a service business, that might be a successfully submitted enquiry. For a shop, it is usually a completed purchase. A button click can help explain the journey, but it does not prove that either outcome happened.
Choose the outcome before choosing the event
Write one sentence that says exactly when to count a lead. For example: “Count an enquiry when the form service accepts a valid submission and returns a success response.” Keep failed submissions, form starts and contact-button clicks separate.
A submitted enquiry is still different from a qualified lead. Your sales team may later reject spam, duplicates or requests outside your services. Compare analytics with CRM outcomes so a rise in form submissions is not mistaken for better business.
Write a small event plan
For each action, record its name, trigger, useful parameters and the person who maintains it. Start with the main customer journey rather than tracking every control on the page.
- Service CTA click: record the article slug, placement and destination service as diagnostic information.
- Accepted enquiry: use a lead event after a successful submission. Google documents
generate_leadin its recommended event reference. - Purchase: base it on a confirmed order, with controls to prevent the same order being counted again.
Send descriptive labels rather than names, email addresses, phone numbers or form-message text. Check page URLs too: personal information can leak into analytics through query strings.
Check how each event fires
Look for existing tracking before adding another tag. The same action may already be tracked by site code, a plugin or Google Tag Manager. Choose a single owner for the event and remove overlapping triggers only after checking what uses them.
For a form that submits without loading a new page, a click on Submit is too early. Use the form system’s confirmed-success signal. A thank-you page also needs care: refreshing it or opening it directly should not create another lead.
Test the complete journey
Use a staging environment or an agreed test route so checks do not send unwanted enquiries to your team. Google’s DebugView instructions explain how to inspect test events and their parameters.
- Follow a tagged article CTA to the service page. Check that the article context reaches the form without replacing the visitor’s original acquisition source.
- Try an invalid submission. It should not count as a lead.
- Complete one valid test submission. Check that one success event arrives.
- Test refreshes, retries and mobile use for duplicate events.
- Check consent choices. Missing events may reflect privacy controls rather than a broken tag.
Mark the business outcome as a key event
After verifying collection, follow Google’s instructions to mark the relevant event as a key event. This affects reporting going forward; it does not rewrite historical results. Google Ads conversion setup is a separate decision about what should inform advertising measurement and bidding.
Review accepted enquiries, qualified leads and sales alongside traffic. Record tracking changes and dates so the team can explain a sudden change in the numbers. For the wider search picture, use our content decay audit guide to investigate why visitors may have dropped before they reached the form.