To be able to have greater control of how user tours are enabled on websites, we need an additional level of control at the tour level so a tour can be made visible to only certain pages within a website, rather than all pages on the site, or any page on the website containing the specified URL for that tour. 
 
This could be useful when needing a tour to display on a homepage of a website only (if homepage CSS exists), or if you have a tour about a particular interface component (for example you want a tour to start on a course home page but only if that interface is present).

 
CSS selector is available at tour level as well as at individual step level, so a tour can be made visible on a website, or for a specified URL, and the tour will only start for users if the CSS criteria set (if option enabled) is matched.
 
If the CSS criterion isn't matched, then the tour does not start and it is also not counted as 'done', i.e. if the user later visits another page where the CSS does match, the tour will start at that point.