The Coca-Cola example on SaliencyLab is not there to claim a performance uplift. It is there to show how a team should read a decision-ready report.
What this example is, and is not
It is a scored public ad used to demonstrate report structure. It is not a client engagement, not a case study, and not evidence of a business result.
We are deliberate about this because the alternative is common and misleading. A fabricated uplift number attached to a recognisable brand reads as proof while proving nothing. The structure of the report is the thing worth teaching.
What the walkthrough is designed to teach
The example report is meant to show four things in one place:
- the asset
- the KPI pattern
- the benchmark and confidence context
- the next action the team should take
That structure matters more than any invented case-study number ever could.
What to look at first
Read the KPI pattern, not just the headline score
The most useful signal is usually the spread between the strongest and weakest KPI. That spread tells you whether the ad is consistently strong or whether one issue is dragging the rest of the performance down.
This is also what the verdict rules encode. Scale requires a composite of 70 or above and no KPI below 55, so a wide spread can hold a creative in Sharpen even when the average looks healthy.
Look for the decision cue
A report should help a team scale, adjust, pause, or replace. If it cannot do that, it is still reporting rather than decision support.
Read the benchmark label with the report, not after it
Benchmark context becomes useful when it changes how urgent the next action feels. Check the sample size alongside it, since a percentile from a thin category slice is orientation rather than a verdict.
What makes the example valuable
- It shows how evidence connects to the score
- It shows how a report can be read in a live stakeholder conversation
- It shows how a diagnostic becomes a concrete next action
How to use this example internally
Use the example report as a review aid when onboarding new teammates or clients. It helps people understand the reporting language before they upload their own work.
Then use the case studies hub for editorial walkthroughs and supporting articles as more examples are published.
The right expectation
This example is a teaching asset. It helps teams understand the workflow, the report structure, and the quality of the diagnostic conversation. It should not be used as a stand-in for a live client result, and the scores in it are model predictions of engagement and click intent rather than measured market outcomes.