RightMessage is showing ‘Compatibility Mode’ in the campaign editor
In order to personalize your campaigns and use the RightMessage campaign editing area, you will need to grant RightMessge specific privileges to be able to personalize your website.
In the RightMessage campaign editing area, you may see the below error screen:
This message will display if your web server or firewall is configured to block being loaded within a frame, iframe or object.
When your site is being shown in compatibility mode, you will not be able to use navigate mode in the campaign editing area to click around the site you are personalizing. If this is the case, type the direct URL into the URL bar.
Resolving compatibility mode
In order to resolve the ‘Compatibility Mode’ message, you will need to make and adjustment to the http, server or site configuration file.
Click on the ‘Click here for helplink to reveal the code that needs to be added or adjusted.
I’m being prompted to remove X-Frame-Options from my website header
One of the solutions for resolving compatibility mode in RightMessage is to make an adjustment to the ‘X-Frame-Options’ header for your website.
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.
Applications using the Rails Framework
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.