Key facts
- Google Analytics 4 (GA4) is event-based rather than session-based like its predecessor, meaning every meaningful action, a form fill, a scroll, a purchase, has to be explicitly configured as an event; nothing tracks itself by default beyond basic page views.
- Google Tag Manager (GTM) is a container that manages your tracking tags without needing to edit site code for each one, but a poorly organized container with undocumented tags and triggers becomes difficult for anyone but its original builder to maintain.
- Consent Mode, Google's framework for adjusting what data is collected based on a visitor's cookie consent choice, affects how complete your GA4 data is for visitors who decline tracking, and a vendor should confirm whether this is configured and how it affects your reported numbers.
- Server-side tagging, running tag processing through a server you control rather than only in the visitor's browser, can improve data accuracy and load speed but is a meaningfully more advanced setup, and a vendor should state clearly whether they are proposing standard or server-side GTM.
- GA4 and Google Ads reporting the same conversion with different numbers is common and usually explained by different attribution windows or tracking gaps between the two systems, not necessarily an error, but a vendor should be able to explain the specific reason for your account.
Scope boundaries
State whether this is a first-time GA4 and GTM setup, a migration cleanup after a previous agency's work, or an audit of an existing setup you are not confident in. Each starts from a different baseline, and a vendor should quote accordingly.
List the specific events you need tracked: form submissions, phone number clicks, purchases if you sell online, scroll depth or engagement if relevant to your goals, and any custom events specific to your business (a quote calculator being used, a video being watched to completion).
State whether consent management (a cookie banner connected to Consent Mode) is in scope, since this affects both your legal compliance posture and the completeness of your GA4 data, and it is a distinct piece of setup work from the tracking itself.
What the vendor must be given
Give the vendor admin access to your GA4 property and your GTM container, created and owned under your own Google account, not a personal account belonging to the vendor.
The vendor also needs a way to publish GTM's base snippet sitewide, either CMS access or a way for you to paste the container code in yourself, since GTM only works once its base code is correctly installed sitewide.
Supply a list of your actual business goals in plain language, what a form fill on your site leads to, what a purchase looks like if you sell online, so the vendor configures events that map to outcomes you actually care about rather than a generic template of common events.
Ownership and exit clauses
The GA4 property and GTM container need to be created under your own Google account from the start, with the vendor added on at an administrator level, so ownership and historical data stay with you no matter how the vendor relationship turns out.
State that any custom code (custom HTML tags, custom JavaScript variables) built inside GTM is documented in plain language, not left as unlabeled code only the original builder can interpret.
The contract should require the vendor to produce a written map of the entire GTM container, every tag, its trigger, and what it does, plus confirmation of who else has access to the GA4 property, on termination, so a future vendor can pick up the setup without rebuilding it from zero.
Milestones and acceptance tests
Set an audit or planning milestone: a written list of every event to be tracked, mapped to the business goal it represents, delivered and approved before implementation begins.
Set an implementation milestone with a specific acceptance test: each planned event fires correctly when manually tested, using GTM's own preview mode and GA4's real-time report to confirm, and any consent management configuration correctly adjusts what is collected when a test visitor declines cookies.
About a month after launch, review the numbers against reality: check whether the reported event counts look reasonable against your actual known activity (a rough gut check against known form volume, for example), and confirming no duplicate or unexpectedly missing events have appeared under real traffic.
Scoring rubric
Documentation and how the vendor tests their own work should drive most of the score: the written event plan and testing process is worth 30 points out of 100, price 25, experience with GA4 and GTM specifically (not general analytics work) 20, documentation quality 15, and references make up the final 10.
Score the event plan on whether it maps each tracked event to a specific business goal in plain language, rather than a generic list of every event GA4 is technically capable of tracking regardless of relevance to your business.
Ask references specifically whether they received a written map of their GTM container after setup, since a vendor with a habit of leaving containers undocumented creates a maintenance problem for the client down the line, even if the initial setup worked.
Questions every bidder must answer
Make every bidder answer in writing: What specific events will you configure, and how does each map to a business outcome I care about? How do you test that an event fires correctly before calling the setup complete? Is Consent Mode part of this setup, and how does it affect the completeness of my data?
Also ask: Will the GA4 property and GTM container be created under my own Google account? Will you provide a written map of every tag and trigger in the container? What happens to my analytics setup and documentation once you are no longer the one running it?
A bidder who names specific events tied to specific business outcomes, and who commits to written documentation of the container, is describing a maintainable setup. A bidder who describes GA4 setup as a quick, generic checklist is likely to leave you with tracking that technically exists but does not answer your actual questions.
Related questions
This is common and usually comes down to different attribution windows or timing between the two systems, not necessarily an error. A good vendor should be able to explain the specific gap for your account rather than dismiss the question.
GTM makes managing multiple tracking tags easier without editing site code every time, which matters once you have more than a couple of tracking needs, forms, calls, ads pixels. For a single simple tracking need, it is not strictly required, but most setups benefit from it.
Consent Mode adjusts what Google's tracking tools collect based on a visitor's cookie consent choice. Whether you need it depends on your privacy compliance obligations, which vary by where your customers are located, so this is worth discussing with whoever handles your legal compliance.
It varies with how many events and how much complexity, ecommerce tracking, consent management, custom events, are involved. A basic lead-generation setup costs meaningfully less than a full ecommerce build with consent management layered on top.
Yes. We fold GA4 and GTM setup into our website and Google Ads work at no extra line item, and the written event plan plus 30-day verification checkpoint this pack asks for match what we would actually build for you.
SearchPod is a vendor for this kind of work and would answer this RFP; the acceptance tests here are the ones we agree to.
Want this scoped and priced for your business?
Get a free, no-obligation proposal within one business day. We look at your site and your market and tell you plainly what we would do, and what we would not.
Get your free proposal