The Modern Marketing Blog covers the latest in marketing strategy, technology, and innovation.

Can I Test in a Content Management System?

Optimization Shorts are a regularly published series of shorter blog articles that answer common questions asked by prospects, clients, and other professionals about all things CXO. If you’re not familiar with the series, please browse some of its latest posts, which cover how to analyze 3rd party data, the definition of positive and negative testing, and how load speed affects conversion rates.

Today, we’re going to address a very common question we get from those interested in using the Oracle Maxymiser platform for testing. "Can we run tests if we use a CMS to host or manage content on our site?"

The short answer is an emphatic, "Yes!"

For those of you who may not be familiar with our solution, the Oracle Maxymiser platform is a front-end JavaScript-based solution that sits on top of the existing code base on the site, and is CMS-agnostic. Many clients have successfully run everything from simple A/B to complex multivariate tests on sites that use a CMS.

There is no need for special integrations with your CMS to run most tests, unless there are very specific requirements. For example, if your CMS is generating specific targeting and personalization capabilities that display different content to different sets of users. Our platform can test within these targeted segments to help find the optimal content to be displayed to the user.

As always, there are best practices to keep in mind. Following this advice when testing within a CMS will ensure not only data integrity but also the best possible user experience.

  1. Changing content on the test page that directly affects or relates to the test element can impact user behavior across all variants, potentially skewing the data you're collecting. To avoid this, keep as much of the page as constant as possible throughout the test period. It is an important part of establishing a baseline.
  2. When building tests on the existing site code base, any changes to content that the test uses or is built on can potentially cause serious issues with the test itself and cause it to break. Any changes to content should only be made after the test is paused and tested with the changes. Then only after all the necessary checks have been made should the test be resumed.

The key takeaway from this week’s Optimization Short? You won't have a problem running tests with us at Oracle Maxymiser within a Content Management System. As long as you're careful with how and when content updates to the test page are made, you can run a successful test that provides valuable metrics and is another step forward on your path to a better site experience for all users.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.