How to Run a Marketing Campaign Post-Mortem: Meeting Guide

Short answer
How do you run a marketing campaign post-mortem?
A campaign post-mortem is a structured meeting where you compare a finished campaign's goal with its actual results. You discuss what worked, what did not, and why. Then you carry the lessons into the next campaign. You do not hunt for someone to blame. Instead, you examine the process, the decisions, and the assumptions behind them.
In this guide, we share the meeting format we use in the field, step by step. You will see what data to gather before the meeting, which questions to ask during it, and what record to keep afterward. You also get a learning log template you can copy and use right away.
The term comes from software and operations teams, where a post-mortem reviews an incident after it ends. However, the same logic works well in marketing. The goal is not to judge the past. The goal is to make better decisions next time.
Why does a campaign post-mortem matter so much?
As soon as a campaign ends, the team moves on to the next task. That is natural, but it means lessons get lost. Three months later, you repeat the same mistake because nobody wrote down the cause last time.
A campaign post-mortem breaks that loop for good. In one short session, you capture the campaign's memory in writing. As a result, the next plan rests on experience rather than guesswork.
The meeting also builds a shared language. The ad manager, designer, sales team, and business owner each see the campaign from a different angle. For example, the ad side may report cheap clicks, while sales noticed that the leads were poor quality. You only see the real picture when both facts sit on the same table.
In addition, regular reviews make budget decisions stronger. If you can prove which channel, message, and offer worked, defending the next budget gets easier. In short, the review is not a cost. It is insurance for the next campaign.
Think about team morale, too. Teams that run regular, blame-free reviews raise problems earlier. They know that flagging an issue brings help, not punishment. That trust pays off mid-campaign as well. When something goes wrong, people speak up right away, so you can correct course in time.
When should you hold the meeting?
The best window is one to two weeks after the campaign ends. If you meet too early, you miss late conversions and sales feedback. If you wait too long, the team forgets the details.
For businesses with long sales cycles, we suggest a two-step approach. First, run a short review right after the campaign ends. In that session, you cover setup, delivery, and early results. Then, once leads turn into deals, hold a second session to complete the revenue side.
Also, book the meeting before the campaign even starts. That way, the review becomes a natural part of the campaign. We explain how to place these dates on the yearly calendar in our guide on how to build an annual digital marketing plan.
Finally, not every campaign needs the same depth. For small, routine campaigns, a short written note is enough. However, for big-budget campaigns, new channels, or campaigns that fell far short, run the full meeting.
Who should attend the meeting?
Everyone who truly touched the campaign should be there. Still, a crowded room keeps the talk on the surface. We usually recommend a group of four to six people.
- The campaign owner: the person who set the goal and made the final calls.
- The operators: the people who ran ads, content, email, or social.
- A sales or support rep: someone who knows the quality of incoming demand.
- The measurement owner: the person who can confirm the data is accurate.
- The facilitator: a neutral person who runs the meeting and guards the clock.
Above all, the facilitator role matters. This person does not take sides. Instead, they ask questions, steer the talk from people to process, and take notes. If nobody on the team can stay neutral, an outside expert often does this better, because they have no emotional stake in the decisions.
On the other hand, if a senior manager attends, set their role up front. They join as a listener and speak last. Otherwise, the team tends to talk to the manager's reactions rather than to the facts.
What data should you prepare before the meeting?
Searching for data during the meeting is the fastest way to waste it. So ask the measurement owner for a one-page summary a few days ahead. That summary keeps everyone looking at the same numbers.
- The original goal and how you planned to measure it.
- Actual results: spend, impressions, clicks, conversions, and revenue.
- A breakdown by channel and by creative.
- A timeline of what changed and when.
- Qualitative feedback from sales or support.
- Key decisions made during the campaign, with the reason for each.
When you read the numbers, prepare the context too. For example, if a price change, stock issue, or site outage happened during the campaign, add it to the timeline. To read the figures correctly, see our guide on how to read a digital marketing report.
Also, if your campaign links carried UTM tags, the channel breakdown will be much cleaner. We explain how they work in our post on UTM parameters.
How do you compare the goal with the results?
The first rule is simple: never change the goal after launch. In the campaign post-mortem, you put the original goal on the table exactly as written. Then you write the actual result next to it.
Next, sort the gap into one of three buckets: we beat the goal, we hit it, or we fell short. However, that is only the start. The real question is why. Even beating the goal deserves questions. Maybe the target was set too low. Maybe an outside factor helped.
Also look at the metrics beneath the main goal. For instance, if you missed the sales target, where in the funnel did things break? Were impressions low, were clicks low, was site conversion weak, or did sales fail to close the leads? This split speeds up the search for the cause.
To pick the right metrics from the start, our guide to digital marketing KPIs helps. If you want a quick return on ad spend check, use our ROAS calculator.
What should a campaign post-mortem agenda look like?
A good agenda keeps the meeting from drifting. We usually suggest a session of sixty to ninety minutes and split the time like this.
- Opening and ground rules: the facilitator restates the purpose and the no-blame principle.
- Goal and results: the measurement owner presents the one-page summary.
- Timeline: the team walks through what changed and when.
- What worked: the team lists practices worth keeping.
- What did not work: the team lists problems and likely causes.
- Root causes: you dig into the two or three biggest issues.
- Actions: you assign an owner and a date to every lesson.
Send the agenda to attendees ahead of time. That way, everyone gathers their thoughts in advance. Also ask each person to write two or three observations before the meeting. This small step stops the loudest voice from taking over.
Sticking to the time limit matters as well. When time runs out, stop the debate and log the open topics for a follow-up.
What does a blameless review actually mean?
A blameless review looks for the cause of a problem in the process, the information, and the system, not in a person. When something goes wrong, you ask "why did that decision make sense at the time" instead of "who did this."
This idea comes from engineering teams. The postmortem culture chapter in Google's SRE book recommends focusing on contributing causes. It also says to assume everyone acted with good intentions based on the information they had. The chapter stresses that writing a postmortem is a learning opportunity, not a punishment.
The same logic holds in marketing. Picture an ad set that went live with the wrong audience. If you blame the person, the team hides mistakes next time. If you ask why, you may find that the setup checklist had no audience step. Then you fix the problem by adding that step.
In short, blame makes people hide information, while curiosity brings it out. That is why the facilitator's first job is to pull the talk back from people to process every single time.
How do you tell what really worked?
Discussing what worked is just as valuable as discussing what failed. If you do not protect good practices, they fade over time. Then the team tries new things next campaign without knowing why the last one succeeded.
To isolate what worked, ask one question: did this result come from our decision or from outside conditions? For example, if sales rose, was it the new ad copy or the season's natural demand? Do not tag a practice as "worked" until you have made that call.
Sometimes you need more data to answer. We explain ways to check whether ads truly drove extra sales in our guide to incrementality testing. These tests help you get closer to the question "what would have happened without the ads?"
Finally, write each winning element in one sentence and attach its evidence. For instance: "Short video creatives brought a lower cost per acquisition than static images; evidence: creative breakdown table." This format ties every claim to proof.
How do you find the cause of what failed?
Spotting what failed is easy, however. Finding the cause takes effort. For that, we use a simple chain of whys. You write the problem down, then ask "why" several times in a row.
Here is an example scenario. The landing page converted poorly. Why? Visitors abandoned the form. Why? The form was long and confusing on mobile. Why? We tested it on desktop only. Why? Our pre-launch checklist had no mobile test step. Now you have reached the root cause: a missing check.
At the end of this chain, you almost always find a process, information, or tool problem. If you land on a person, step back once. Then ask why that person lacked the right information.
We also collected the most common reasons behind falling returns in our post on ROAS drop causes. Skimming that list before the meeting helps the team scan likely causes quickly. Still, never act on a generic list without checking it against your own data.
How do you review each channel separately?
In a multichannel campaign, the total result hides each channel's real contribution. For example, total sales may hit the target, yet one channel carried most of it while others burned budget. That is why part of the review goes channel by channel.
Ask the same four questions for each channel. How much did we spend here? What role did this channel play: reaching new people, bringing interested people back, or closing the sale? Did it deliver what we expected for that role? Next time, do we raise or lower its share?
The role question is key. If you judge an awareness channel on direct sales alone, you reach an unfair verdict. On the other hand, judging every channel only by its own role can become an easy excuse. So write each channel's role before launch, and return to that note in the review.
Finally, log the channel breakdown in its own row of the learning log. Over time, you see which channel is strong for which campaign type. That insight becomes your best basis for the yearly budget split.
How do you account for outside factors?
No campaign lives in a vacuum. Season, competitor moves, price changes, inventory, and even the weather can shift results. If you ignore them, you may credit or blame yourself for an outcome you did not cause.
To handle this, add an "outside events" row to the timeline. During the campaign, log every external development you notice, with its date. For instance, if a competitor launched a big sale on the same day your click costs jumped, you see the link right away.
Above all, be careful with seasonal campaigns. Conversion rates shift naturally during peak periods. The Google Ads Help page on seasonality adjustments notes that this setting is meant for short events where you expect a major change in conversion rates. If you used one, note it on the timeline before the review.
In short, logging outside factors helps you tie each result to its true source. Then, next time, you change only the things you can actually control.
What do you gain by running this with an expert?
Judging your own campaign fairly is hard because you are too close to it. You made the calls and put in the work. So the meeting can slide into defense or into harsh self-criticism. An outsider, on the other hand, asks the questions without falling to either side.
That is a good moment to hire a digital marketing expert to shape the review with you. As Talha Aslan and team, we prepare the data summary, run the agenda, trace the chain of whys with you, and keep the learning log. Meanwhile, you bring the knowledge of your business and your customers.
The value does not stop at the meeting. The real difference is that the lessons actually reach the next campaign. When the next setup starts, the expert opens the learning log and checks whether last time's actions happened.
We describe how that check fits into weekly work in our post on the weekly workflow with a digital marketing expert. A review works best when it is a normal part of that rhythm.
How do you keep a learning log?
A learning log is a short, standard record you fill in at the end of every review. Its purpose is to make lessons searchable and reusable. Rather than opening a new file per campaign, we suggest adding rows to one shared table.
| Field | What you write | Example |
|---|---|---|
| Campaign | Name, date range, channels | Spring sale, search and social |
| Goal and result | Original goal and actual value | Lead goal; result below target |
| What worked | Practice to keep and its evidence | Short video creatives; creative breakdown |
| What did not | Problem and root cause | Long mobile form; no mobile test on checklist |
| Lesson | One-sentence general rule | Test every form on mobile |
| Action | Task, owner, due date | Add mobile step to checklist; operator; next week |
| Status | Open, done, or dropped | Open |
Specifically, this table is only a sample structure. You can change the fields to suit your business. What matters is filling the same fields for every campaign. The values above come from an example scenario, not a real campaign.
Which questions should you ask in the review?
The right questions set the quality of the meeting. We suggest the facilitator keeps the list below at hand. You do not need to ask every question. Instead, pick the ones that fit the campaign.
- What was our goal, and how did we plan to measure it?
- What actually happened, and where did the gap come from?
- Which assumptions held, and which ones missed?
- What decisions did we make mid-campaign, and why did they make sense then?
- What information, had we known it sooner, would have changed a decision?
- Which signal from customers or sales did we miss?
- Was our tracking reliable, or did we see gaps or double counting?
- What do we keep as is next time, and what do we change?
What these questions share is that they point at decisions and information, not at people. For example, you ask "what did we know at that moment" instead of "why did you make this mistake." So the talk turns to discovery rather than defense.
Also, end the meeting with one question for everyone: "What is the most important thing you learned today?" The answers give you a quick summary of the lessons in each person's own words.
How do you carry lessons into the next campaign?
A campaign post-mortem only pays off when its lessons enter the next campaign. If a lesson stays in the log, the meeting was just a chat. That is why you need to turn the handoff into a process.
We suggest three simple rules. First, every new campaign's planning meeting starts by opening the learning log. Second, the owner of each open action gives a status update in that meeting. Third, you build recurring lessons into checklists and templates. As a result, a lesson no longer depends on someone's memory.
For example, "test every form on mobile" becomes a permanent step in the pre-launch checklist. Meanwhile, "short video creatives worked well" becomes a test in the next campaign's creative plan.
Some lessons are not firm rules but ideas worth testing. Add those directly to your test list. We explain how to build and rank that list in our guide on how to build a marketing experiment backlog. That way, one campaign's question becomes the next campaign's experiment.
What are the most common campaign post-mortem mistakes?
Review meetings tend to fall into the same traps. Knowing them is the first step to avoiding them.
- Hunting for data during the meeting and spending half the time arguing over numbers.
- Changing the goal after the fact to make the result look better.
- Focusing only on failures and never logging what worked.
- Pointing the talk at people and pushing the team into defense.
- Leaving actions without an owner or a date.
- Keeping the log but never opening it for the next campaign.
Most of these mistakes come from having no fixed format. The agenda, the data summary, and the learning log template fill that gap.
Another frequent mistake is saving the campaign post-mortem only for campaigns that went badly. Successful campaigns deserve a review too. In fact, understanding why something worked can be harder than understanding why it failed, because teams rarely question success. So review every major campaign in the same format, no matter the outcome.
How do you write the report after the meeting?
When the meeting ends, the facilitator writes a short report. This report lets people who missed the meeting learn the lessons too. We suggest keeping it to one page.
- Summary: the goal, the result, and a one-line overall verdict.
- What worked: two or three practices to keep, with evidence.
- What did not work: two or three problems and their root causes.
- Lessons: short sentences framed as general rules.
- Actions: an owner and a date for each one.
Also, write the report in blameless language. Use roles instead of names, such as "ad setup" or "content team." That way, the report reads as a learning document, not a verdict.
Then share it with everyone involved and link it from the learning log. Also leave space for questions. People who missed the meeting can add observations there. Sometimes the most valuable insight comes from a support rep who was not in the room.
How can small teams keep the process simple?
Not every business has a team of six. Still, a two-person team, or an owner who runs marketing alone, can run a campaign post-mortem. You simply shrink the format.
For small teams, a thirty-minute session is enough. You write the goal and result side by side, list three things that worked and three that did not, then pick one lesson and one action. Even filling in just the "lesson" and "action" fields of the log makes a big difference.
Still, when you review alone, watch for blind spots. Questioning your own decisions is hard. In that case, showing the campaign summary to an outside pair of eyes can surface a cause you missed.
Also, small teams skip reviews easily, because everyone feels they already know everything. Yet knowledge that stays in someone's head fades. A short written note will save you time six months later when you plan a similar campaign.
Do long campaigns need a mid-point review?
Yes. For campaigns that run several months, reviewing only at the end is risky. If you spot a problem only when the campaign is over, you lose the chance to fix it. So we suggest adding checkpoints to long campaigns.
A mid-point review is a smaller version of the full campaign post-mortem. Where are you against the goal? Which assumption is not holding? What can you change now? You answer these three questions in a short session. Then you log the decisions, so the final review shows how the campaign evolved.
However, do not rush at the mid-point. Some channels and bid strategies need time to deliver. For example, if you change everything based on the swings of a new campaign's first days, you never give the system room to learn. So discuss the timing of such changes in the mid-point review as well.
In short, a mid-point review lets you correct course early. The final review then helps you learn from the whole journey.
How do you share lessons beyond the marketing team?
A lesson from a campaign often matters to more than the marketing team. For example, a question customers kept asking may reveal missing information on a product page. Likewise, a struggle the sales team faced may point to a flaw in the offer itself.
So at the end of every review, ask: who outside marketing benefits from this lesson? Based on the answer, send a short note to the relevant teams. In the note, include only the lesson, the evidence, and the suggested action. Then attach the full report for anyone who wants detail.
Also, review the learning log as a whole every few months. Repeating lessons point to a company-wide issue, not a one-off campaign problem. For instance, if every campaign surfaces a mobile experience issue, that is no longer a campaign lesson. It is a website priority.
As a result, the review stops being a ritual inside marketing. It becomes a habit the whole company learns from, and teams stop repeating the same mistakes in different departments.
Where should you start your first campaign post-mortem this week?
Pick your most recently finished campaign and book a thirty-minute campaign post-mortem this week. First, write the goal and the result on one page. Then list three things that worked and three that did not. Finally, choose one lesson and one action.
Next, create the learning log table and add this first entry. Open the next campaign's planning meeting with that table. After the second and third entries, you will see how valuable this shared memory becomes.
If you would rather run this process with an experienced team than build it alone, working with a digital marketing expert saves you time. As Talha Aslan and team, we set up the data summary, the meeting format, and the learning log with you. Then we carry the lessons into your next campaign plan.
Core guide: What Is Digital Marketing? Its types, examples and how it is done, on one page with an interactive film that travels through the brain.



