Yieldr Ads Update – Audience Insights & Reporting Updates

We are happy to share with you the first set of release notes for Yieldr Ads in 2019. Here's to many more to come!

In this update, you can read all about the things we have been adding and improving in the last couple of weeks. The main points of focus are:

  • The addition of Audience data insights in the reporting section; and
  • The option to select which case should be used to calculate conversion metrics in the Reporting Overview.

As always, if you have any questions or suggestions, please reach out to us via support@yieldr.com.

Introducing Audience Reporting

With our latest deployment, we are introducing a new tab in the Reporting section of the platform: Audience data.

The Audience section of Reporting allows you to analyze the users who match the Cases you have set up for your Advertiser. For example, you can get a breakdown per language on a specific case to see which languages you should support in your creatives.

The two main metrics are:

  • Case Loads: The total number of loads that occurred for the item you are viewing.
  • Unique Case Loads: The number of unique users that match the item you are viewing.

If you have any questions about this new feature, please reach out to us via support@yieldr.com.

Reporting Updates

Conversion Case Selection

We have added a new feature that allows you to select which case(s) should be used to calculate the conversion related metrics in the Reporting Overview. By default we select all cases with funnel stage "Thank You Page", but now you can also get conversion metrics for other cases.

This feature allows you to analyze, as an example, what your campaign's eCPA is when looking at steps higher up in your sales funnel.

You can find this feature in the top of the data table. Simply open the "Conversion Case" dropdown and select the cases you would like to use. Upon closing the dropdown menu, we will automatically update the conversion metrics in the data table.

Improved Metrics Calculation

While running performance checks on the reporting data, we found that some improvements could be made to how the number of Impressions and Verified Clicks are calculated. The improvements we applied may lead to some small discrepancies if you compare the data to reports you may have extracted before January 1st.

Faster Data Retrieval

We made some huge improvements to the databases containing the data for the Reporting Overview. As a result, you will see your requests return data a lot faster than before.

As a temporary downside, we currently ask you to restrict the timeframe of your requests within a single month, as we are preparing to backfill the new databases with last year's data.

Rens van der Lee

Rens van der Lee

Product Manager