Track enquiries, calls, and bookings

A conversion is a business action worth measuring. GA4 calls an important action a key event.

Webrenew's base GA4 and Meta tags do not automatically confirm leads, calls, bookings, or revenue. Those need event setup.

1. Use generate_lead for a successfully accepted enquiry, after the form's success response.
2. Use a separate phone_click event for a phone-link click. A click does not prove that a call connected.
3. Use a booking provider's confirmed-appointment event for a completed booking.
4. Keep failed submissions, spam, button clicks, and page views out of the confirmed-lead count.

The default No hosting form only prepares an email. An open email app does not prove that the visitor sent the message.

• Google recommended event definitions

Use this no-code GA4 option only if the form already redirects to a dedicated confirmation URL after success.

Webrenew does not create that redirect when an owner saves an Analytics ID. Ask the form provider or developer to confirm the behaviour.

1. Submit a test enquiry and copy the final confirmation URL.
2. In GA4, open Admin → Data display → Events → Create event.
3. Name the event thank_you. Select Create without code and the correct web stream.
4. Choose page_view as the source event. Enter the dedicated confirmation URL in the URL condition.
5. Mark it as a key event, choose the counting method, and save.
6. Test successful and failed submissions before using the event in reports.

Direct visits and reloads can count again. Treat this as a confirmation-page proxy. Use a success event for reliable lead deduplication.

• Google no-code event setup

Use a developer or a supported form integration when success happens inline, in an external booking tool, or without a unique URL.

1. Ask for generate_lead only after the server accepts the enquiry and returns a unique success reference.
2. Keep one event per accepted enquiry, including after a refresh or retry.
3. Send only approved non-personal parameters, such as service type. Do not send form text or contact details.
4. Test the event in DebugView, then mark it as a key event under Admin → Data display → Events.

Goal: measure accepted quote requests.
Event: generate_lead after confirmed success.
Do not count: clicks, invalid forms, spam, or failed requests.
Deduplicate: one event per accepted enquiry.
Privacy: honour consent. Exclude personal data.
Proof: one success event, zero events for each failure case.

For external bookings, confirm the provider's supported integration and cross-domain setup. A click to the booking page is only an outbound click.

• Mark a GA4 event as a key event

For phone links, ask a developer to emit phone_click when a visitor activates a tel: link. Keep this a secondary intent signal.

To measure connected calls, use a call provider's supported conversion integration. Define a qualified call with the team before choosing an event.

For external appointments, start with the booking provider's official analytics integration. Track the confirmed appointment, not the calendar-open action.

1. List every phone and booking link on the website.
2. Ask the implementer to identify the supported event and the account that receives it.
3. Test a phone click without placing a call. It must not report a connected call.
4. Complete one test appointment, then cancel it. Check how both actions appear in the provider's records.
5. For cross-domain analytics, configure both domains through the supported integration and test the complete journey.

If the provider cannot send confirmed outcomes, record them manually. Label click events as clicks in reports.

• Google cross-domain measurement

Keep a dated record of the test URL, event name, and outcome. Use test contact details controlled by the business.

1. Connect Tag Assistant to the live domain. Open GA4 DebugView for the test device.
2. Submit one valid request. Confirm that the team receives it and exactly one intended event appears.
3. Submit an invalid form. Confirm that no success event appears.
4. Test a failed request with the developer. Confirm that no success event appears.
5. Reload the confirmation or success screen. Check for duplicate events.
6. Test the configured consent decline, acceptance, and withdrawal paths.
7. Repeat the normal customer journey on mobile.

Do not send paid traffic until the event represents the intended result. If a proxy still counts duplicates, label that limitation in reports.

• Inspect events in DebugView

For Google Ads, link the correct GA4 property and create a conversion from the verified key event. Check its goal and optimization settings.

Use one intended primary conversion for bidding. Keep duplicate measurements secondary so one enquiry does not count twice.

For Meta, the hosted Analytics tab accepts a Meta Pixel ID and installs PageView. A Lead or booking event requires additional setup.

1. Test the platform's event before selecting it as a campaign goal.
2. If both browser and server events exist, ask the implementer to verify platform-specific deduplication.
3. Compare ad-platform results with the actual lead record before increasing spend.

Platform attribution differs. Two platforms can claim the same customer. Do not add their conversion totals together.

• Google Ads conversions from Analytics
• Ask for help with event setup

Do not report the full job price as revenue when someone only asks for a quote. Record won work separately.

If a lead value helps planning, use a documented estimate and label it as an estimate.

Example: 1 in 4 qualified enquiries becomes a job with $400 contribution before marketing. The expected contribution is $100 per qualified enquiry. Actual results can differ.