Analytics SpySearch

Buttons for different services lead to the same contact page. Knowing that a user opened “Contact” does not preserve the difference between interest in a vehicle inspection, trace analysis or securing a meeting room.

The website also supports two submission paths: a full message form and a short callback request. Their outcomes had to be distinguished, while separating the choice of contact method from a confirmed form submission.

We designed the intention_click event with parameters describing user intent and service type. Rules use the button text, the page on which it was clicked and the destination URL. “Order trace analysis,” “Check the vehicle now” and “Secure the room” received separate service labels. For “Book an audit” and “Book a discreet audit,” we separated the audit-booking intent, including transitions from the homepage and the About page.

Phone-number and email-address clicks were described with the shared contact_click event and a contact-type parameter. This allows contact-channel choice to be analyzed independently from service-button transitions.

The two Contact Form 7 forms received separate analytics identifiers: contact_form for a message and callback_form for a callback request. GA4 and Clarity submissions were tied to wpcf7mailsent, the form mechanism's confirmation of a successful send. This allows both paths to be distinguished within the generate_lead event.

Before passing a submission to GA4 and Clarity, we added a check of the event-ID format and whether it had already been handled in the current browser session. Only a verified signal triggers the submission tags, limiting repeated processing of the same event.

We also tracked three separate form problems: validation error, message-send failure and spam classification. The lead_form_error event passes the error type and form identifier to GA4 and Clarity, providing a basis for identifying which path contains friction.

In Clarity, we prepared events and labels for service intent, contact type, submitted forms and errors. They make it possible to select sessions connected with a specific action and inspect how that interaction unfolded. We also added Analytics client-ID and session-ID variables.

In Google Ads, we configured the form tag and tags for phone-number and email-address clicks, together with the Google tag and conversion-linking mechanism.

Custom events describe the service, contact channel and form-handling outcome. They do not transmit the content of the enquiry or data entered into fields, which matters given the nature of submissions made to SpySearch.