A B2B website can attract visitors without producing relevant enquiries. It can also generate valuable conversations that are difficult to connect with a single visit. Measurement needs to recognise both realities.
Google Analytics 4, or GA4, helps you understand recorded website activity and useful actions. The value comes from choosing the right events, checking how they are collected and interpreting them alongside your business's wider sales process.
How do GA4 events and key events work?
GA4 uses events to record interactions, such as page views or configured form-success actions. Events that matter particularly to your business can be marked as key events.
GA4 calls these important actions key events; Google Ads conversions are a related but separate advertising measurement concept. If you use GA4 data in Ads, check the configuration and counting rules rather than assuming both tools report identical totals.
Some interactions can be collected automatically or through enhanced measurement. Others need implementation specific to your website. Automatically collected form activity should be validated before you treat it as a confirmed enquiry.
Which actions should a B2B website measure?
Begin with the outcomes the website supports. A successful enquiry submission may be a primary action. A technical download or a contact-link click may show interest without confirming a conversation.
Keep different signals distinct
- Confirmed form success: a request accepted by the relevant system.
- Phone or email click: an attempt to open a contact route, not proof of contact.
- Resource download: access to useful content, not necessarily buying intent.
- Booking confirmation: a completed booking, distinct from opening the scheduler.
- Sales qualification: a later business outcome usually held in a CRM.
Use consistent event names and document their meaning. Marking every interaction as a key event makes it harder to distinguish genuine outcomes from routine browsing.
Trigger tracking at the right point
A submit-button click is not reliable evidence that a form succeeded. Validation may fail or the server may reject the request. Where practical, trigger the success event from confirmed application behaviour.
Prevent duplicate recording when both website code and a tag manager track the same action. Test repeated clicks, page reloads and failed submissions, not just the successful path.
Third-party forms and booking systems may need separate configuration. Where an integration is restricted, make the measurement limitation explicit rather than reporting an approximation as a completed action.
Configure privacy and consent deliberately
Review consent and data protection requirements for your audience and jurisdiction. A consent-management setup should control analytics behaviour as intended; Google Consent Mode is not itself a consent banner or a guarantee of compliance.
Do not send names, email addresses, message contents or other prohibited personally identifiable information to GA4. Check event parameters and URLs, including pages where form data could appear in a query string.
Consent choices, browser restrictions and blockers can leave gaps in observed data. GA4 should not be presented as a complete record of every customer interaction.
Keep campaign and attribution context clear
Use consistent campaign parameters for appropriate external links, such as email and paid social activity. Avoid using campaign tags on internal navigation, where they can confuse interpretation.
Review attribution settings and reporting scope before comparing channel results. A B2B buying journey may involve several visits, devices and people. Analytics can support that discussion without establishing exactly which touchpoint caused a sale.
Test events and reconcile outcomes
Use suitable debugging tools, including GA4 DebugView where applicable, to check event names and parameters. Verify consent states, devices and any third-party journey your reporting depends on.
Compare recorded enquiry events with form-system records over an agreed period. Investigate differences while recognising that consent and collection limitations may prevent an exact match. Review CRM outcomes separately to understand enquiry quality.
Trustworthy tracking starts with clear definitions.
BBI connects website functionality with practical reporting. Agreeing what an action means and testing the full journey makes the resulting data more useful for decisions about content, campaigns and website improvements.
Check your most important action first
Choose your main enquiry or booking journey and verify its success, failure and duplicate behaviour. A small number of dependable events provides a stronger foundation than a large collection of unchecked signals.

