Choose the decision the meeting must produce
A retrospective is useful after a bounded campaign or a significant incident. State whether the team must change the approval route, creator mix, destination or measurement setup. A meeting with no decision can become a replay of the reporting deck.
Invite the owners of the affected work and send the evidence beforehand. The creative team, publisher and analyst may hold different parts of the timeline. Do not ask everyone to remember a disputed event from memory during the meeting.
Prepare a one-page retrospective record
This template is an original meeting structure. It does not imply a retrospective can establish causal impact from observational data. Keep unverifiable recollections labelled as recollections until another source confirms them.
Preserve the campaign’s original question. Replacing it with whichever metric later looks strong makes the discussion less useful.
| Block | Write |
|---|---|
| Intended result | Campaign question and original assumptions |
| Timeline | Dated events with source references |
| Accepted delivery | Work that met the scope |
| Exceptions | Missing or changed work and affected period |
| Interpretation | Possible mechanisms and confidence |
| Next action | One change, owner and review date |
| Evidence needed | Observation that would support or reject it |
Reconstruct the timeline before judging the result
Put briefing, approval, upload, link changes, product changes and capture times in order. Identify the window each event affected. A broken destination for part of a launch can alter outcomes even when the creative and audience are unchanged.
Keep counter sources distinct. Google Analytics campaign fields can describe tagged acquisition paths, while platform counters describe their own viewing or engagement scope. One source should not silently replace the other.
Use the campaign reporting framework for the source evidence, then apply the attribution plan when the discussion concerns credit for a recorded outcome.
Talk to us
Pick a 30-minute slot, or DM us on Telegram.
Bring an anonymised delivery timeline and measurement notes. We can discuss the next experiment.
Campaigns from $2,000, with 10% off your first. We reply within one working day.
Work through a destination-failure example
The example is hypothetical. It demonstrates a proportionate conclusion: repair the journey and retest, rather than blaming a creator for every missing conversion or inventing the revenue the fault supposedly lost.
If the exact affected window is unknown, record that limitation and investigate it. Do not choose a convenient start time merely to make the report cleaner.
| Layer | Example |
|---|---|
| Fact | Approved link redirected to an unavailable page during a known window |
| Evidence | Dated checks and destination log |
| Interpretation | Some recorded attention may not have had a usable next step |
| Limit | The lost conversions cannot be measured from views alone |
| Action | Add final redirect QA before the next slot |
| Test | Verify a permitted test journey and first live placement |
Keep the action list short enough to finish
Select the changes most likely to resolve the observed problem. “Improve communication” is too broad. “Put one accepted caption and destination beside each final file” gives an owner something concrete to implement.
Avoid changing the creator, offer, format and destination simultaneously when the next exercise is intended to test one cause. If several repairs are necessary for eligibility or usability, describe the next campaign as a new configuration rather than a clean comparison.
Check that the next team inherited the change
Before the next launch, inspect the revised brief, register or test route. A completed meeting does not prove the action exists in the workflow. Keep the owner and review date visible until the change is verified.
Archive the final record with the campaign sources. The best retrospective makes the next decision easier to explain and prevents the same exception from becoming another surprise.
Frequently asked questions
What is a campaign post-mortem in influencer marketing?
A campaign post-mortem is a structured review after a bounded campaign or significant incident that explains what happened and changes the next operation. It keeps three things separate: the factual timeline, the team's interpretation and the proposed next experiment. It should end in a decision, such as changing the approval route, creator mix, destination or measurement setup, rather than replaying the reporting deck.
Which sections belong in a one-page retrospective record?
Use seven blocks: intended result, a dated timeline with source references, accepted delivery, exceptions, interpretation with confidence, one next action with an owner and review date, and the evidence that would support or reject it. Preserve the original campaign question instead of swapping in whichever metric later looks strong. Label unverifiable recollections as recollections until another source confirms them.
Who should attend an influencer campaign retrospective?
Invite the owners of the affected work, typically the creative team, the publisher and the analyst, because each may hold a different part of the timeline. Send the evidence beforehand so nobody has to reconstruct a disputed event from memory during the meeting. Pull source evidence from your iGaming influencer campaign reporting, and bring in the attribution plan only when the question is about credit for a recorded outcome.
How do you analyse a broken link during a creator launch?
Separate the fact, evidence, interpretation, limit, action and test into distinct layers. In a hypothetical case, an approved link redirected to an unavailable page during a known window, so the proportionate conclusion is to add final redirect QA and retest, not to blame the creator or invent the revenue the fault supposedly lost. If the affected window is unknown, record that limitation instead of picking a convenient start time.
How do you make retrospective actions actually stick?
Keep the list short and concrete: 'improve communication' is too broad, while 'put one accepted caption and destination beside each final file' gives an owner something to implement. Before the next launch, inspect the revised brief, register or test route, because a completed meeting does not prove the change exists. If an iGaming influencer marketing agency runs your campaigns, ask it to keep each owner and review date visible until the change is verified.
Results from campaigns our team has run
Web3 game · gaming creators, streams and events
Illuvium
6,550 new players and 24,000+ followers
Read the Illuvium caseCrypto exchange · KOLs on X, YouTube and TikTok
Binance
4,245 new users and more than $510M in trading volume, double the target
Read the Binance caseCrypto banking · influencers and growth
Swissmoney
32,000+ users onboarded and CPA cut 4x
Read the Swissmoney case
3betmedia launched in 2026; most of these campaigns ran before the name existed. See all 19 cases.
Sources and further reading
Prepared with AI assistance using the linked references. Planning tables and worked scenarios are illustrative, not client results. Check current product, platform and market requirements before using them.