Run an influencer campaign postmortem by rebuilding what happened, what each person knew, and which conditions limited the result. Separate questions about audience fit, the offer, execution and measurement. Then assign changes to people who can make them. A missed sales goal alone cannot tell you which creator made a poor decision.
Google's postmortem guidance focuses on contributing causes and preventive actions while avoiding accusations against individuals. The method below adapts that engineering practice to a campaign review. Its four categories and meeting timings are editorial recommendations, not platform rules.
Prepare a record people can correct
Send a short evidence packet before the meeting. Include:
- The original goal, reporting period and counting rule.
- The approved brief, subsequent changes and approval timestamps.
- Product delivery dates, publication timestamps and live content links.
- Offer terms, stock availability and relevant checkout issues.
- The report export, its settings and any missing records.
- Questions that remain unresolved, with the person best placed to answer each.
Keep the original target visible. If sales were the goal, content delivery can explain progress or constraints, but it does not replace the sales result after the fact. If the reporting period was never agreed, record that gap. Use a consistent cutoff for this review and flag its retrospective selection. For the next launch, choose the reporting window before looking at results.
Ask creators to correct the timeline and explain constraints before discussing renewal decisions. Offer a written response route if they cannot attend. Include the people responsible for commerce, reporting and approvals, rather than asking the creator manager to speak for every function.
Choose a facilitator who can interrupt unsupported accusations, including those from a senior stakeholder. Explain how the review will be used. Do not promise that no commercial decision will follow if the team cannot keep that promise.
Rebuild decisions before judging them
For each material event, record the time, available information, decision, constraint and evidence link. Distinguish contemporary records from later recollections.
Etsy's account of blameless postmortems asks participants to describe actions, observations, expectations and assumptions. Adapt those prompts to a creator campaign:
- Which brief version did you have when you filmed?
- What told you the product or offer would be ready?
- Who could approve a date change?
- When did you learn the link or code had changed?
- What could you change yourself, and what required another team's response?
Record disagreement rather than forcing consensus. A message timestamp may establish when someone sent an update. It does not establish when the recipient read or understood it.
Modash's practitioner article on campaign failures describes unclear expectations, rushed schedules and coordination problems. Treat those as prompts for investigation. They do not establish why your campaign missed its goal.
Sort evidence into four questions
Allow an event to appear in more than one category. A late product delivery can affect both execution and the creator's ability to assess product fit.
| Category | Question to answer | Evidence to seek | Avoid concluding |
|---|---|---|---|
| Fit | Was the selected audience suitable for this product and market? | Selection rationale, audience information available then, content context | Low sales prove the creator has a poor audience |
| Offer | Could an interested buyer act on the promise? | Price and shipping terms, stock records, code validity, checkout checks | Every lost order reflects weak persuasion |
| Execution | Did the agreed work happen under the agreed conditions? | Brief versions, delivery dates, approvals, publication records | A late post proves the creator caused the delay |
| Measurement | Can the report answer the original question? | Counting rules, exports, missing records, attribution settings | An unrecorded result equals zero |
Give each finding a status: observed fact, plausible explanation or unresolved question. Reserve observed fact for something the packet supports. A plausible explanation should name what evidence would strengthen or weaken it.
Where Google Analytics supplies the report, preserve its attribution settings. Google defines attribution as assigning credit along the path to an important action. Its settings include the reporting model, eligible channels and key-event lookback window. A credit allocation needs that context before it enters a creator assessment.
If the record is incomplete, report the missing campaign data explicitly. Keep uncertainty attached to the finding through the final decision.
Work through a hypothetical missed launch
The following launch, records and numbers are hypothetical. They illustrate the review method and describe no real brand or creator.
A team planned eight creator publications. Its agreed goal was 100 paid orders using campaign codes during a seven-day launch. The team counted distinct order IDs and excluded cancelled or refunded orders as of the review cutoff. This is the example's counting rule, not a universal commerce metric.
| Hypothetical record | Value or event |
|---|---|
| Goal | 100 eligible orders |
| Recorded result | 62 eligible orders |
| Difference from goal | 100 minus 62 = 38 orders |
| Goal attainment | 62 divided by 100 = 62% |
| Publication record | Six posts within the planned window; two after it |
| Delivery record | Two creators received samples after their filming deadline |
| Offer record | One campaign code failed a launch-day checkout check |
| Measurement gap | No reliable record of how long that code failed |
The result missed the agreed goal by 38 orders. The review cannot assign those 38 orders to the late posts or failed code. It has no evidence of what buyers would have done under different conditions.
The late delivery is an observed constraint. Its contribution to the sales shortfall remains unknown. The failed checkout check supports fixing code readiness. It does not support inventing lost sales. Audience fit remains unresolved unless the team has evidence beyond the total order count.
Likewise, the team cannot rank the two late creators fairly against the other six without examining the conditions each received. It can still document whether each person followed the approved plan and communicated changes.
Facilitate a 60-minute review
Use the packet to keep the meeting focused. Move disputes needing new evidence into an investigation list.
| Minutes | Discussion | Required output |
|---|---|---|
| 0 to 5 | Restate the goal and counting rule | One agreed description of the miss |
| 5 to 20 | Reconstruct the timeline | Corrections and unresolved dates |
| 20 to 35 | Examine the four categories | Facts separated from explanations |
| 35 to 45 | Hear constraints and alternative accounts | Evidence gaps and investigation owners |
| 45 to 55 | Select corrective actions | Owners, deadlines and closure evidence |
| 55 to 60 | Read back decisions | Follow-up date and remaining disagreements |
When someone says a creator failed, ask for the agreed requirement, the observed deviation and the evidence. Then ask what information and control that creator had. Apply the same questions to the brand team.
Handle suspected misconduct or a payment dispute through the appropriate separate process. The learning meeting should preserve relevant facts without improvising legal or disciplinary judgments.
Close with an action log
For the hypothetical launch, an action log might look like this. Deadlines run from the review date.
| Finding | Action and owner | Due | Evidence needed to close |
|---|---|---|---|
| Samples arrived after filming deadlines | Campaign lead makes confirmed delivery part of date approval | Within five working days | Next schedule records receipt before filming |
| A code failed checkout | Commerce lead adds a prepublication checkout check | Before the next post | Dated successful check for every planned code |
| Code failure duration is unknown | Analyst investigates available records | Within three working days | Supported time range, or a documented unresolved gap |
| Fit remains unresolved | Creator manager revisits selection evidence | Before renewal decisions | Written rationale and limits for each proposed renewal |
Avoid actions such as communicate better or choose better creators. Each action needs an owner with authority, a deadline and visible proof of completion. Limit the initial list to work the team has agreed to resource.
Turn the findings into a decision report, keeping the missed target and unresolved causes visible. Before ending the meeting, schedule the action review and name who will check the evidence for each closed item.
