Cross‑Platform Ad Reporting Template: Weekly Dashboard for Google, Meta, and Microsoft Ads

Overview

Combining Google, Meta, and Microsoft Ads data is less about finding one perfect dashboard and more about creating a dependable reporting process. Each platform uses different labels, attribution settings, campaign structures, and export formats. A useful weekly PPC reporting template creates a common layer between those raw exports and the decisions you need to make.

Use the workbook as a simple reporting system with five tabs:

1. Instructions: Record the reporting period, source files, owner, and update checklist.
2. Metric mapping: Document how each platform field maps to a shared KPI.
3. Raw exports: Paste or import unchanged data from Google Ads, Meta Ads, and Microsoft Ads.
4. Weekly snapshot: Summarize spend, impressions, clicks, conversions, revenue, CPA, and ROAS by platform and campaign.
5. Four-week trend: Compare the current week with the previous three reporting periods.

Keep raw exports separate from calculated fields. This makes the report easier to audit when a total looks unusual, a platform changes an export label, or an attribution window differs from the previous period.

The dashboard should answer practical questions: Which channel spent the most? Which produced the most conversions? Is efficiency improving or declining? Are reported results comparable? What requires investigation before budget or bid changes are made?

How to estimate

Start by choosing one reporting period and one reporting level. For a weekly report, use the same seven-day date range across all platforms and select either account, campaign, or ad set as the main comparison level. Campaign-level reporting is usually a useful compromise between detail and readability.

Map each source field to a normalized column. A basic mapping table can look like this:

The mapping is only useful if the definitions are consistent. For example, do not combine landing-page views from one platform with link clicks from another and label the total simply as clicks. Choose a definition, record it in the mapping tab, and apply it consistently.

Use these formulas in the calculated columns:

• CTR: clicks divided by impressions. Format the result as a percentage.
• CPC: spend divided by clicks. Leave blank or mark as not available when clicks are zero.
• Conversion rate: conversions divided by clicks, provided the conversion definition is comparable.
• CPA: spend divided by conversions.
• ROAS: revenue divided by spend.

For a total row, calculate metrics from total inputs rather than averaging campaign percentages. For example, total CPA should equal total spend divided by total conversions. An average of campaign CPAs can be misleading because it gives a small campaign the same weight as a large one.

Inputs and assumptions

Before building the weekly dashboard, write down the assumptions that determine how the numbers should be interpreted.

Reporting dates and time zone

Set a fixed week definition, such as Monday through Sunday, and use the same account time zone wherever possible. If one export uses a different time zone, note the difference in the instructions tab rather than silently combining the records.

Conversion definition

Decide whether “conversions” means all recorded actions, primary actions only, purchases, leads, or another business event. A Google Ads conversion total, a Meta result count, and a Microsoft Ads goal total may not represent identical actions. Use a normalized conversion column only when the business meaning is close enough for the intended comparison. Otherwise, create separate columns such as leads, purchases, and qualified inquiries.

Revenue and attribution

Record whether revenue is platform-reported, analytics-reported, or imported from a sales system. Also document the attribution window or reporting rule used by each platform. Platform ROAS figures can differ from one another and from finance or analytics data even when spend is correct. The report should show those figures as measurement outputs, not as unquestionable facts.

Currency and data quality

Convert currencies before calculating combined spend or ROAS, using a documented conversion rule. Do not mix account currencies in one total. Add validation checks for blank campaign names, duplicate rows, negative or unexpectedly large spend, zero-click rows, and missing conversion values.

Use UTM parameters to connect ad clicks with downstream analytics. A consistent naming convention for source, medium, campaign, and content makes it easier to compare platform exports with website sessions and conversions. The UTM tracking governance guide provides a framework for naming rules and audits.

Worked examples

Assume the weekly export contains the following intentionally simplified figures:

For Google, CPA is $1,200 divided by 48, or $25. ROAS is $3,600 divided by $1,200, or 3.0. Meta has a CPA of $30 and ROAS of 2.5. Microsoft has a CPA of $25 and ROAS of 3.0.

The combined totals are $2,500 in spend, 6,200 clicks, 94 conversions, and $7,050 in revenue. The blended CPA is therefore about $26.60, and blended ROAS is 2.82. These blended figures should be calculated from the combined totals, not by averaging the three platform CPAs or ROAS values.

In the four-week trend tab, add one row per platform per week and include a total row for each week. Useful comparison columns include week-over-week spend change, conversion change, CPA change, and ROAS change. Use conditional formatting sparingly: highlight material changes that warrant investigation, not every fluctuation.

If the current week shows lower conversions, check tracking completeness, conversion lag, landing-page changes, campaign status, and attribution settings before concluding that media performance declined. A message-match audit can help when clicks are stable but conversion rates fall.

When to recalculate

Generate the report weekly using the same cutoff and export procedure. Re-download or refresh the template before each reporting cycle, then confirm the date range, currency, conversion definition, and attribution settings. Compare the current totals with the source platforms before sharing the dashboard.

Review the report monthly. Revisit the four-week trend, investigate large changes, and check whether benchmark rows or target thresholds still reflect current business priorities. Benchmarks should be treated as reference points rather than automatic decision rules.

Update the metric mapping table quarterly, or sooner if a platform renames a field, changes an export layout, introduces a new conversion definition, or alters an attribution setting. Refresh export instructions after a major platform interface or API change. Recheck currency rules, UTM conventions, and conversion tracking whenever the website, checkout, CRM, or analytics implementation changes.

Keep a short change log in the workbook. Record the date, field changed, reason, and person who approved the change. This prevents unexplained differences between weekly reports and makes the dashboard easier to maintain.

For the next reporting cycle, begin with three checks: confirm that all platforms cover the same dates, verify that the mapped conversion events are comparable, and reconcile total spend with each source export. Once those checks pass, calculate the shared KPIs and use the four-week trend to guide questions—not to replace judgment about tracking quality, attribution, or business outcomes.