1 of 20
2 of 20
3 of 20
4 of 20
5 of 20
6 of 20
7 of 20
8 of 20
9 of 20
10 of 20
11 of 20
12 of 20
13 of 20
14 of 20
15 of 20
16 of 20
17 of 20
18 of 20
19 of 20
20 of 20

doc

Using A/B tests through Azion’s Marketplace

Overview

Mainly, you can use A/B tests to validate certain addresses, interfaces, or even workflows. Tests enable you to experiment with variations and how they work with your users, providing two or more options to access certain content or complete task.


1. Getting the solution
2. Using the solution
3. Configuring the A/B Testing Edge Application
4. Instantiating the A/B Testing Edge Application

1. Getting the solution

To use the A/B test solution provided by Azion’s Marketplace, follow these steps:

  1. Access Real-Time Manager (RTM) and log in.
  2. On the upper-left corner of the page, select Products Menu > Marketplace.
  3. On the Marketplace’s homepage, type “test” in the search box or browse through the cards below it to find the desired A/B testing solution.
  4. Select the desired A/B testing card. The solution’s page appears.
  5. On the Subscribe for section at the bottom-right corner of the page, click the Get It Now button.

    A successful message appears. Your solution is installed and ready to use.


2. Using the solution

Your Edge Functions library holds the solutions you get on Marketplace. To use the A/B testing solution, you must create a new Edge Application to use with your new A/B testing edge function.

To learn how to create an Edge Application, visit the documentation on getting started. You can also create an Edge Application through RTM > Products Menu > Edge Application and follow the instructions.


3. Configuring the A/B Testing Edge Application

On the Edge Application page, locate the new A/B testing Edge Application and select it.

On the Main Setting tab, locate the Edge Functions switch. This switch should be on the off position, you must turn it on:

  1. Activate the switch.
  2. On the bottom-right corner, click the Save button.

    A successful message appears informing that the Edge Application is updated.

This will enable the Functions tab on your Edge Application, enabling you to instantiate an A/B testing edge function on your Edge Application.


4. Instantiating the A/B Testing Edge Application

To enable the A/B Testing function, follow these steps:

  1. On the top list, select the Functions tab.
  2. Click the Add Function button.
  3. On the Edge Function’s name text box, type a significant and easy name to remember.
  4. On the dropdown function menu, select the A/B Testing [Global] function.

This will load the function, showing a box with the code of the functions and two tabs: Code and Args.

If you click on the Code tab, you can navigate through the code to become familiar with it without making changes. On the Args tab you can change the configuration of your A/B testing function. Select the Args tab to open the code box for the Args where you can add the parameters to execute your application.

Note that the parameters have divisions of at least three sections: params, a, b. If you need to perform more than two tests, you’ll have more sections (for example: c, d, e etc.).

You add the general parameters to the functions in the first section.

These parameters are:

  1. name: the name of the cookie you’ll choose (choose a significant name that will be easy to remember).
  2. expiration: the expiration date of this cookie.
  3. max_age: the time (in seconds) for the lifespan of a cookie.
  4. domain: the domain where you’re running the tests.
  5. path: the subdomain to the cookie (you can use / to set the subdomain to all the domains).

On the second section, called a, you can add the parameters to the first test:

  1. cookie_value: a value to identify the cookie for this test variation.
  2. prob: the probability to send this address to the user (this value should be between 0 and 1, with 0 being 0% of chances and 1 being 100% of chance).
  3. adressess_list: the address for the a test (for example: www.mytest_ab_of_my_site.com:443).
  4. originid: the identification ID for the origin (this will automatically generated by RTM).
  5. live_ingest: it indicates if the origin is a live streaming (a Boolean value should used here, true or false).
  6. protocol_policy: you can force HTTP or HTTPS, or even keep the default value by passing the preserve value.
  7. path: it indicates the subdomain of the cookie (you can leave it blank, “”, to indicate that this is valid for all domains).
  8. cache_key: here you have to give a name to identify the cache, it should be unique and you can’t repeat it elsewhere.
  9. host: the name of the host that the requisition sends.

Note: the Args box shows an example of a function’s parameters.

Important: for the other instances, such as b, c, and any other you need to configure, the parameters are the same as the ones from a. Pay attention if you’re adding the right ones for each domain/text you have.


Visit the use cases about the A/B testing page for more information and reference.


Didn’t find what you were looking for? Open a support ticket.