GUIDE
Conversion tracking for a service website
A measurement plan starts with the action that matters to the business. For a service website, that is often a successfully submitted enquiry, followed by an assessment of whether it is relevant.
Define the event before installing a tag
Write down the action, the signal that confirms it, the event name, the allowed parameters and who owns the report. Agree how the business will assess the enquiry afterwards.
Keep contact-page visits, email-link clicks and successful form submissions as separate events. Each describes a different stage. The analytics and conversion tracking service can help turn these definitions into an implementation plan.
Use the form result as the trigger
For Contact Form 7 in Ajax mode, wpcf7mailsent signals a completed submission in which mail was sent. Validation errors, spam and mail failures have their own events. The measurement should follow the relevant result.
Check how the chosen form behaves before configuring the event. A button press can be followed by validation failure. A thank-you page needs protection against reloads being counted as new enquiries. Successful sending still needs a separate inbox-delivery test.
Design a small, safe event payload
Useful event details can include a stable form identifier, page type and language. Record only the information required to interpret the result. Keep names, email addresses, message text and other personal details out of the Analytics event.
Also check the page URL, title and campaign parameters. Form values can leak through a redirect or query string even when the event code itself contains no contact fields. Google provides separate guidance for preventing personally identifiable information from reaching Analytics.
Test the consent states
List the analytics and marketing tools on the website and document when each is allowed to run. Test a new visitor, an explicit refusal, an accepted choice and a later withdrawal. Inspect actual network requests as well as the banner.
For this theme, the optional event bridge waits for the configured Complianz permission and an existing Analytics setup. It sends no contact-field values and does not replay earlier actions after consent. Any other tags installed on the site need their own check.
Prevent duplicates and verify delivery
Use one implementation for the agreed form event. Check the theme, tag manager, plugins and any automatic measurement to see whether the same action is being counted twice. Test both language versions and mobile layouts.
Run a valid submission, an invalid submission, a mail-error scenario where feasible and repeated clicks. Record the expected event count. Check the analytics debugging view, the form response and the receiving mailbox separately.
Read the report in context
Review landing pages, channels and key events over a period that provides enough activity for the question. Keep a record of releases and tracking changes. Consent choices, blockers and different measurement definitions affect the available totals.
Combine the aggregate report with your internal assessment of enquiry relevance. Search Console helps with search queries and clicks; Analytics helps describe measured website activity. Compare their trends with attention to their different definitions.
Turn measurement into improvements
Identify the page and step that need attention. A visitor may need clearer service scope, an example, a shorter form or an answer about the process before making contact. Test the proposed change against the agreed goal.
Conversion optimization connects those observations with page improvements. AI visibility measurement adds the separate question of how the business appears in AI search.
Sources
YOUR NEXT STEP
Connect your website activity to useful enquiries.
Tell me what you need to measure and which tools you use. We can review conversion events, reporting and the measurement setup.