Common Set Up Issues

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.

Problem 1: “Snippet Not Detected”

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.

First off, ensure that your script is added to your website.

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.

Problem 2: Compatibility Mode and “X-Frame Options”

One of the solutions for resolving compatibility mode in RightMessage is to make an adjustment to the ‘X-Frame-Options’ header for your website.

Issue 2

The X-Frame-Options header, or ‘XFO header’, is one of the security based HTTP response headers on your website that can attribute to a safer browsing experience for your website visitors.

Why the X-Frame-Options needs to be adjusted for RightMessage to work with your website.

For your website to work with RightMessage, the ‘X-Frame-Options’ headers must be removed in order for RightMessage to load pages you wish to personalize, run the personalizations you add to a website, and track the results added to your conversion goals.

If ‘X-Frame-Options’ permissions are enabled, modern browsers will be unable to work with RightMessage. As a result, your visitors will not see the personalizations you have added to enhance their experience with your website.

Do you use Ruby on Rails?

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.

Problem 3: Compatibility Mode and “Content-Security-Policy”

One of the solutions for resolving compatibility mode in RightMessage is to make an adjustment to the ‘Content-Security-Policy’ header for your website.

Issue 2

When your browser loads a website, it loads other assets to help the website render correctly in the browser, such as stylesheets, fonts, and javascript files.

Adding a ‘Content-Security-Policy’ (CSP) to your website header allows you to define a whitelist of approved sources of content for your site. By restricting the assets that a browser can load for your site, a Content-Security-Policy can act as an effective countermeasure to website attacks.

Why your content security policy needs to be adjusted for RightMessage to work

For your website to work with RightMessage, the ‘content-security-policy’ headers must be updated in order for RightMessage to load pages you wish to personalize, run the personalizations you add to a website, and track the results added to your conversion goals.

Without the correct ‘Content-Security-Policy’ permissions enabled, modern browsers will be unable to work with RightMessage. As a result, your visitors will not see the personalizations you have added to enhance their experience with your website.

Content-Security-Policy spec (W3C Recommendation)

Next up

Integrations

RightMessage creates a two-way link between your website and your ESP/CRM of choice.