A/B Test

if you haven't gone through the prerequisites and the v2 structure, please have a look at overview docid\ czeodl0skcuv 18ipuplr klevu can also power your category pages using a/b testing this means that for a given test and variant combination, the products for a given category are retrieved using the visual merchandising rules configured for that a/b test and variant allocating variants to store categories klevu allocates for each category, an a/b test and a variant with their ids for category merchandising, the type will always be “cat nav” our recommendation is that this request be polled at an interval between 20 minutes and 1 hour, to get either new allocations or skewed allocations of variants to categories that were not yet clicked by a shop customer as long as an a/b test id is received as a response on this call, said a/b test is considered active once an id is no longer received in the response of this call, it should be removed from the local browser storage for each assignment, the distribution of variants can be different for the same a/b test id and categories if a category with an a/b test variant id is selected and viewed by a shop customer, that state of having been visited should be recorded, and once another variant id is received on the response for a visited category, it should be ignored if a variant id is received for a category that has not yet been visited by a shop customer, that variant id can be assigned to the category and it can overwrite any already existing values in the local browser storage category product search with a/b test try it here!