Skip to main content

Install Push

Overview

Once you have been provisioned by dentsu, the application is available for you to install. This article explains how to install Push, configure the Merkury Explorer connection, verify the installation, set up the required Snowflake objects and share, assign application roles, and grant Push access to your audience data.

Before installing Push, review Before you begin to confirm that your Snowflake account, roles, privileges, and Merkury Explorer resources meet the application requirements.

Install the application

To install the application, you need the appropriate privileges in your Snowflake account, such as ACCOUNTADMIN. For more information about role requirements and account privileges, see Snowflake’s Install an app from a listing article.

Snowflake sends an email to your account administrator when a private listing is shared with your account. To access the listing, use the link in the email or navigate to the listing in Snowsight.

To install the application:

  1. Sign in to Snowsight.
  2. In the navigation menu, select Catalog > Apps.
  3. Under Recently shared with you, select the tile for the listing.
  4. Select Security to review the privileges and logging requests for the application, including:
    • Account-level privileges
    • Privileges on objects
    • Connections
    • App events
  5. Select Get.

    Application preparation time

    Snowflake takes some time to prepare the application. When the application is ready, Snowflake sends another email to your account administrator.

  6. Optionally, enter a name for the application.

    Application name requirements

    The application name is set by dentsu, and changing it is not required. The default name is DENTSU_COMPOSABLE_PUSH_APP. If you rename the application, note the application name because you need it in subsequent steps. You can also rename the application later from the Options menu.

  7. Select the warehouse that you want to use to install the application.
  8. Select Get.

    Installation confirmation email

    When the application is installed, Snowflake sends an automated email to your account administrator.

  9. Select Open to view the application or Done to finish.

Post-installation set-up and verification

After installing Push, configure the Merkury Explorer API refresh token and external access integration, and then verify that the application is ready for use.

Setup Your Merkury Explorer API Refresh Token and External Access Integration

Push uses an external access integration and a Merkury Explorer API refresh token to connect to the required Merkury services.

A Merkury Explorer API refresh token is associated with a specific user or service account that has access to Merkury Explorer. We recommend using a service account so the application does not depend on an individual user’s access.

To configure the connection:

  1. Open the Push application in Snowsight.
  2. Go to the Configuration tab.
  3. Under External Access Integration, review the external access configuration.
  4. Confirm that the connection status displays Connected.
  5. Ensure that your browser allows pop-up windows, then click Authenticate or Reauthenticate.
  6. In the pop-up window, enter the email address associated with the token you want to use with Push.
    If you are signed in to Snowflake with your user credentials but want to authenticate using a service account, sign out of any active identity provider (IdP) sessions before continuing.
  7. Complete the configuration and confirm that the Merkury Explorer API token location appears in the application.

The external access integration uses the following endpoints:

  • api.us.m1pbm.com:443
  • auth.us.m1pbm.com:443

These endpoints are populated in the Snowflake configuration. You do not need to enter them manually.

Refresh token configuration

You configure the Merkury Explorer API refresh token once after installing the application. If you uninstall and reinstall Push, you must configure the refresh token again.

Verify application installation

Once installed, verify the state of the application by running the following query. Replace <APPLICATION_NAME> and <INSTALLER_ROLE> with the application name and role used during installation.

If you retained the default settings, use DENTSU_COMPOSABLE_PUSH_APP for <APPLICATION_NAME> and ACCOUNTADMIN for <INSTALLER_ROLE>.

USE ROLE <INSTALLER_ROLE>;

SELECT *
FROM <APPLICATION_NAME>.app_core.push_status;

If the query completes successfully and returns a count, the application is ready for use. If the query returns an error, submit a dentsu.Composable support request.

Set up required application objects

Push requires a database and schema containing a runtime storage table and secure view. The secure view is shared with the DataBridge Snowflake account so DataBridge can deliver your audience data to Merkury Explorer.

The runtime storage table is an empty table that Push uses while processing an audience. Do not load your source audience data into this table. Push populates the table during runtime.

Create a separate runtime storage table for each Merkury Explorer advertiser that you use with Push. The advertiser-specific tables can use the same database and schema.

If you already have a database and schema that you want to use, you do not need to create new ones. Otherwise, run the following statements using ACCOUNTADMIN or a role with the required privileges.

Replace the following values:

  • <consumer_defined_db>: Database containing the Push objects
  • <consumer_defined_schema>: Schema containing the Push objects
  • <consumer_defined_table>: Runtime storage table for the advertiser

