The essentials
- The principle: everything that has been configured must be documented and must belong to you. Without that, you depend on your provider.
- Nine deliverables in three families: setup (measurement plan, GTM container, configured property), verification (audit, test procedure), handover (dashboard, training, access, transfer).
- The most important: the measurement plan, a one-page table listing every event, its trigger and its value.
- Warning sign: accounts created in the provider's name.
A GA4 engagement is judged by what it leaves behind. An account that works on delivery day but that nobody knows how to maintain, a dashboard whose definitions are written down nowhere, access held by the provider: so many debts that fall due at the first change. Here are the nine deliverables to write into the quote, with the format you should expect.
Family 1: setup
1. The measurement plan
The central deliverable. A table (Google Sheets or equivalent) listing, for each event: name, type (automatic, enhanced measurement, recommended, custom), precise trigger (page, click, action), parameters sent, value, key event status, creation date, author. Ten to twenty rows for a small business. Without this document, nobody knows three months later why clic_cta_2 exists. What it should contain is described in which events to track first.
2. A documented Google Tag Manager container
A clean GTM container: tags, triggers and variables named to a convention, folders by purpose, notes in every published version. The container must be created in a GTM account belonging to your company, with the provider holding "Publish" access that can be withdrawn. Guide: GA4 and Google Tag Manager.
3. A configured GA4 property
Following the setting GA4 up properly from the start checklist: time zone and currency, 14-month retention, internal traffic excluded, payment referrers, enhanced measurement set up, key events with values, Google Ads and Search Console links, BigQuery export where relevant, Consent Mode v2 verified. With a screenshot or a summary table of the settings applied.
Family 2: verification
4. The audit report and action plan
When taking over an account: the state of play, control by control (status, fix, priority, owner). One to five action-focused pages, not a catalogue of screenshots. The format is described in auditing a GA4 account.
5. The test procedure and acceptance report
For each key event: how to trigger it, what should appear in DebugView, and the test result at delivery. This document lets your team re-check after every site update, without the provider.
Family 3: handover
6. The dashboard
If the engagement includes one: a dashboard (Looker Studio or a platform) with its connected sources, a written definition of every metric, and how often it should be read. The dashboard must be created in your account or be transferable. Templates in examples of marketing dashboards.
7. Training or a handover session
One to two hours, recorded, in which the provider shows where the figures live, how to read the reports and how to test events. For genuine independence, a structured day of training: building GA4 skills.
8. The access list
Who has access to what (GA4, GTM, Google Ads, Search Console, CMP), and with what role. At least two administrators on company email addresses. The provider as editor, never as owner.
9. The handover pack
Everything above, gathered in a shared folder, plus a contact and a warranty period (30 days of tracking bug fixes is customary).
The checklist to attach to the quote
| # | Deliverable | Format | Owner |
|---|---|---|---|
| 1 | Measurement plan | Shared spreadsheet | You |
| 2 | Documented GTM container | GTM account | You |
| 3 | Configured GA4 property | GA4 account + summary | You |
| 4 | Audit and action plan | A 1- to 5-page document | You |
| 5 | Test procedure and acceptance | Document | You |
| 6 | Dashboard | Looker Studio or a platform | You, or transferable |
| 7 | Training / handover | Recorded session | — |
| 8 | Access list | Table | You |
| 9 | Handover pack and warranty | Shared folder | You |
What should never appear in a GA4 engagement
- GA4, GTM or Google Ads accounts created in the provider's name.
- A measurement plan of 50 events or more "so we don't miss anything".
- A 30-page monthly report with no commentary and no recommendations.
- Metric definitions that exist only in the consultant's head.
These points are negotiated when the quote is drawn up; our advice on choosing a GA4 consultant or agency and the benchmark rates will help you frame the discussion.
How GreenRed helps
Rather than juggling several tools, GreenRed's Traffic module brings these metrics together in a single dashboard, compares them over time and tells you which actions come first. You can try it free, with no card, from the Pricing.
Frequently asked questions
What is a GA4 measurement plan?
A table listing every event tracked on the site with its name, its type, its precise trigger, its parameters, its value and its key event status. It is the reference document that lets you understand, test and evolve your tracking without depending on whoever set it up.
Can the provider keep ownership of the GA4 account?
No, and that is a point to refuse. Your GA4, Google Tag Manager and Google Ads accounts must belong to your company, with at least two internal administrators. The provider gets editor access, which can be withdrawn at the end of the engagement.
What should the documentation of a Google Tag Manager container contain?
A naming convention applied to every tag, trigger and variable, folders by purpose (GA4, Google Ads, Meta, consent), a note in every published version describing the changes, and a link to the measurement plan. A documented container can be picked up in an hour; a jumbled one needs a full audit.
What warranty should I ask for after a GA4 engagement?
A 30-day period during which any tracking errors found (a missing event, a duplicate, a conversion not coming through) are fixed at no extra charge. That period lets you check the data over a full cycle and covers the cases acceptance testing didn't catch.