TrafficWisp

Conversion measurement

How to measure a contact funnel

By TrafficWisp · Published · Updated

A contact-button click is a promising signal. It is not an enquiry. If you count every click as a lead, you can miss a broken form or a confusing step after the click. A small contact funnel helps you see where the evidence gets stronger and where it stops.

Start with the outcome you can confirm

Write down what a successful contact looks like for your site. For a form, that might be a submission accepted by your server and recorded in your inbox or CRM. For a phone route, it might be a connected call in your call records. A visit to a thank-you page can be a useful proxy if that page appears only after a successful submission, but check that it cannot be reached directly or shown after an error.

Work backwards to the steps you can observe. A simple form journey could be: visit a relevant service page → open the contact page → attempt the form → confirm the enquiry arrived. A phone journey may need a different final check. Keep each route separate so a phone click is not quietly reported as a completed form.

Give each step an honest name

A contact-page view shows interest in the page. A form submit event shows an attempt; client-side validation, a network error or a server rejection can still prevent delivery. A button click is weaker still. Label those figures as views, attempts and confirmed enquiries rather than calling all three “conversions”. Google’s guide to measuring key events likewise starts by defining the particular form submission that matters, rather than treating every form event as the same outcome.

Read the gaps with the right denominator

Suppose 200 measured visits start on a service page, 30 reach contact, 12 attempt the form and seven enquiries are confirmed. In this example, 30 of 200 reached contact, while seven of 12 attempts were confirmed. Those are different questions. The first may point to a weak route from the service page. The second may point to form errors, delivery problems or people abandoning a later step. Inspect the actual journey before changing copy.

Count a person or visit consistently within each step. Do not divide form attempts by page views if one visit can reload the page or submit twice. Decide whether the funnel requires steps in order and within one visit; people who arrive directly on the contact page should not be counted as having passed through a service page. Google’s funnel exploration documentation explains how open and closed funnels can count different entrants. Write your own rule down so comparisons mean the same thing next month.

If the site has only a handful of visits, treat a change in the percentages as a prompt to investigate, not proof. Look at counts, sources and devices. A burst of unrelated traffic can make the overall rate fall while the route for relevant visitors stays healthy.

Check the break before redesigning the page

When many people reach contact but few enquiries arrive, try the form yourself, inspect any error messages and verify delivery. When the form works but few relevant visitors open contact, check whether the service page answers the questions that precede an enquiry and makes the next step easy to find. Our landing-page guide covers that wider page decision.

Measure the same route again after one change. Keep the date, traffic source and device mix alongside the counts. A clearer contact link may raise contact-page visits without raising confirmed enquiries; that is useful to know before making a second change.

See the steps before the enquiry

TrafficWisp is in private beta. Its page journeys and tracked interactions can help you investigate visits and contact attempts. Confirmed enquiries still need a reliable check in your own form or call system.

Request beta access

Further reading