Streaming live typically involves a lot of focus on planning the live event, crafting content, coordinating and scheduling the entire production. However, the most critical moment in this entire process is the instant that the stream goes live. Not only do you want to be ready for that moment, you also want to carefully pick a time to go live so that you have the highest possibility of getting the following from your target viewers:
Availability
Attention
Effort
Picking a time for your live stream requires a little bit of work, starting with a good understanding of who will be viewing your live stream.
Identify who the target viewers are for your live stream
It is important to consider your organisation, the content you want to live stream and who exactly are your target viewers. For example,
Are you a course provider streaming professional development content targeted at professionals?
Are you a brand streaming a promotional event with a celebrity to consumers?
Are you a company live streaming internal announcements to employees?
Each of these streams will have a different time which is most appropriate for the type of content and availability of the target viewer. Ideally, you will be aligning your stream content and target viewers with your marketing personas (example shown on the right, details at the end of the post).
Determine when your target viewers are available to watch your live stream
Think of the daily routines your target viewer might have, the different locations they are in during the day and when they will have time to view your content. For the course provider example we used above, we can predict what the daily routine for typical professionals looks like:
Work during business hours from 9 to 5pm
Commute in the car or public transport from 8am-9am to 5pm-6pm
Have some free time during the lunch break (~1pm) at work and after dinner (~7.30pm) at home
Decide what kind of attention you want from your live stream viewer
Think about the message you want to convey in your live stream, how you want to engage with your viewer and what action you want them to take during and after the live stream. Then decide how much attention does your content need from your viewer?
Does your viewer have to concentrate deeply to understand your content?
Can the viewer watch it while simultaneously doing other things?
Will they need to follow your live session for a few minutes or over an hour?
Consider the example of a brand streaming a promotional event with a celebrity. The brand might desire a viewer to casually view a 5-minute stream in a social setting and ideally lead to a discussion with friends and/or family about the live stream.
Consider what kind of effort you want from your live stream viewer
Apart from getting a viewer’s attention, you’ll also want your viewer to take action during or after the live stream. Consider how much effort (mental, emotional, physical) you require from the viewer to take desired actions. Will your content and call to action require high effort or low effort from the viewer? When is the viewer more likely to do effortless tasks or tasks requiring greater effort?
Here are a few examples that illustrate what effort you might need from the viewer:
Considering, thinking and reflecting on your content for an action such as registering for a course or buying a product requires greater effort
Watching and simply performing a single click or touch action such as a “Like” requires little effort
For the case of a company live streaming announcements or weekly Town Hall style Q&A to employees might choose to live stream during after-work drinks on a Friday (5.30pm-6pm) in a country where it has the largest presence. The desired action is that colleagues will discuss the live content with each other over drinks, which is effortless in that setting. The image on the right depicts another example of a low effort task.
Other important considerations:
Which device do you want the viewers to watch the live stream on?
Which timezone are the majority of your viewers in?
What platform are you streaming to (own website, third party destinations or social media sites)?
What can you learn from statistics reported by platforms delivering scheduled content such as email campaigns and social media posts (details at the end of this post)?
Review live viewer reports and refine the time that you broadcast
While this post will help you clarify how to determine the best time to live stream, think of your first few live streams as tests. Live streaming at a few different times will give you very valuable data. Make sure you review both the real-time stats of your live stream as well as a full report on views of your live stream and use the insights gained to optimise accordingly. An example of StreamShark’s reports is in our post on StreamShark’s Real Time Viewer Stats.
We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept”, you consent to the use of ALL the cookies. However you may visit Cookie Settings to provide a controlled consent.
This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie
Duration
Description
__cfruid
session
Cloudflare sets this cookie to identify trusted web traffic.
__hssrc
session
This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session.
_GRECAPTCHA
5 months 27 days
This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks.
cookielawinfo-checkbox-advertisement
1 year
Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .
cookielawinfo-checkbox-analytics
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional
11 months
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
CookieLawInfoConsent
1 year
Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie.
JSESSIONID
session
New Relic uses this cookie to store a session identifier so that New Relic can monitor session counts for an application.
viewed_cookie_policy
11 months
The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Cookie
Duration
Description
__cf_bm
30 minutes
This cookie, set by Cloudflare, is used to support Cloudflare Bot Management.
__hssc
session
HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie.
bcookie
2 years
LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID.
bscookie
2 years
LinkedIn sets this cookie to store performed actions on the website.
client_token
never
Description is currently not available.
lang
session
LinkedIn sets this cookie to remember a user's language setting.
lidc
1 day
LinkedIn sets the lidc cookie to facilitate data center selection.
messagesUtk
5 months 27 days
HubSpot sets this cookie to recognize visitors who chat via the chatflows tool.
UserMatchHistory
1 month
LinkedIn sets this cookie for LinkedIn Ads ID syncing.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Cookie
Duration
Description
__hstc
5 months 27 days
This is the main cookie set by Hubspot, for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session).
_ga
2 years
The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.
_ga_*
1 year 1 month 4 days
Google Analytics sets this cookie to store and count page views.
_gat_gtag_UA_24477138_4
1 minute
Set by Google to distinguish users.
_gat_UA-*
1 minute
Google Analytics sets this cookie for user behaviour tracking.
_gat_UA-24477138-6
1 minute
A variation of the _gat cookie set by Google Analytics and Google Tag Manager to allow website owners to track visitor behaviour and measure site performance. The pattern element in the name contains the unique identity number of the account or website it relates to.
_gid
1 day
Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.
CONSENT
2 years
YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data.
hubspotutk
session
HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts.
km_ai
5 years
No description available.
ln_or
1 day
Linkedin sets this cookie to registers statistical data on users' behaviour on the website for internal analytics.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Cookie
Duration
Description
_fbp
3 months
This cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website.
fr
3 months
Facebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin.
li_sugr
3 months
LinkedIn sets this cookie to collect user behaviour data to optimise the website and make advertisements on the website more relevant.
NID
6 months
Google sets the cookie for advertising purposes; to limit the number of times the user sees an ad, to unwanted mute ads, and to measure the effectiveness of ads.
test_cookie
15 minutes
doubleclick.net sets this cookie to determine if the user's browser supports cookies.
VISITOR_INFO1_LIVE
5 months 27 days
A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.
YSC
session
YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.
yt-remote-connected-devices
never
YouTube sets this cookie to store the video preferences of the user using embedded YouTube video.
yt-remote-device-id
never
YouTube sets this cookie to store the video preferences of the user using embedded YouTube video.
yt.innertube::nextId
never
This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen.
yt.innertube::requests
never
This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen.
Preston Barnes
Good info