Losing admin access to a Google Analytics 4 property is more common than it may seem. It usually happens when the account was originally set up with a single administrator and, later on, that person leaves the company, their corporate account is deleted, or no one knows anymore who still has the permissions needed to manage access.
In these situations, recovering control does not depend on finding the former administrator. It depends on following the process Google has established to prove ownership of the website or app linked to the GA4 account. Although Google’s own documentation explains the steps, in practice there are still a lot of doubts, especially when the process is not clear from the start or when the recovery form fails when you try to submit it.
Contents
What it really means when no one has admin access in Google Analytics 4
When people say that “no one has admin access” in Google Analytics 4, it does not always literally mean that no one can access the property. In many cases, there are still users who can log in, but only with Viewer, Analyst, or Editor permissions. The problem is that the Administrator role is the only one that allows users and permissions to be managed, both at account level and at property level.
If no user still has that level of access, there is no way to add new administrators from within the GA4 interface itself.
It is also worth remembering that GA4 permissions can be granted at different levels. A user can be an administrator of one specific property without being an administrator of the entire account. On top of that, Google distinguishes between direct permissions and effective permissions, which are the permissions a user inherits from higher levels in the hierarchy or from user groups.
That is why, before assuming the account is completely blocked, it is worth checking whether there is any inherited access that still has the ability to manage users.
In practice, the real problem starts when there is no longer any user with the ability to manage access at the level required. That is when the company realises it still owns the website, the app, or even the tracking implementation itself, but it can no longer recover control of the property through the usual route. That is exactly the scenario Google’s admin access recovery process is designed for: a process based on proving ownership of the assets linked to the account.
In which cases the account can be recovered, and in which cases it cannot
Not every case in which a company has lost admin access to GA4 can be solved through the same route. Google does provide a recovery process when the person requesting access can prove ownership of the website or app that is sending data to the property.
That is the real starting point of the process: it is not enough to explain that the former administrator no longer works at the company or that the corporate account was deleted. You need to be able to prove technical ownership of the assets linked to Analytics.
This also means recovery can become more complicated when the account or property includes several websites or several apps. Google explicitly states that if you cannot prove ownership of all the sites identified in the account, it will not be able to grant access. The same applies when there are linked Google Ads or AdSense accounts. In that case, it is not enough to prove ownership of the website or app. You also need to prove ownership of those linked accounts.
By contrast, there are situations where this procedure does not apply. Google’s own documentation makes it clear that this process cannot currently be used to recover access to Google Tag Manager or Google Analytics for Firebase. That is why it is important to understand from the beginning exactly what you are trying to recover: a GA4 property with no administrators may have an official recovery path, but that does not mean every Google measurement-related product follows the same process.
Put differently, this process is designed for cases where the company still controls the assets feeding the property, even though it has lost control of permissions inside Analytics. If that relationship cannot be demonstrated, the request will usually not go through.
What Google requires before giving access back
Google does not restore admin access to a GA4 property just because a company says the property is theirs or because the former administrator is no longer available. What Google asks for is proof of ownership of the assets sending data to Analytics. In the case of a website, that verification is usually done by adding an analytics.txt file to the corresponding domain. If it is an app, the verification is carried out through the app’s public listing.
On top of that, the verification does not simply identify one isolated property. Google states that, in order to validate the request, you need to include the Measurement ID for every property in the account or, alternatively, the Account ID. It also makes clear that if you cannot prove ownership of all the sites or apps identified in the account, access will not be granted. This matters because many recovery attempts fail not because of the form itself, but because the proof of ownership is incomplete.
If the Analytics account has links to Google Ads or AdSense, the process requires additional proof. In those cases, it is not enough to prove that you control the website or the app. You also need to prove ownership of those linked accounts. Only once all of that information is properly prepared does it make sense to submit the recovery request to Google.
In other words, Google is not asking you to “prove that you used the account.” It is asking you to prove that you control the assets and accounts connected to it. That distinction explains quite well why the process can feel stricter than many users expect.
Step by step: how to recover admin access in GA4
The recovery process Google provides does not consist of asking for access by email or explaining that the former administrator no longer works at the company. The basis of the procedure is proving that you control the assets sending data to the property. In a web implementation, this is usually done through an analytics.txt file uploaded to the relevant domain.
That file must include a very specific string in the exact format Google requires, and it is best to follow that format exactly. Along with the email address to which access should be restored, you need to include the Measurement ID for every affected property or, alternatively, the Account ID. Google allows this to be done on separate lines, on a single line with the IDs separated by commas, or by using the account identifier directly.
Once the file is ready, it must be uploaded to the top-level domain, for example at a path such as domain.com/analytics.txt. If data is being collected from a subdomain, Google accepts the file being placed either on the subdomain or on the main domain. That detail matters, because many errors come from placing the file in an internal path, inside a blog folder, or in a location that does not match the one Google will validate.
If the website does not allow files to be uploaded, Google provides an alternative: adding that same string in a meta tag inside the page identified as the Website URL in Analytics. It is not the best-known option, but it can be useful in environments where there is no server or file system access, but there is access to the code or to the page header.
When the Analytics account has linked Google Ads or AdSense accounts, the process does not end with domain verification. Google also asks for proof of ownership of those linked accounts. In the case of Google Ads, for example, it requests information related to payment, the payment method, the legal business name, the billing address, and the visible URL of the ads.
That is why, before submitting the request, it is worth checking whether the property has active integrations that could block the recovery if they are not documented properly.
Once all of that information is ready, the final step is to submit the request to Google through the contact form linked in the documentation. From there, the review depends on whether the proof of ownership is sufficient and whether no additional validation is missing.
The most common errors that cause recovery to fail
Although Google’s process is not especially long, it is quite strict. One of the most common problems lies in the analytics.txt file itself. The text must match Google’s required format exactly, with no changes to the string, no extra spaces, and no missing parts. The documentation also makes clear that, in addition to the email address, you need to include the Measurement ID for every affected property or, alternatively, the Account ID. If any of that information is missing or not written correctly, the validation may fail.
Another common error has to do with the file location. It is not enough to upload it somewhere on the website. Google requires it to be placed at the top-level domain, in an accessible path such as domain.com/analytics.txt. If the file is uploaded inside an internal folder, inside a blog section, or at a URL different from the one Google expects, the validation can fail even if the content itself is correct.
It is also important to make sure the file is public and loads properly, because if it cannot be accessed externally, it will not work as proof of ownership.
It is also quite common for the issue not to be on the website side at all, but in linked accounts that no one has taken into consideration. If the GA4 property is linked to Google Ads or AdSense, Google requires additional proof for those accounts. In those cases, verifying the domain is not enough. If that part is missing, the request may be considered incomplete even if everything else is properly prepared.
Finally, some requests fail because people try to recover an account or property without being able to prove ownership of all the assets identified inside it. Google states that, if you cannot prove ownership of all the sites or apps in the account, access will not be granted. That is why, before submitting the request, it is important to review the real scope of the account carefully and not assume that validating only the main website will be enough.
What to do if the form fails or will not submit
If you get an error when trying to submit the form, the first thing to do is rule out a browser problem. At this point, it is worth running the most basic checks before touching anything else: clear cache and cookies, try again in an incognito window or in a different browser, and temporarily disable extensions or a VPN. Sometimes the issue is not with the request itself, but with the way the form loads or validates in that environment.
If it still fails after that, the most likely explanation is that there is a problem with the ownership verification. There is no need to rebuild the whole process from scratch, but it is worth reviewing the most sensitive points carefully: that the string included in analytics.txt is exact, that the file has been published in the correct location and is publicly accessible, and that no extra proof is missing if the property has linked accounts. Google makes it clear in its documentation that the validation is strict and that recovery depends on correctly proving ownership of the assets associated with the account.
If, after checking the browser and reviewing the verification again, the form still will not submit, one useful alternative is to leave that flow and go to the general “Contact us” portal in the Google Ads help centre. There, it is best to describe the case as Access Request in the field where Google asks what you need. After moving through the initial steps and clicking Next Step, the option to submit a request by email should appear.
If the email option does not appear, go back to step 1 of the form and try describing the case in a much vaguer way. Also keep in mind that you need to select the email contact option. The form may offer a phone call as a contact method, and it may look like the faster route, but email is the method that allows the case to be escalated correctly to the right team.
In the end, losing admin access to a GA4 property can be frustrating, but it is not necessarily final. If the company still controls the website, the app, or the linked accounts, there is still a path to recover that access. The key is understanding that this is not a process based on explaining what happened, but on correctly proving ownership of the assets linked to the account.
