Plan A/B variants of a page #

Compare two versions of a landing page.

Life cycle: Plan, example 19 of 35. Worked out on the Fit & Healthy site of Exponential 6.0.15+.

Contents #

1. In the Layouts editor
2. With templates
3. Which to choose
4. Check

In the Layouts editor #

1. Add a mapping Path prefix showcase + Query parameter variant (priority 3000) beside the regular Showcase mapping. Since explayouts 1.4.42 the resolver does not cache an answer that depends on a Query parameter condition, so /showcase and /showcase?variant=b each get their own layout on every request. Verified on the live installation: a mapping with Query parameter p643b=b on one article showed layout_4 with ?p643b=b and the regular layout_2 without it, on both Apache and Velocity, in any request order.
2. Split the traffic outside (campaign links, newsletter halves). The page cache does not keep an address whose query has a parameter outside [HttpCacheSettings] QueryStringParameters, so the variant is rendered on every view.

With templates #

1. Two full view templates, chosen by override.ini per node or remote ID, are the template way to the same.

Which to choose #

One address with a Query parameter for a test; two pages with their own address (for example /offer-a and /offer-b) when both variants should come from the page cache.

Check #

• Each variant address shows its own layout in a private window.

Related pages #

• Which layout does a page get?
• Known editor behaviors
• Plan examples, every page
• Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.