RightMessage has a built-in tracking script checker that will attempt to verify that the script is included correctly on your website. Sometimes that checker shows an error – but it’s almost always never an issue. Here’s what you need to know.
If you’re seeing a “Snippet Not Detected” notice, this simply means that our servers aren’t able to verify that your tracking pixel is loaded onto the webpage we’re checking.
Once you’ve done that, verify that the page you’re trying to load in RightMessage starts with
https://... and is secure. Browser security settings require that our backend dashboard, which is secure, can only “communicate” with other secure websites.
Make sure that any caching plugins or scripts are either disabled or refreshed. Here’s a handy guide on how to have technical details output to your browser’s console – this only happens if the script is actually loaded and running, so it’s a great way to verify that, yes, RightMessage IS loading as intended.
There are certain websites that we can’t load perfectly into our personalization editor because of settings/headers on those sites’ servers. Those headers are called “X-Frame-Options” and “Content-Security-Policy”.
When this happens, the website will load in our editor in “Compatibility Mode” instead.
This is usually still very usable, there are just a couple of limitations:
Clicking and personalizing parts of your site should still work fine in Compatibility Mode.
However, there are a very small number of sites that won’t show up in our editor at all if their X-Frame-Options or Content-Security-Policy haven’t been adjusted.
In those cases, you have two options:
If the website you are using has been built on the ‘Rails’ framework, the X-Frame-Options HTTP header value has been set by default as SAMEORIGIN as of Rails 4.
For more information on how to make the necessary adjustments, please read the article here.
Content-Security-Policy spec (W3C Recommendation)