Skip to main content

Before you begin

Overview

Before installing dentsu.Composable Push, review the prerequisites in this article to confirm that your Snowflake account, roles, permissions, Merkury Explorer resources, and required Snowflake objects are configured and ready for deployment.

Enable sharing of a Snowflake listing

To begin the installation process, our team must first enable your access to the Snowflake listing for the applicable application, which requires a few details from you regarding your Snowflake account.

If you have not already done so, contact dentsu.Composable sales to request the application.

In your request, provide the following details:

  • Client name: The name of the client or company related to your request.
  • Primary contact name
  • Primary contact email
  • Snowflake Organization Name: The unique name of your Snowflake organization, as shown in your Snowflake account details.
  • Snowflake Account Name: The name assigned to your Snowflake account, as shown in your Snowflake account details.
  • Snowflake Account Locator: The unique identifier for your Snowflake account, as shown in your Snowflake account details.

You can find your Snowflake information in the Snowflake UI under Account > View Account Details, or by running the following statement in your Snowflake account:

SELECT
  current_organization_name() AS org_name,
  current_account_name() AS account_name,
  current_account() AS account_locator;

Snowflake account requirements

This application requires:

  • Snowflake Enterprise Edition or higher.

Snowflake role requirements

See the Snowflake Native Apps documentation for more information about role setup in the context of the application’s general installation.

Before installation, ensure the appropriate Snowflake roles are available.

  • Installation role: A role with privileges to install the application from the Snowflake listing. Note the name of the role used to install the application because you may need it in subsequent steps.
  • Enablement role: A role, such as ACCOUNTADMIN, that can grant the required account-level privileges to the application. After installation, you assign the appropriate account role to the application role.

App enablement requirements

Account privileges

The application requires the following Snowflake account privileges:

  • Compute pools
  • Warehouses
  • Tasks
  • External access integration

The ability to grant the required account-level privileges requires ACCOUNTADMIN or a similar role.

To enable functionality

This application requires:

  • A Merkury Explorer service account
  • The Merkury Explorer advertiser ID for each advertiser used with Push
  • A Merkury Explorer API refresh token
  • A Snowflake share granted to the DataBridge Snowflake account

A Merkury Explorer API refresh token is tied to a specific user or service account that has access to Merkury Explorer. We recommend using a service account to prevent disruption to the application if an individual user’s access changes. You use the refresh token to configure the application after installation.

Retrieve the API refresh token

For details on retrieving an API refresh token, refer to the Post-installation set-up and verification instructions.

If you do not have a Merkury Explorer account and advertiser set up, contact your dentsu representative for assistance. Note the advertiser ID because you need it when configuring Push and delivering audiences. When logged into Merkury Explorer, the advertiser id can be found in the URL (https://merkuryplatform.com/<advertiser_id>/explorer).

Push uses DataBridge to securely connect your Snowflake environment to Merkury Explorer. DataBridge is proprietary dentsu technology that enables secure data transfer between external platforms and dentsu solutions. It reads audience data made available through a secure Snowflake share and delivers it to Merkury Explorer without requiring manual file transfers. During installation, you review the external access integration that allows the application to make external calls to DataBridge.

About event logging

Snowflake Native Application Event Sharing enables effective use of this application for observability by providing the necessary information to dentsu while maintaining customer data privacy and security. Event sharing is enabled when you install the application.

  • The SNOWFLAKE.TELEMETRY.EVENTS table is the default event table for telemetry data collection. If you have not configured an event table, Snowflake uses this table by default. For information about event logging and locating and reviewing your event table, see the Snowflake event logging documentation.
  • Details about the required event types are available from the application homepage under App Events. You can review the events table at any time to confirm that the information shared with dentsu does not include sensitive information.

To review application logs, open your application instance and select App Events. Select View Logs to open a Snowflake worksheet containing a query for reviewing the application logs.

For example, if you use a custom event table and retain the default DENTSU_COMPOSABLE_PUSH_APP application name, run a query similar to the following. Replace the database, schema, and table names with the location of your event table:

SELECT
  TIMESTAMP AS time,
  RECORD['severity_text'] AS severity,
  VALUE AS message
FROM analytics_db.monitoring.push_app_events
WHERE RESOURCE_ATTRIBUTES['snow.application.name'] = 'DENTSU_COMPOSABLE_PUSH_APP'
   OR RESOURCE_ATTRIBUTES['snow.database.name'] = 'DENTSU_COMPOSABLE_PUSH_APP'
ORDER BY TIMESTAMP DESC;

Observability

Allowing developers to receive detailed logs and metrics from customer usage of a Snowflake Native Application enhances support. It enables proactive debugging, performance tuning, and faster issue resolution. With access to telemetry, developers can optimize application behavior, ensure reliability, and improve the user experience while maintaining customer data privacy and security.

This is done through Snowflake’s data-sharing capabilities, allowing developers to understand and optimize application performance without requiring access to customer data.

Logging, tracing, and metrics are among the observability features Snowflake provides to make it easier to debug and optimize applications. From the application homepage, these appear as event types that include Errors and Warnings, Metrics, Traces, Usage logs, and Debug logs.