Project tracking-measurement-rebuild-for-one-site · revised 11 October 2026
Project
Rebuild the measurement of one website so each number can be traced to a test
One site gets a measurement plan, a data layer specification, a clean container and the agreed events, each proven with a named test.
This asks for a proposal by email. Nothing is charged, and nothing starts, until you have agreed the list, the price and the terms in writing.
The result you are buying
Measurement has grown by accident: tags from earlier agencies, events with inconsistent names, no written list of what matters and no tests. Fixing one event at a time does not help when nobody knows which events should exist or how to prove them.
Who it’s for: A site owner, marketer or agency inheriting a site whose analytics nobody trusts and no one can explain.
Usually starts when: A redesign, a platform change or a change of agency left old tags, missing events and numbers that disagree with the business.
The result: You buy the rebuilt measurement, not the individual tags. Every event in the agreed plan has a specification, an implementation and a named test with evidence, the container is documented, and Search Console is linked to the right stream.
How the work fits together
The project is complete when every event in the agreed plan has passed its named test and you have accepted the plan, specification, container version, test book and Search Console link. You accept the finished set, not each internal step.
Clean up one Google Tag Manager container so every tag has a reason Job Included
One Tag Manager container is inventoried, stripped of unused and duplicate tags, and saved as a named version for you to publish, with a before and after test.
The container is documented and cleaned first so every later change can be tested.
Get one GA4 key event recording again, proven with a test event Job Included
One named action on your site produces one GA4 event with the agreed name, visible in DebugView and then counted as a key event.
One for each key event in the agreed plan that does not record correctly
After: Clean up one GTM container
Count successful enquiry form submissions in GA4 for one form, ignoring failed attempts Job Optional
One form sends one named GA4 event only when a valid submission succeeds, with no personal details in the event.
One for each form in the plan, up to three, if the plan includes them
After: Clean up one GTM container
Send your shop's GA4 funnel events: view item, add to cart, checkout and purchase Job Optional
One store sends view_item, add_to_cart, begin_checkout and purchase with items, currency, value and transaction ID, checked in DebugView, one report and one exploration.
For shops only.
After: Clean up one GTM container
Keep one visitor as one visitor when your site hands them to a separate checkout Job Optional
A test journey from your site to your checkout domain stays in one GA4 session, with the checkout not listed as the traffic source.
Only if a separate checkout or booking domain is used.
After: Clean up one GTM container
Make your cookie banner's choices reach your Google tags in the right order Job Optional
Consent defaults load before any tag, a banner choice updates them, and Tag Assistant shows the same states you agreed with your own policy.
Technical wiring from your own policy; not legal advice.
After: Clean up one GTM container
Keep your key tracking events working, with scheduled tests and a monthly report Standing service Optional
We run your named test events on the live site on an agreed schedule and tell you with evidence when one stops firing or changes.
Offered after handover to keep the tested events working.
After: One GA4 key event recording
How an engagement works
The price covers the agreed event list only. Extra events are quoted separately; items that need platform changes we cannot make are named and re-scoped with you.
How it starts
You send the site address, the five actions that matter most and what you distrust today.
We review the site and propose the measurement plan and a fixed price for the agreed event list.
You agree the plan, price and terms in writing. Nothing starts before then.
We write the specification, clean the container, build the events and run the tests, sending each result for your review.
You create the Search Console link as the property's verified owner, following our written steps; we publish its reports in the property library, check that they load, publish nothing without your approval, and send the handover note and test book.
Who decides what
You decide the plan, approve each change and publish. Search Console ownership and GA4 admin rights stay with you, and you create the Search Console link yourself, because Google requires a verified owner of the Search Console property to create it.
Handover
You receive the plan, the specification, the test book, the named container version and the inventory. Anything unfinished is handed back with notes.
Sharing your product safely. Send a description and the site address, never exports with personal data. Before work starts we agree with you in writing which identity receives the scoped roles.
What is included, and what is not
- The measurement plan and the data layer specification as documents you keep
- A container saved as a named version, with an inventory of every tag, trigger and variable
- A test book: every event, its test action, expected parameters and DebugView evidence
- Written steps for creating the Search Console link, and a short handover note on who owns what and how to check each event again
Included
- One website, one GA4 property and web stream, one web container
- A written measurement plan: the business questions, the events and key events that answer them, and who uses each
- A data layer specification for the pages and actions in the plan, with names and example values
- A cleaned container (up to 50 tags; a larger container is quoted first) and the agreed events built and tested; optional parts added from the list of components
- Search Console linked to the web stream, created by the verified owner of the Search Console property (you) following our written steps, and the Search Console reports published in the property library
Not included
- Ad campaign management or creative
- Legal advice on consent or privacy, or choosing a consent tool
- Server-side tagging unless added to the agreed list
- Reconciling GA4 to your accounts
- Any promise about ad performance, revenue or rankings
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
Every event in the agreed plan has a named test action, and performing that action produces exactly one event with the specified name and parameters in DebugView.
Evidence: The test book with a DebugView screenshot per event.
The data layer specification matches what the site pushes: each specified field is present with the specified type on the page named in the specification.
Evidence: A table of specified versus observed values from Tag Manager preview on each named page.
The Search Console link, created by the property's verified owner following our written steps, exists for the web stream, the Search Console report collection is published in the library, and the Google Organic Search Traffic report loads for the property, with data shown after the delay Google states.
Evidence: Property link screen, library screen and the report once data appears.
Sign-off. You review each event's test result and the finished plan, then accept the finished set in writing.
If it fails. An event that cannot pass its test is named with the reason and what it would take, and is removed from the plan with a matching change to the price. Nothing is billed as delivered that you have not accepted.
When it fits, and when we stop
It fits when
- One site with test routes for the actions in the plan, without real payments or real customer contact
- Admin-level agreement from the account holders to grant scoped roles on GA4 and Tag Manager
- A person who is a verified owner of the site's Search Console property and has the Editor role or higher on the GA4 property can create the link, following our written steps, on a day we agree; we are given no Search Console role
- A person on your side who decides the plan and publishes
We stop and tell you if
- The site has several domains, brands or properties that need separate plans
- No one who is a verified owner of the site in Search Console can create the link
- The plan needs events the platform cannot expose
- The container has more than 50 tags, so the clean-up is quoted separately
What could go wrong
The container is saved as named versions so any earlier version can be republished; theme or plugin changes are listed with the previous file or setting. If the project stops, accepted parts stay accepted and the rest is handed back with notes.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| The plan asks for events the platform cannot send. | The plan is checked against the platform before pricing, and events that cannot be sent are named and re-scoped. |
| Rebuilding breaks a report someone still uses. | The existing events are listed first, the container is versioned and nothing is removed without a named confirmation. |
Each build step is reviewed separately from the work that produced it, and you accept the finished set. No human supervisor is included unless your proposal names one. At launch the work is largely automated, and we say so.
Questions
Do I buy tags or a result?
A result: a plan, a specification and events that each pass a named test. How we build them is our job.
What if my shop needs ecommerce events?
They are an optional component in the agreed list, with their own tests.
Can you promise better reports?
We promise tested collection against the plan, not any business result.
Why do I create the Search Console link myself?
Google requires the person who creates the link to be a verified owner of the Search Console property as well as an Editor on the Analytics property. Ownership stays with you, so you create the link from our written steps, and we check that it and its reports work.
Send an enquiry
Send us
- The site address, the platform it runs on and the five actions that matter most to the business
- What you report on today and which numbers you distrust
- No logins and no customer data.
Later, once you agree
- Scoped roles on GA4 (Editor) and Tag Manager (Approve, so container versions can be saved for you to publish), granted to the identity we agree with you before work starts. We hold no Search Console role: the verified owner of the Search Console property creates the link from our written steps
- A theme or staging route, where the plan needs data layer changes
- Your decision on the plan and the person who publishes
Your site, accounts, containers and data stay yours. We work in a Tag Manager workspace and, where the plan needs it, on a theme or staging copy, with the lowest role each step needs, granted to an identity we agree with you in writing before work starts. You review and publish. We never ask for passwords.
Email fallback: open your mail app
If website submission is unavailable, review and send the fallback email yourself. An email fallback is not a website receipt. Or write to hello@syntheticindustry.ai with “tracking-measurement-rebuild-for-one-site” as the subject.