AInora
Webinar ReplayShow Up RateWebinar AttendanceOn-DemandWorking Session

Should You Offer the Webinar Replay? Nobody Has Tested It

JB
Justas ButkusFounder, Ainora
··13 min read

The replay is the recording of a live webinar, sent afterwards - usually to everyone who registered, whether they attended or not. The replay question is whether promising that recording is what stops people attending live, and therefore whether you should keep sending it, restrict it, or stop. It is the decision that follows directly from the most-cited reason registrants give for skipping a live session, and it is the decision almost nobody answers.

The short answer, and why it is uncomfortable

Nobody has run a controlled test of this. No study, no disclosed A/B test, no vendor report that isolates a replay policy and measures what happens. The strongest reported cause of webinar no-shows is also the least studied thing in the entire subject. Every confident answer you will read - including "never lead with the replay" - is a preference wearing the clothes of a finding. What follows is the trade-off in both directions, the options in between, and the only honest way to settle it, which is to test it on your own list.

This page is the sequel to a ranking. In why webinar registrants do not show up we put the replay at the top of the causes, because that is where registrants themselves put it. Establishing the cause and then never addressing the policy it implies is the gap this page exists to close. We are not going to restate the ranking; we are going to take the decision seriously.

34%
Registrants who watched live on a syndicated B2B network, 2021 - vendor data, US and global English-language
Source: BrightTALK Benchmarks Report 2021
15%
Registrants in the same dataset who watched on-demand instead - the audience a replay ban removes
Source: BrightTALK Benchmarks Report 2021
46%
Total registration-to-view conversion, live and on-demand combined, same dataset
Source: BrightTALK Benchmarks Report 2021
1 in 3
Roughly the share of all registrant viewing that happened on-demand rather than live: 15 of the 46 printed as the total. Note the chart figures do not sum - 34 plus 15 is 49, not 46 - so treat this as indicative. Our arithmetic on BrightTALK 2021 (2020 data, US/EN vendor source).

Read the source label on every one of those. It is vendor platform data, from 2021, from a US and global English-language syndicated network, and the report itself does not disclose how many webinars are behind it - only "thousands of data points" from its platform and its own user survey. The same report prints three different numbers for the live figure: 36% on its benchmark page, 34% on the audience-conversion chart, and 33% in the prose. We publish the chart figure, disclose the other two, and would rather you knew the benchmark disagrees with itself than pretend it does not.

Replay policy: the vocabulary

Replay policy
The rule your business follows about who receives the recording and for how long. Most operators have never made this an explicit decision - the platform default made it for them.
Expiring replay
The recording is available for a fixed window - commonly 24 to 72 hours - and then withdrawn. The most frequently recommended compromise, and no more tested than the extremes.
Attendee-only replay
The recording goes only to people who joined the live session, sometimes only to those who stayed past a threshold. Rewards showing up rather than registering.
Gated replay
The recording is not sent automatically. The registrant has to ask - a form, a reply, a click. Reintroduces a small cost and tells you who actually wanted it.
On-demand viewing
Watching the recorded session at a time of the viewer choosing. In vendor benchmarks this is counted as a conversion, which is why vendor totals look higher than a live show up rate.
Evergreen webinar
A pre-recorded session presented on a rolling or just-in-time schedule. It is a different product rather than a setting, and the replay question mostly does not apply to it.

Has anyone actually tested whether the replay reduces live attendance?

No. We looked specifically for this and found nothing: no academic study, no vendor report that varies replay policy and measures the result, no operator publishing a split test with a disclosed sample. What exists is a large volume of consistent, unmeasured testimony pointing one way, and a large volume of confident advice built on top of it.

0
Controlled tests of a webinar replay policy found in our research - no study, no disclosed A/B test, nothing
0
Published show up rates segmented by whether a recording was promised at registration
3
Separate operator recommendations we found to restrict or delay the replay - none of them with data attached
1
Reported idea that beat the replay: run the session as a working session. One operator, no measurement.

I don't go to webinars because everyone sends a recording now.

One operator, in a public forum. The most-upvoted explanation for skipping a live webinar that we found anywhere in the research - an individual report, not a measurement.

That sentence is the whole problem in fourteen words, and it is worth being precise about what kind of thing it is. It is one person, saying what they do, in a public discussion, agreed with by many others in the same thread. It is the highest-voted explanation in a corpus that contained a great many explanations. That makes it strong evidence of what people say and no evidence at all of what happens to a show up rate when a business changes its policy.

