Measurement contract
Agree which actions need events, which should be key events, and the names, parameters, conditions and owners for each.
GA4 & GTM implementation
Track the actions that matter with GA4 and GTM you can actually test.
Define the events behind your decisions, implement the collection path and prove what fires in real journeys. The scope follows your site, business model and consent requirements.
When implementation needs attention
A property can contain data while still missing the actions needed for useful reporting.
- A new site or product journey has no agreed measurement plan.
- Forms or purchases are recorded inconsistently across pages and releases.
- Events fire, but their parameters cannot describe the action or its value.
- Multiple tags capture the same outcome and nobody owns the test procedure.
What we build
Only the relevant lead, ecommerce and domain journeys become part of the implementation brief.
Collection and GTM
Configure the GA4 collection path and appropriate GTM tags, triggers and variables. Specify dataLayer or developer work when the site must supply reliable values.
Leads or purchases
Instrument real submission or order-confirmation states, including value, currency and transaction IDs when ecommerce applies. A button click alone is not a completed lead.
Journey continuity
Review cross-domain flows and referral context where users move between properties or checkout domains. Reflect the site's consent choices in the tagging plan.
How the setup is tested
Acceptance follows an action from the interface to its event payload and GA4 observation. Tests include relevant consent and repeat-action cases.
Lead form
Submit a valid test enquiry
One completion event with expected parameters after confirmed submission, not on a click or failed request.
Ecommerce
Complete a test purchase when applicable
Purchase payload, value, currency, items and transaction ID checked against the order record; repeats inspected.
Cross-domain
Move through a scoped external checkout or booking step
Tag firing, referral source and journey continuity checked under the applicable consent state.
From requirements to handoff
- 01
Specify
Map business actions, existing tags, consent rules and the people who can change the site.
- 02
Implement
Set up GA4 and GTM, or hand developers a precise dataLayer contract for site-side work.
- 03
Test
Reproduce lead or purchase journeys, inspect event payloads and resolve duplicate or missing signals.
- 04
Hand over
Document definitions, configuration, test evidence, open dependencies and a retest procedure.
What you receive
Measurement plan
Agreed event and parameter definitions, key-event choices and an implementation owner for each dependency.
Configured measurement
GA4 and GTM changes in the agreed scope, including documented developer requirements when GTM alone cannot supply the signal.
QA record
Test journeys, observed payloads, duplicate checks and known limits in the relevant consent states.
Handoff notes
A concise guide to maintaining and retesting the setup after future site changes.
Access and prerequisites
Access is limited to the agreed implementation and remains in accounts you control.
- GA4 property and GTM container access appropriate for review and approved changes.
- A safe test path for forms or orders, plus site or developer access when code and dataLayer changes are needed.
- The domain and checkout journey, existing consent configuration and any measurement documentation.
- Approval to publish container or site changes after the tests have been reviewed.
Scope and next decisions
A full GA4 diagnosis, server-side tagging infrastructure, data warehouse, advertising campaign management and continuing monitoring are separate scopes. A GTM change cannot replace application code when the required business event or value is unavailable.
Your team can use the handoff checks in later releases. Additional advertising conversion signals or broader data integration can be scoped once the base events are dependable.
- Audit an uncertain existing GA4 setup Diagnose before changing tags
- Configure Google Ads website conversions Use validated web actions for bidding
- Set up Meta Pixel and Conversions API Connect the agreed events to Meta
- Plan broader Analytics Infrastructure Connect CRM, product and revenue data
- Design a server tracking path Route selected events after defining source events
- Validate Shopify purchase measurement Trace ecommerce orders through GA4
Questions about GA4 and GTM setup
What is the difference between an event and a key event?
An event describes an observed interaction. A key event is an event selected as important to the business; we decide that status from the measurement plan, not from every available click.
Can everything be done in GTM?
No. GTM can configure and route tags when dependable data already exists. A confirmed order, form success, product detail or stable transaction ID may require changes in website code or a dataLayer contract.
How do you avoid duplicate events?
We map existing tags and test the same journey once and again, including reloads and repeated submissions. Trigger conditions and transaction identifiers are checked where relevant.
How do consent and privacy affect the work?
We check collection in the consent states provided by the site and follow the agreed privacy requirements. This service does not supply legal advice or bypass consent.
Do you include ecommerce and cross-domain tracking?
They are included when those journeys exist and are explicitly scoped. They need test access, reliable site-side values and, in some cases, developer changes.
What happens after implementation?
We hand over the event plan and test evidence. The team can retest after releases, or separately scope monitoring and additional integrations.
Define the work
Make your next GA4 event verifiable
Share the actions you need to measure, the site stack and where the current setup breaks. We can agree on the implementation and tests before changing tags.