Why can't you see your own website analytics?
If the only view you get of your website's performance is a monthly PDF from the vendor, two things are true: you can't ask your own data a question, and the party being evaluated is producing the evaluation. Analytics access isn't a technical privilege; the property should belong to your company, with the vendor added as a user. The reverse arrangement is common, backwards, and checkable in about ten minutes with the steps below, most of them inside Google Analytics itself.
What it usually means
Vendor-owned analytics usually starts innocently: they set up the property during the build because someone had to, under whatever Google account was open at the time. Sometimes that's the agency's account. Sometimes, worse, it's the personal Gmail of whoever did the setup, which means your traffic history is one job change away from being orphaned.
The arrangement quietly shapes what you can know. You see the metrics the vendor chooses, at the cadence they choose, framed as they choose. Asking a follow-up question requires a request, and every request has a toll: a delay, sometimes an invoice, always the small friction that stops the question being asked at all. Companies that live like this for a few years generally stop interrogating their data entirely, which is exactly the wrong habit for the channel your buyers actually use before they call you.
There's also a second, quieter lock-in inside this one: history. Years of traffic data is how you know whether anything ever worked, and if the property belongs to the vendor, that history is theirs. Leaving them then means losing your memory, which is one more thumb on the scale at every renewal.
What it costs while it stays this way
Concretely, these are questions you can't answer without direct access, and a monthly PDF answers none of them: which pages produce quote requests (and whether your RFQ page is one of them), where buyers drop off between the product page and the contact form, whether the services page redesign changed anything, which campaigns or trade shows actually sent visitors who did something, and what your buyers read in the week before they filled in the form. Every one of those is a decision input; every one is invisible from a summary.
History has already been lost this way at scale, once. When Google shut down Universal Analytics, it deleted all remaining UA data in 2024, and the companies that kept their history were the ones positioned to export it themselves before the deadline. Companies whose analytics lived in a vendor's account were dependent on that vendor caring enough to export on their behalf. Many found out afterward which kind of vendor they had.
There's a gotcha worth knowing even if you have some access: GA4's event-level data retention defaults to two months, and raising it to the fourteen-month maximum is a setting someone has to change on purpose (Admin, then Data settings, then Data retention). A vendor who never changed it has quietly capped how far back your own explorations can look, and no monthly PDF will ever mention it.
How to confirm it yourself
- Log in to Google Analytics itself, not the vendor's dashboard. Go to analytics.google.com signed in with a company Google account. If your site's property isn't listed there for anyone at the company, your company has no access at all, and everything below is about fixing exactly that.
- Check who holds Administrator on the property. In GA4: Admin, then Property access management. GA4 has five roles: Administrator, Editor, Marketer, Analyst, and Viewer. The question isn't whether you appear in the list; it's whether anyone with a company email holds Administrator. Viewer on someone else's property is the same dependency with better cosmetics.
- Check the account above the property. GA4 nests properties inside accounts, and the account is what ownership really means: Admin, then Account access management. A vendor can grant you Administrator on the property while their account still contains it, which lets them remove you later. Ownership lives at the account level.
- Check the retention setting while you're there. Admin, then Data settings, then Data retention. If it says two months, the default was never changed, and your ability to explore your own past is shorter than your sales cycle.
- Audit who else has access. Still in access management: count the personal Gmail addresses and ex-employees. Vendor-configured properties accumulate ghosts, and each one is an account that can read your traffic data today.
- If you're not on Google Analytics. The same questions apply to Plausible, Fathom, Matomo, or PostHog: whose email is on the workspace, who pays for it, and can your team log in directly? Privacy-focused tools change the vendor, not the ownership question.
What the vendor's answers actually mean
When you raise this, you will hear one of a few stock replies. None of them is a technical fact; each is a position, and it helps to know what each one is actually saying.
“Our dashboard gives you everything you need.”
The dashboard shows you what was chosen for you. The statement may even be true today; it says nothing about the question you will have next quarter, which is the entire value of direct access.
“Raw analytics would just be confusing.”
Sometimes sincere, always convenient. Confusion is an argument for a walkthrough, not for the vendor holding the keys to your own traffic history.
“Analytics is bundled with our reporting package.”
The report can be bundled. The property can't be, because the data in it's generated by your website and your visitors. A vendor can sell you analysis; the underlying account isn't theirs to bundle.
“We can add you as a viewer.”
An improvement, and not the fix. Viewer access can be revoked by the person granting it, which is precisely the dependency you're trying to end. The target is Administrator at the account level, or a property move.
What actually fixes it
If the property exists and the vendor cooperates, the fix is ownership transfer, and GA4 supports it directly: an Administrator can use Move property (Admin, then Property settings) to move the property into a Google Analytics account your company owns. Nothing about the site's tracking changes; the data and its history move with it. Then re-grant the vendor whatever role their work genuinely needs, which is usually Editor, rarely Administrator. If replacing the arrangement is on the table, how to choose a B2B web design agency covers what to ask before you sign the next one.
If the vendor stalls, or the property is tangled up with other clients in their account, run the parallel path instead: create a company-owned GA4 property today and add its tag alongside the existing one. You lose nothing that wasn't already at risk, and every week of delay is another week of history accruing to an account you don't control. For the old data, ask for a BigQuery export or, at minimum, exports of the reports that matter; the response to that request tells you how the rest of the offboarding will go.
Keep the dashboard if you like the dashboard. Reporting layers read from a property through a connector, and they work exactly the same when the property underneath is yours. Any claim that the dashboard requires the vendor to own the data is describing a preference as a requirement.
Then use the access. The point of owning the data isn't the ownership; it's that questions stop having a toll booth. What pages do buyers actually read (and which ones they leave immediately, the bounce rate question), where do quote requests come from, did the redesign of the services page move the conversion rate. A company that can ask its own data questions makes different decisions than one that reads summaries.
The message to send
If you want the outcome without composing the ask, this is the whole email. It's deliberately unremarkable: a routine housekeeping request between professionals, which is exactly what it should be.
Hi [name],
We're consolidating ownership of our accounts and need our Google Analytics property moved into a company-owned Analytics account, or our account granted Administrator access at the account level, whichever is simpler on your end.
We would also like data retention set to 14 months if it's not already, and a current list of everyone with access to the property.
Happy to keep your team's access in place for the ongoing work. Can we get this done by [date two weeks out]?
Common questions
Who legally owns Google Analytics data, us or the agency?
Google's terms tie the data to the Analytics account that collected it, so in practice the account holder controls it, whatever your service contract implies. That's why the fix is structural rather than legal: get the property moved or get account-level Administrator, and the question stops mattering. If a contract dispute is already underway, the parallel-property route protects your future data while the lawyers discuss the past.
What is the difference between a GA4 account and a property?
An account is the container a business owns; properties live inside it, one per site or app, and the data lives in the property. Access can be granted at either level, which is where the confusion hides: property-level Administrator feels like ownership but the account holder above you can still remove it. When this page says ownership, it means the account.
The vendor says their dashboard is better than raw GA4. Are they wrong?
Not necessarily; GA4's interface is genuinely disliked and a good reporting layer earns its keep. The dashboard and the ownership are separate questions. A dashboard reads from a property through a connector and works identically when the property is yours. Keep the dashboard, move the property.
What analytics access should a marketing manager have day to day?
Direct login with at least Analyst or Editor on a company-owned property, plus one person in the company holding Administrator at the account level. Not because anyone will live in the tool, but because ad-hoc questions are where analytics earns its keep, and any arrangement where a question requires a vendor request means the questions mostly stop being asked.
We only have the vendor's monthly report. Is that worthless?
No, a competent summary is genuinely useful. It's just not a substitute for access, for the same reason a bank statement isn't a substitute for being able to log in to the bank. Keep the report; add the login; judge the report differently once you can check it.