Skip to main content

Release Notes, August 26, 2022

Hi everyone,

We have been very busy working on a bunch of new features and improvements. Our latest release includes a lot of cool stuff such as some much-requested ATS.js events, a brand new Estimated Revenue metric and under-the-hood performance improvements for ATS Analytics.

New

  • New Technology dashboard in ATS Analytics for detailed insights on bidding performance for browser, device and operating system.

  • New Estimated Revenue metric on the Overview dashboard of ATS Analytics that shows the expected revenue based on the estimated winning bids and average winning bid CPM.

    • The number shown is a rough estimate based on the average of sampled data therefore please consider these values simply as projections.

    • The calculation/metric requires a minimum of 7 days of data.

  • You can now run ATS in New Zealand! Make sure you check our English-speaking countries recommendation before adding New Zealand to your list of countries.

  • Debug logs for ATS.js v2 will show a message if it detects that ATS.js v1 is loaded on the page.

  • New event available in ATS.js for when a new or existing envelope is stored in configured storage.

    • lrEnvelopePresent

  • New events available in ATS.js events available in ATS.js for when each module within the library is fully loaded:

    • detectionModuleReady

    • dropMatchPixelModuleReady

    • envelopeModuleReady

Improved

  • As you may have noticed in the past couple of weeks, ATS Analytics has been experiencing time-outs which has sadly resulted in empty or incomplete dashboards. This release we have worked on the following to improve this situation:

    • Many under the hood changes to improve our ATS Analytics product’s loading speed and reliability.

    • We have disabled the option to show data for the previous day in ATS Analytics in order to prevent incomplete reporting data to be shown in Console. This is due to the sheer amount of data for which our aggregation process needs more time to finish. We will continue investigating how to improve this process.

  • Re-triggering the detection of identifiers for when ATS.js is already loaded before the user has set its consent preferences.

  • Renaming of "Dashboard" to "Adapters" in the menu for ATS Analytics.

  • UX improvements for ‘Root Domain’ functionality on the placement configuration page.

  • ATS.js will now only check TCF consent if the user is in the EU and not just when TCF API is available on page.

  • We have made the domain regex validation less strict in Console to allow the upload of domains with longer names.

Fixed

We have fixed an incorrect behavior for when ATS.js needs to remove the envelope from storage. There are instances when a publisher loads their CMP after ATS.js. When that happens, ATS.js cannot communicate with the TCF API and interprets that as ‘no consent’. With this fix ATS.js will not remove the envelope from storage but instead wait for the CMP to be present on the page. ATS.js will only remove the envelope from storage if there is an explicit ‘no consent’ signal.

In this section: