Start with a question for the data
Instead of collecting every possible event, ask which pages help visitors contact the business. A relevant page view and contact click may initially be enough. Measuring sale cost requires a confirmed inquiry, deal outcome and an agreed connection to the advertising source.
Name the metric owner. They should know which source confirms the result and which information is still missing. The website, messenger, CRM and payment provider observe different parts of the journey; one counter does not verify everything.
Write an event specification
- Name and condition: for example, a hypothetical contact_click fires on a particular button click, not on page load.
- Parameters: page, language and contact channel; send an agreed minimum without message text or visitor contact details.
- Evidence source: a browser action, a confirmed form submission or external-system status.
- Check: test steps, expected event count, no unwanted repeat and a named result owner.
Separate an action from a confirmed outcome
In GA4, generate_lead represents submitting a form or request for information. Clicking a messenger link without confirmation of sending does not satisfy that condition. If confirmation is absent, call it a contact click and show that limitation in the report.
A sale needs its own outcome source. Do not convert a form’s success screen into revenue. If CRM or payment data is not connected to analytics, agree the integration and acceptance first; do not fill missing stages with assumptions.
Official source: Google Analytics: recommended events
Run one scenario before publishing
Hypothetical test: open a service page with a test campaign tag, click contact once and check the event name, language, page and count. Repeat with a double click, back navigation, a form error and another language. Save expected and actual results.
GTM preview helps check tags before publishing. Then verify event receipt in the chosen analytics tool and repeat the scenario on the published page. A working tag alone does not prove a correct business metric.
Official source: Google Tag Manager: preview and debugging
Hand over a metric dictionary
For each metric, document meaning, condition, parameters, source, known limits and test date. Agree access, visitor-consent handling and the event-change procedure. Repeat affected checks after editing a form, language switcher or contact button.
Keep clicks, confirmed inquiries, qualified leads and sales separate in reports. Make missing data at any stage visible. This lets you compare channels under the same rules without presenting technical activity as a business outcome.
Discuss your project
Tell us your goal, languages and required functions. We will agree on the scope and next steps.