Why the operator quotes on this page carry no links

The candid discussion of webinar attendance happens in public forums whose platforms now refuse automated access - both the main domain and the old-interface mirror return a refusal to any fetch, so we cannot re-verify a permalink at source. We therefore quote without hyperlinks and never treat a forum post as data. Every quote here is labelled for what it is: one operator, reporting their own experience. Where something came from a study, we link the study.

The asymmetry is the interesting part. The replay is the strongest reported cause of no-shows and the weakest evidenced one, while the cause with the best evidence behind it - reminder timing - is near the bottom of any honest ranking. The subject has its research effort pointed at the wrong end of its own problem, and it has been that way long enough that a category of vendors now sells against the least important cause.

The claimWho makes itWhat kind of evidenceStatus
The replay is why people skip liveOperators, repeatedly, with the highest vote counts we foundIndividual reports in public discussionsConsistently reported, never tested
Killing the replay raises live attendanceConsultants and course-creator coachesAssertion, usually with nothing attachedPlausible mechanism, zero controlled evidence
You should always send the replayWebinar platforms, including ones whose product is on-demand hostingVendor guidance sitting beside vendor platform dataReal data, real commercial interest - read both
On-demand is a large share of your total audienceOne large syndicated-network datasetVendor platform measurement, 2021, US and global English-languageMeasured, on one platform, for one population
A working session beats the replayOne operatorA single report with no measurementThe only replay-beating idea we found; unverified

What do you gain by not sending the replay?

The argument for removing the replay is a scarcity argument, and it is a coherent one. If attending live is the only way to get the material, the choice the registrant faces changes shape: it stops being "now or later at no cost" and becomes "now or not at all". That is a real change in the decision, and it is the reason the recommendation keeps resurfacing.

What is claimed to follow, in the order operators claim it:

  • Live attendance rises, because the alternative has been priced out of existence. This is the headline claim and it is the untested one.
  • The room is warmer. People who chose to be there rather than defaulting into a recording are, on average, more engaged - which matters if you sell from the session.
  • The event becomes an event again. A session that cannot be caught up on has a deadline, and deadlines are the only thing a calendar respects.
  • Your reminders start meaning something. A reminder for something that will be available anyway is a notification. A reminder for something that expires is information.

The cost nobody in this argument counts

The recording is very often advertised on the registration page, as a reason to sign up: can't make it live, register anyway, we'll send the recording. Removing it does not only change what happens after registration - it changes the offer that produced the registration. How many registrations you lose by withdrawing that promise has never been measured either. An operator who kills the replay and watches their live show up rate climb while their registration count falls has improved a ratio and may have shrunk the business. Measure both numbers or you have measured nothing.

What do you lose by not sending the replay?

Here the evidence is better, because at least one large dataset speaks to the size of the on-demand audience. In the BrightTALK Benchmarks Report 2021, registration-to-view conversion was 34% live, 15% on-demand, 46% in total. Roughly one in three of the registrants who watched anything at all watched only the recording. Remove the replay and, in that population, you are removing about a third of your total viewing to try to grow the other two thirds.

Label it properly before you use it: vendor platform data, 2021, US and global English-language, a syndicated content network rather than a house list, no webinar count disclosed, and three internally inconsistent figures for the live number. It is not your business. It is the closest published measurement of the thing you would be giving up.

Always share the content with no-shows by giving them the opportunity to interact at their own speed and on their own schedule.

BrightTALK Benchmarks Report 2021, page 25 - the vendor's own recommendation, printed beside its own on-demand data. BrightTALK sells on-demand hosting; read the advice and the interest together.

And the people behind the percentage are not interchangeable with the people you are trying to convert. Removing the replay costs you, specifically:

  • Everyone who genuinely could not make the time. A client emergency, a school run, a timezone, a shift. These are not people avoiding you, and punishing them is a strange way to build a list.
  • The international part of your audience. One live slot cannot be convenient in three timezones, and no reminder solves a clock.
  • The internal share. B2B recordings get forwarded to a colleague, a manager, a procurement contact. That forward is often where the deal actually starts, and it cannot happen without a link.
  • The searchable asset. A recording keeps earning after the session. Withdrawing it converts a durable asset into a one-day event to buy an unmeasured attendance gain.
  • Goodwill you will spend later. "I registered and got nothing" is a bad first impression, and it is the impression you create for the people your live slot did not fit.

The honest gap in both directions

