Skip to main content

Translate 2.2.0 release notes

Overview

This article details the new feature and improvements included in the dentsu.Composable Translate 2.2.0 release.

New features

Hashed phone translation

dentsu.Composable Translate now supports matching SHA-256 hashed phone numbers to Merkury IDs through the new hashed_phone_match and hashed_phone_match_to_table templates. These templates provide the same matching capabilities for hashed phone numbers that phone_match provides for clear phone numbers, enabling consumers to perform phone-based translation without using clear phone number values.

Hashed phone translation is enabled for all existing consumers that already have access to phone translation.

The following is an example of using the hashed_phone_match template:

CALL <APP_NAME>.ALLOWED_SPROCS.RUN(
    'hashed_phone_match',
    PARSE_JSON('{
        "dimensions": ["p.phone_256", "p.hmid"],
        "consumer_resource": "MY_DB.MY_SCHEMA.MY_HASHED_PHONE_TABLE",
        "consumer_join_field": "HASHED_PHONE"
    }')
);

Improvements and updates

Improved billing visibility

Billing activity now includes the outcome of each billing call, including whether the call succeeded, was skipped, or failed. When applicable, the reason for the outcome is also recorded. This enhancement provides greater visibility into billing activity and makes potential billing issues easier to identify and troubleshoot.

Expanded application hosting support

dentsu.Composable Translate can now be deployed from the new provider account for both stage and production environments. This infrastructure update does not change the consumer experience or require changes to existing workflows.

Separation of demo and production data

Additional safeguards have been introduced to maintain separation between demo and production environments. Demo data can only be matched using demo keys, while production data can only be matched using production keys. This prevents production keys from being used with demo data, or demo keys from being used with production data, and ensures matching occurs within the appropriate environment.