GA4 Reporting With a Virtual Assistant: Access and Monthly Report Template
A monthly Google Analytics reporting task does not automatically require Administrator access.
If you want to set up GA4 reporting with a virtual assistant, separate two questions from the beginning: what information does your VA need to see, and what should they actually be allowed to change?
Google Analytics gives you several ways to make that distinction. A user with the Viewer role can share and export standard reports, while creating and publishing the newer native Dashboard requires Editor or Administrator access.
Google launched native Dashboards in Google Analytics on September 9, 2026. That gives small businesses another useful reporting surface, but it does not mean the person preparing your monthly report needs broad control over the property.
The better setup is to define the reporting job first, grant only the access needed for that job, and give your VA a consistent output to return each period.
Start With the GA4 Access Level, Not the Task List
Before you tell a VA which metrics to collect, decide what they need permission to do.
Google currently provides five main roles. Their differences matter because “GA4 access” can range from simply viewing and exporting reports to changing events, property settings, or users.
| Role | Relevant reporting capability | When it may make sense |
|---|---|---|
| Viewer | View data and settings, change how data appears in reports, and share or export standard reports | A sensible starting point for many routine reporting assignments |
| Analyst | Includes Viewer capabilities and can share Explorations | Consider when the VA needs to prepare and share deeper analysis or create annotations |
| Marketer | Can manage audiences, events, key events, and attribution settings | Usually separate from a routine reporting role |
| Editor | Full control of property settings and can create or publish native Dashboards | Use only when changing the reporting setup is genuinely part of the person’s responsibility |
| Administrator | Includes Editor permissions and can manage users | Appropriate for account administration, not simply because someone prepares a monthly report |
Google documents the full distinction in its Analytics roles and data restrictions guidance.
For many small businesses, Viewer is a reasonable place to start when the VA’s responsibility is to read reports, apply approved comparisons, export data, and prepare the recurring deliverable.
Analyst becomes more useful when the assignment includes sharing Explorations or adding contextual annotations.
Editor is a much broader decision. It gives control over property settings and is required to create or publish native Dashboards.
Administrator goes further again because it includes user management.
Add access at the level the VA actually needs
If your VA only needs one GA4 property, property-level access is usually more contained than granting the same role across the entire Analytics account.
Google’s current process for adding a user to Analytics is:
Open Admin.
Under the relevant Property, open Access Management.
Select +, then Add users.
Enter the Google Account email address.
Select the required permission.
Add the user.
Adding someone at account level can give them corresponding access to the properties beneath that account, so check which level you are changing before confirming access.
GA4 also supports restrictions for cost and revenue metrics. If financial visibility is not necessary for the reporting assignment, review those options rather than assuming every user needs unrestricted access to every metric.
Build One GA4 Reporting Surface Before You Delegate the Monthly Routine
A reporting VA should not have to rediscover the right GA4 screens every month.
Decide where the approved numbers come from.
For a small business, there are three useful reporting surfaces to understand.
Native Dashboard for the recurring KPI view
Google’s newer Dashboard gives you one page for selected business KPIs.
It supports scorecards, tables, line charts, bar charts, donut charts, and funnels. Standard properties currently support up to 15 cards per Dashboard.
There is an important permission distinction: Editor or Administrator access is required to create and publish the Dashboard, but users who already have access to the property can view a published Dashboard.
That creates a practical option for delegated reporting.
The owner, marketing lead, or analytics specialist can define the Dashboard once. Your VA can then use that approved reporting surface during the monthly routine without needing permission to redesign it.
That is not the only possible setup, but it keeps report architecture separate from recurring report preparation.
Standard reports for repeatable exports
Standard GA4 reports remain useful when the VA needs a consistent table or file rather than another dashboard.
With Viewer access, Google currently allows standard reports to be exported to:
Google Sheets
PDF
CSV
That makes standard reports particularly useful when your final reporting process lives in a spreadsheet or document outside GA4.
Explorations for questions that need deeper analysis
GA4 Explorations are designed for deeper and more flexible analysis than standard reports.
They can be useful when a recurring report surfaces a question that the approved Dashboard does not answer.
Treat that as a different type of work.
Your normal month-end process should not require the VA to rebuild an analysis from scratch every time unless that work has been deliberately included in the role. Analyst access is required to share an Exploration with other users.
The goal is to give the reporting process a stable home, not force every possible analytics question into one screen.
Give the VA a Reporting Specification, Not “Tell Me What Happened”
“Send me the Google Analytics report every month” leaves too much undefined.
Your VA still has to work out:
which dates to use;
which comparison period matters;
which metrics the business actually cares about;
where each metric should come from;
which filters should be applied;
how changes should be calculated;
what counts as unusual;
and what they should do when the data looks wrong.
Define those rules once.
At minimum, your reporting specification should state:
| Reporting rule | What to define |
|---|---|
| Reporting period | Exact monthly, weekly, or other approved date range |
| Comparison period | Previous period, previous year, or another approved comparison |
| Business KPIs | The configured outcomes that actually matter to this business |
| Supporting metrics | Approved acquisition, content, engagement, ecommerce, or local metrics |
| GA4 source | Exact Dashboard, report, or Exploration used |
| Filters | Any geography, channel, page, device, campaign, or other approved filter |
| Output location | Spreadsheet, document, task, folder, or other maintained destination |
| Change calculation | One consistent rule for showing increases and decreases |
| Known context | Where launches, campaigns, outages, website changes, or other events are recorded |
| Exception rule | What should be flagged rather than silently corrected |
| Reviewer | Person responsible for interpreting results and deciding next actions |
Google supports different date and comparison ranges in Analytics reports, but you should still tell the VA which comparison your business uses. Otherwise one report may compare with the previous month while another compares with the previous year.
This follows the same principle I use for broader recurring report preparation: define the KPI, source, period, comparison, template, and exception rules before the task becomes routine.
If the process will be repeated regularly, you can also document the reporting process in a short SOP rather than leaving the important rules scattered across messages.
Use a Two-Layer Monthly GA4 Report
A useful monthly report should do more than copy numbers from Analytics.
It should give the reviewer two things:
a traceable performance layer showing what GA4 recorded;
a context and review layer showing what deserves attention.
This structure keeps facts separate from explanations that have not yet been established.
Layer one: verified performance numbers
Start the report with the basic reporting controls.
| Report field | What the VA records |
|---|---|
| Reporting period | Exact current date range |
| Comparison period | Approved comparison range |
| GA4 property | Property being reported |
| Prepared by | Person completing the report |
| Prepared date | Date the report was completed |
Then use a performance table.
| Metric or KPI | Current period | Comparison period | Change | Exact GA4 source | Data-quality flag |
|---|---|---|---|---|---|
| Business outcome KPI | |||||
| Approved acquisition metric | |||||
| Approved landing/content metric | |||||
| Approved engagement metric | |||||
| Ecommerce metric, if applicable | |||||
| Other business-specific metric |
Do not treat those example rows as a universal GA4 scorecard.
A lead-generation company may care about a configured lead event. An ecommerce company may focus on purchases or revenue. A publisher may need a different content and engagement view.
Your reporting template should reflect the business model and the measurement that has actually been implemented.
If a comparison value is zero or unavailable, do not force a misleading percentage calculation. Record the exception consistently and flag it where necessary.
Layer two: context, flags, and review questions
Below the numbers, add a short review layer.
| Field | What belongs here |
|---|---|
| Known context | Verified campaign, launch, website change, outage, seasonality note, or other known event |
| Annotation | Relevant GA4 annotation, if one exists |
| Data-quality flag | Missing event, unexplained zero, inconsistent range, blank value, or suspected measurement break |
| VA observation | Factual description of what changed |
| Review question | What the owner, marketer, or specialist should investigate or decide |
| Next owner | Person responsible for the follow-up |
Google’s GA4 annotations can be useful for recording campaigns, launches, observations, and other events around changes in the data.
Analyst access or above is currently required to create an annotation, while Viewer users can see existing annotations.
That means a VA with Viewer access can still incorporate known annotation context into the monthly report. If the VA only has Viewer access and new context needs recording, it can remain in the reporting template until the appropriate person adds the annotation.
Train the VA to Describe the Evidence Without Inventing the Cause
Reporting and diagnosis are not the same job.
A report should make clear whether a statement is:
an observation from the data;
known business context;
a data-quality concern;
or a question requiring investigation.
For example:
| Avoid | Better reporting language |
|---|---|
| “Traffic dropped because SEO got worse.” | “Organic sessions were lower than the approved comparison period. No confirmed cause is recorded. Review SEO and technical context.” |
| “The campaign worked.” | “Traffic attributed to the approved campaign source increased during the reporting period. Review the configured business outcome before judging campaign performance.” |
| “Tracking is broken.” | “The configured metric returned an unexpected zero. Flagged for measurement review.” |
| “Customers are less engaged.” | “The approved engagement metric declined versus the comparison period. Cause not established.” |
The second version is less dramatic, but it is more useful.
It tells the reviewer what GA4 showed without turning a correlation, movement, or missing value into a conclusion that the data does not prove.
During the first few reporting periods, review this wording closely.
Correct:
metric definitions;
date ranges;
comparison choices;
source reports;
acceptable observations;
and escalation rules.
Then update the reporting specification so the same correction does not need to be made every month.
Keep Tracking and Configuration Changes Outside Routine Reporting
A VA preparing the report may be the first person to notice that something looks wrong.
That does not mean they should silently change the measurement setup.
GA4’s roles deliberately separate these responsibilities.
The Marketer role can manage audiences, events, key events, and attribution settings. Editor has broad property-setting control. Administrator can manage users.
Those are materially different permissions from routine report preparation.
Treat measurement configuration as a separate responsibility unless the person has the appropriate expertise, authority, and defined scope.
For example, the VA can flag that:
a previously used business outcome suddenly reports zero;
expected revenue data is blank;
a Dashboard card stops returning expected information;
the approved reporting period was changed;
a metric is missing from its usual report;
or a result looks inconsistent with the previous reporting process.
The next action should be to record and escalate the problem, not invent a fix.
This distinction is particularly important for business events. Google’s recommended GA4 events, including events associated with activities such as purchases or lead generation, still require appropriate implementation. You should not assume a metric exists correctly simply because it would be useful in the monthly report.
If you want the same person to handle technical measurement work, define that as a separate assignment with its own access, instructions, testing, and review requirements.
Review the Reporting Setup When the Business Changes
A recurring report should be consistent, but it should not become permanent simply because the template already exists.
Review the setup when something material changes.
That may include:
a different business objective;
a new website or major redesign;
a new ecommerce setup;
a change to key events;
new campaigns or acquisition channels;
a change to the person responsible for analytics;
a reporting Dashboard being rebuilt;
or a new GA4 integration becoming relevant.
For local businesses, for example, Google added Business Profile engagement information to GA4 in 2026. My earlier guide to the Google Business Profile and GA4 reporting update explains what that integration adds and where its current limitations matter.
Changes like that should be incorporated deliberately.
Do not let the monthly process drift because somebody noticed a new metric and quietly added it to the spreadsheet.
The point of delegating GA4 reporting is not to produce a larger pile of numbers.
It is to receive the same decision-ready evidence each reporting period, know where every important number came from, see what changed, and immediately spot anything that needs investigation.
At Boost VA, I support founders, agencies, and online businesses with recurring data management, reporting, research, and backend execution. If you already know what needs to be reported but the recurring preparation is taking too much time, tell me what you need help keeping on track.
