(IMPLEMENTATION GUIDE / SEARCH TO CRM)
A click is a signal.
A received enquiry is a different event.
A useful search measurement system follows what happened after discovery. At JMI, the website enquiry path distinguishes an action on the page from an accepted form delivery and the sales work that follows. Here is a practical way to structure that measurement.
Define the stages before adding tags
| Stage | What happened | What it does not establish |
|---|---|---|
| Discovery | The page appeared in search or an answer surface. | A visit or sales conversation. |
| Contact action | A visitor clicked a diagnosis, email or WhatsApp link. | A message was sent or a request was received. |
| Submission attempt | The form passed browser validation and tried to submit. | The backend accepted the request. |
| Accepted delivery | The intended form-delivery endpoint returned a successful receipt. | Sales qualification or won revenue. |
| Qualified opportunity | The team confirmed fit and the next step in the CRM. | A closed deal. |
Keep Search Console and GA4 connected
Link the verified Search Console property to the web stream that measures the same site. Google’s integration provides query and organic landing-page reports, with its documented reporting delays and dimension limits. Verify the property and hostname before using the numbers.
Do not expect GSC clicks and GA4 sessions to match exactly. They describe different events and are affected by reporting windows, consent, attribution and processing. Compare consistent periods and explain gaps.
Send the lead event on a receipt
For JMI’s native external-form integration, a form-specific observer watches the delivery response without changing the request. The received state and analytics lead event should occur once, after successful acceptance for the intended form. An error, timeout or unrelated request must not trigger success.
- Keep the form ID and destination unambiguous.
- Prevent duplicate success handling for retries or repeated callbacks.
- Keep entered information available when delivery is uncertain.
- Confirm that the resulting CRM record, source tags, service and pipeline are correct.
Keep personal data out of Analytics
A useful enquiry event can describe the form, requested service, business type, market and page language without including the person’s name, email, phone, website field or message. Avoid sending raw form payloads or personal URL parameters to GA4.
Optional Google Analytics measurement should respect the visitor’s choice. A visitor who declines analytics should still be able to submit a valid enquiry. The CRM handles the contact details needed to respond; web analytics measures the consented action.
Give the CRM a clear operating role
Source and service tags help explain where a request came from and what was requested. Pipeline choice and ownership then make the request actionable. A dashboard should distinguish enquiries from qualified opportunities, and qualified opportunities from revenue.
Join business outcomes through a documented, authorized data path. Do not send personal CRM records into an analytics event merely to make two reports reconcile.
A short release test
- Decline analytics and confirm that no Google Analytics request is sent.
- Accept analytics and check one page view with safe page information.
- Check that a CTA or WhatsApp handoff is recorded as an action, not a received enquiry.
- Test success, failure and duplicate delivery handling before counting lead events.
- Verify the live CRM route and monitor reporting latency after launch.
Sources and review
Updated 22 October 2026. Platform guidance and provider pages can change; confirm scope and current details before making a decision.
(your next move)