Google Analytics/GTM

We configure GA4 and Google Tag Manager: container structure, events and key events, ecommerce, consent mode and server-side collection.
Project order

What the configuration covers

From an audit of the container you already have to a document your own team can read to see what is counted and how. The accounts stay yours.

Audit of the current setup

We review what is already on the site: duplicate tags, legacy counters, goals that measure nothing. The output is a prioritised list of errors.

AuditGA4GTM

GTM container structure

One naming scheme for tags, triggers on the dataLayer, variables for parameters, workspaces for changes. A container the next person can actually navigate.

GTMTriggersVariables

Events and key events

An event map with parameters, split into key and analytical events. Forms are captured on the server response, not on a button click.

EventsConversionsdataLayer

Ecommerce

The chain from product view to purchase, with item parameters and protection against a repeated purchase event. We write the specification for your developers.

EcommercepurchaseDev spec

Links to ad platforms

Google Ads, Search Console and the import of key events into the accounts. The algorithms start learning from real enquiries instead of page views.

Google AdsSearch Console

Consent mode and server-side

Consent Mode for the cookie banner, and server-side collection where part of the events dies at the blockers. We add it when the losses are genuinely measurable.

Consent ModeServer-side

Our clients’ results

We build long-term partnerships — and the numbers speak for themselves: our average client relationship lasts 5 years, and our partners' financial results grow quarter after quarter.

Reviews

We build long-term partnerships — and the numbers speak for themselves: our average client relationship lasts 5 years, and our partners' financial results grow quarter after quarter.

How we work

The number of events is not a measure of quality. Thirty events nobody looks at are worth less than eight that decisions are made on.

Fewer events, more meaning

We measure what you actually respond to with budget decisions. The rest is either not collected or kept for reference without being marked as a key event.

Changes in the container, not in the code

As long as a task can be closed in GTM, the site stays untouched. We edit code only where correct data is impossible without a dataLayer, and always together with your developers.

Every event is verified by hand

We walk the journeys ourselves: DebugView, preview mode, the realtime report. A green tag is not proof that the event arrived with the right parameters.

Request a consultation or audit

Tell us about your task and we will suggest a solution and show how it adds up in numbers. The consultation is free, with no obligations.
Error: Please make sure all the required fields are properly filled and try again

What correct measurement gives you

GA4 data does not stop inside GA4: it goes to the ad platforms as a training signal and into reports as grounds for changing budgets. A faulty tag does not stay a reporting problem — it starts steering bids.

01

Advertising learns from the right signal

When the key event is a genuine enquiry, Google Ads looks for people similar to those who really got in touch. When it is a button click, the algorithm looks for people who like clicking.

02

A container that can be handed over

Consistent naming, a note on every version, the event map as a document. The next contractor starts with the work rather than with excavation.

03

Accounts and history stay yours

GA4 and GTM are registered to your company. If our work together ends, the data, the configuration and the access remain where they are.

How we set measurement up

The event map comes first, the tags second. A container built the other way round turns into a landfill nobody dares delete anything from.

01

Audit and access

We take access to GA4 and GTM, review what is running now and compare the number of events with the real enquiries for the same period.

02

Event map

Every action is documented: event name, parameters, trigger, whether it is a key event. The map is approved with you and your developers before implementation.

03

Implementation in GTM

Tags, triggers and variables are built in a workspace; where needed we hand developers a dataLayer specification. We publish as a separate version with a change note.

04

Verification and handover

We walk the user journeys through DebugView and Tag Assistant, then reconcile a week of data. The event map and the access stay with you.

Gift
Show promo code

Additional services

All competencies in-house — complex tasks solved quickly, without losing quality or time on communication between contractors.

Google Ads

Targeted advertising

Display network banner advertising

Call tracking

YouTube advertising

Frequently asked questions about GA4 and GTM

The questions that come up before the work starts.

01

A plugin installed GA4 for us. Is that enough?

