How to Choose an Analytics Agency
The questions to ask before you sign, and the proof to demand instead of slideware.
Hiring an analytics agency is different from hiring most vendors, because you are not buying a deliverable you can inspect on delivery - you are buying trust in numbers your team will make decisions on for years. A bad hire here does not just waste a budget line; it produces reports that look correct and are not, which is worse than no reports at all.
This guide is the buyer's-side companion to our Analytics Agency page. It does not pitch Webclat - it gives you a diligence checklist you can use on any vendor, including us.
Questions to ask before you sign
1. How do you document a tracking plan?
You want to see a real artifact - named events, typed properties, an owner for each - not a verbal description of "best practices."
2. Is collection client-side, server-side, or both - and why?
The answer should be specific to your stack and your data-loss risks (ad blockers, browser ITP, app-tracking transparency), not a default answer given to every client.
3. How is consent state captured and respected in the data itself?
Every event should carry its consent basis. If consent is handled only at the banner level and never touches the data, it will not survive an audit.
4. What happens to access and code when the engagement ends?
You should retain full ownership of accounts, repositories, and documentation. Anything less is a dependency, not a deliverable.
5. Can you show me a rollback or migration plan?
Tracking changes can break historical reporting continuity. A serious vendor plans for this before touching production.
6. Who on your team will actually do the work?
Sales conversations are frequently staffed differently than delivery. Ask to meet the engineer, not just the account lead.
The proof to demand, not the slides to accept
Evidence-first evaluation means asking for artifacts that are hard to fake, not stories that are easy to tell.
- A live event firing in a network or tag debugger
- A sample tracking plan or schema document
- A reference contact you can actually call
- A before/after data-quality comparison from a past engagement
- Clear answer on who owns code and credentials after handoff
- Generic framework slides with no reference to your stack
- Client logos with no named contact you can reach
- A dashboard screenshot presented as proof of tracking accuracy
- Vague answers to "how is consent handled"
- Pressure to sign before an audit or scoping call
Red flags worth walking away from
A few patterns are worth treating as disqualifying rather than merely cautionary: a vendor who cannot explain the difference between client-side and server-side tracking in plain language; a proposal that never mentions consent or privacy regulation; a contract that keeps admin access with the vendor after the engagement ends; and pricing that is the same regardless of how many platforms or events are involved. Analytics engineering work scales with the complexity of your stack - a flat, one-size number usually means a templated implementation, not a scoped one.
How we hold ourselves to this
We wrote this checklist because it is the one we expect to be judged against. Every Webclat engagement starts with a written audit, not a sales deck; every tracking plan is a real document you keep; every account stays in your ownership; and consent state travels with the event, not just the banner. We would rather lose an engagement to a competitor who can answer these questions than win one from a client who never asked them.
Common questions when vetting an agency
▸What is the single most important question to ask an analytics agency?
"Can you show me one of your own tracked events firing live, right now, in a debugger?" A vendor who lives in this work daily can answer in under a minute. A vendor who resells someone else's template usually cannot.
▸Should an analytics agency own my Google Analytics or Tag Manager account?
No - not permanently. A reputable agency works inside accounts and properties you own, documents what they changed, and hands over full admin access at the end of the engagement. If access reverts to them or the relationship becomes hard to unwind, that is a lock-in structure, not a service.
▸How long should an analytics agency audit take?
A scoped audit of a single platform typically runs one to a few weeks depending on the number of source systems involved. Be cautious of an audit promised in a single call - that is a sales pitch wearing an audit's name.
▸What proof should I ask for instead of case studies?
Ask for a live walkthrough of your own site or a comparable one in a network debugger or tag debugger, a sample of the documentation format they use for tracking plans, and a reference you can actually call. Named client logos and screenshots of dashboards are not evidence of engineering quality - they are marketing assets.
Run this checklist against us.
Book an audit and see the tracking plan, the live event debugging, and the documentation before you commit to anything larger.