Field notes

Measuring completed enquiries.

Count confirmed submissions, keep contact clicks separate and test the failed journeys too.

Define the outcome in plain language

A completed form event should mean that the server accepted the enquiry, not simply that a button was pressed. Record separate events for the start of a form, a validation error and a confirmed completion if those steps answer a real reporting question.

Phone and WhatsApp links need different labels. A contact-link click shows intent to leave the website; it does not establish that a call connected, a message was sent or a sale occurred. Keep those categories separate in dashboards.

Write an event specification before adding tags

For each event, define the trigger, the responsible code path, allowed properties and the expected reporting destination. Decide whether repeated actions should be counted again and how duplicate firing will be prevented.

  • Event: enquiry accepted
  • Trigger: confirmed successful server response
  • Properties: form identifier and relevant page context
  • Exclude: message contents, email addresses and phone numbers from general analytics
  • Failure behaviour: show an honest form error without recording a completed enquiry

Validate successful and failed journeys

Test a successful submission, invalid fields, a server failure, repeated clicks and a visitor who has not granted any required analytics consent. Verify the actual request and the reporting view. If the reporting library is blocked, the form should still function.

Campaign attribution also needs consistent naming. Document the campaign parameters you use, and distinguish a technical tracking change from a genuine change in enquiry volume. One test enquiry is useful for validation but is not evidence of an improved conversion rate.

Turn reporting into a decision

Compare a meaningful period using the same event definition and note any website or traffic-source changes. Review qualified enquiries alongside total completions; more spam is not a business improvement. Start with a clear question, such as where people abandon a form, before adding more tracking.

Consent requirements depend on the tools, data and applicable rules. This guide is a measurement design aid, not legal advice or a compliance certification.