Smart autoplay and unmute restart: how VSL players get the hook heard

A paid click is usually a first visit to that domain. The browser will not start audio for a stranger on its own.

Chrome's autoplay post states the rule in five words: "Muted autoplay is always allowed." Sound on that same visit needs a prior gesture on the domain, a high enough Media Engagement Index on desktop, or an install to the home screen.

Mozilla's media guide draws the line on the element itself. Autoplay blocking is skipped when the file has no audio track, or when that track is muted. A sales video has an audio track, so the reliable path on a new visit is to mute it.

Safari, from macOS High Sierra onward, uses an inference engine to block media with sound on most sites. WebKit's note tells developers to handle a rejected play() call, because the start is not something a script can assume.

Practitioners land in the same place. In an r/marketing thread, one reply treats a muted file as the condition for autoplay at all.

That browser policy on muted video autoplay is why the first frames on a new sales page have no audio.

These three players can restart from the opening when the viewer unmutes, and the click that does it is different on each.

Vidalytics restarts on a click anywhere

On Vidalytics, a click anywhere on a muted autoplay restarts the video and unmutes it. Its smart autoplay page describes that as immediate. Playback settings also include Unmute & Restart, which begins again at the opening frame and brings the audio on.

TrackPlay restarts when the viewer clicks the video

TrackPlay begins with audio when the browser allows it, and it starts silent only on the visits the browser blocks. The default click is on the video itself. That click restarts from the top with audio, which is how the spoken hook gets heard. A tap on the rest of the page enables audio and leaves the playhead where it is. The setting can be switched so the video click unmutes in place as well.

Panda Video restarts from the first frame

Panda Video restarts playback when the lead clicks the video, and its feature page says playback then begins from the very start so the full message is delivered.

I'd match the click target to the script. A hook that must be heard from the first word needs the player to rewind when the viewer clicks to unmute. If people tap the headline before they tap the player, you need to know which tap rewinds and which only enables audio.

How you are billed, and how a sale is tied to a play, are compared in TrackPlay vs Vidalytics.

I'd read unmute rate beside raw plays. A silent page load and a viewer who heard the hook are different events on these meters.

Vidalytics defines the rate from the overlay. A click on the overlay counts the viewer as unmuted. So does a video the browser allowed to start with audio. No interaction leaves that viewer out of the rate. Pro plans and above can pick Unmute Rate as the only success metric inside Experiments.

TrackPlay reports an unmute rate per video from the views that turned audio on.

Video hosting with A/B testing is where scoring a sales video on one number is covered.

One practitioner at Conversion Gods split autoplay against click-to-play on a client sales video, and the click-to-play arm won on engagement. The post's advice is to test it on your own traffic.