For looking at traffic, yes. For advertising, usually not: plugins add the base code and rarely distinguish a successful form submission from a click on a button. The audit shows which of your current numbers are false.

02

How long does configuration take?

A service site with forms and calls usually takes one to two weeks. An online store with full ecommerce takes longer, because part of the work is done by your developers to our specification, and the timeline depends on their queue.

03

Will the site code have to be touched?

It depends on the task. Clicks, forms and messenger links are handled in GTM without a release. Ecommerce, user ID and server-side collection need changes on the site, and we scope those after the audit.

04

Can goals and data be migrated from Universal Analytics?

No. GA4 uses a different data model: events with parameters instead of sessions and goals. We rebuild the logic of the old goals as events, but historical UA data does not move across — it can only be preserved as an export.

05

Do you build end-to-end analytics with a CRM?

We do, but that is a separate web analytics service. This page covers the measurement layer on the site. If you need the enquiry followed all the way to the deal, say so at the brief and we will scope one project.

06

Why a server-side container if the normal one works?

Not everyone needs one. It earns its place when a visible share of traffic is lost to blockers, or when the requirements around personal data are strict. We measure the loss first, then decide whether the server cost is justified.

07

Why does GA4 not match Google Ads?

A gap of up to a quarter is normal: different attribution models, different conversion windows, different ways of counting a session. A larger gap is technical — duplicate tags, lost tracking parameters or redirects that strip them.

08

Who owns the container once the work is finished?

You do. The accounts are registered to your company and we work as users with permissions. The event map and the container documentation are handed over as a document.

GA4 and Google Tag Manager configuration

GA4 and Google Tag Manager configuration

An installed tag does not yet mean usable data. Out of the box GA4 collects page views and a few automatic events, but it has no idea what counts as an enquiry in your business, or how a real form submission differs from a click on a button. That difference is the work. Adcore has been configuring measurement since 2014, with analysts in-house.

The GTM container: triggers, variables, data layer

We build the container so it can still be read a year later: one naming scheme for tags, triggers on dataLayer events or stable selectors, variables for parameters. Every publish stays as a version, so a rollback takes a minute.

Events and key events in GA4

We define what is genuinely measured: a form submission confirmed by the server response, a jump into a messenger, views of decisive screens. Only what advertising pays for is marked as a key event.

Ecommerce tracking

The chain — view_item, add_to_cart, begin_checkout, purchase — with item parameters and transactions free of duplicates. It needs a dataLayer on the site, so we agree code changes with your developers before we start.

Filters, links and consent

We exclude internal traffic and staging domains, link the property to Google Ads and Search Console and configure Consent Mode. Where a visible share of traffic is lost to blockers, we add a server container.

What we usually find in existing setups

Each of these errors damages the statistics in its own way, and none shows up until you check the data by hand.

Configuration errorHow it looks in the report
the GA4 tag sits in the code and in the containerduplicated sessions, a suspiciously low bounce rate
the conversion fires on a button clickmore enquiries in the report than emails in the inbox
purchase fires on every reload of the thank-you pageduplicate transactions and inflated revenue
twelve events marked as key events at onceGoogle Ads optimises towards page scrolling

When this service is the wrong purchase

  • the site is about to move to another platform — the tracking would be built twice;
  • you need enquiries tied to CRM deals and dashboards — that is the broader web analytics service;
  • most contacts arrive by phone — start with call tracking, since GA4 alone misses the main channel;
  • the site has just launched and there is almost no traffic — there is nothing to measure yet.

How this differs from web analytics

What we build here is the measurement layer: correct events, clean data, working links to the ad platforms. End-to-end reporting with a CRM and dashboards is a separate service resting on this configuration. If you need both, we take them as one project.

Who we have worked with

Agency clients include Hyundai, Heineken, Kärcher, CLAAS, Hilti, PepsiCo, Silpo and Materia Medica, plus residential developments and clinic networks.

Adcore digital agency © 2012-2026 LLC "АДКОР" Kyiv, Ukraine