MEASURE MEANINGFUL ACTIONS
A useful measurement plan starts with the decision you need to make. Specify the user action, when an event should fire and how the team will know it represents the intended action.
Import the UTF-8 CSV into your spreadsheet app using comma-separated columns. Save a working copy and replace the fictional example rows.
Separate an enquiry from a click
| Business question | Event | Trigger | Interpretation |
|---|---|---|---|
| Which pages lead to submitted enquiries? | generate_lead | Confirmed successful form submission | A submitted request; qualify it separately |
| Do visitors use the phone link? | phone_click (custom) | Click on a tel: link | Intent to call; not proof of a connected call |
| Which resources are useful? | file_download | Download link click | Download intent; not proof the file was read |
Use the recommended generate_lead event for a submitted form or request. Trigger it from confirmed success rather than the submit button, which can be clicked before validation succeeds.
Fill one row per distinct action
- Write the business question and the action it requires.
- Choose a GA4 recommended event where it fits. Document custom names and parameters consistently.
- Specify the GTM trigger and exact success condition. If an application supplies a data-layer event, agree on its name and timing with the developer.
- Record existing automatic or enhanced measurement so a manual tag does not count the same action twice.
- Document the consent behavior, owner, reporting use and acceptance evidence before enabling a tag.
A safe example payload
{ event: 'enquiry_success', form_id: 'contact', service: 'website_redesign' }This illustrative data-layer event describes the action without names, email addresses, phone numbers or free-text messages. The developer must emit it only after the application confirms success. Map it to the chosen GA4 event in your own implementation.
What to record before release
- One confirmed action produces one event; failed validation produces none.
- The correct event and allowed parameters appear in GTM Preview and GA4 DebugView under your approved test setup.
- The intended consent state and existing tags behave as documented.
- A report owner knows the event’s limits. A phone click is not a sale, and an enquiry is not revenue.
The downloadable plan does not install tags or collect data. Adapt it to your privacy requirements and reporting needs.
Reference: GA4 recommended events.