(888) 310-0589 x2
You should always test your campaigns before you publish them to ensure they display the way you intended. Evergage provides two methods you can use to safely test campaigns within your actual site. Once you are confident that your campaign looks the way you want it to and will display to the right audience, you need to publish your campaign to make it live for your intended audience.
This article details both methods and how to enable them for a campaign as well as how to publish your campaign when it is ready to be seen by qualified visitors. While most customers develop their own QA checklist, and you should do so depending on the goals and design of your campaign, this article includes a list of items you can use to build from.
Test Method 1: Test an Entire Campaign with Testing Mode in the Visual Editor
This method of testing also gives you the flexibility to enter a specific experience ID directly into the Evergage Google Chrome extension. Once a campaign is in testing mode, you can continue to enter different experience IDs for any campaign in Testing mode without having to locate the campaign on the campaign list screen. If a campaign is in Testing state, you can test it with this method. This method is a good choice if you want to test your campaign with qualification rules in place. This method will abide by all rules in place for the campaign, experience, and message.
- Navigate to the page on your site that has the campaign you want to test
- Log into the Visual Editor with Campaign Author or higher permissions
- Click CAMPAIGNS
- Locate the campaign on the campaign list screen
- Change the campaign state drop down to Testing
- Click the Evergage Google Chrome extension
- Enable Testing Mode
- OPTIONAL - enter a specific experience ID and click
You can enable this testing method manually by adding the string evergageTestMessages=true to the end of the page URL. Evergage will set a cookie to remember this string for the following 30 minutes. That means that if you navigate away from the page and the parameter drops from the URL, you will still be in testing mode. To turn this feature off before the 30 minutes are up, change the URL parameter string to evergageTestMessages=false
If the URL has parameters already, add the parameter to the URL preceded by & as shown:
If the URL does not have parameters at the end, add the parameter to the URL preceded by ? as shown:
With this parameter added to the end of the URL string, you can view how any campaign in Testing state will appear to visitors on your site. You can make edits to your campaign, but after you save changes, you must refresh the page to see them.
Test Method 2: Test a Specific Experience with the Eye Icon
You can also test a specific campaign experience using, which will show the selected experience without having to be in Testing Mode. This method of testing will show the experience in the browser for 30 minutes even when it would not be shown outside of test mode. For example, it will show even if:
- The campaign is disabled
- The user's segment membership does not match the campaign rules
- The current page does not match the campaign rules
- The user is in the control group for an A/B test
- The user has dismissed the campaign
Additionally, you can configure a custom campaign test URL which will direct you to the page the campaign targets and display the campaign experience when you clickfor that experience.
- Log into Evergage with Campaign Author or higher permissions
- Click CAMPAIGNS
- Locate the campaign you want to test
- On the Overview tab under Experiences, click customized campaign test URL next to the experience you want to test. The campaign experience will open on the home page of your site unless you add a
You can enable this testing method manually by adding the string evergageTestMessages="experienceID" to the end of the page URL, where "experienceID" is alphanumeric experience ID for the experience you want to test. If the URL has parameters already, add the parameter to the URL preceded by &. If the URL does not have parameters at the end, add the parameter to the URL preceded by ?. With this parameter added to the end of the URL string, you can view how messages will appear to visitors on your site. You can make edits to your campaign, but after you save changes, you must refresh the page to see them.
Evergage will set a cookie to remember this string for the following 30 minutes. That means that if you navigate away from the page and the parameter drops from the URL, you will still be in testing mode. To turn this feature off before the 30 minutes are up, change the URL parameter string to either &evergageTestMessages=false or ?evergageTestMessages=false
You can string together multiple experience IDs from different campaigns, separating each with a comma, such as: evergageTestMessages=OR7Mm,u8o7m,0yhKl. Be aware that Evergage will not display multiple experiences from the same campaign at the same time, and that all experiences must be in the same dataset.
You can create a customized campaign test URL to specify where you want to test specific experiences in a campaign.
Publish a Campaign
Once you have thoroughly tested your campaign, you need to publish it to make it visible to qualified site visitors. The process for publishing a campaign can be done on the campaign list page or while editing the campaign.
Suggested Campaign QA Checklist
You can use this checklist to design your own QA checklist or script. This checklist is similar to the one the Evergage team uses during the campaign QA process, but yours may vary based on campaign design or campaign goals.
General QA Suggestions
- Check page targeting
- Check device type targeting is on highest level possible WHAT DOES THIS MEAN?
- Confirm all rules function as expected
- Check images appear as expected (including if protocol is HTTPS) WHAT DOES THIS MEAN?
- Confirm links and clickthroughs work as expected
- Test fields & actions WHAT ARE THEY TESTING FOR?
- Confirm dismissals work as expected
- Inspect ALL message content and item blocks with Chrome Developer Tools to confirm that there is no interference with Evergage elements and other elements on the page
- Test overall page functionality to confirm that there is no interference with other elements on the page
- Confirm that message placement and size do not interfere with other elements on the page
- Do elements use absolute positioning? Do they interfere with other elements on the page?
- For React sites only: Are there any React errors occurring on the page? Does the campaign continue to display if you navigate away from the page and return to it?
- For e-commerce sites only: Test add to cart functionality on the page
- Test on different browsers/devices
- Test control experiences for Internet Explorer exclusions WHAT DOES THIS MEAN?
Recommendations-specific QA Suggestions
- Test variable product names, images, descriptions, and other product details
- Multi-rec: ensure all items look similar and render properly
- Badges, tags, and custom attributes: confirm that they display properly and for the correct items