Nobody has published what a replay viewer is worth relative to a live attendee. Not a conversion rate, not a revenue-per-view, not a comparison of any kind. So the trade-off cannot be resolved with arithmetic: you are weighing an unmeasured attendance gain against an unmeasured audience loss, and anyone who hands you a ratio for that has made it up. What you can do is measure it in your own business, which is the last section of this page.

What sits between "always send it" and "never send it"?

Almost the entire argument is conducted between two extremes that few businesses actually need. The useful moves are in the middle, and they are all cheap to implement. None of them has been tested either - but a policy you chose beats a platform default you never noticed.

Replay policyWhat changes for the registrantWhat it costs youWhat is known about it
Send it to everyone, alwaysAttending live is optional, and they know that before they registerThe live audience, if the operator reports are rightThe unexamined default. No controlled test either way.
Send nothingLive is the only way to get itThe on-demand audience, plus everyone with a genuine conflictNo test. Also untested: what happens to registrations.
Expiring replay, 24 to 72 hoursThe recording exists but it is not a substitute for the calendarLittle in principle - but the deadline must be real or it teaches the opposite lessonThe most commonly recommended compromise. No published test.
Replay only for people who attended part of itTurning up briefly is rewarded; registering alone is notThe genuine conflicts, unless you handle exceptions by handNo published test. Operationally the fiddliest option.
Replay behind a form or a replyA small cost returns, and asking becomes a signalSome passive replay views, in exchange for a list of who wanted itNo published test. Turns a broadcast into a stated intent.
Replay with the offer or the Q&A removedThe teaching survives; the part that sells does notLittle, if you say plainly what was cutNo published test. Keeps the goodwill, removes the substitute.
A shorter cut instead of the full sessionThe recording is a summary, not a replacementEditing timeNo published test. The mildest version of scarcity.

Three implementation notes that decide whether any of these work:

  • Say the policy on the registration page. Whatever you choose, the registrant should learn it before they sign up, not after they miss the session. A replay withdrawn by surprise reads as a bait and switch; a replay that was never promised reads as a rule.
  • Enforce the expiry. An expiring replay that gets re-sent to whoever complains is not an expiring replay - it is a full replay with an extra email, and your list learns that within two events.
  • Cut the offer, not the teaching. If the session sells something, the version that removes the pitch and the live Q&A gives away the least while withdrawing the most. It is the least resented of the restrictions because nobody feels short-changed on the substance.

Is there a way to beat the replay without removing it?

One idea in the entire corpus claims to have done this, and it is a format change rather than a marketing one.

Framing the live event as a working session rather than a lecture shifted the perceived value from "I can catch the recording" to "I need to be there."

One operator, in a public forum, describing a change to their own format. No measurement was reported, and this is the only replay-beating idea we found anywhere in the research.

The logic is that the replay only competes with a lecture. If the live session is a lecture, the recording is a strictly better version of it - same content, at 2x speed, when convenient. If the session is something you do, the recording is a video of other people doing it, and that is not the same product at all. The replay stops being a substitute without anyone having to withhold it.

What makes a session genuinely un-replayable, in ascending order of effort:

  • They bring something. A page, a number, a draft, a screenshot - submitted at registration and reviewed in the room.
  • Their case gets answered. Questions taken on specifics, not on the topic. The recording answers somebody else's question; live answers theirs.
  • They finish something. Time inside the session to build, write, or configure the thing, with help available while they do it.
  • Something is decided in the room. A choice made, a plan committed to, a template filled in - an output that leaves with them.
  • A resource is limited. Hot seats, review slots, a headcount cap on a breakout. Real scarcity, honestly bounded.

Label this one honestly

A single operator, describing their own experience, with no before-and-after numbers attached. We are giving it prominence because it is the only structural answer anyone offered to a problem that everyone else answers with a better reminder email - not because it is proven. If you adopt it, you are running the first test of it we know about, and the section below is how to run that test properly.

It also has a property the other options do not: it is the only move that raises live attendance without taking anything away from anyone. The ranked list of everything else that plausibly moves a show up rate is in how to increase webinar attendance, including the lever that is larger than any of this and that most vendors leave out because they do not sell it.

What if you run evergreen or automated webinars?

Then most of this page does not apply to you, and it is worth saying so plainly rather than letting you read to the end and work it out. Evergreen is a different product, not a setting on the same one. The session is already a recording; the registrant already knows it; there is no live moment to protect and no replay to withhold. The replay question, as a question, mostly dissolves.