Template

CREATE DATABASE IF NOT EXISTS <consumer_defined_db>;

CREATE SCHEMA IF NOT EXISTS
  <consumer_defined_db>.<consumer_defined_schema>;

CREATE OR REPLACE TABLE
  <consumer_defined_db>.<consumer_defined_schema>.<consumer_defined_table> (
    HMID VARCHAR(16777216),
    CUSTOMATTRIBUTELIST VARCHAR(16777216),
    AUDIENCE_ID VARCHAR(16777216)
  );

Example

CREATE DATABASE IF NOT EXISTS DENTSU_PUSH_APP_DB;

CREATE SCHEMA IF NOT EXISTS DENTSU_PUSH_APP_DB.DATA;

CREATE OR REPLACE TABLE
  DENTSU_PUSH_APP_DB.DATA.ADVERTISER_ONE_DATA_STORAGE (
    HMID VARCHAR(16777216),
    CUSTOMATTRIBUTELIST VARCHAR(16777216),
    AUDIENCE_ID VARCHAR(16777216)
  );

If you configure another advertiser, create a separate runtime storage table for that advertiser:

CREATE OR REPLACE TABLE
  DENTSU_PUSH_APP_DB.DATA.ADVERTISER_TWO_DATA_STORAGE (
    HMID VARCHAR(16777216),
    CUSTOMATTRIBUTELIST VARCHAR(16777216),
    AUDIENCE_ID VARCHAR(16777216)
  );

Setting up a Share

Create a secure view over the runtime storage table, and then create a Snowflake share that makes the view available to DataBridge. The secure view controls the data that DataBridge can access.

Create the secure view

Replace <consumer_defined_view> with the name of the secure view.

Template

CREATE SECURE VIEW
  <consumer_defined_db>.<consumer_defined_schema>.<consumer_defined_view> AS
SELECT
  HMID,
  CUSTOMATTRIBUTELIST,
  AUDIENCE_ID
FROM
  <consumer_defined_db>.<consumer_defined_schema>.<consumer_defined_table>;

Example

CREATE SECURE VIEW
  DENTSU_PUSH_APP_DB.DATA.ADVERTISER_ONE_DATA_STORAGE_VIEW AS
SELECT
  HMID,
  CUSTOMATTRIBUTELIST,
  AUDIENCE_ID
FROM
  DENTSU_PUSH_APP_DB.DATA.ADVERTISER_ONE_DATA_STORAGE;

Get your Snowflake account name

Run the following statement to retrieve your Snowflake account name:

SELECT CURRENT_ACCOUNT_NAME();

You use the returned account name when naming the Snowflake share.

Create and grant access to the share

The share name must use the following format:

PUSH_<SF_ACCOUNT_NAME>_<ADVERTISER_ID>_HMID

Replace the following values:

  • <SF_ACCOUNT_NAME>: Snowflake account name returned by CURRENT_ACCOUNT_NAME()
  • <ADVERTISER_ID>: Merkury Explorer advertiser ID
  • <consumer_defined_db>: Database containing the secure view
  • <consumer_defined_schema>: Schema containing the secure view
  • <consumer_defined_view>: Secure view created for the advertiser

If you use database, schema, or view names that differ from the examples in this article, update the grant statements accordingly.

Template

CREATE SHARE
  PUSH_<SF_ACCOUNT_NAME>_<ADVERTISER_ID>_HMID;

GRANT USAGE ON DATABASE DENTSU_PUSH_APP_DB
  TO SHARE PUSH_<SF_ACCOUNT_NAME>_<ADVERTISER_ID>_HMID;

GRANT USAGE ON SCHEMA DENTSU_PUSH_APP_DB.DATA 
  TO SHARE PUSH_<SF_ACCOUNT_NAME>_<ADVERTISER_ID>_HMID;

GRANT SELECT ON VIEW DENTSU_PUSH_APP_DB.DATA.ADVERTISER_ONE_DATA_STORAGE_VIEW
  TO SHARE PUSH_<SF_ACCOUNT_NAME>_<ADVERTISER_ID>_HMID;

ALTER SHARE
  PUSH_<SF_ACCOUNT_NAME>_<ADVERTISER_ID>_HMID
  ADD ACCOUNT = MERKLE.MERKLEDATABRIDGE;

