The Site Coverage Report allows you to see how many of your visitors are using your playbooks over the past 7 days. This allows you to build playbooks for specific audiences and understand what the most popular areas of your site are.This feature is available for Premium, and Enterprise users.
You'll find the Site Coverage report by navigating to Reports >Chat Playbooks > Site Coverage.
From here, you'll be able to see the average coverage for your site, the highest coverage page, and the lowest coverage page. Coverage can be defined as the percentage of visitors who see playbooks after visiting a page. This includes playbook views on a page load, but also playbook views after a playbook loads on a sub-page from your site.
It is possible that your site coverage shows at over 100%. No, it's not an error in reporting! If you're seeing this happen, it's most common result is because you're using Driftlinks to drive your traffic. Additionally, this could also be obtained by having a forced interaction type of playbook, or if the playbook is set to fire on every page load.
You can see further details by hovering over your pointer over each bar on the graph shown, or you scroll down on this page to find further statistics on the total amount of visitors a page has, the total about of visitors who have been shown a playbook, and the number of playbooks firing on each page.
You can also go directly to the playbooks firing on each page by clicking the Playbook link in the Playbooks firing on this page column, and then selecting the playbook you'd like to view or modify.
Additionally, if you'd like to generate a New Playbook from a page in the list, you can do so by selecting the Create playbook button in the same column.
When you decide to create a playbook via the Site Coverage report, you'll notice that in the Summary box your Audience is already pre-selected, you can modify this later on by going to Playbooks > Chat playbooks and selecting the Playbook you've created.
Need some more help? Email us at firstname.lastname@example.org.