01
Measurement specification
A written event, parameter, value, consent and destination plan tied to the business actions that matter — agreed before anything is configured.
- └event + parameter schema
- └key event → conversion map
- └owner per event
GA4 setup and conversion tracking services
GA4 setup and conversion tracking sales can trust
Digital Otters builds and repairs GA4, Google Tag Manager and conversion tracking for US lead-generation and ecommerce teams. Events, parameters, values, consent states, advertising conversions and CRM outcomes are specified and tested around the actions your business is actually paid for.
US-focused commercial strategyStrategy and implementation in one teamClient-owned accounts and dataClear scope, boundaries and reporting
Implemented and validated in
Google Analytics 4Google Tag ManagerGoogle AdsMeta Conversions APIBigQueryLooker Studio
The short answer
GA4 and conversion tracking: the short answer
GA4 setup and conversion tracking services implement Google Analytics 4 properly — event architecture, key events, ecommerce tracking, Consent Mode, server-side tagging and validated conversion feeds into Google Ads and Meta. Most accounts we audit are measuring something. Far fewer are measuring the thing the business is paid for.
Direct definition: Digital Otters provides GA4 setup and conversion tracking services covering measurement planning, Google Tag Manager, events, parameters, key events, Google Ads conversions, ecommerce, Consent Mode, server-side tagging and implementation QA.
- Scope
- GA4, Tag Manager, consent, server-side, ad platform feeds
- Validation
- Every key event tested end to end before sign-off
- Consent
- Consent Mode configured to your regional policy
- Documentation
- A measurement plan your next hire can read
Commercial deliverables
What you receive from GA4 & conversion tracking
The exact scope follows your current systems, commercial objective and who is implementing.
02
GA4 and GTM implementation
Properties, data streams, containers, tags, triggers, variables, data layers and advertising integrations configured to the agreed scope.
- └container structure + governance
- └ecommerce + lead events live
- └Ads / Meta feeds connected
03
Acceptance testing
Browser, device, consent-state, duplicate, ecommerce and downstream validation, with a documented test log you keep.
- └cross-browser + device checks
- └duplicate + value inflation tests
- └reconciliation vs orders / CRM
Measurement model
GA4 records events. The business still needs a model
Four layers decide whether the numbers can be trusted. Select one to see the requirement, what failure looks like, and the work that fixes it.
Tracking layers
Sign-off rule100%Every key event tested end to end before handover — no partial acceptance.
gtm · dataLayer.push({ event })Foundation
An event name without parameters answers nothing
Events must fire on the real success state and carry page, product, form, value, currency and campaign context. Without parameters and user properties, the event cannot answer a commercial question — only confirm that something happened.
Failure looks like
- Every click marked important, nothing prioritised
- Events named ad hoc per developer or per release
- Thank-you page used as the only success signal
What we implement
- Named event and parameter schema, owner per event
- Success states defined with the business, not guessed
- Data layer specification handed to your developers
Validated via
Tag Assistant, DebugView and event-level checks in BigQuery.
ga4 · key events → AdsDifferent jobs
Reporting and bidding are not the same list
A key event is an event important to business success in GA4 reporting. A conversion is what Google Ads measures and bids on. Treating the two as one list means campaigns optimise toward interactions nobody is paid for.
Failure looks like
- Every key event imported to Ads as a conversion
- Micro-interactions bid on as if they were revenue
- Conversion definitions nobody can explain
What we implement
- A short bidding list agreed with the people paid on it
- Behavioral key events kept for reporting, not bidding
- Every imported conversion documented and dated
Validated via
Google Ads conversion diagnostics and GA4 key-event reports side by side.
consent · analytics_storageBefore the tag
Consent Mode is a signal, not a banner
Consent Mode receives the user's choice from your banner or CMP and adjusts tag behavior. It does not collect consent, it does not replace the banner, and it cannot repair tags that already fired before a choice existed.
Failure looks like
- Tags firing before the banner is answered
- Consent Mode installed with no CMP behind it
- One configuration applied to every region
What we implement
- Consent signals wired to the banner or CMP properly
- Tag behavior tested in every consent state
- Regional configuration documented per market
Validated via
Tag Assistant consent-state checks and per-region network inspection.
server · first-party endpointOptional
Server-side recovers signal, not compliance
A server container routes measurement through a first-party endpoint you control, recovering signal that browser privacy features strip from client-side tags. It does not exempt you from consent — privacy law applies to the data, not the transport — and it adds infrastructure you now own.
Failure looks like
- Server-side sold as a way around consent
- Duplicate conversions from browser and server both firing
- Infrastructure cost and ownership never discussed
What we implement
- Server container paired with a correct Consent Mode setup
- Duplicate control tested across both paths
- A cost and maintenance model handed over with it
Validated via
Server container logs, duplicate checks and reconciliation against orders.
Server-side tagging: what it fixes and what it does not
Server-side tagging routes measurement through a first-party endpoint in a container you control, recovering signal that browser privacy features and blockers strip from client-side tags. What it does not do is exempt you from consent: regional privacy law applies to the data itself, not to the transport. It also adds infrastructure and maintenance you now own. Our implementations pair a server container with a properly configured Consent Mode setup, so recovered accuracy never arrives at the price of compliance — and every recovered conversion is one the bidding algorithms can finally learn from.
Why tracking breaks
A tag that fires is not a number you can defend
Implementation quality depends on naming, parameters, identity, consent and the relationship between behavioral key events and advertising conversions. These five patterns cause most of the tracking we are asked to repair.
Get a tracking review01
Everything is marked important
no priorityGoogle defines a key event as an event important to business success. Not every click deserves that status, and a report where all events matter equally tells no one what to do next.
02
Advertising and analytics use different words
spend on noiseGA4 key events support behavioral reporting; conversions drive Google Ads measurement and bidding. When the two are treated as one, campaigns optimise toward interactions nobody is paid for.
03
Event names arrive without parameters
unanswerable questionsWithout page, product, form, value, currency, campaign or content context, an event can confirm that something happened but never explain what it was worth.
04
Tags fire before the consent choice
compliance exposureConsent Mode receives consent choices from your banner and adjusts tag behavior. It does not replace the banner, and it cannot fix tags that already fired before a choice existed.
05
Testing ends in preview mode
silent breakagePreview confirms a tag fired. Realtime reports, network requests, consent states, duplicate checks, advertising imports and order reconciliation confirm the number is right.
Free tool
Check your GA4 setup in ten questions
Tick everything that is already true of your implementation. The score is a readiness signal, not a verdict on your data — but the gaps it names are the ones we fix first.
Implementation checklist
// Nothing is submitted or stored. Send the result with an audit request if you want us to verify it.
Readiness0 / 24 weighted
0%Rebuild territory
The foundations are not in place. Optimising spend against this data will cost more than fixing it.
Fix first
Have us verify it- Install GA4 and Tag Manager consistently across every page and domain
- Agree key events with the people paid on the outcome
- Add the parameters, values and currency that make an event answerable
Services
What a GA4 and conversion-tracking project can include
We document the business actions before configuring a single tag. Every item ships documented, in accounts you own.
Plan01
Measurement plan
Objectives, events, parameters, user properties, key events, advertising conversions and named owners.
Audit02
GA4 and GTM audit
Existing property, container, tag, trigger, consent and data-quality review with a prioritised fix list.
Setup03
GA4 property and stream setup
Account structure, data streams, settings, retention, internal traffic, access and cross-domain rules.
GTM04
Tag Manager architecture
Containers, tags, triggers, variables, environments, naming conventions and publishing governance.
Leads05
Lead conversion tracking
Form, call, chat, booking and qualified-lead events, with CRM outcomes linked back where possible.
Ecommerce06
Ecommerce event tracking
Item, cart, checkout, purchase, refund, value and currency events via the platform data layer or APIs.
Ad platforms07
Google Ads and Meta measurement
Conversion imports, enhanced conversions, Pixel events and Conversions API planning or implementation.
Consent08
Consent Mode implementation
Consent signals wired to tags, regional behavior configured and every tag state documented.
Server-side09
Server-side tagging
Server container, first-party endpoint, duplicate control and a cost and maintenance model you own.
Delivery process
How a GA4 implementation project runs
Stages vary by platform, but business definitions, data design, implementation, testing, documentation and ownership stay explicit.
01PlanDefine events from business actions
Map the customer journey, commercial outcomes, data requirements and consent conditions before any code is written.
measurement plan02ConfigureBuild GA4 and GTM architecture
Set properties, streams, variables, tags, triggers, parameters, naming conventions and access.
container build03IntegrateConnect advertising, ecommerce and CRM
Implement conversions, values, enhanced or offline data where appropriate and documented.
conversion feeds04ValidateTest browsers, devices and consent states
Use Tag Assistant, DebugView, reports, network checks, duplicate tests and transaction reconciliation.
QA test log05DocumentWrite the measurement specification
Record names, parameters, owners, dependencies, privacy decisions and QA evidence in one place.
spec + handover06MonitorDetect breakage and drift
Review data freshness, event volume, key-event trends and the impact of each site release.
monitoring planMeasurement
What should be evaluated
The work should improve data confidence, customer progression, commercial outcomes and the time your team spends managing the process. GA4 will never reproduce every advertising platform number exactly — and a good implementation explains why.
Implementation controls, not guarantees
- Event accuracyEvents and parameters fire on the intended success state and carry the required context.
- Duplicate preventionBrowser, server and imported events are tested for duplicate counting and value inflation.
- Consent behaviorTags are validated across the consent states and regions your implementation defines.
- Downstream usabilityPriority conversions reach the advertising and CRM systems that actually need them.
Implementation accuracyspec match
Events and parameters match the specification, fire on the intended success state and are not duplicated.
Business coveragejourney
Priority actions and values are measured across the customer journey, not only at the final step.
Consent compliance supportconsent states
Tags respect recorded consent states and the regional configuration your policy defines.
Advertising usabilitybidding
Conversions are available for reporting and bidding with documented, agreed definitions.
Data stabilitydrift alerts
Unexpected volume changes, missing events and release-related failures are detected early.
Client fit
When a tracking rebuild is worth doing
We would rather name a constraint before a proposal than bury it in a tag list. If the right-hand panel describes you, the honest answer is not yet.
Strong fit when
- 01The current GA4 setup is incomplete, duplicated or poorly documented
- 02Marketing and sales can agree which actions are commercially important
- 03Website, tag manager, advertising and consent access can be provided
- 04You want tracking that survives future website and campaign changes
Poor fit when
- 01You want to bypass consent or collect data without lawful review
- 02No one can confirm what counts as a qualified lead, sale or valuable action
- 03The website cannot expose reliable success states or transaction data
- 04You expect GA4 to reproduce every advertising platform number exactly
Engagement model
Pricing follows event scope, platforms, consent and integration complexity
We scope websites, domains, apps, ecommerce journeys, forms, advertising platforms, CRM, consent management, server-side infrastructure, environments and QA. Cloud, consent-management and third-party connector fees remain separate.
01
GA4 and GTM audit
shapefixed projectScope an auditA structured review of properties, containers, events, consent and data quality, ending in a prioritised fix list.
02
New GA4 implementation
shapephased buildGet an estimateMeasurement plan, property and container build, event architecture, QA and documented handover.
03
Lead-generation conversion tracking
shapefixed sprintFix lead trackingForm, call, chat and booking events, Ads and Meta conversion feeds, and CRM outcome linkage where data allows.
04
Ecommerce tracking implementation
shapefixed sprintPlan ecommerceFull ecommerce event set with value, currency, refund handling and reconciliation against real orders.
05
Consent Mode and server-side tagging
shapeproject + retainerDiscuss server-sideConsent signals wired to tags, regional behavior configured, server container scoped, built and duplicate-tested.
You receive a tailored US-dollar proposal with deliverables, responsibilities, milestones, assumptions and support boundaries — plus the order we would run the work in if budget has to be staged.
Request a scopeProof before proposal
Evidence you can review before you sign
We do not publish invented case studies or anonymous performance claims. In discovery we show the structure of the work and agree what proof is relevant to your project.
event-matrix.xlsxanonymized
Event matrix example
The structure we use to define event names, parameters, success states, values and the business owner for each.
└event + parameter schema└success state per event└named owner per eventtag-architecture.pdfanonymized
Tag architecture example
An anonymized container and data-flow diagram showing browser, server and platform destinations before build.
└container + trigger map└consent gating points└browser vs server routingqa-reconciliation.xlsxanonymized
QA and reconciliation log
How test conversions are checked against forms, orders, advertising platforms and CRM records before sign-off.
└consent-state test grid└duplicate + value checks└GA4 vs Ads vs CRM countsPlatforms and tools
The stack behind our GA4 and tracking work
Major, verifiable platforms only — configured in accounts you own, documented so your team can run them.
AnalyticsGoogle Analytics 4
Property architecture, events and key events.
TaggingGoogle Tag Manager
Web and server containers with governance.
BiddingGoogle Ads
Enhanced conversions and offline import.
Paid socialMeta Conversions API
Server-side signal to Meta.
ValidationGoogle BigQuery
Event-level checks and reconciliation.
// All properties, workspaces and data remain under client ownership.
Frequently asked questions
Questions buyers ask about GA4 & tracking
Send your site, current GA4 or GTM access and the actions that matter to sales. A senior consultant replies — not a sales sequence.
Ask a questionWhat is the difference between a GA4 key event and a conversion?
A key event is an important event used in Google Analytics behavioral reporting. A conversion is an important action used to measure and optimize advertising campaigns, including Google Ads conversions created from GA4 key events.
Do you set up Google Tag Manager?
Yes. We can create or restructure containers, tags, triggers, variables, consent settings, environments and publishing governance.
Can you track qualified leads rather than form submissions?
Yes, when CRM or offline outcome data can be linked back to the original lead and campaign identifiers.
What is Consent Mode?
Consent Mode communicates a user's consent choices to Google tags and adjusts their behavior. It works with a consent banner or management platform and is not legal advice.
What is server-side tagging?
Server-side tagging processes measurement requests in a server container controlled by your organization rather than sending every tag directly from the browser. It adds infrastructure and maintenance responsibility.
Can you implement ecommerce tracking?
Yes. We can specify and validate item, cart, checkout, purchase, refund, value and currency events using the platform's data layer or APIs.
How do you test the implementation?
Testing can include Tag Assistant, DebugView, realtime and standard reports, network requests, consent states, duplicate checks and reconciliation against forms, orders or CRM records.
How much do GA4 setup services cost?
Pricing depends on the number of sites, events, forms, ecommerce journeys, advertising platforms, consent requirements, CRM integrations and whether server-side infrastructure is included. We quote the implementation after a tracking audit.
Can you set up Google Ads and Meta conversion tracking?
Yes. Scope can include Google Ads conversions, enhanced conversion support, Meta Pixel events and Conversions API planning or implementation, subject to platform access, consent and technical readiness.
Can you support US privacy and consent requirements?
We can implement the agreed consent behavior and document tag states, but Digital Otters does not provide legal advice. The client should confirm applicable requirements with qualified counsel.
Why Digital Otters
Why US companies choose us for GA4 & tracking
We combine commercial strategy, platform implementation and measurement without taking ownership of your accounts or your data.
// Methodology reviewed against current official platform and search documentation on August 4, 2026.DefinitionsBusiness events before tags
Valuable actions and acceptance criteria are agreed before any implementation code is added.
AlignmentAdvertising and analytics aligned
Google Ads, Meta and GA4 events are designed for their different reporting and optimization roles.
EvidenceTested, not assumed
Every priority event is validated across browsers, devices and consent states, with the log handed over.
OwnershipDocumentation your team keeps
Naming, ownership, test evidence and change-control guidance stay in accounts you own.
Know which conversions are real before you optimize spend
Share your website, current GA4 or GTM access and the actions that matter to sales. We will recommend an implementation and QA plan — and say which part to fund first.
Digital OttersIn the reply
A read on what your current tracking can and cannot proveThe implementation and QA plan we would run, in priority orderWhich part to fund first and what it unlocksA US-dollar range with assumptions written down