You have created your variations in our graphical editor and are ready to launch your test. To preview your changes: use preview mode.
To test your test, you have 3 test modes:
- Pre-prod mode
- Cookie targeting
- IP inclusion targeting
The "Preview" feature lets you preview the changes. This feature is only operational when the AB Tasty code is present on your site.
The preview does not replace a real test, because preview mode forces changes to be shown in order to give an overview.
To preview a variation, click the Variation menu and then click the "Preview" option.
A new tab will open in your browser with a navigation bar at the bottom of the page. It allows you to browse from variation to variation and make sure that all of your page’s elements are positioned correctly.
A fragment is also added to the URL (ex: www.myurl.com/#applyVariation=29465). This fragment only appears in preview mode and is not shown when the test is activated. You can add this URL fragment to any page on your site to force changes to be applied on the page in question. In this example, "29465" corresponds to the variation’s ID (identifier). If you change the variation, this identifier will be different, as each variation has a unique ID.
If you want to see the impact of your variation on another page, just copy the variable "#applyVariation=29465" (replacing the ID with that of your variation) at the end of the URL.
In preview mode, applying changes via this method is de-correlated from the targeting of your test.
In other words, you can force changes to be applied to a page that will not meet the targeting criteria and will not participate in the test. The navigation bar tells you, however, and for information purposes, whether the page meets the targeting criteria in Details.
This method does not replace a real test, since you can not test click tracking or targeting.
This method directly integrated in the editor allows you to test in real conditions and only using the browser with which you are logged in to AB Tasty. The pre-prod mode works by installing a cookie that allows you to see your test only on your browser. In Pre-prod mode, you test in conditions that are nearly real since all your configuration parameters are respected, including targeting conditions and traffic allocation. The only difference with an active test is that you are the only one assigned to the test.
By launching the test in Pre-prod mode, you can check the display and verify the feedback from your click tracking in the reports by clicking on the selected items. If you want more information about click tracking and how to correct them, here's a help page.
To activate a test in Pre-prod mode, go to the WYSIWYG editor and select the "Pre-prod" option from the "Start Test" drop-down menu or click on the play logo available in the Dashboard or in the editor’s sidebar. A pop-up is shown to launch pre-prod mode, after a few minutes of loading you can go to the page loaded.
Once the Pre-prod mode is activated, you are redirected to a new browser tab which will show you the page you are going to test. The page being tested is the page you loaded in your Editor (in Step 1 Control Version). The page loaded in your browser contains the #abtastypreprod parameter at the end of its URL. If the page you targeted is not the page loaded in the editor you can add this setting to the targeted page, reload the page, and the pre-prod mode will be launched.
A blue AB Tasty icon with a red lock is added at the bottom left of your screen. By clicking on it, a list of all active tests on this page is shown, including your current test under way. By clicking on the name of this test, you can force yourself to be assigned to any variation so you can check each one.
If this icon does not appear immediately, you can reload the page to show it. You can also empty your cookies, and reload the page again.
In this mode, we save the objectives that you have set up to ensure that the data is properly uploaded, whether it is tracking clicks, or page views or tunnels like for an active test. If you want more information about click tracking and how to correct them, here's a help page.
Once your test has been completed, you just need to activate Production mode from the editor to definitively roll out the test to your audience.
If you generated conversions during the test, the reporting data is not automatically reset. Before launching the test definitively, you must manually reset it by clicking on the "Delete Data" button, as shown below.
If you activate Pre-prod mode on a test that is already active, a message warns you that your test will no longer be visible to users because Pre-prod mode takes precedence over Production mode. Do not forget to restart the test in Production mode.
IP inclusion targeting
This method allows you to limit your test’s visibility to users who share a specific IP address, typically that of your organisation or company. This is very practical if you want to receive a test in real condition but you want it to be only visible to other collaborators who need to validate the recipe before final upload.
This test method is useful if you want to test more complex test scenarios, such as multi-page tests that require navigating through several pages, or on different devices (PC, mobile, tablet).
You can find IP targeting in "Add Targeting" in the Visitors section. You can specify your IP address (which appears under the targeting name) or your range of IP addresses in the test targeting options. You can specify multiple IP addresses if necessary (e.g. your organisation, your branch or another technical service provider). You can combine this targeting criterion with others.
In Traffic Modulation, assign 100% of the traffic to the variation you want to test, so you can be sure of accessing to the desired page directly.
You start the test in production (it will only be visible on your IP) and open a browser window with the targeted URL. Indeed, to test by IP, you must empty these caches or test in private browsing to ensure you reach the desired variation.
Once the test is complete and the GO for deployment is given, be sure to remove IP targeting and save; also, be sure you change the modulation and publish it so that your script is updated.
This last method lets you test in real conditions and only on the browser to which you add the cookie. This is useful if you want to test more complex test cases, such as multi-page tests, and do not want to open the test to all your employees sharing the same IP from the start.
In this case, the test is activated but only displayed for users with a specific cookie on their browser. You define the name and value of this cookie yourself in the targeting interface and then create this cookie on your browser to be assigned to the test. The procedure to follow is detailed below.
- Add a cookie targeting in your test settings.
Enter a cookie name and value as shown below. Make sure you give your cookie a neutral name like "cookie_test", "beta_test" or "test_ab". If you add a cookie name that is already on your site, the user will be tested. Do not forget to save your changes and publish your test in production.
- Be sure you are assigned to the variation
Assign 100% of the traffic to the variation you want to test so you are sure to see it. Publish your test and wait 2 minutes for your script to update.
- Now you need to add the cookie to your browser
You can do this manually or by using the Edit this Cookie plugin.
- To add the cookie manually in your browser
To add the cookie manually, load the page targeted by your test in your browser, open your console (F12) and add the following line: document.cookie="cookiename=cookievalue". Press "Enter" then refresh your page, you will be assigned to the test and the variation. You can then check that everything is correct.
- To add the cookie with the "Editthiscookie” plugin
You can also add this cookie by using a plugin (ex: Editthiscookie for Chrome). Once the plugin is installed, go to the page to be tested, click on the cookie to the right of your address bar and then on the "+". Add the cookie’s name and value. Confirm and refresh the page to be assigned to the test.