---
title: "What to fix first in your weekly paid media review"
description: "Compare matched weeks, check how much spend is at risk, and turn your Google and Meta reports into a clear list of what to fix, check or hold."
url: https://adctrl.ai/blog/weekly-paid-media-review/
last_updated: 2026-11-20
---

Weekly Paid Media Review

# What to fix first in your weekly paid media review

Build a ranked queue for Google and Meta with one action, owner and deadline per issue.

![Kaan Catalkaya](https://adctrl.ai/media/founder-kaan-v1.webp)

By [Kaan Catalkaya](https://adctrl.ai/blog/weekly-paid-media-review/#author), Founder of AdCtrl

Published 20 November 2026 · 11 min read

![Weekly paid media review cover with Google Ads, Meta and Google Analytics reporting.](https://adctrl.ai/media/blog/weekly-paid-media-review/hero-v1.webp)

## Short answer

- Compare completed weeks with the same campaign scope, conversion action and reporting age.
- Act on a confirmed issue that needs immediate attention. Give each unresolved issue a dated check and a named owner.
- Estimate the extra spend before that check and compare it with your remaining agreed exposure. Bring the check forward if the estimate would use up the allowance.
- Keep platform-attributed results and verified business outcomes in separate columns so the decision can be traced to its evidence.

A weekly paid media review should tell you which account to open first. Compare equivalent weeks and check what changed. Estimate how much each campaign could spend before the next report or event check. Act on confirmed issues, investigate open questions and set a date to check the rest.

If an expired offer recorded impressions this morning, put that ad at the top of the list.

I build AdCtrl, which can pull the Google Ads, Meta Ads and Google Analytics 4 (GA4) reports used here[1](https://adctrl.ai/blog/weekly-paid-media-review/#ref-1). The review also works with exports. For a full inventory of Google Ads settings, use the [Google Ads audit checklist](https://adctrl.ai/blog/google-ads-audit-checklist/).

Checked 20 November 2026 against the platforms' reporting documentation[2](https://adctrl.ai/blog/weekly-paid-media-review/#ref-2), [3](https://adctrl.ai/blog/weekly-paid-media-review/#ref-3), [4](https://adctrl.ai/blog/weekly-paid-media-review/#ref-4).

Line up the reporting periods and outcomes, check the evidence and decide which campaign needs attention before the next review.

## What do you need before a weekly paid media review?

Begin the weekly review with **two completed, comparable weeks** and a written limit for how much spend you can risk while a decision is open. Use each account's reporting time zone and currency. Identify the account and campaigns, agree which action counts as the outcome and record when you pulled the report.

Imagine an operator opening the 2–8 and 9–15 November reports on a Monday. Both weeks cover Monday to Sunday. A fresh pull on Monday can still make the older week look healthier because it has had longer to pick up conversions. A copy of the older report from the same time after its week closed gives you a fairer view of progress[5](https://adctrl.ai/blog/weekly-paid-media-review/#ref-5).

Note the target for the outcome you actually care about. A lead campaign might have a cost target for qualified enquiries. The platform might report form submissions. Keep each measure in its own column and get qualified counts from the sales team. Use the [CPA calculator](https://adctrl.ai/tools/cpa-calculator/) to calculate cost per acquisition (CPA) from spend and the relevant outcome count, with the action named beside the result.

Agree the allowable **additional spend while the issue is unresolved**. Record what has already been spent against that allowance since the issue was raised. If you agreed to risk $500 and have already spent $200 against that allowance, you have $300 left. Put the source of the authorization and its owner beside that number.

## How do you compare two weeks fairly?

Compare both weeks with a row per campaign and platform and **matching dates, currency and outcomes**. Write the account ID beside the campaign name so the person acting on the row can locate it. Mark the data that is still coming in, then verify the specific piece of evidence that could change the decision.

1. **Pull the same columns for both periods.**
**Manual:** Export campaign spend, the named result and the count for each week. Save the date and time of each export. In Meta, record the reporting attribution setting alongside purchases or leads. Attribution is the rule for assigning credit for an outcome to an ad.
**With AdCtrl:** Use the campaign prompt in the next section and add the verified attribution settings to the result.
2. **Check which day gets the result.**
**Manual:** In Google Ads, export campaign spend without the conversion action segment. Export the named action counts separately and match them to spend by campaign ID and exact dates.
**With AdCtrl:** Use the separate reads in the campaign prompt. Verify that the campaign IDs, dates and conversion columns match your review before calculating CPA.
3. **Verify the signal that could change the call.**
**Manual:** If paid traffic might have changed, open GA4 Traffic acquisition for the same dates. If a purchase is missing, trace one known paid order through checkout and measurement. Compare equally mature groups when you check qualified lead counts with sales.
**With AdCtrl:** Use the GA4 prompt below for a separate view of sessions. Bring the manual order or qualified-lead check back to the review with its source and date.
4. **Find any relevant account change.**
**Manual:** Open Google Ads Change history for the affected campaign and date range. Record what changed and who changed it. Then look for corroborating evidence, such as when the campaign began serving the edited offer.
**With AdCtrl:** Pull a campaign report broken down by date to see when the reported movement began. Add the change history timestamp next to that row.

Google Ads can leave Cost blank under the conversion action segment. Standard Conversions uses the click date and Conversions (by conv. time) uses the event date. Use click-date counts to calculate CPA alongside campaign spend for click-attributed traffic. Conversion-date totals line up aggregate timing. To verify that a specific purchase or lead arrived, check that event separately[6](https://adctrl.ai/blog/weekly-paid-media-review/#ref-6), [7](https://adctrl.ai/blog/weekly-paid-media-review/#ref-7).

Use Session source / medium in GA4 Traffic acquisition to compare sessions assigned to the same traffic sources. For a missing purchase, the [Tracking Checker](https://adctrl.ai/tools/tracking-checker/) can inventory recognized tag IDs on the public landing page. Keep the checkout evidence for the known order with the result[4](https://adctrl.ai/blog/weekly-paid-media-review/#ref-4), [8](https://adctrl.ai/blog/weekly-paid-media-review/#ref-8).

Google Ads Help explains how Change history places changes beside account data. Use the timestamp to investigate what happened around the change[2](https://adctrl.ai/blog/weekly-paid-media-review/#ref-2).

If CPA worsens on Wednesday after a Tuesday edit, check whether it also worsened in campaigns whose settings stayed the same. Check whether conversions are still arriving. Keep possible causes separate from confirmed findings. For the underlying date and attribution checks, see [why conversion reports disagree](https://adctrl.ai/blog/conversion-discrepancy/).

Common mistake

A fresh export of last week beside a mature export from the week before can send you after the wrong campaign. Use snapshots pulled at the same reporting age when you have them. For a recent Google Ads period, put an exact reread on the calendar if delay could change your decision.

On a sales account, check the source that answers the question. The store's all-channel paid order count tells you how the store did that week. Check the scope of Meta's attributed purchases beside it. If Shopify shows a paid order GA4 missed, give the [checkout-to-purchase trace](https://adctrl.ai/blog/shopify-ga4-missing-purchases/) to the person who can verify that order.

In AdCtrl, write: only reads your accounts

```
For the connected GA4 property I select, show sessions by Session source / medium for the exact completed date ranges I provide. Keep each period separate and show missing rows as unavailable. Make no changes.
```

## Which campaign should you deal with first?

Give confirmed problems that need immediate action the first slot. For unresolved changes, **estimate how much spend can accrue before the next useful check**. Divide the remaining agreed allowance by the observed daily spend pace to estimate how long you have from now.

At a steady $200 a day with $300 remaining, there is about a day and a half before expected spend uses up the allowance. If the next evidence is due in two days, schedule an earlier check. Rank issues with similar consequences by how soon each allowance could run out.

Use spend from comparable active days and account for any known gaps in the delivery schedule. If a sale or budget edit makes the daily spend rate uncertain, estimate a range and use the high end to choose a review time.

If the allowance is unset, send the authorized owner today's spend pace and the next check that could settle the question. Keep the approved budget in place while they decide. Move confirmed issues to the front and escalate sooner if continuing to spend could conflict with the client's instructions.

Use an approved pause or other spending control if exposure must stop. Confirm who has approval to make the change, then verify the status of the item you changed.

In Claude or ChatGPT

Use the returned rows to build the queue. Add your written spend allowance and the evidence you still need before deciding.

In AdCtrl, write:

```
Compare these exact periods for the selected Google Ads and Meta Ads accounts. Report dates, campaign IDs, currency, spend and named outcome counts per platform. For Google, keep unsegmented spend and action counts separate. Flag unavailable data. Read only.
```

[Start free](https://app.adctrl.ai/app) [How it works](https://adctrl.ai/docs/#changes) 3-day free trial · no card needed

### A worked queue for Monday morning

Imagine you have three campaigns to review at 9 a.m. on Monday. All amounts are in dollars. Each campaign has its own allowance for additional spend during the investigation. Use **one row per decision**, with the evidence you have and the next piece you need.

| State | What the operator can verify | Estimated spend before next check | Decision |
| --- | --- | --- | --- |
| **Act now** | A Meta ad is active and recorded impressions today after its offer ended Sunday. The offer dates and the ad ID are confirmed. Allowance remaining is $0. | About $180 if left until tomorrow at $180/day | Get or confirm authorization to pause the affected ad, then read back its status. |
| **Investigate** | Meta credited 10 purchases in the earlier week and 6 in the later week on $1,400 in each. The store recorded 15 paid orders in both weeks across all channels. Allowance remaining is $300. | $400 over two days at $200/day | Move the check to Tuesday. Compare attribution settings and trace one known purchase. |
| **Hold** | Google Search went from 10 to 8 attributed purchases with $700 spent in each week. The snapshots are the same age. Previous weeks added credit after Monday. Allowance remaining is $250. | $200 over two days at $100/day | Keep approved settings and compare matching Wednesday snapshots. |

Bring the second campaign's check forward. At the observed pace it would use $200 by Tuesday, with $100 of the allowance left.

Source: Fictional accounts and amounts. The reporting cases use the scope and conversion lag documented by Google and Meta[5](https://adctrl.ai/blog/weekly-paid-media-review/#ref-5), [3](https://adctrl.ai/blog/weekly-paid-media-review/#ref-3).

The offer issue goes first because the ad has recorded impressions outside the offer dates and its status is active. On prospecting, a stable store total leaves open how much Meta contributed. On Search, the recent CPA works out to $87.50 versus $70 in the matching older snapshot. The history of later credit gives you a reason to wait within the agreed allowance.

If Tuesday's Meta check shows that one ad set is taking most of the spend, use the [Meta campaign budget guide](https://adctrl.ai/blog/meta-cbo-spending-on-worst-ad-set/) before choosing a new split.

If Wednesday's Google report could still pick up late conversions, use the [conversion lag guide](https://adctrl.ai/blog/google-ads-conversion-lag/) to work out how many would change your decision. Compare the fresh read with the previous week's saved Wednesday snapshot. If that snapshot is missing, label the comparison provisional.

## What should be in the weekly handoff?

Write the weekly handoff so another operator can **open the right campaign and know when to act**. Keep a short record of the observed change, the next decision and its deadline. Give the recipient the reporting source and the conditions that would move the decision up.

Copy this line into your weekly note.

`Campaign and account ID | Periods and reporting setting | Observed evidence and source | Remaining allowance | Next check and trigger | Decision and owner`

| Field | Example handoff for the investigation |
| --- | --- |
| Scope | Meta prospecting, account 410 and campaign 207. Compare 2–8 and 9–15 November in the account's time zone, with purchases under the same reporting setting. |
| Observed | Meta credited 10 and 6 purchases. Spend was $1,400 each week. Store export shows 15 paid orders each week across all channels. |
| Decision | Investigate the change in attributed purchases. Budget stays at its current approved level until the next check or a new decision. |
| Owner and deadline | Account lead checks attribution settings and traces a known purchase by Tuesday at 9 a.m. |
| Bring forward if | Delivery pace puts you on track to use up the $300 allowance before the deadline. |

Copy the field names into a weekly note. The recipient can see what was observed, who owns the next check and when spend changes the deadline.

Source: Fictional handoff based on the worked queue. Meta documents the scope of its performance reporting[3](https://adctrl.ai/blog/weekly-paid-media-review/#ref-3).

If a change is authorized and applied, record the time and verified status in a separate sentence. For the expired offer, log the affected ad ID and authorization. Once that ad is paused, confirm its status. A teammate reading the note should be able to pick up the work at the right point.

A client may ask whether both channels pay for themselves. Use paid media spend and total store revenue as separate inputs to the [blended ROAS guide](https://adctrl.ai/blog/blended-roas/). Keep that business-level result beside the platform-attributed rows. Revisit which campaigns to change once their own checks are complete.

## What should you check before sending the review?

Check that every line in the review has a **decision or a next check someone owns**.

- Do both periods cover the same weekdays and use the same campaign scope?
- Did you write down the outcome definition and reporting date basis?
- Does the note identify which figures are platform-attributed and which came from a business record?
- Did you timestamp the exports and mark rows where the reporting age differs?
- Does each open issue have a remaining spend allowance and a dated next check?
- Can the person taking over locate the campaign and see who can authorize a change?
- Did you verify the live state for any change marked complete?

## Frequently asked questions

### What if I review accounts in different currencies?

Keep each row in its account currency and compare its projected spend with that account's remaining allowance. If you need a combined amount for one finance meeting, record the exchange rate and the date you used it.

### When should I recheck during a promotion?

Set the next review at the point when you can still act on the offer, budget or landing page. Estimate spend up to that point from comparable promotional days when you have them. If the allowance could run out sooner, bring the check forward.

### How do I report outcomes when a client has yet to share the CRM numbers?

Name the platform outcome you actually have, such as submitted forms. Give someone a deadline for the qualified lead or closed deal export. Keep that business outcome marked pending until a source confirms it.

### What CPA should I report for a campaign with zero recorded outcomes?

Record spend and the verified zero count. Leave CPA blank because it has no value when you divide by zero. Label a missing outcome field separately and check whether the selected report has the data you need.

### What if I only have one saved weekly report?

Pull the previous period again for context and label the difference in reporting age. Save the current export and arrange a second pull. You will have a dated record of what moves by the next check.

## What to do next

Open the account with the confirmed issue you can act on today. Give the next uncertain row an owner and a check time that fits its remaining spend allowance. Keep the same timestamps and outcome columns for the next review so you can see what changed.

For a more detailed look at one account, use the [Google Ads audit checklist](https://adctrl.ai/blog/google-ads-audit-checklist/). To pull campaign performance and GA4 reports for your review, [connect AdCtrl](https://adctrl.ai/docs/#getting-started).

## Sources

1. [What you can do](https://adctrl.ai/docs/), AdCtrl. Accessed 20 November 2026.
2. [About change history](https://support.google.com/google-ads/answer/19888?hl=en), Google Ads Help. Accessed 20 November 2026.
3. [Ads Insights API](https://developers.facebook.com/documentation/ads-commerce/marketing-api/insights), Meta for Developers. Accessed 20 November 2026.
4. [GA4 Traffic acquisition report](https://support.google.com/analytics/answer/12923437?hl=en), Google Analytics Help. Accessed 20 November 2026.
5. [About conversion lag reporting](https://support.google.com/google-ads/answer/9347141?hl=en), Google Ads Help. Accessed 20 November 2026.
6. [Understand your conversion tracking data](https://support.google.com/google-ads/answer/6270625?hl=en), Google Ads Help. Accessed 20 November 2026.
7. [Use segments in your tables](https://support.google.com/google-ads/answer/2454072?hl=en), Google Ads Help. Accessed 20 November 2026.
8. [Tracking Checker](https://adctrl.ai/tools/tracking-checker/), AdCtrl. Accessed 20 November 2026.

## Related articles

- [**Google Ads audit checklist 2026: 40 checks, real API fields** 40 Google Ads audit checks for 2026 (AI Max, Performance Max, Demand Gen), each with its report, the API field if any, and whether AI can judge it.](https://adctrl.ai/blog/google-ads-audit-checklist/)
- [**Is Google Ads conversion lag driving up your CPA?** Calculate how many late conversions Google Ads needs to hit your target CPA, then use your delay history to decide whether to wait or investigate.](https://adctrl.ai/blog/google-ads-conversion-lag/)
- [**GA4 conversions don't match Google Ads: normal or broken?** Google Ads, GA4 and Meta count conversions on different dates and rules. Line up the right columns, then tell a normal gap from broken tracking.](https://adctrl.ai/blog/conversion-discrepancy/)
- [**Meta Ads CBO spending on your worst ad set?** See why Meta CBO can favor an ad set with a higher CPA, how to compare results fairly, and when to hold the budget or run a test.](https://adctrl.ai/blog/meta-cbo-spending-on-worst-ad-set/)
- [**Blended ROAS: check what Google and Meta really made** Blended ROAS is store revenue divided by all ad spend. Work it out from four numbers, see how much Google and Meta double count, and find break-even.](https://adctrl.ai/blog/blended-roas/)
- [**Shopify GA4 missing purchases? Trace one order** Shopify got the order but GA4 seems to have missed it? Trace one paid order to find out if checkout, event collection or attribution broke.](https://adctrl.ai/blog/shopify-ga4-missing-purchases/)

## Keep going

[Learn more first **Google Ads audit checklist 2026: 40 checks, real API fields** Keep reading before you change anything.](https://adctrl.ai/blog/google-ads-audit-checklist/) [Ready to try it **Run this in Claude or ChatGPT with AdCtrl** Connect Google Ads and Meta Ads, ask in plain words and approve every change. 3-day free trial.](https://app.adctrl.ai/app)

![Kaan Catalkaya](https://adctrl.ai/media/founder-kaan-v1.webp)

About the author

[Kaan Catalkaya](https://adctrl.ai/#founder), Founder of AdCtrl

Kaan Catalkaya founded AdCtrl and runs his own performance agency, where he manages Google Ads and Meta Ads for clients. AdCtrl gives Claude and ChatGPT the playbooks he uses on that client work.

## Put your AI to work on your campaigns.

AdCtrl connects Claude or ChatGPT to Google Ads, Meta Ads, GA4, Tag Manager and Search Console. Ask in plain words and approve every change.

[Start free](https://app.adctrl.ai/app)

3-day free trial · no card needed

A product by mondaybrew ApS · CVR 45217779 · Vesterbrogade 74, 3. sal, 1620 København V, Denmark

Google, Meta, ChatGPT and Claude are trademarks of their respective owners. AdCtrl is an independent product by mondaybrew ApS.
