There are several conditions that are considered when attempting to autoplay audio, including mobile- and browser restrictions, stored play state and browser window focus.
Visitor's previous play state
If X3 detects that the visitor has already interacted with the audioplayer (clicked to play or stop audio), the visitor's last play state will be given priority before the autoplay setting. For example, if the visitor has STOPPED the audio on previous visit, audio will NOT attempt to autoplay. If the visitor was PLAYING audio on previous visit, audio will attempt to autoplay (even if autoplay option is disabled). If visitor has not yet interacted with the audioplayer button (all new visitors), the autoplay setting will be used.
Autoplay browser restrictions
All mobile browsers and some desktop browsers (notably Chrome and Safari) will block audio autoplay [read more], until the visitor interacts with the website by click or touch. For browsers that do not allow immediate autoplay, X3 will autoplay audio after the visitor interacts with the website by click or touch within 1 minute after the website loads.
Browser window focus
Autoplay requires that the website's browser tab is in focus when the website loads. If the visitor is viewing a different website/tab, they would not want audio to autoplay from a background tab. Similar to above, X3 will instead autoplay audio after the visitor interacts with the website within 1 minute after the website loads.
Audio will only autoplay on mobile devices if the visitor has previously interacted with the audioplayer and left it in PLAY state. Even then, because of mobile browser restrictions, autoplay will only be able to trigger once the visitor interacts with the website by touch. Autoplay on mobile devices is a bad idea, because mobile visitors don't expect audio to blast from their device just because they touch the screen, and not to mention unexpected bandwidth usage and poor sound quality. If they really want audio, they will click the play button.