What to remember
- Define the business action before implementing the event.
- Use a small naming system that teams can understand.
- Validate events in real time before trusting reports or ad optimization.
Build a measurement plan first
List the customer actions that represent progress: qualified form submissions, booked calls, applications, purchases or other meaningful steps. Separate them from supporting interactions such as scrolls or generic clicks.
Use consistent event naming
A simple naming convention makes reports easier to maintain. Document what triggers each event, where it fires and whether it is considered a key event or conversion.
Track forms carefully
Prefer a confirmed successful submission event over a generic submit-button click. Test duplicate submissions, validation failures and thank-you-page access.
Preserve campaign attribution
Use consistent UTMs for campaigns you control. Avoid overwriting source information with internal links. Document how CRM or offline outcomes relate back to the original source where practical.
QA before trusting reports
Use browser debugging, real test submissions and GA4 DebugView or equivalent validation. Then compare website events with actual leads or transactions.
Document the setup so it survives staff changes
Create a simple tracking register with event name, business meaning, trigger, page or component, GA4 status, ad-platform use and owner. This turns analytics from tribal knowledge into an operating asset.
When the website changes, use the register as a regression checklist. A redesign that changes form behavior or URL structure can silently break measurement even when the page looks perfect.
Useful reports for a lead-generation site
- Landing pages by qualified conversions.
- Source / medium by key event.
- Campaign traffic with consistent UTMs.
- Form completion by device.
- Top organic entry pages connected to conversions.
- Pages with high traffic but weak next-step behavior.
Lead-generation measurement map
Relevant landing or service page viewed.
High-value interaction such as form start or call click.
Successful enquiry submission.
Mark the action that matters to the business.
Add CRM feedback when possible.
Use the data to improve pages and acquisition.
Example: form submission tracking
A form button click is not the same as a successful lead. Track the completed submission after server or client confirmation, then distinguish spam and qualified leads later in the CRM. That creates a more useful chain from marketing source to commercial outcome.
Google Analytics: conversions vs key events · Google Analytics: report on key events
Frequently asked questions
Should every GA4 event be marked as a key event?
No. Reserve key events for actions that genuinely matter to the business.
Can GA4 replace a CRM?
No. Analytics explains behavior and acquisition; a CRM manages contacts, opportunities and sales context.