25%
Live show up rate given as a baseline by a course-creator practitioner - US and English-language, no sample size disclosed
Source: Scale For Impact
38%
Show up rate the same practitioner gives for evergreen or on-demand sessions - same source, same absence of a sample
Source: Scale For Impact
70%
Stay rate target: the share of attendees still present through the sales section - practitioner figure, no sample
Source: Scale For Impact
Below 20%
The live show up rate that same practitioner calls a signal the pre-event sequence needs work
Source: Scale For Impact

Those four numbers come from one practitioner who discloses a basis - 114 webinars built and optimised over ten years - but no methodology, no measurement period per figure, and no per-figure sample. We include them because they are the only course-creator-specific figures in the literature, and we would rather show you a labelled weak number than a confident invented one. Do not put them next to a platform benchmark and treat the difference as a finding.

Two structural things follow for anyone running evergreen. The gap between registering and the session starting is frequently minutes, not days, which means most pre-event sequences have nowhere to happen. And the thing that decides whether an evergreen funnel works is the stay rate and the offer, not attendance mechanics.

What we do and do not build for

Everything we do is built for scheduled live sessions: a fixed date, a registrant list, and a window before it in which a conversation can happen. If you run evergreen, we are the wrong supplier and we would rather tell you here than after a call. We would also rather tell you than let you leave the page assuming it and never ask - operators told us plainly that they would not email to find out.

How would you test the replay policy on your own list?

Since nobody has tested this, the only real answer available is: you test it, on your own list, and you become the first person you know of with an actual number. That is less satisfying than a benchmark and considerably more useful, because your traffic source and your offer are the two variables the missing research would not have controlled for anyway.

The practical design is to alternate the policy across your next several events, holding everything else still:

  • Same traffic source and same mix. If one event runs on paid traffic and the next on your house list, you have measured the traffic, not the replay. This is the mistake that ruins most operator tests.
  • Same offer, same session, same length. Change one thing.
  • Same day of week and time slot. A Tuesday event and a Friday event are not comparable, and neither is a session that moved by three hours.
  • Alternate rather than switch. Replay, no replay, replay, no replay - so a seasonal drift affects both arms roughly equally instead of landing entirely on one.
  • Several events, not two. A single pair tells you about two Tuesdays. Run enough of them that a difference has to survive being repeated.
  • Announce the policy at registration, both times. Otherwise you are testing surprise, not scarcity.

Measure four numbers, not one

1. Registrations per event - the number the replay promise was helping. 2. Live show up rate - the number you are trying to move. 3. Total viewing, live plus replay - so you can see whether you grew the audience or moved it. 4. Sales, and which viewing state they came from - the only one that pays for anything. A replay policy that lifts show up rate, cuts registrations and leaves revenue flat is a change, not an improvement. If you only track number two, that is exactly the result you will fail to notice.

Alternating across events is not a clean randomised trial, and it is worth knowing why. Time is confounded with the treatment: your list gets more saturated, your ads get more expensive, the season moves. The cleaner design is to split one event's registrant list in half and send the replay to only one half - same day, same session, same everything - but that means treating two groups of customers differently for the same event, which many operators will not do and some are right not to do. If you are willing, it answers the question far faster. If you are not, alternate, and accept a noisier answer honestly obtained.

One more note on what a result would mean. Whatever you find applies to your list, your offer and your audience, and to nothing else. That is not a limitation of the method - it is the actual state of knowledge in this subject, which is why we have been careful all the way down this page not to hand you someone else's number dressed as an answer.

So should you offer the replay?

Our position, stated as a position rather than a finding, because a finding does not exist:

  1. Do not kill the replay to fix attendance. You would be trading a measured audience - roughly a third of total viewing in the one dataset that speaks to it - for an attendance gain nobody has ever measured. That is a bad trade to make on testimony alone.
  2. Do make it a decision. The default is "send everything to everyone forever", and almost nobody chose it. Choosing an expiring window, or an attendee-only rule, or a cut without the offer costs an afternoon.
  3. Change what live is for, first. The working session is the only reported way to beat the replay without taking anything away, and it is the change that would still be worth making if the replay question were settled tomorrow in either direction.
  4. Announce whatever you decide at registration. Half the resentment in this subject comes from the policy changing after the sign-up, not from the policy itself.
  5. Test it, and count registrations as well as attendance. Several events, alternating, one variable, four numbers.
  6. Do not buy a reminder cadence to solve this one. A reminder that says the session starts in an hour is arguing with somebody who has already priced the alternative at zero. That is a different problem with a different fix, and we have written about which is which.

