If you are transitioning all pages across your site from HTTP to HTTPS (or vice versa) simultaneously, no changes are required to maintain full functionality of your Chartbeat tracking. Our tracking code is able to handle both secure and non-secure protocols, and you should not see any interruption of your service due to a protocol change.
Our standard website snippet loads our tracking library as a protocol-relative URL, so it will work seamlessly after your migration:
For cases where only some page of your site will be transitioned to the new protocol either temporarily or as a permanent solution (for example, your homepage is switched to HTTPS prior to the rest of your site), there may be a change needed to maintain accurate tracking of your visitors in Chartbeat.
By default, no referrer data is sent for traffic that flows from HTTPS to non-secure HTTP pages, and our tracking script collects this data as visitors access each page of your site so we can identify how your users arrived to their current page (i.e. Traffic Sources in your Real-time & Historical dashboards).
In this case, to ensure that referrer data is passed when visitors move from secure to non-secure pages on your site, you should implement one of the following meta referrer tags in your site's HTML
<meta name="referrer" content="unsafe-url">
<meta name="referrer" content="origin-when-crossorigin">
The meta referrer tag allows referrer data to be passed while preserving the benefits of encrypted, secure pages. For more information on meta referrer tags, check out this blog post from Moz detailing HTTPS and its implications for referrer data: https://moz.com/blog/meta-referrer-tag