We create digital solutions that work for businesses
Many websites have GA4 installed but still cannot answer a basic question: which pages and channels generate customers? Page views alone do not reveal whether visitors submit forms, call, open a messenger, book an appointment, or purchase.
A reliable setup starts with a measurement plan. Define valuable business actions, send them as events, mark the most important actions as key events, and verify that every real action is recorded once. The current terminology is important: an action is an event, an important GA4 action is a key event, and that action can become a conversion when used in Google Ads.
Separate actions into three levels: business outcomes, intent signals, and engagement. A confirmed enquiry or purchase is a business outcome. A phone or messenger click signals intent but does not prove that a conversation happened. Scrolls, downloads, filters, video plays, and internal search help diagnose user behaviour.
For a service website, a useful minimum is generate_lead, form_start, phone_click, email_click, and messenger_click. An online store should use recommended ecommerce events such as view_item, add_to_cart, begin_checkout, and purchase.
Document each event’s name, firing condition, parameters, key-event status, and test owner. A shared naming convention prevents one action from being split across lead, form_success, and submit_form.
Create a property, set the correct time zone and currency, and add a web stream for the production domain. Keep ownership inside the business account instead of an agency-only account. Confirm that test-domain traffic is excluded and review the data-retention setting.
The Measurement ID has the format G-XXXXXXXXXX. Avoid creating a new property when suppliers change; historical data is a business asset.
You can use the Google tag, a CMS integration, or Google Tag Manager. A direct tag is sufficient for a simple website. GTM is more practical when the site has multiple forms, ecommerce, advertising tags, consent settings, and custom interactions.
Do not install the same Measurement ID through both a WordPress plugin and GTM. Duplicate installation inflates page views and events. Use Tag Assistant Preview and GA4 Realtime to confirm that one page load produces one page_view.
Enhanced measurement can collect page views, scrolls, outbound clicks, site search, video engagement, downloads, and some form interactions. It is helpful, but automatic form_submit is not always a verified lead.
AJAX forms may not trigger it, and failed submissions may be counted. The robust approach is to send generate_lead only after a success page, form callback, or server-confirmed dataLayer event. Keep form_start as a diagnostic event: the gap between starts and successful submissions reveals form friction.
Send useful parameters with generate_lead, such as form_id, form_name, lead_type, and page location. Add value and currency only when the business has a defensible lead-value model.
Track tel: links as phone_click, mailto: as email_click, and messaging links as messenger_click with a platform parameter. These are micro-conversions, not confirmed leads. Call tracking is needed to measure completed phone enquiries, while CRM integration is needed to assess lead quality and sales.
Avoid arbitrary names such as buy_done. Use purchase with a unique transaction_id, total value, currency, and an items array. The unique transaction ID helps prevent duplicate purchases when a thank-you page is refreshed.
Revenue values should come from validated order data, not scraped page text. Test discounts, delivery, taxes, different payment methods, failed payments, and refunds where applicable.
For service websites, generate_lead is normally a key event. For stores, purchase is essential. Do not mark every scroll or button click as a key event; the resulting rate becomes meaningless.
When importing a GA4 key event into Google Ads, avoid counting the same action as a primary conversion through a second native Ads tag. Choose a clear source of truth and use secondary actions only for comparison.
Use UTM parameters for email, social, partner, influencer, and banner campaigns. Agree on lowercase values and a controlled vocabulary, for example:
utm_source=instagram&utm_medium=social&utm_campaign=summer_offer
Do not mix facebook, Facebook, fb, and meta for the same source. Never add UTM tags to internal links because they overwrite the original session attribution. Connect GA4 and Google Ads and use auto-tagging for Ads traffic.
A cookie banner collects a visitor’s choice; Consent Mode communicates that choice to tags. Review analytics_storage, ad_storage, ad_user_data, and ad_personalization for the website’s actual use cases.
Do not send names, email addresses, phone numbers, or other personal data in event names, URLs, or parameters. The privacy policy must reflect real collection. Legal requirements vary by market, so technical implementation is not a substitute for legal advice.
Open GTM Preview, complete a test action, inspect the trigger and parameters, confirm the event in DebugView or Realtime, and ensure one action creates one event. Test mobile and desktop, all language versions, validation errors, AJAX forms, payment outcomes, and third-party booking flows.
After publishing, compare GA4 with CRM records and test orders. A tag can fire correctly while the business definition is still wrong. Validation must cover both technical delivery and business reality.
Start with five numbers: users by channel, confirmed leads or purchases, key-event rate by landing page, paid cost per lead, and qualified-lead share from CRM. Add a funnel from landing page to service view, form start, and successful enquiry.
If traffic exists but enquiries remain low, link to the BB STUDIO guide about 12 reasons a website gets traffic but no leads and use the data to test the offer, trust elements, form, and mobile experience.
installing the tag twice;
counting a form before server confirmation;
firing multiple events for one enquiry;
treating a phone click as a completed sale;
sending personal data;
marking every interaction as a key event;
using inconsistent UTM values;
omitting transaction_id from purchases;
publishing GTM without Preview and DebugView;
never reconciling analytics with CRM or orders.
GA4 becomes useful when it measures outcomes rather than visits. Start with business actions, use recommended events, separate micro-conversions from confirmed leads, test before publishing, and reconcile analytics with CRM. The goal is not a larger dashboard; it is a reliable answer to which pages and channels create customers.
The standard GA4 product is free and sufficient for most small and medium-sized websites. Analytics 360 provides higher limits and enterprise capabilities.
GA4 stores and analyses data. GTM controls tags and the conditions under which events are sent to GA4 and other platforms.
Automatic tracking may miss a custom form or count an attempt before server success. Send generate_lead only after confirmed submission.
Use Realtime and DebugView for testing. Standard reports can take longer to process, so do not judge a new setup only minutes after publication.
Yes, through an integration, plugin, theme code, or GTM. Use one primary method and verify that the Measurement ID is not loaded twice.
E-commerce
Design & UI/UX
For business
Web development
Let’s create something amazing together Leave your number — we will call you back within 15 minutes during working hours.
We will call you back shortly.
