Recommendations Web Test Mode

You can run Recommendations Web in test mode by modifying it's script. Typically, this will be done on a staging website where testing is conducted prior to promoting those changes to your production site.

When using test mode, several changes in behavior will occur:

  • If available, draft versions of recommendation identifiers and layouts will be used instead of published versions. This allows you to test changes to your identifiers and layouts without having an impact on your production site. To make drafts available when running in test mode, click the Promote Changes for Testing button in the app. Whenever you make changes to your draft identifiers and layouts, you must click this button again to see your changes reflected on your test site.
  • Browse events will not be stored for the contacts you use for testing. This means you can test using real contact email addresses without affecting their browse history or triggering Browse Recovery emails (if you use this app).
  • Metrics will not be captured on the Recommendation Effectiveness report.
  • Google Analytics click events will not be triggered.
To run in test mode, place the following function call code on every page:
<script type="text/javascript">
bronto('enableTestMode');
</script>
after the Web Integration Manager code. All of your other site configuration code must also be properly set up for test mode to work.

To make drafts available when running in test mode, click the Promote Changes for Testing button in the app. You will still need to publish identifiers individually to make them available on your production site.

If you do not see your changes on your testing site, try opening a private browsing session in your browser.