Release Notes, March 8, 2021

You can now view, create, edit, and delete templates.

Save Privacy Manager configurations as templates and apply the templates to new or existing configurations.

Templates can now be applied in bulk from the overview screen.

You can now select all configurations of a certain type (Web, Mobile, AMP) in the configuration overview screen.

We have made many under the hood changes to decrease the footprint of the Privacy Manager and increase loading speed.

Console now keeps track of the state of your configuration whether you are editing.

Showing only top 5 devices and versions in dashboard.

We’ve added a loader to the dashboard until reports are visible.

Fixed an issue where Console became unresponsive when uploading a large set of vendors in a Privacy Manager configuration.

The purpose overview has a new design, which should make it more clear and less daunting to the end-user. The state of nested purposes is shown below the stack name. Users are able to see the stack description as well as control the state of nested purposes by expanding the stack.

We’ve added a tooltip to vendors and purposes in order to clarify that the vendors are processing data under the legal ground of legitimate interest.

The layout of the notice bar for GDPR for Web and AMP has been redesigned. The new layout is cleaner, has a lower profile, and no longer allows scrolling within the unit. Additionally, this new notice layout improves user experience by allowing them to navigate the site without interacting with the CMP. Note: users will now find the stack and purpose descriptions in "Manage Settings."

The vendor overview now has a search filter.

You now have the option to show a custom stack instead of individual custom purposes. This is a cleaner and more concise approach that has been better received by end-users. Note: custom stack titles and descriptions are configurable in Console and will only be shown on the notice.

A default custom stack that captures all custom purposes will be added on all newly created configurations.

We now publish a “filtered vendor list” which contains the vendor selection after publisher restrictions have been applied.

Now you can show optional Imprint and Privacy Policy links on the Notice and Manager screens. The labels and URLs for the links are configurable from Console.

We have made many changes under the hood to decrease the footprint of the Privacy Manager and increase loading speed.

Nested purposes have been removed from the notice (center position). Only the stack or purpose description will be shown under the title. This will make the notice more user friendly and faster to load.

By default custom purposes will not be disclosed on the notice for new configurations.

Changed standard “Audit ID” description to specify that the audit id is not stored unless a consent action has been performed.

We increased the max items per page to 20 in the Publisher Restrictions drawer within your Privacy Manager configuration.

GDPR for Web is now compatible with the standard IAB stub.

Updated Lithuanian translations.

Fixed an issue where the ‘Last Day Edited’ column was empty in the Integrations section.

We’ve fixed an issue when uploading a large number of vendors using the csv bulk upload.

Fixed a couple of console errors when viewing old Privacy Manager CCPA configurations.

The purpose overview has a new design, this will make it more clear and less daunting to the end-user. The state of nested purposes is shown below the stack name. Users are able to see the stack description as well as control the state of nested purposes by expanding the stack.

We’ve added a tooltip to vendors and purposes in order to clarify that the vendors are processing data under the legal ground of legitimate interest.

The layout of the notice bar for GDPR for Web and AMP has been redesigned. The new layout is cleaner, has a lower profile, and no longer allows scrolling within the unit. Additionally, this new notice layout improves user experience by allowing them to navigate the site without interacting with the CMP. Note: users will now find the stack and purpose descriptions in "Manage Settings."

The vendor overview now has a search filter.

You now have the option to show a custom stack instead of individual custom purposes. This is a cleaner and more concise approach that has been better received by end-users. Note: custom stack titles and descriptions are configurable in Console and will only be shown on the notice.

Now you can show optional Imprint and Privacy Policy links on the Notice and Manager screens. The labels and URLs for the links are configurable from Console.

Due to AMP framework limitations it is not possible to show a logo on notice and therefore we removed the option from configuration.

Nested purposes have been removed from the notice. Only the stack or purpose description will be shown under the title. This will make the notice more user friendly and faster to load.

Changed standard “Audit ID” description to specify that the audit id is not stored unless a consent action has been performed.

We increased the max items per page to 20 in the Publisher Restrictions drawer within your Privacy Manager configuration.

Updated Lithuanian translations.

We’ve fixed an issue when uploading a large number of vendors using the csv bulk upload.

We now have the checkConsent function available as part of the adequacy API. You will be able to use Adequacy API to check for consent per vendor and purpose.

Consent Trigger version is now available across the different Privacy Manager products to allow for managing the trigger version when syncing consent across different platforms.

In order to provide a quick overview of what data are processed in which schema, the data fields section now contains a new table showing all data fields that are being used and where.

When deleting subject data, it is now required to specify the schema you want to delete data from.

It is no longer possible to delete or rename a data field that is associated with a schema.

It is no longer possible to remove data fields from a schema.

We’ve improved the design of the password input field during sign-up.

We’ve updated icons in the navigation pane.

Many minor styling and design improvements.