GA4 & GTM Setup

A measurement setup that comes out of your website, not out of a template.

Mateq scans your pages, proposes the events that genuinely exist there, and — once you approve them — builds the whole configuration in Tag Manager, publishing included.

Book a demo

What does a GA4 and GTM setup consist of?

A complete setup is more than one installed tag: a GA4 configuration, triggers for the interactions that matter, variables for the data behind them, an event tag per interaction, the important events marked as GA4 key events, optionally a server-side layer on your own tracking subdomain — and finally a published container version that holds it all together.

Where do-it-yourself setups come apart

Creating individual tags is easy. Staying consistent is not: triggers, variables, and tags have to reference each other correctly, and the version has to be published. That is where hand-built containers accumulate their debt — a renamed element here, an orphaned trigger there.

The second problem is derivation. Off-the-shelf "GA4 starter containers" measure what an average website does. Your website is not average: it has particular forms, particular buttons, maybe a booking widget that changes views without a real page load.

And third, a setup is not finished when it is published. Websites change; a relaunch can invalidate every trigger without anyone noticing.

What Mateq actually creates

GA4 configuration

Configuration tag with your measurement ID, plus a Conversion Linker where one does not already exist.

Event tags and triggers

One per approved event — either as a dataLayer variant or as granular tags per interaction.

Form and click capture

Listeners and variables that capture form submissions and relevant clicks, with no per-event code on the page.

SPA and e-commerce triggers

History-change triggers for view changes, and triggers for cart, checkout, and purchase events.

GA4 key events

Events you marked as conversions are set as key events through the GA4 admin API.

Optional server side

Server container including hosting and a first-party tracking subdomain — you add exactly one DNS record.

The sequence, step by step

1
Connect
Connect your Google account via OAuth; you pick the GTM account, container, GA4 property, and data stream.
2
Scan
Mateq opens your website in a real browser and detects forms, clicks, e-commerce steps, SPA route changes — and whether a consent banner is present.
3
Approve
You decide per event whether it gets tracked and whether it counts as a conversion. An optional AI review proposes additional events — you confirm those individually too.
4
Implement
Mateq creates the GA4 configuration tag, Conversion Linker, triggers, variables, event tags, form listeners, e-commerce and SPA triggers, and optionally Meta Pixel tags.
5
Publish
A container version is created and published, and the chosen events are marked as key events in GA4 at the same time.
6
Verify and repeat
Mateq then checks in a real browser whether the events fire — and repeats that weekly or daily depending on plan.

What a typical website ends up with

A twelve-page services website with two forms, contact clicks, a brochure download, and a booking widget:

Illustrative example

Detected in the scan: 2 forms, phone/email clicks, 1 download, widget with view changes
Approved as conversions: 2 (form, phone click)
Created in the container: GA4 configuration, Conversion Linker, form trigger + tag, click tags, history-change trigger
Set in GA4: 2 key events
Developer effort: no ticket

The build follows what the scan found — not a list of standard events that do not exist on this site.

What Mateq sets up, and what it deliberately does not

"No code on your website" is meant literally, with one footnote: everything runs through Tag Manager, so you never paste snippets per event. Tag Manager itself has to be installed on the site — which it usually already is.

On consent, Mateq stays with what it really does: it detects common consent banners and your site's Consent Mode v2 status and takes both into account during verification. It does not configure consent for you.

Nor does Mateq audit your existing GA4 property for settings, data retention, or attribution models. The focus is building measurement for performance marketing — not reviewing your analytics configuration.

For the server-side layer the rule is the same: Mateq provisions the infrastructure and verifies what is provable from outside — DNS, SSL, and the published container. What a platform books server-side is not something we claim.

Common questions about GA4 and GTM setup

What is the difference between GA4 and Google Tag Manager?

Tag Manager decides which event fires when and with what data — it is the control room. GA4 is one destination for those events, and the place where an event counts as a key event, meaning a conversion. A clean setup needs both.

Do I have to add code to my website?

Not per event. The configuration is built in Tag Manager and delivered from there. The only prerequisite is that Tag Manager itself is installed on the site.

What happens to my existing container?

Mateq works inside your container, creates the missing elements, and publishes a new version. Existing tags that Mateq does not manage are surfaced in the verification report so you keep the full picture.

How much work is the server-side setup?

For you: one DNS record. Mateq creates and publishes the server container, handles the hosting — you do not need your own account with the hosting provider — and registers the tracking subdomain. DNS and SSL are then checked automatically.

Let the setup come out of your website

Run the scan, approve the events, have the container published — then verified in a real browser.