GA4 implementation

GA4 implementation should answer a simple question: which marketing activities help acquire customers? At WebHeaven, we combine analytics configuration with tests of forms, telephone links and purchases. You receive an agreed measurement plan, event configuration and an explanation of what the data shows and where its limitations lie.

When to review analytics

You have traffic but do not know where valuable enquiries come from. The advertising platform shows a different purchase count from the store. Forms send messages, but conversions are not recorded. In these situations, increasing the budget before checking measurement makes results harder to assess.

A review also helps after changing a theme, form, domain or payment provider. A Google tag’s presence does not confirm that the right actions are measured. We therefore start with the website’s purpose before selecting events.

What GA4 configuration includes

• Review of the current GA4 property, tags and how they are installed.
• An event map: name, trigger, parameters and business meaning.
• Configuration of agreed forms, telephone clicks and email links.
• For stores: review of product, basket, order and revenue measurement.
• Checks of Google Ads connections and basic reporting.
• Tests, limitations and instructions for reading the key data.

We confirm scope before starting. Custom CRM or application integration and server-side measurement need separate analysis. We do not add tools simply to increase the number of charts.

Forms, calls and purchases are different signals

A submitted form should be measured after successful submission is confirmed, rather than whenever the button is pressed. A telephone click signals contact intent but does not prove a conversation took place. Both events can be useful if the report explains the difference.

In ecommerce, we check purchase values, currencies and transaction identifiers. Google explains using transaction_id to reduce duplicate purchases in the GA4 documentation. We compare sample events with orders instead of treating every purchase event as proof of correct implementation.

Implementation acceptance

We agree test scenarios before work. For a service website, these may include a valid form, an invalid form, a telephone click and reopening the thank-you page. For a store, we add the purchase journey and check whether refreshing confirmation inflates reports.

We account for consent behaviour and browser limitations. Analytics is not accounting and may not record every transaction. The acceptance report should distinguish missing measurement caused by user settings from configuration errors.

What determines the price?

Forms, domains, store type, existing tags, data layer quality and integrations affect cost. A website address and list of actions to measure are enough for initial pricing. Technical access is agreed after the scope is defined.

Questions about GA4 implementation

Does GA4 replace Search Console?

No. GA4 describes website behaviour, while Search Console helps analyse Google visibility. Together they give a wider picture from a service search to contact.

Can existing measurement be repaired?

Yes. We first review the current configuration. A new property is not always needed and can make historical comparisons harder.

What will I receive?

Configured events, agreed test results, limitations and reporting instructions. The quotation records the detailed scope.

Want to know which campaigns generate enquiries? Describe your website and measurement needs. We will define GA4 implementation around how your company operates.

Form measurement: an example acceptance checklist

For each form, record its URL, success condition, event name and allowed parameters. An example checklist separates invalid fields, a correctly received enquiry and a sending error. A success event should correspond only to the second situation.

Tests after a form change

• No success event from a button click alone.
• One event after confirmed receipt.
• No additional success from an ordinary refresh.
• A consistent event name and form context in reports.

Message contents, names, email addresses and phone numbers are not sent to analytics. Where lead quality needs assessment, we agree a separate sales status source and an appropriate way to connect the data.

At acceptance, we record actual test results and consent-related limitations. A completed event table makes errors after theme or form plugin updates easier to identify.