To give access to Google Analytics 4, an administrator adds the agency’s Google Account email in Access management. First decide whether the agency needs one property or the whole Analytics account. That decision matters when several brands or websites share an account.
Ask for the property name and numeric property ID before requesting access. Also record the website URL. A measurement ID beginning with G- identifies a web data stream; it is not the property ID you should use in the handover record.
How the account owner gives GA4 access
- Open Google Analytics and select the intended account and property.
- Go to Admin.
- Open Property access management for a single property, or Account access management for all properties in that account.
- Select + → Add users and enter the agency’s Google Account email.
- Choose the role, review any data restrictions, and enable Notify new users by email.
- Select Add, then ask the agency to open the property using that email.
You need the Administrator role at the level where you are granting access. Google’s user-management guide explains the process and the distinction between account and property scope.
For a one-website reporting engagement, start by considering property access. If a client asks you to cover multiple properties, list them explicitly before requesting the broader account scope.
How the agency requests access
Send the client a request that can be forwarded directly to their Analytics administrator:
Please add [Google Account email] to GA4 property [name and numeric ID] for [website]. We need [role] to [specific task]. Please use Property access management unless we have agreed to manage every property in the account. Let us know once added so we can verify the property and reporting data.
If you receive a report link without access, Google also documents an in-product access-request route. Its instructions include account-administrator prerequisites, so do not assume every new external collaborator will see that option. If it is unavailable, ask the client administrator to add your email directly.
After access is granted, open the property yourself. Check its ID, website stream, recent reporting dates, and the settings needed for your assignment. A client’s confirmation email is useful, but it does not establish that you received the right property.
Which GA4 role should you request?
| Agency task | Starting role |
|---|---|
| Read reports and make personal explorations | Viewer |
| Share explorations with other property users | Analyst |
| Manage audiences, events, and key events | Marketer |
| Configure broader property settings | Editor |
| Manage user access | Administrator |
Google defines these capabilities in its roles and data-restrictions reference. Editor does not manage users. Review the actual task before escalating beyond Viewer; “we’re the agency” is not a permission requirement.
Account permissions flow down to properties. A lower property role does not cancel higher access inherited from the account. Cost and revenue restrictions can also affect the metrics a user sees. Check effective permissions when access differs from the role you expected. Google’s permission model explains inheritance.
Common Google Analytics client access problems
The property is missing from the selector
Check the signed-in email and ask the administrator to confirm both the recipient email and property ID. Clients sometimes share a historical or test property with a similar name. Do not ask them to create a new property before identifying the one collecting production data.
Reports load, but settings cannot be changed
Name the blocked task before requesting a higher role. For example, preparing a monthly report and changing measurement settings are different assignments. Keep reporting staff on the access needed for reporting.
Reports have no recent data
Separate access from measurement. Confirm the date range and expected traffic, then have the tracking owner check collection. A permission upgrade will not repair an uninstalled tag. If the investigation requires container changes, use the Google Tag Manager access guide.
The client cannot find an administrator
Ask the internal analytics owner, IT contact, or previous agency who originally set up the property. Keep this as a named blocker with a follow-up owner. Starting a new property would create a separate measurement history and needs a deliberate migration decision.
Security checks before closing the request
Keep a client-controlled administrator, use named work identities and two-step verification, and record the resource scope alongside the role. For a multi-brand client, check that an account-wide grant will not expose properties outside your engagement.
At handover or offboarding, have the administrator review direct and inherited access. Document the permission review date in the account record. Once access is verified, the Google Ads monitoring checklist provides ongoing checks for conversion activity and business-outcome reconciliation.
Collect access without another set of client instructions
When onboarding includes several Google products, LeadUp can help you collect client account access through one guided connection link. Its Analytics request is account-level, with Viewer, Analyst, Editor, or Admin options; it does not currently offer the Marketer role in that flow.
Use that route when the agreed scope covers the Analytics account. For a single property inside a shared account, or a Marketer-specific assignment, use Google’s native access management instead. Whichever route you choose, verify the actual property before reporting setup begins.