Welcome to the Relevant Yield Feature and Information Letter!

Welcome, dear user of Relevant Yield, to the first release after the summer holidays.

During the last couple of months, we have focused on building up some new Dashboard templates, and adding more functionality for graphs handling in the tool.

  1. Performance Dashboard widgets (new templates)
  2. Improved graphs handling
  3. Prebid configs sent to GAM and imported back to Relevant Yield for holistic optimisation
  4. Support for Adnuntius as an ad server

The release will be made available today and throughout the rest of the week.

1. Performance Dashboards widgets

We have added 4 new templates to the system, all focusing on general performance metrics in the system:

In the image above, we focus on the current API performance, but we have added new templates for different modules and different scenarios:

  • Current API performance
  • Historical API performance
  • Current headerbidder performance
  • Historical Headerbidder performance

The difference between the current and the historical is how far they stretch back date wise.

The current performance dashboard widgets are now set as the default for new users, and will appear when a new user account is created.


As a bonus we also improved the template structure, so it is easier to find the right template:


What's in it for you?

The new templates are intended to be used by new and experienced users, but especially newer users might find them a good starting point; as they have some preset metrics that give a quick overview over the total performance of your setup.

If you are working with publisher users, these templates can also be used as a good starting point for new users that are less experienced in the system.

We have also added the possibility to have your Historical HB Analytics data as a Dashboard widget.


2. Improved graphs handling

We have added some nice and practical features for the handling of graphs in reporting and dashboard widgets. Before the release it was not possible to use multiple graphs on the same “line”, which resulted in a lot of scrolling when working with multiple metrics in the same report.

With the new function, you can select both how many graphs you would like to see in each line; but also customise their appearance:

What's in it for you?

Better usage of space on the screen, when it relates to graph; and easier use of multi metric settings - without losing the graphical overview.

These settings are available for both new and old reports/widgets. Feel free to experiment; there’s no risk of breaking anything!


3. Prebid configs sent to GAM and imported back to Relevant Yield for holistic optimisation

From now on, everytime you create a new configuration in Relevant Yield, you can opt to have that configID being sent as a keyword to GAM. This will enable you to track the configuration performance through the full flow of Prebid & GAM.

Please note that this feature requires us to have API access to your GAM setup, and it must be activated in the Configuration - Global programmatic tag. Your Customer success team can help you out if you would like to activate this feature.



So far this is supported in Prebid Client-side and Prebid Server-side; and we are looking into a solution for Prebid mobile also, but that one is a few months away.

Once the data starts getting sent to the Adserver for logging, we can also start bringing the data back into Relevant Yield (1 day delay), and you can monitor the performance in the HB Analytics historical report. As part of this, we have also added a few new metrics, based on the return we get from the Adserver:

AdServer revenue: The revenue reported back (per configuration) from the Adserver. This revenue unfortunately might differ slightly depending on the Adserver you are using, so here is a description:

  • For GAM: Revenue generated both from the Prebid line-items, and revenue coming from any other source in the adserver (that has the configurational keyword). Please notice that when using this metric, you should not add the "normal" revenue values, as they are roughly counted through the Prebid line-items revenue.
  • For Equativ: Only revenue that is generated from the Adserver (no prebid revenue), so in order to understand the full revenue value, you should add the "normal" revenue values also. 

AdServer impressions: The number of impressions that got sold in total on a specific configurational keyword.

AdServer requests: The number of requests to the adserver on any particular configurational Keyword.

AdServer eCPM: The calculated value of the Adserver revenue/Adserver requests *1000. This is a good value for determining the configurations efficiency, but please notice to factor in how the revenue is treated slightly different depending on which adserver is used; and especially if Prebid revenues are counted in this value or now.


You can read more about how to set it up and interpret the data here:



What is in it for you?

The data is reimported in the HB Historical report type, and will make sure that you have a much better understanding of the effects of your optimisation!

It works with all optimisation features, and of course also with multivariate testing:

  • Floor price optimisation 
  • Geo targeting for configuration setups
  • Refresh optimisation (Full auction reloads)
  • TimeOut optimisation.

And anything else that can be changed / set in a configuration or child configuration.


4. Support for the Adnuntius Ad Server

We have now added support for the Adnuntius ad server!