A/B Test Dashboard

Dashboard purpose
This Dashboard was designed for Publishers to run an A/B test, customize the UX for their audience, compare the results and decide which ad layout is best for higher RPM, Viewability, CTR and more.

Where to start?

If you haven’t configured an A/B test layout, jump to our A/B Testing Guide to learn how, and get inspired by the best practices of AB testing!

How to use?

1. Choose the desired filters in the top selection bar; Relevant site, Device and Dates.
   Please notice that the selection options will only include placements that have an A/B Layout configured.

   Open

   

2. Below the Selection bar, both groups are presented - Control and Testing, with a Pageviews count for each in the chosen time period.
   Easy access to the layout configuration is also available from this screen.

Open

Be clicking on one of the groups you can switch the test group. This will be reflected in the data Visualization

3. A variety of KPIs and data generated by the two groups will be presented in tiles containing Revenue and Performance data. The two groups are presented in different color tones to enhance their performance differences.

Data requirements and explanations

Browsi Traffic

The data presented in this Dashboard will reflect only on Browsi powered units.

Required Key values

• BrowsiId key is generated for each layout and will have an addition _A/ _B in the end to indicate which group it is.

• BrowsiId key will be set up on GAM for all Browsi slots in order to reflect the performance generated by Browsi. (Revenue, Impressions, Line Item allocation)

Data sources

• Total Complete Pageviews - measured by Browsi (affects RPM and ads per page calculation).

• Impressions - measured by GAM (affects ads per page, CPM and viewability calculation).

• Viewability - measured by Browsi, GAM, and Moat. Selection available on the viewability tile.

• Revenue and clicks - measured by GAM (affects RPM, CTR, and CPM calculation).

• IVT (invalid traffic) - derived from MOAT analytics