A weekly Facebook Ads review should end with a decision, not just a screenshot of the results column.
What needs fixing? What deserves a test? What should we leave alone until there is enough evidence? Those are the questions I would bring to the review, whether the account is managed internally or through Facebook ads management services.
This is a recurring operating review, not a full account audit. The goal is to connect what changed in the campaign with what happened in the business, then give the next action a clear owner.
Start with a consistent reporting window
I would use the last seven complete days as a starting point and compare them with the previous seven. Keep the account time zone, selected campaigns, result definition, and attribution settings consistent. Write down any exceptions, such as a promotion ending halfway through the period.
That weekly window is a working rhythm, not a rule that every decision needs to happen within seven days. If the account produces only a few useful outcomes each week, widen the performance view. A small change in the number of leads can make the percentage change look dramatic.
Also separate today's delivery check from the completed-period review. A partial day is useful for spotting an outage, but it is not a fair comparison with a full day of spend.
Check delivery and spending before judging performance
First, confirm that the campaigns intended to run are actually delivering. Look for unexpected pauses, rejected ads, payment problems, broken destinations, or spending that does not fit the agreed plan.
Then compare month-to-date spend with the budget and the days remaining. A simple pacing estimate is spend to date divided by elapsed days, multiplied by the number of days in the month. Treat that as a baseline, not a forecast you can trust without context. Scheduled promotions and deliberate budget changes can make a straight-line estimate misleading.
If delivery is lower than planned, “increase the budget” should not be the automatic answer. Check whether the campaign is already spending what it has, whether the destination works, and whether there is an operational issue to resolve first.
Put the reported result next to the business outcome
Meta's campaign optimization documentation defines Results according to the selected objective and settings. That is why I would label the actual event in the review rather than writing only “conversions.”
For a lead campaign, keep submitted forms separate from contacted leads, qualified inquiries, and customers. A form submission tells you an action occurred. It does not tell you whether the person needs the service or whether anyone followed up.
Ask whoever handles the inquiries for a short, consistent review: relevant, irrelevant, duplicate, unreachable, or still being worked. Keep that feedback in private business records. The campaign discussion needs the pattern, not a public list of personal details.
Do not force platform totals and CRM totals to match. Check the date definitions, source capture, duplicate records, and stage being counted before deciding that either number is wrong. If the sales team has not reviewed the newest leads yet, mark quality as pending.
The guide to Meta conversion leads and CRM feedback covers sending downstream information back into the advertising system. The weekly management task is more basic: make sure someone is reviewing what the leads turned into.
Use creative metrics to choose the next question
Look at which messages received meaningful delivery, what people did after clicking, and whether the resulting inquiries were useful. Avoid declaring a winner because one ad has a cheaper click or because another received almost no spend.
Meta supports saved reporting columns and breakdowns for reviewing performance. I would keep a small, repeatable column set rather than rebuilding the report every week: spend, the specific result, cost per result, link clicks, and the downstream outcome you can actually verify.
For website campaigns, compare traffic with the next step on the site. If people click but do not complete the form, the next investigation may be the page or the offer, not the image. For instant-form campaigns, inspect the form experience and lead quality instead of using a website funnel that does not apply.
Turn the observation into a focused creative request. “Test a version that states who this service is for” gives a designer or copywriter something to work with. “Make the ad better” does not. The creative refresh workflow explains how to turn that request into a production queue.
Read the change log before making another edit
Check what changed since the previous review: budget, audience, creative, offer, destination, or measurement. If several things moved together, do not attribute the outcome to your favorite change.
Meta warns that significant edits can trigger a new learning period. Its documentation also notes that making several changes together makes it harder to identify which individual change affected performance. That is a reason to plan changes deliberately, not a reason to leave a broken campaign untouched.
I would separate urgent repairs from performance experiments. Fix an incorrect link or a broken form promptly. For a proposed audience or creative test, write down the question, the spending boundary, and when you will look again. A weekly review does not require a weekly account overhaul.
A decision log you can copy
Use one row per issue. Keep observations separate from explanations so a working hypothesis does not quietly become a fact.
| Field | What to record |
|---|---|
| Scope | Dates, campaign or ad set, event definition, and comparison window. |
| Observation | What changed in the data or the customer feedback? |
| What remains unknown | What prevents a confident conclusion? |
| Decision | Fix now, investigate, test, or leave unchanged. |
| Owner and boundary | Who does the work, who approves it, and what spending limit applies? |
| Next review | When to revisit it and what evidence would change the decision. |
Hypothetical example, not a client result: a service business sees more form submissions, but the team reports that several inquiries concern a service it does not offer. The observation is a mismatch in inquiries. The cause is not yet established.
The next action could be to review the ad and form together, then test clearer service wording. Keep the existing budget boundary while the revised message is reviewed. Assign someone to classify the next batch of inquiries and set a review date. That is more useful than celebrating a lower cost per form or immediately changing the audience.
End with three short notes
I would close the review with what is working, what is not working, and what is blocked. For each problem, name the next action and its owner. If nothing needs changing, say why and record when you will review it again.
If you are evaluating Facebook and Instagram campaign management support, ask to see the proposed review process. The useful deliverable is not a long list of optimizations. It is a clear explanation of what the account is telling us, what remains uncertain, and what we should do next.
Platform guidance checked November 6, 2026. Meta's linked documentation is written for Horizon app advertisers; the general reporting and change-management points cited here are separated from the practitioner workflow above. No app-specific thresholds or performance benchmarks are assumed.