Redesigned, lighter, faster and offering better performance: AB Tasty framework 2.0 has landed! Info, tips and new features: this support post gives you the full lowdown.
So what is the framework 2.0?
It's an upgrade of our AB Tasty script which applies the dynamic layer for changes to your pages and collects data from your tests.
We've optimised the code in this script to make it lighter and more responsive – particularly if lots of tests and customisations are active simultaneously on your site. This will improve your site's overall performance!
What do I need to do?
Nothing! The framework change is managed automatically by AB Tasty. The tag itself, already implemented on your site, does not change.
What are the advantages?
- The tag is now lighter: on average it is 40% lighter, so it loads faster. The average load time is now 80 milliseconds.
- In the console, you'll have direct access to all information on active tests on your pages (ID, variation, targeting, etc.).
- Tag updates are faster.
- Based on another technology (Node.js instead of php) with increased performance.
- Framework 2.0 is essential for using Nirror, our new session recording tool.
Are there any risks to my ongoing tests and customisations ?
No. Framework 2.0 runs tests and customisations in the same way as framework 1.x.
The only thing to be careful about is active tests that have a complex JS addition – just make sure that everything works as it should by re-testing the test.
Are there any risks to my ongoing tests and customisations?
It's nothing to worry about! To save time and make them more user friendly, we've developed more comprehensive features to determine whether or not a test is active on the page.
How do I know whether a page is included in a test?
You can find out which test you're currently included in and which variation you're assigned to by using your web browser's console.
To do that, go to the page you want to check and display the console (F12 in Chrome, Internet Explorer and Firefox if you have the Firebug plugin installed).
A browser bar opens at the bottom of your screen. Select the "Console" tab.
Enter the instruction: ABTasty.getTestsOnPage() then OK. The ID of active tests on the page will appear, 1XXXX
For example, this shows that you have 2 active tests on your site homepage:
If you click the test 149915, you see that:
- It's an A/B test thanks to masterType
- The name of my test:“Test framework 2.0”
- The ID of the variation you're assigned to “207877”. This figure will differ for each variation because it represents the variation ID (identifier). Each variation has a unique ID. To determine which variation this figure corresponds to, you can preview your variation in the editor (using Preview). In the preview mode URL, you'll see the ID of each variation.
- You're accepted in the targeting:“accepted”
If you click “targetings”, you can see what the targeting parameters are: here there is targeting by geolocation, and you're included (include :1).
How do I know which tests are active on my whole site?
Enter the following instruction in the console: ABTasty.results then OK. The IDs of all tests and all customisations active on the site are displayed.
This is how you find out why you're not included in one test in particular: if you click the test ID you can find out why you've been excluded from the test (rejected by URL, by targeting, etc.).
For example, you know that you're not included in test 34026 because your URL is not specified in the URL targeting settings:
For multipage/multivariate tests or customisations with multiple segments, the ID of the main test will always be excluded from the targeting; make sure you look at the sub-test ID
What are the other command lines to be aware of in 2.0?
Similarly, you can type into the console:
ABTasty.DCInfos: to check your IP address, your geolocation, and the traffic allocated to the test.
ABTasty.accountSettings: to find out your account settings.
ABTasty.redirectedFrom: to find out whether you've been included in a redirect test.
Does #abtastyoptout=1 still work?
Yes, you can still ensure that you're not included in tests active on your site using the opt-out option. To do that, just add the #abtastyoptout=1 parameter to the end of the URL. For example:
Using this parameter creates a cookie in your browser in order to store the opt-out information. You will then need to delete your cookies to be included in tests again.