Campaign goal

    Run a Limited-Time Sale With Video

    A discount is not a reason. It is the mechanism.

    The goal, stated plainly

    Concentrate demand into a defined window without repositioning the product's price permanently.

    Sales are the most over-used and least examined promotion on this list, largely because they always appear to work. Revenue goes up during the window, which is treated as proof. The uncomfortable version of the question is whether that revenue was created or merely moved, and answering it is the difference between a mechanism you can use repeatedly and one that slowly erodes what people think your product is worth.

    Everything below is built around making that answerable. One code so redemptions are unambiguous. A split by customer status so pulled-forward demand is visible. A stated reason so the price cut is understood as temporary. And an ending that is honoured, because the credibility of every future window depends on this one.

    Definition of done

    The one number that moves

    Redemptions of a single campaign code, split by new and existing buyers

    What counts

    One code for the whole campaign, so every redemption is unambiguous. The split matters more than the total: existing buyers redeeming mostly means demand was pulled forward, while new buyers redeeming means the window actually created something.

    Set it up before you start

    Issue exactly one code and refuse to make a second for anyone who asks. Tag it against customer status at redemption so the split is available without reconstruction.

    The decoy — looks like success, is not

    Revenue during the sale window. It is almost always higher and says nothing about whether the same money would have arrived anyway a fortnight later at full price.

    The viewer

    Where their head is already

    Already considering, waiting for a nudge

    What they already know
    The product and roughly what it costs. Sales almost never convert people encountering you for the first time; they convert the ones who had already decided and had not acted.
    What actually stops them
    The absence of a deadline. Without one, buying today and buying next month are identical choices, and the one that requires no action wins.

    The mechanic

    A stated reason plus a real end

    The reason is what stops the sale reading as a price correction — an anniversary, a season, clearing a line, a milestone. Any true reason works; the absence of one signals that the usual price was never serious.

    The constraint that turns intention into action

    An end that is actually enforced. Extending a sale once is the single most expensive thing you can do to future campaigns, because it converts every later deadline into a suggestion.

    The campaign

    Four assets, four jobs

    Each asset is responsible for something none of the others cover. The order is the order the viewer needs them in, not a schedule — run them at whatever pace your calendar allows.

    1. 1

      The reason this is happening

      The job

      Frame the discount as an event rather than a correction. Without this asset the campaign quietly redefines your price.

      Hook shape

      Open with the reason, not the number. 'Here is why this is happening' resists the scroll far better than a percentage, and it also survives being seen by someone who paid full price last week.

      What has to be on screen

      Whatever makes the reason real — the anniversary, the season, the line being cleared. A reason nobody can see is a claim.

      The ask

      The window is open now and closes on a stated date. Name the date.

    2. 2

      The single item, in detail

      The job

      Give the campaign something specific to be about. A sale across a whole catalogue gives the viewer a browsing task rather than a decision.

      Hook shape

      Lead with the problem the item solves, and let the sale be the second thing mentioned. The discount is the reason to act now, not the reason to want it.

      What has to be on screen

      The item working. This asset is doing normal product persuasion; the window is only the deadline attached to it.

      The ask

      Buy this one, with the code, before the stated date.

    3. 3

      How to claim it

      The job

      Remove the mechanical friction. A meaningful share of abandoned sale purchases are people who could not work out where the code goes.

      Hook shape

      Straight into the steps, in order, with no persuasion at all. Persuasion here delays the only thing the viewer wanted.

      What has to be on screen

      The actual screens, in sequence, including where the code is entered.

      The ask

      Follow the three steps shown. Nothing else.

    4. 4

      The closing statement

      The job

      Convert the deferrers, once, without begging. It runs near the end of the window and does not repeat.

      Hook shape

      State the ending as a fact and move on. Escalating urgency reads as anxiety and undermines the reason you established in the first asset.

      What has to be on screen

      The date, plainly. Nothing else needs to be on screen.

      The ask

      Last chance at the stated price, ending on the stated date.

    Distribution

    Where each asset runs

    Existing customers and list, first

    They convert at the highest rate and cost nothing to reach. Reaching them first also means the window's early performance tells you whether the offer works before you spend on it.

    Warm paid audiences next

    People who have engaged but not bought are the group a deadline is actually designed for. This is where sale spend earns its keep.

    Cold, only with the single-item asset

    A stranger cannot act on a catalogue-wide discount. If cold traffic is worth running at all, run the asset that is about one specific thing.

    The claim asset on demand

    Send it to anyone who asks how the code works, and place it wherever the code is displayed. It is a support document that happens to be a video.

    Resistance

    What they are thinking, and what answers it

    Will this be cheaper again soon?

    The stated reason is the answer. A window tied to something real implies it recurs only when that thing does, whereas an unexplained discount invites exactly this question and deserves it.

    I bought it last week at full price.

    Anticipate this before the campaign runs and decide the policy in advance. Whatever you choose, having an answer ready is what stops a good campaign generating its own complaints queue.

    The code did not work.

    The claim asset exists for this, and one code rather than several removes most of the causes. Multiple codes multiply both the failure modes and the support load.

    I need to think about it.

    That is what the stated end date is for, and it only functions if it is honoured. Nothing else in the campaign answers this objection.

    Measurement

    How to know whether it worked

    1. 1

      Issue exactly one code

      Every additional code creates an attribution gap and a support burden. Say no to requests for a second one.

    2. 2

      Split redemptions by customer status

      New versus existing is the split that reveals whether demand was created or moved. Without it, the campaign cannot be evaluated at all.

    3. 3

      Compare the window against the fortnight after it

      A sharp drop immediately afterwards is the signature of pulled-forward demand rather than new demand.

    4. 4

      Record whether the end date was honoured

      Write it down. This is the variable that determines how well the next window performs, and it is the one nobody records.

    The usual failure

    How this campaign goes wrong

    Extending the window. It rescues a disappointing campaign once and permanently converts every future deadline into a suggestion — the audience learns faster than the marketing team does, and the next sale is structurally weaker for it.

    Frequently asked questions

    Does a sale need a stated reason?+

    Yes, or it reads as a price correction rather than an event. Any true reason works — a season, an anniversary, clearing a line — and its function is to signal that the usual price is the real one.

    Why insist on a single code?+

    Because attribution has to be unambiguous for the result to be interpretable, and because every extra code multiplies the ways redemption can fail. One code, no exceptions, is easier to hold than a policy of a few exceptions.

    How do I know whether the sale created demand or moved it?+

    Split redemptions between new and existing buyers, then compare the window against the period immediately after it. Existing buyers plus a sharp subsequent drop is the signature of demand that was going to arrive anyway.

    Can I extend a sale that is underperforming?+

    You can, once, and every future deadline you set will be weaker for it. It is usually better to end on time and treat the result as information about the offer rather than about the window.

    Should the discount be in the hook?+

    Lead the first asset with the reason and the single-item asset with the problem it solves. The discount is the reason to act now — it is rarely the reason to want the thing, and hooks built on the number alone attract people who only ever buy on discount.

    Other goals

    Build it with

    Footnote — what the recipes cost

    Figures are each recipe’s own published cost and move when the catalogue does. How credit costs are calculated.

    Build the four assets in one sitting

    The all-in-one AI studio for creators. 60+ models for video, image, voice, music and lipsync in a single app.