Google Analytics 4
Setting up or reworking the GA4 property with meaningful events, useful parameters and key events marked as conversions.
Analytics, tracking & conversion measurement
Analytics, Tracking and Conversion Measurement for Decisions You Can Defend
Professional tracking doesn't start with a tag — it starts with a question: which action on your website actually matters commercially? Only then come the measurement plan, the dataLayer, Google Tag Manager, GA4 and consent-aware firing. TRIKI DIGITAL sets up that chain so your numbers stay explainable.
Professional analytics and tracking includes a measurement plan tied to business goals, a consistent event and conversion schema, a clean dataLayer implementation, Google Tag Manager configuration, Google Analytics 4 as the reporting layer, and consent-aware activation through Consent Mode V2. Reliable data matters because without it you cannot tell which page, campaign or contact path actually produces enquiries — and budget gets allocated on gut feeling. Properly measured events such as form submissions, WhatsApp clicks or audit interactions show where visitors drop off and where investment is justified. Consent and privacy are part of the implementation from the start: analytics and marketing tags only fire after the corresponding permission, the choice stays revocable, and only the data the measurement plan justifies is collected. TRIKI DIGITAL implements GA4, GTM, Consent Mode V2, event and conversion tracking, plus implementation-ready setups for Google Ads, Enhanced Conversions and the Meta Pixel.
Common tracking problems
Nearly every setup measures something. The difference is whether the numbers can carry a decision — or merely reassure.
- Page views are recorded but leads are not — the action that matters never appears in reports
- Duplicate events caused by tags installed twice or two measurement methods running at once
- Missing conversion events: the form sends, but nothing measurable happens
- Tags firing before consent, producing values that are questionable both legally and analytically
- Inconsistent event names, so reports cannot be consolidated
- No distinction between qualified and unqualified leads
- Broken thank-you-page or cross-domain tracking, leaving sessions cut in half
- Unreliable ad attribution, and differences between GA4 and the advertising platforms
The TRIKI DIGITAL approach
We build tracking backwards: business goal first, then the metric, then the event — and the tag last.
Define business goals: what should the website achieve, and how would you recognise it?
Write the measurement plan: goals, metrics, events, parameters and ownership, in writing
Set the event and conversion schema so naming and structure stay identical across the site
Implement the dataLayer so events come from the page, not from brittle click rules
Configure Google Tag Manager: tags, triggers, variables and consent conditions
Consent-aware activation via Consent Mode V2 instead of firing everything unconditionally
Test in GTM Preview and Tag Assistant, verify in GA4 DebugView before going live
Hand over documentation and monitor continuously, so site changes don't quietly break measurement
What TRIKI DIGITAL implements
Google Tag Manager
A structured container with readable tags, triggers and variables, and documented versions.
Consent Mode V2
Signals denied by default, granular categories and a consent update after the choice — tags wait for the user.
Event and conversion tracking
Defined events for the interactions that matter, and an explicit decision about which of them count as conversions.
Form and WhatsApp click tracking
Measurement of form start, submission and confirmation, plus clicks on the WhatsApp contact.
Audit and assistant interactions
Tracking when the AI mini-audit is started and completed, and when the chat assistant is opened.
Google Ads & Enhanced Conversions — ready to implement
Technical readiness for Ads conversions and Enhanced Conversions. Activation only after explicit approval and account access.
Meta Pixel — ready to implement
A prepared, consent-bound Meta Pixel integration. It is never switched live without agreement.
Custom dataLayer events
Bespoke events for flows no standard tag covers, with defined fields and firing points.
Funnel measurement and reporting workflows
Measuring the path from first contact to enquiry, plus automated recurring reports.
Monitoring, QA and debugging
Reviewing existing setups, removing duplicate events and checking on an ongoing basis that measurement still works.
Who this fits
Local businesses
Companies that want to know whether calls, forms and WhatsApp contacts really come from the website.
Service providers
Businesses with enquiry and quote processes that want to see the path to a qualified lead.
E-commerce businesses
Shops that want cart, checkout and drop-off points measured cleanly and with consent respected.
Agencies
Providers needing comparable measurement standards and dependable reporting across several clients.
Education providers
Course and programme providers with sign-up flows who want to see where people drop out.
Startups
Teams that need to understand early which channels and pages genuinely create demand.
Businesses running Google Ads or Meta Ads
Advertisers who can only steer budget properly when conversions are reported back correctly.
Businesses without reliable conversion data
Anyone currently seeing only page views and unable to draw a decision from them.
How a tracking project runs
- 01
Goals & current state
Clarify business goals and review the existing setup: tags, events, data quality and gaps.
- 02
Measurement plan & schema
Events, parameters, conversions and naming conventions are documented and agreed.
- 03
Implementation
dataLayer in the code, configuration in Google Tag Manager and connection to GA4 — always consent-aware.
- 04
Testing & sign-off
GTM Preview, Tag Assistant and GA4 DebugView, including behaviour before and after consent.
- 05
Documentation & operation
Handover of documentation, reporting setup and ongoing checks for measurement outages.
Privacy, consent and control
- Categories stay separate: necessary functionality, analytics and marketing are distinct choices
- Consent Mode V2 with analytics and advertising signals denied by default, updated after the choice
- Consent-aware firing: no analytics or marketing tag runs before permission is given
- The choice can be revoked at any time through the cookie settings in the footer
- Data minimisation: only the events and parameters the measurement plan justifies are collected
- Traceability: documented tags, triggers and data flows instead of a container that grew by accident
- A legal review of your privacy notices by a qualified party may still be necessary — we deliver the technical implementation, not legal advice
Example measurement flow and events
Example measurement flow
Website visit → CTA interaction → form start → form submission → qualified lead → thank-you confirmation → CRM or workflow update. The exact setup depends on your systems.
Example event names
generate_lead, form_start, form_submit, audit_start, audit_complete, whatsapp_click, chat_open, pricing_view, service_cta_click. Final naming is fixed in the measurement plan.
Qualified, not just submitted
A submitted form is not yet a usable lead. Additional parameters make it possible to tell which enquiries actually fit.
Thank-you page as a checkpoint
The confirmation page acts as an extra verification point so submissions aren't counted twice — or missed entirely.
Differences between GA4 and ad accounts
Attribution models and consent signals differ, so the numbers differ too. The measurement plan defines which source is authoritative for what.
Reporting instead of raw data
The measured events feed a recurring report built around the metrics decisions actually need.
Frequently asked questions about analytics and tracking
Why isn't Google Analytics 4 enough on its own?
GA4 reports what it is given. Without a measurement plan, defined events and a clean implementation you mostly see page views and sessions, not the interaction that led to an enquiry. The value is created before GA4 ever sees the data.
What does Google Tag Manager do?
It is the control layer: it decides which tag runs on which trigger and under which conditions, including the consent check. That lets measurement evolve without editing the website code every time.
Does tracking work without consent?
Analytics and marketing tags do not run without permission. With Consent Mode V2, cookieless signals are sent instead, from which Google can model some values. Those figures are less detailed than with consent granted.
What is Consent Mode V2?
Consent Mode V2 is the interface through which your site communicates analytics and advertising consent status to Google. Signals start as denied and are updated after the choice in the banner. Visitors can change that choice later via the cookie settings.
How is a conversion defined?
In the measurement plan. We decide together which action carries commercial weight — a submitted enquiry, a WhatsApp contact, a completed mini-audit — and mark only those as conversions. Everything else stays context.
Can Google Ads and Meta Ads be connected?
Yes, the connection is prepared technically: Google Ads conversions, Enhanced Conversions and the Meta Pixel can be added in a consent-bound way. They are activated only after explicit agreement and with access to the relevant ad accounts.
How is existing tracking audited?
We review the container, tags, triggers and events, test in GTM Preview and Tag Assistant, and compare behaviour in GA4 DebugView — before and after consent. The output is a list of concrete findings: duplicates, missing conversions, inconsistent names.
Do small businesses need professional tracking?
As soon as budget goes into ads or content, the question is fair. A small, well-measured set of three to five events is usually worth more than a large setup nobody trusts. Scope follows the decisions you actually want to make.
Next step: have your measurement reviewed
Start with the free AI mini-audit, or describe in a few lines which numbers you're missing today. You'll get a first assessment of measurement gaps, duplicate events and consent-aware implementation.
Start the mini-audit