Copyable client message
Hi [client name], please add [agency email] to Google Analytics so we can review performance and confirm tracking before making recommendations.
We need viewer access at minimum. If we are configuring conversions or events, please grant editor access and confirm which property is the primary source of truth.
Request checklist
| Section | Ask for |
|---|---|
| Account details | Analytics property name, website URL, GA4 property ID |
| Permission | User email to invite, role needed, who approves access |
| Tracking | Key events, conversions, form submissions, ecommerce tracking |
| Reporting | Primary KPIs, reporting cadence, existing dashboard links |
| Connected tools | Tag Manager, Search Console, Ads, Looker Studio |
What to avoid
Do not ask the client to send their Google password. Ask them to invite a named account and confirm the property you should inspect.
Portal upgrade
In Kicklayer, analytics access can sit next to website copy, screenshots, ad account links, and approval notes, so access does not get lost in the same thread as everything else.
Client-ready request
A version you can paste into an email, Slack thread, or Kicklayer portal.
Hi [client name], please invite [agency email] to the correct Google Analytics property and confirm the property name, website URL, permission level, connected Google Ads account, conversion events, reporting goals, and any historical reports we should preserve.
How to structure the request
Break the ask into fields a client can answer cleanly, rather than a single vague upload request.
GA property
Required text
Ask for the exact account and property name so the wrong site is not reviewed.
User access
Required access
Request viewer, analyst, editor, or administrator based on the work.
Website URL
Required url
Match the property to the production website, staging site, or app being measured.
Conversions
Required text
Collect key events, form submissions, purchases, calls, or lead actions.
Linked tools
Optional access
Ask whether Google Ads, Search Console, Tag Manager, or Looker Studio are connected.
Client request breakdown
These are the asks that make the request specific enough for the client to complete without a follow-up loop.
Invite
Add [agency email] to the correct Google Analytics property.
Screenshots do not provide enough access for implementation or audit work.
Permissions
Confirm the permission level and reason for it.
Reporting work and configuration work require different roles.
Tracking
List the conversions and events that matter.
The analytics setup should support the client goal, not just pageview reporting.
Connections
Confirm linked Ads, Search Console, Tag Manager, and dashboards.
Missing integrations can hide important campaign or SEO context.
History
Share old reports, dashboards, or tracking notes.
This helps avoid breaking definitions the client already uses.
Make the request easier to complete
Small wording choices change whether a client sends useful material or another incomplete reply.
Do
- Ask for user access through Google, not exported screenshots.
- Name the account, property, website, and required permission level.
- Collect conversion definitions before changing reports.
- Ask about Tag Manager if tracking edits are part of the work.
Avoid
- Assume the first property in the account is the right one.
- Use administrator access when viewer access is enough.
- Overwrite events before documenting what they currently measure.
- Forget to ask who owns reporting decisions.
When the checklist becomes a portal
The same request becomes more reliable when every field has an owner, a status, and a place to submit it.
Analytics access, Tag Manager, Search Console, and Ads can be requested in one workflow.
Clients can see exactly which invitations are still incomplete.
Your team can keep reporting goals attached to the access request.
Practical questions
What permission level should I request in Google Analytics?
Viewer is enough for review, analyst is useful for reporting work, editor is needed for configuration, and administrator should be reserved for account management.
Should I ask for screenshots instead?
Screenshots can help orientation, but they do not replace access when you need to audit settings, configure events, or connect tools.
What else should I request with GA access?
Ask about Tag Manager, Search Console, Google Ads, Looker Studio, conversion events, and the business goals behind the reports.