Website visits do not show how many suitable prospective customers have reached the business. A phone link click does not mean a conversation took place, and a submitted form does not mean a suitable project.
A service website needs a measurement plan that separates interest, a confirmed enquiry and the outcome of handling it. GA4 records events, but the business defines each event’s meaning and source of confirmation.
Start with questions for the report
Agree on what you want to understand:
- which services generate enquiries;
- where people start a form but do not complete it;
- how many requests the team actually receives;
- how many meet your working requirements;
- which sources bring qualified enquiries and customers.
Then choose the events. Dozens of actions without a clear purpose complicate the report without helping you make a decision.
If enquiries are scarce, first check the customer journey using our plan for a website with traffic but no leads.
Separate interactions from a received enquiry
The events form_start and form_submit help diagnose forms. GA4 enhanced measurement provides them when the relevant option is enabled. Check that measurement works for the particular form. Google’s enhanced measurement event guidance.
An automatically recorded form submission is not a substitute for confirmation that the website accepted the request. For generate_lead, choose a reliable signal: a successful handler response or confirmed creation of the enquiry. Do not trigger it merely when someone clicks “Submit”.
A visit to a thank-you page also needs checking: reopening the page must not create a new enquiry in reporting.
Track clicks on phone and messaging links separately. You can agree on custom names such as click_phone and click_messenger. These are examples of custom events, not standard confirmation of a call or conversation. Confirmation of actual contact requires data from the relevant service or CRM.
Use events for the stages of lead handling
Google recommends a set of events for online and offline lead generation:
- generate_lead — an enquiry was received;
- qualify_lead — the contact was assessed as meeting the qualification criteria;
- disqualify_lead — the contact did not qualify;
- working_lead — interaction with a company representative took place;
- close_convert_lead — the contact became a customer;
- close_unconvert_lead — the contact’s journey ended without becoming a customer.
The names and purposes appear in the official list of GA4 recommended events. These events do not happen automatically just because you use a CRM: transmission of the corresponding facts must be configured.
Define qualification consistently for all staff. For example, agree on suitable requirements, markets and minimum project scope. Do not send qualify_lead immediately after every form: that removes the distinction between a received enquiry and a suitable one.
Create a specification for each event
For each event, record:
- Its name and business meaning.
- The trigger condition and source of confirmation.
- Permitted parameters, such as service type, form and page language.
- How repeated transmission of the same fact is prevented.
- Who is responsible for setup and verification.
- Whether it should be marked as a key event.
You can agree on parameters such as service_type and page_language for your project. These are custom examples. To use them in reports, configure the relevant definitions where required.
Do not put the customer’s name, phone number, email or full enquiry text in ordinary event parameters. Check URLs too: personal data can reach analytics through the page address. Google’s guidance on preventing transmission of personally identifiable information.
Organise the CRM connection
The website usually confirms receipt of the enquiry, while the CRM confirms qualification and subsequent stages. Connecting them requires a matching method, retention of permitted identifiers and control over transmission.
One technical option is Measurement Protocol for server and offline events. Google describes it as a supplement to tag-based collection rather than a universal replacement. Sending an event alone does not guarantee correct linkage with the original session and advertising: a specialist must check identifiers, timing and applicable limitations. Measurement Protocol documentation.
Hypothetical example: the website confirms one development enquiry, and a sales representative then checks whether it fits the service. The first fact triggers generate_lead; the second triggers qualify_lead. Saving the CRM record again without a new status transition must not create another qualification event.
When enquiries are few, comparing specific control records is useful. Do not promise a complete match between total event counts and CRM records: measurement is affected by settings, identifier availability and data collection conditions.
Choose key events deliberately
In GA4, actions important to the business can be marked as key events. This is a separate decision after the event itself has been configured. Google’s key event instructions.
For a service website, consider confirmed enquiries and qualification. Keep a contact link click as a diagnostic metric if it does not confirm the target outcome.
If the data is used in Google Ads, check conversion creation and configuration separately. Do not add an enquiry and its qualification together as two customers in a report. For financial assessment, see our article on CPL and customer acquisition cost.
Measurement acceptance checklist
- A successful form submission creates one confirmed lead.
- A form error or an ordinary button click does not create it.
- Refreshing the thank-you page does not add a duplicate.
- The required service, form and language are retained without personal data.
- Qualification is triggered after a sales representative’s check.
- Saving the CRM record again does not repeat the same fact.
- The mobile version and planned consent states have been checked.
- Events appear in diagnostics, and control records have been compared with the CRM.
Use GA4 DebugView to check event arrival and parameters, then check the operational reports. An event appearing in debugging does not yet confirm that all reporting is correct.
A website audit can begin with a review of the current enquiry journey and measurement plan. Agree on event setup and integrations as a separate scope of work with clear acceptance criteria.