Repeat the storage-table, secure-view, and share-creation steps for each additional Merkury Explorer advertiser that you configure.

Register the advertiser with Push

Run the following procedure to register the advertiser and its runtime storage table with Push. Repeat this procedure for each advertiser that you use with Push.

Replace the following values:

  • <APPLICATION_NAME>: Name of the installed Push application
  • <ADVERTISER_ID>: Merkury Explorer advertiser ID
  • <consumer_defined_db>: Database containing the runtime storage table
  • <consumer_defined_schema>: Schema containing the runtime storage table
  • <consumer_defined_table>: Runtime storage table created for the advertiser

Template

CALL <APPLICATION_NAME>.APP_CORE.REGISTER_ADVERTISER_SHARE(
  '<ADVERTISER_ID>',
  SYSTEM$REFERENCE(
    'TABLE',
    '<consumer_defined_db>.<consumer_defined_schema>.<consumer_defined_table>',
    'PERSISTENT',
    'SELECT',
    'INSERT',
    'DELETE'
  )
);

Example

CALL DENTSU_COMPOSABLE_PUSH_APP.APP_CORE.REGISTER_ADVERTISER_SHARE(
  'ADVERTISER_ONE',
  SYSTEM$REFERENCE(
    'TABLE',
    'DENTSU_PUSH_APP_DB.DATA.ADVERTISER_ONE_DATA_STORAGE',
    'PERSISTENT',
    'SELECT',
    'INSERT',
    'DELETE'
  )
);

A successful response identifies the registered advertiser, the generated alias, and the HMID data type. If the statement returns an error or an unexpected response, submit a dentsu.Composable support request.

After creating the share, submit a dentsu.Composable support request to notify dentsu. The DataBridge team must accept the share and complete the remaining setup.

Grant account role to the application role

Create the account roles that use Push and assign the appropriate Push application roles.

If you renamed the application during installation, replace DENTSU_COMPOSABLE_PUSH_APP with the name of your application.

CREATE ROLE IF NOT EXISTS DENTSU_PUSH_APP_USER;

GRANT APPLICATION ROLE
  DENTSU_COMPOSABLE_PUSH_APP.app_user
  TO ROLE DENTSU_PUSH_APP_USER;

CREATE ROLE IF NOT EXISTS DENTSU_PUSH_APP_ADMIN;

GRANT APPLICATION ROLE
  DENTSU_COMPOSABLE_PUSH_APP.app_admin
  TO ROLE DENTSU_PUSH_APP_ADMIN;

GRANT ROLE
  DENTSU_PUSH_APP_USER
  TO ROLE DENTSU_PUSH_APP_ADMIN;

The DENTSU_PUSH_APP_USER account role receives the Push app_user application role. The DENTSU_PUSH_APP_ADMIN account role receives the app_admin application role and inherits the DENTSU_PUSH_APP_USER account role.

Grant access to objects required by the app

The following grants allow Push to read the database, schema, and table containing your audience data.

Run these statements for each database and schema containing audience data. If subsequent audience tables use the same database and schema, grant SELECT on each new table. You do not need to repeat the database and schema grants.

Use a Snowflake role that has permission to grant access to the applicable objects. Replace <APPLICATION_NAME> with the installed Push application name.

Template

GRANT USAGE ON DATABASE
  <consumer_defined_db>
  TO APPLICATION <APPLICATION_NAME>;

GRANT USAGE ON SCHEMA
  <consumer_defined_db>.<consumer_defined_schema>
  TO APPLICATION <APPLICATION_NAME>;

GRANT SELECT ON TABLE
  <consumer_defined_db>.<consumer_defined_schema>.<consumer_defined_table>
  TO APPLICATION <APPLICATION_NAME>;

Example

GRANT USAGE ON DATABASE
  AUDIENCE_DB
  TO APPLICATION DENTSU_COMPOSABLE_PUSH_APP;

GRANT USAGE ON SCHEMA
  AUDIENCE_DB.SINGLE_ATTR_AUDS
  TO APPLICATION DENTSU_COMPOSABLE_PUSH_APP;

GRANT SELECT ON TABLE
  AUDIENCE_DB.SINGLE_ATTR_AUDS.AUDIENCE_SUMMER_2026
  TO APPLICATION DENTSU_COMPOSABLE_PUSH_APP;

Grant Push SELECT access to each new audience table added after the initial configuration.