Skip to main content

About Push

Overview

dentsu.Composable Push automates audience delivery from your Snowflake environment to Merkury Explorer. Push eliminates manual file transfers and external staging by enabling you to send audience data directly from Snowflake for activation in Merkury Explorer.

Push uses anonymized Hashed Merkury Identifiers (HMIDs) to deliver audiences without directly sharing personally identifiable information (PII) outside your Snowflake environment. This Snowflake-native workflow reduces manual data movement, simplifies audience delivery, and helps your team activate audiences more efficiently.

Features

  • Automated audience delivery from Snowflake to Merkury Explorer
  • Support for single-attribute, multi-attribute, and opt-out audiences
  • Support for up to 1,000 custom attributes in a multi-attribute audience
  • Audience delivery without manual file transfers or Amazon S3 staging
  • Audience-ingestion status tracking
  • Optional audience expiration dates
  • First-party data flagging

Benefits

  • Improve operational efficiency: Automate audience delivery directly from Snowflake to Merkury Explorer, reducing the manual effort and errors associated with exporting, staging, and transferring audience files.
  • Protect sensitive data: Deliver audiences using anonymized HMIDs without directly sharing PII outside your Snowflake environment.
  • Support richer audiences: Include up to 1,000 custom attributes in a multi-attribute audience to support more detailed audience segmentation and activation.
  • Simplify audience workflows: Use one application to deliver single-attribute, multi-attribute, and opt-out audiences.
  • Accelerate audience activation: Reduce the steps between preparing an audience in Snowflake and making the audience available in Merkury Explorer.

Audience types

Push supports the following audience types:

  • Single-attribute audience: Delivers a list of HMIDs as one audience in Merkury Explorer.
  • Multi-attribute audience: Delivers HMIDs with up to 1,000 custom attributes. The delivery creates a parent audience and child audiences based on the custom-attribute columns in the source table.
  • Opt-out audience: Delivers a list of HMIDs to exclude from Merkury Explorer audiences. Opt-out audiences support privacy-oriented suppression workflows and do not appear in the Merkury Explorer interface.

Key use cases

  • Automate audience delivery: Send single-attribute or multi-attribute audiences from Snowflake to Merkury Explorer without manually exporting files or staging data in Amazon S3.
  • Create detailed audience segments: Deliver multi-attribute audiences containing custom attributes that can be used as child audiences in Merkury Explorer.
  • Support suppression workflows: Send opt-out audiences to exclude identifiers from Merkury Explorer audiences and support permission-based marketing.
  • Activate first-party audiences: Identify first-party audiences at the point of delivery to support processing and activation across marketing channels.

How Push delivers audiences

Push uses DataBridge to securely connect your Snowflake environment to Merkury Explorer. DataBridge is a proprietary dentsu technology used to securely transfer data between platforms and dentsu solutions.

When you submit an audience, Push prepares the audience data in a customer-managed Snowflake table and makes the required data available to DataBridge through a secure Snowflake share. DataBridge then delivers the audience to Merkury Explorer.

Only anonymized HMIDs leave your environment. PII is not directly shared.