Skip to main content

Match 1.3.0 release notes

Overview

This article details the new features and improvements that are included in the dentsu.Composable Match 1.3.0 release. 

Improvements and updates

PII Encryption Capabilities

The Match App now supports end-to-end PII encryption. When encryption is enabled by your provider, designated PII fields in both input and output tables are encrypted at rest, making them inaccessible to consumer-side roles, including ACCOUNTADMIN.

Encryption settings are established by the provider during onboarding and cannot be modified by consumers. Three encryption modes are available:

  • No Encryption (default, backward-compatible): Input and output data are stored and returned in plaintext.
  • PII Encryption: Only provider-designated PII fields are encrypted in input and output datasets.
  • Full Encryption: All fields are encrypted except REQUEST_ID, RECORD_ID, and COUNTRY_CODE in both input and output datasets.

Customers using PII Encryption or Full Encryption may experience slightly longer processing times due to the additional encryption and decryption operations required during request processing.

Note

For additional details about available encryption options and instructions for requesting encryption enablement, see Match App PII Encryption.

We value your feedback

To provide feedback on this release, submit a request.