AdSense monthly report preparation turns a month of changing numbers into a short record of what happened, why it may have happened, and what you will do next. A useful report does more than copy estimated earnings from the dashboard. It compares equivalent periods, separates traffic volume from monetization efficiency, identifies the segments responsible for movement, and records decisions that can be reviewed later.
This guide includes a reusable template for publishers, bloggers, and small content teams. You will learn which metrics to capture, how to calculate month-over-month and year-over-year change, how to investigate pages, countries, platforms, and ad formats, and how to convert findings into controlled actions. The workflow is deliberately practical: one monthly review should produce clarity, not a spreadsheet that nobody reads.
Quick answer: Close the full calendar month, export consistent AdSense reports, record estimated earnings, page views, Page RPM, impressions, CTR, and CPC, then compare the same metrics with the previous month and the same month last year. Investigate the largest changes by page, country, platform, and ad format. Finish with evidence-based observations, one to three actions, an owner, and a review date.
What Is an AdSense Monthly Report?
An AdSense monthly report is a recurring performance review built from AdSense data and, where useful, supporting analytics or Search Console data. It gives stakeholders a stable snapshot of monetization performance for one completed month. The report should make the numerator and denominator behind every conclusion visible. For example, higher earnings can come from more page views even when Page RPM falls, while lower earnings can occur during a traffic decline even when each thousand page views earns more.
The report is not an invoice, a forecast, or proof that one site change caused a result. Google describes AdSense report earnings as estimates of account activity. Finalized earnings appear later in Transactions and may include adjustments. Therefore, label revenue in the performance template as estimated unless you deliberately reconcile it with finalized transactions after month end.
A Dashboard Is Not Yet a Report
A dashboard displays metrics. A report adds a question, comparison, interpretation, and decision. Screenshots of green and red percentages may look complete, but they do not explain whether a change came from traffic, auction demand, geography, devices, content mix, seasonality, or implementation. The written insight layer is what makes monthly reporting useful.
Why Use an AdSense Monthly Report Template?
A stable template prevents metric shopping. When results disappoint, publishers sometimes search through dozens of dimensions until they find a positive number. When results improve, they may credit the latest change without checking traffic mix or seasonal demand. A fixed template establishes the same core questions every month and makes selective interpretation harder.
- It creates a comparable history of traffic and monetization efficiency.
- It distinguishes a revenue change from a Page RPM change.
- It exposes concentration risk when a few pages or countries drive most earnings.
- It records anomalies, releases, policy events, and content changes beside the data.
- It turns observations into owned actions with deadlines.
- It gives future reviewers context that a raw export cannot preserve.
Choose a Clean Reporting Period
Use the first through the last day of a completed calendar month. Avoid preparing the final report while the current month is still in progress because a partial month cannot be compared fairly with a complete one. In AdSense, select Last month or enter the exact dates. Keep the account reporting time zone and currency consistent across exports.
Google allows report date comparisons with a previous period, previous year, or a custom range, but comparison ranges must cover the same duration. A line chart is generally the clearest chart for date comparisons. For monthly reporting, compare the completed month with both the preceding calendar month and the corresponding month one year earlier when enough history exists.
Month-over-Month and Year-over-Year Answer Different Questions
Month-over-month, or MoM, comparison detects recent movement and is helpful for operational monitoring. However, it can be distorted by the number of days, holidays, publishing cadence, campaigns, or advertiser budget cycles. Year-over-year, or YoY, comparison helps account for recurring seasonality, although changes in the site, search visibility, consent coverage, and market conditions can still limit comparability.
| Comparison | Best question | Main caution |
|---|---|---|
| MoM | What changed since the previous month? | Adjacent months may have different seasonality and day counts. |
| YoY | How did the same seasonal period change? | The site and traffic acquisition may have changed over a year. |
| Custom matched period | What happened around a release or event? | Choose the dates before inspecting the desired outcome. |
Core KPIs for Your AdSense Monthly Report
Keep the executive table small. Six core metrics usually explain most of the story: estimated earnings, page views, Page RPM, ad impressions, Page CTR, and CPC. Depending on the site, add Active View Viewable, coverage, ad requests, or sessions as diagnostic metrics. Never combine similarly named RPM or CTR metrics without checking their denominators.
| KPI | What it measures | How to interpret it |
|---|---|---|
| Estimated earnings | Revenue estimated in the selected report period | Affected by traffic volume and subject to later adjustments. |
| Page views | Views of pages displaying or requesting ads | Primary traffic-volume context for Page RPM. |
| Page RPM | Estimated earnings per 1,000 page views | Useful normalized monetization measure, not a guaranteed payment rate. |
| Ad impressions | Individual ad impressions served | Can move differently from page views when ad load or formats change. |
| Page CTR | Clicks divided by page views | Treat unusual increases cautiously; do not optimize for accidental clicks. |
| CPC | Estimated earnings from clicks divided by clicks | Influenced by auction demand, intent, geography, and advertiser mix. |
Use the Official Page RPM Formula
Google defines Page RPM as estimated earnings divided by page views, multiplied by 1,000. If estimated earnings are $240 from 80,000 page views, Page RPM is ($240 ÷ 80,000) × 1,000 = $3.00. For a detailed calculation audit, use the related guide on how to calculate AdSense Page RPM.
Page RPM lets you compare periods with different traffic volume, but it does not remove differences in country, device, page type, advertiser demand, or reader intent. A higher sitewide Page RPM can occur simply because more traffic shifted toward a strong segment. Always investigate the mix before claiming that an optimization worked.
Copy-Ready AdSense Monthly Report Template
The table below is the numeric center of the template. Add one row per KPI, retain raw values with consistent decimal precision, and calculate percentage change in separate columns. If a prior value is zero, mark percentage change as not applicable instead of dividing by zero.
| Metric | Current month | Previous month | MoM change | Same month last year | YoY change | Note |
|---|---|---|---|---|---|---|
| Estimated earnings | [value] | [value] | [%] | [value] | [%] | Estimated, not finalized |
| Page views | [value] | [value] | [%] | [value] | [%] | Check analytics consistency |
| Page RPM | [value] | [value] | [%] | [value] | [%] | Separate volume from efficiency |
| Ad impressions | [value] | [value] | [%] | [value] | [%] | Review impressions per page |
| Page CTR | [value] | [value] | [percentage-point and relative change] | [value] | [change] | Review sudden movement |
| CPC | [value] | [value] | [%] | [value] | [%] | Segment before interpreting |
| Active View Viewable | [value] | [value] | [percentage-point change] | [value] | [change] | Use measurable inventory context |
Percentage and Percentage-Point Formulas
For ordinary metrics, calculate percentage change as ((current − previous) ÷ previous) × 100. If Page RPM rises from $2.50 to $3.00, the relative increase is 20%. For rates such as CTR or viewability, report both relative change and percentage-point change when clarity matters. A CTR move from 1.0% to 1.2% is a 20% relative increase but only a 0.2 percentage-point increase.
In Google Sheets or Excel, if the current value is in B2 and the previous value is in C2, use =IFERROR((B2-C2)/C2,"") and format the result as a percentage. Keep a blank result when the comparison is undefined. Do not replace missing data with zero because zero has a specific numeric meaning.
Build the AdSense Monthly Report Step by Step
Step 1: Write the Reporting Scope
At the top, record the site or account, currency, reporting time zone, exact dates, comparison dates, data extraction date, and report owner. Also note whether values are estimated or reconciled. This small scope box prevents confusion when exports are reopened months later.
Step 2: Save a Reusable Custom Report
In AdSense, open Reports, create a new report, select the date range, choose breakdowns and metrics, apply only necessary filters, and save it with a stable name such as “Monthly publisher KPI.” Google also permits saved custom reports to be scheduled and emailed regularly. Scheduling reduces forgotten exports, but the email is still an input; interpretation remains a human task.
Step 3: Capture the KPI Snapshot
Copy values directly from the same report configuration for all periods. Avoid reading one month from the homepage card and another from a custom report with different filters. Confirm that currency, product, site scope, and date range match. Preserve the exported source file or at least its configuration notes.
Step 4: Calculate MoM and YoY Variance
Calculate changes after raw values are recorded. Flag material movements using thresholds chosen for your site, not arbitrary universal benchmarks. A low-volume site may experience wide natural variation, while a high-volume site may treat a smaller shift as operationally meaningful. Document the threshold before reviewing outcomes.
Step 5: Find the Drivers
Begin with the largest material change, then add one breakdown at a time. A decline in earnings with stable page views points toward monetization efficiency. A stable Page RPM with lower earnings points mainly toward traffic volume. When both change, quantify how much each contributed before exploring smaller dimensions.
Step 6: Add Context and Annotations
Record publishing volume, ranking changes, major traffic campaigns, consent changes, layout releases, ad-setting experiments, outages, policy notices, and unusual events. An annotation does not prove causation, but it creates hypotheses that can be tested against timing and segment data.
Step 7: Assign Actions
End with no more than three priority actions. Every action needs an owner, due date, expected mechanism, success metric, guardrail, and next review date. “Improve RPM” is not an action. “Audit the five pages responsible for 60% of the mobile Page RPM decline by August 10” is specific and reviewable.
Diagnose Revenue with a Simple Metric Tree
Estimated earnings can be understood through traffic volume and monetization efficiency. At a high level, approximate earnings equal page views multiplied by Page RPM divided by 1,000. This is an identity when the matching values come from the same scope. It is useful for explaining direction, not for forecasting guaranteed income.
| Pattern | Likely first interpretation | Next check |
|---|---|---|
| Earnings up; page views up; Page RPM flat | Growth is mainly traffic-driven | Countries, landing pages, and traffic sources |
| Earnings up; page views flat; Page RPM up | Monetization efficiency improved | Device, country, format, viewability, and demand |
| Earnings down; page views down; Page RPM stable | Traffic loss is the main driver | Search visibility and top-page traffic |
| Earnings down; page views stable; Page RPM down | Value per thousand views weakened | Auction mix, geography, platforms, pages, and implementation |
| Earnings flat; page views up; Page RPM down | Traffic growth was offset by weaker yield | Quality and mix of incremental traffic |
Use Breakdowns Without Creating Noise
Page and URL Breakdown
Identify pages with the largest absolute earnings contribution and the largest material variance. A high percentage change on a page with ten views is rarely a priority. Review contribution and change together. For a deeper measurement setup, follow the guide to track AdSense performance by page and URL.
Country Breakdown
Country mix can change Page RPM and CPC even when the site behaves normally. Compare each country’s share of page views with its share of earnings, then inspect changes in the largest markets. Do not assume that a lower-RPM country sends “bad” traffic; the purpose is to explain portfolio movement, not to devalue readers.
Platform Breakdown
Compare mobile, desktop, and tablet using the same dates and site scope. A rise in mobile share can lower or raise sitewide Page RPM depending on layout, viewability, intent, and demand. Inspect both the segment’s own performance and its share of total traffic. Weighted mix often explains a sitewide change that no device-specific optimization caused.
Ad Format and Ad Unit Breakdown
Review formats or units when there was a layout change, Auto ads adjustment, or unusual impression movement. Do not compare a unit-level RPM directly with site Page RPM as if the denominators were identical. Look for missing units, implementation changes, viewability shifts, and disproportionate impression growth.
Create an Insight and Anomaly Log
The insight log is where the report becomes institutional memory. Each entry should separate observation, hypothesis, evidence, confidence, and next test. Avoid causal language when the evidence is merely correlated.
| Field | Example |
|---|---|
| Observation | Mobile Page RPM declined 12% MoM while desktop was stable. |
| Scope | Completed month; all article pages; same currency and time zone. |
| Evidence | Mobile country mix shifted and two high-traffic templates lost measurable impressions. |
| Hypothesis | Traffic mix plus a template implementation issue contributed to the decline. |
| Confidence | Medium; timing aligns, but no controlled experiment exists. |
| Next action | QA the two templates and compare matched country-device segments. |
| Review date | [date] |
Write a One-Paragraph Executive Summary
Use this structure: “During [month], estimated earnings were [value], [change] MoM and [change] YoY. Page views changed [x], while Page RPM changed [y], indicating that [traffic volume / monetization efficiency / both] drove the result. The largest supported contributors were [driver one] and [driver two]. Important limitations were [data or comparability note]. Next month we will [action], measured by [metric], while protecting [guardrail].”
Keep facts and hypotheses distinct. “Mobile Page RPM fell 12%” is an observation. “The new layout caused the decline” is a causal claim and requires stronger evidence. If you only have timing and segment correlation, say the layout is a candidate explanation and schedule a controlled check.
AdSense Monthly Report Action Tracker
| Priority | Action | Owner | Due date | Success metric | Guardrail | Status |
|---|---|---|---|---|---|---|
| 1 | [Specific diagnostic or test] | [Name] | [Date] | [Metric and target] | [UX/policy/quality limit] | Planned |
| 2 | [Content or traffic action] | [Name] | [Date] | [Metric and target] | [Quality limit] | Planned |
| 3 | [Reporting improvement] | [Name] | [Date] | [Completion condition] | [Data consistency rule] | Planned |
Carry unfinished actions into the next report with their original date and explanation. Do not silently delete a failed test or missed task. A monthly system becomes valuable when it reveals which decisions worked, which did not, and which assumptions need revision.
Common AdSense Monthly Report Mistakes
- Comparing a partial current month with a complete previous month.
- Calling estimated earnings a finalized payment.
- Using earnings alone without traffic or Page RPM context.
- Comparing metrics with different denominators as if they were interchangeable.
- Treating a tiny segment’s large percentage change as a major business event.
- Adding several breakdowns at once and losing the source of the change.
- Ignoring country, device, page, or traffic-source mix.
- Claiming causation from a before-and-after coincidence.
- Changing definitions, currency, time zone, or filters between months.
- Listing observations without an owner, deadline, or review plan.
A 60-Minute Monthly Reporting Routine
| Time | Task | Output |
|---|---|---|
| 0–10 minutes | Confirm scope, dates, time zone, currency, and report configuration | Clean reporting frame |
| 10–20 minutes | Record KPIs and calculate MoM/YoY changes | Completed scorecard |
| 20–40 minutes | Investigate the two or three largest movements | Driver notes and evidence |
| 40–50 minutes | Write summary, limitations, and anomaly log | Decision-ready narrative |
| 50–60 minutes | Assign up to three actions and schedule review | Owned action tracker |
If the analysis takes much longer, the scope may be too broad. Preserve deeper questions for a focused investigation rather than turning the standard monthly review into an endless audit. Conversely, if the report takes only five minutes, it may be copying metrics without interpretation.
Quality-Control Checklist for an AdSense Monthly Report
- The month is complete and exact dates are shown.
- Comparison periods cover equal durations.
- Currency, time zone, site scope, filters, and product are consistent.
- Estimated earnings are labeled accurately.
- Every percentage is calculated from preserved raw values.
- Page RPM uses page views as its denominator.
- Rate changes use percentage points where that improves clarity.
- Large changes are checked for contribution and sample size.
- Observations are separated from hypotheses and causal claims.
- Anomalies and site changes are annotated.
- Actions have owners, deadlines, metrics, and guardrails.
- Official exports and source notes are retained.
How to Improve the Template Over Time
After three months, review which sections influenced actual decisions. Remove decorative metrics that never change an action. Add a diagnostic only when it repeatedly explains meaningful variance. Keep definitions in a data dictionary so another team member can reproduce the report.
After twelve months, the archive becomes a seasonality reference. Compare recurring peaks and declines, but do not turn historical patterns into guarantees. Advertiser demand, search algorithms, privacy choices, content mix, and economic conditions can change. Use history to set a range of expectations and detect unusual departures.
Frequently Asked Questions
What should an AdSense monthly report include?
Include scope, dates, estimated earnings, page views, Page RPM, impressions, Page CTR, CPC, MoM and YoY comparisons, major segment drivers, anomalies, limitations, an executive summary, and an action tracker.
Should I use estimated or finalized earnings?
Use estimated earnings for the performance report and label them clearly. If finance reconciliation is required, add finalized earnings from Transactions later as a separate field rather than silently replacing the original performance value.
When should I prepare the report?
Prepare it after the calendar month is complete and reporting data has settled enough for your operating process. Record the extraction date because estimated results may later change.
Is month-over-month comparison enough?
No. MoM is useful for recent movement, but YoY can provide seasonal context. Use both when data exists, then note differences in traffic, content, implementation, and market conditions.
Which metric matters most?
There is no single universal metric. Estimated earnings describes revenue, page views describe volume, and Page RPM describes normalized efficiency. Interpret them together, then use CTR, CPC, viewability, and breakdowns diagnostically.
How many breakdowns should I use?
Start with the metric tree, then add one breakdown at a time. Page, country, platform, and ad format are common options. Investigate only material segments with enough volume.
Can I automate the monthly report?
You can save and schedule AdSense custom reports and automate spreadsheet calculations. However, annotations, causal caution, prioritization, and action selection still require review.
What if the previous month had zero revenue?
Do not calculate a percentage change from zero. Show the raw values, mark relative change as not applicable, and explain the new activity in the notes.
Does higher CTR always mean better performance?
No. CTR must be interpreted with revenue, CPC, traffic quality, placement safety, and user experience. A sudden increase can require investigation for accidental-click or implementation risk.
How many actions should come from the report?
Choose one to three priority actions. More actions dilute ownership. Each should state the expected mechanism, responsible person, due date, success metric, and safety guardrail.
Final AdSense Monthly Report Checklist
A strong AdSense monthly report is consistent, cautious, and actionable. It uses completed periods, preserves raw values, compares like with like, distinguishes traffic from monetization efficiency, and avoids unsupported causal claims. Most importantly, it closes the loop by reviewing last month’s actions before creating new ones.
Start with the copy-ready scorecard in this guide. Save one stable custom report, export it on a regular schedule, add only the breakdowns needed to explain material changes, and keep the final narrative short enough to guide a decision. Over time, the archive will show not only how earnings changed, but also how reliably your team learned from the evidence.


