Release Notes: November 2020

November’s releases feature new integrations like DoubleVerify measurement, and several improvements such as a new reporting dashboard, upgraded roles/permissioning, and more.

Highlighted Release

New Reporting Dashboard: We are retiring our old dashboard for a new, powerful dashboard available directly from the main nav bar! The new dashboard provides at-a-glance insights with clear visualizations to allow users to quickly and easily understand campaign performance. The dashboard is available to all Report Builder enabled customers; please reach out to your customer success manager if you still need to be enabled

Campaign Setup and Execution

Roles/Permissions on Buzz 2.0: As we continue our migration to the 2.0 API, the UI and API for “Roles” has been overhauled, providing significant UX enhancements. Customers on our new Report Builder will see the new roles UI; if you are not yet enabled for Report Builder, please contact your customer success manager. As part of this update, we have also changed some existing concepts and added several new ones such as permission groups and dashboard permissions.
- Changes to Existing Concepts
  - Active: Has been renamed to “Archive,” no other functional changes.
  - Global: Has been renamed to “Shared Across Accounts.” Multi-account admin users can now create and edit roles that are shared across accounts.
  - Field Name Aliases: This feature has been removed.
  - Field Permissions: Field Permissions on Buzz 2.0 now apply across all reports vs. requiring manual changes to each report for consistency.
- New Concepts
  - Permission Groups: “Permission Groups“ apply to “Report Field Permissions,” “Permissions Groups” are logical groupings of reporting fields that can be enabled and disabled as a group to streamline permissions settings for many individuals. Please note permissions can still be set individually on the field level.
  - Dashboard Permissions: As part of this release, we’ve revamped our Dashboards, and as such, have added support for "Dashboard Access" in Permissions. Dashboards will respect the same permissions as your Reports, so note that for more nuanced permissions, Dashboards may not display as expected.

IronSource Supply Integration: IronSource in-app display and video inventory is now available
Name Macros: We now have support for the macros below
- PUBLISHER_NAME: publisher name that the impression was served on
- ADVERTISER_NAME: advertiser name for the impression
- CAMPAIGN_NAME: campaign name for the impression
- LINE_ITEM_NAME: line item name for the impression
- CREATIVE_NAME: creative name for the impression

New Experiment Test Plans: Six new experiment test plans have been added per your feedback. These new experiment test plans and group distributions include the below

Test Plan	Test Groups (with IDs)
One Percent Hold-Out Plan (ID:9)	Control Group (1%) (ID: 27) Test Group (99%) (ID: 28)
Three-Way Split with Ten Percent Hold-Out Plan (ID:10)	Control Group (10%) (ID: 29) Group A (45%) (ID: 30) Group B (45%) (ID: 31)
Three-Way Split with Eighty Percent Hold-Out Plan (ID:11)	Control Group (80%) (ID: 32) Group A (10%) (ID: 33) Group B (10%) (ID: 34)
Three-Way Split with Ninety Percent Hold-Out Plan (ID:12)	Control Group (90%) (ID: 35) Group A (5%) (ID: 36) Group B (5%) (ID: 37)
Four-Way Split Plan (ID:13)	Group A (25%) (ID: 38) Group B (25%) (ID: 39) Group C (25%) (ID: 40) Group D (25%) (ID: 41)
Four-Way Split with Ten Percent Hold-Out Plan (ID:14)	Control Group (10%) (ID:42) Group A (30%) (ID: 43) Group B (30%) (ID: 44) Group C (30%) (ID: 45)

Reporting and Measurement

DoubleVerify Measurement for Display and Video: DoubleVerify measurement for measurable, viewable, and invalid impressions for display and video are now available for web and in-app inventory. Please note the following eligibility requirements apply:
- Web video inventory must support VPAID
- App display inventory must support MRAID or OMSDK
- App video inventory must support OMSDK

DoubleVerify measurement will only be able to report on invalid impressions for CTV environments.

Change to {IS_GDPR} macro: Previously {IS_GDPR} represented that an auction was governed by GDPR and that a user had not consented. Starting on November 12, the {IS_GDPR} macro will solely represent whether or not an auction is regulated by GDPR. We are adding a new macro, {IS_GDPR_CONSENTED}, to signal whether a user has granted consent. {IS_GDPR_CONSENTED} will also be provided as a column in auction, bid, and win logs once the change occurs.
New send-from email for Report Builder: As of November 5, scheduled emails from Report Builder will now come from the no-reply@bidderreport.com domain instead of no-reply@beeswax.com. This does not apply to emails from Query Tool.

Please be in touch with any feedback you may have.