If you want the full picture of what does move a show up rate - and the honest ranking of how strong the evidence is for each item - start with why webinar registrants do not show up for the diagnosis and webinar attendance statistics: every study for what the published numbers really measure. If you want the system rather than the reading, that is AI webinar attendance, and the part that usually matters more than the empty seat - the hundreds of registrants nobody speaks to while the offer window is open - is post-webinar follow-up calls.

Frequently Asked Questions

Frequently Asked Questions

Operators say so consistently, and it was the most-upvoted explanation for skipping a live session that we found anywhere in our research. But nobody has tested it. There is no study, no disclosed A/B test and no vendor report that varies replay policy and measures the result. The strongest reported cause of webinar no-shows is also the least studied thing in the subject, and any source that gives you a percentage for this has invented it.

Our position, which is a position and not a finding: do not remove the replay purely to raise attendance. In the BrightTALK Benchmarks Report 2021 - vendor data, 2021, US and global English-language, no webinar count disclosed - registration-to-view conversion was 34% live and 15% on-demand for 46% total, so roughly one in three of the registrants who watched anything watched only the recording. Two caveats travel with that: the same report prints 36% on its benchmark page and 33% in its prose for the live figure, and its chart figures do not sum - 34 plus 15 is 49, not 46. Removing it trades a measured audience for an unmeasured gain. Choose a middle option instead, announce it at registration, and test it on your own list.

Not that we could find, and we looked for exactly this. No academic study, no platform report isolating replay policy, no operator publishing a split test with a disclosed sample. What exists is consistent unmeasured testimony pointing one way and confident advice built on top of it. Three separate operator recommendations we found say to restrict or delay the replay; none of them attached data.

An expiring replay is available for a fixed window, commonly 24 to 72 hours, and then withdrawn. It is the most frequently recommended compromise between always sending the recording and never sending it, and it has no more published evidence behind it than either extreme. Two implementation points decide whether it does anything: the expiry has to be announced at registration, and it has to be enforced. A deadline that gets waived for anyone who complains is a full replay with an extra email attached.

It is a legitimate middle option: it rewards turning up rather than registering, and it removes the substitute for everyone who was simply choosing convenience. The cost is that it also penalises people with genuine conflicts - a timezone, a client emergency, a shift - who are not avoiding you. Operationally it is the fiddliest of the options because exceptions arrive by email and get handled by hand. Like every other replay policy, it has never been tested in public.

Nobody has measured it, and it is the cost most often left out of the argument. The recording is frequently advertised on the registration page as a reason to sign up - cannot make it live, register anyway, we will send the recording. Withdrawing it changes the offer that produced the registration, not only what happens afterwards. An operator who kills the replay, watches show up rate climb and never checks registration volume has improved a ratio and may have shrunk the business.

The one replay-beating idea in our whole research corpus is a format change rather than a messaging change: run the session as a working session rather than a lecture, so being present is required. One operator reported that this shifted the perceived value from being able to catch the recording to needing to be there. That is a single report with no measurement attached, and we label it as such. Practically it means people bring something, get their own case answered, finish something in the room, or draw on a genuinely limited resource such as review slots.

Barely. Evergreen is a different product rather than a setting: the session is already a recording, the registrant knows it, and there is no live moment to protect. The gap between registering and the session starting is frequently minutes, so most pre-event sequences have nowhere to happen. For reference, one course-creator practitioner gives 25% as a live baseline and around 38% for evergreen - US, English-language, no sample size or methodology disclosed - and everything we build is for scheduled live sessions rather than evergreen funnels.

Alternate the policy across your next several events - replay, no replay, replay, no replay - holding the traffic source, the offer, the session, the day of week and the time slot constant, and announce the policy at registration every time. Track four numbers, not one: registrations per event, live show up rate, total viewing including replay, and sales by viewing state. A cleaner design is to split a single event's registrant list in half and give the replay to only one half, which answers the question faster but means treating two groups differently for the same event.

JB
Justas Butkus

Founder & CEO, AInora

Building AI digital administrators that replace front-desk overhead for service businesses across Europe. Previously built voice AI systems for dental clinics, hotels, and restaurants.

View all articles

Ready to try AI for your business?

Hear how AInora sounds handling a real business call. Try the live voice demo or book a consultation.