TUNE provides an enterprise-grade, cross-platform messaging API for reliably delivering push notifications through Apple Push Notification Service (APNS) and Google Cloud Messaging (GCM). This article describes how to configure TUNE in your Customer Data Hub account.

Table of Contents Placeholder


  • TUNE Push API keys (public and private)
  • TUNE In-App Marketing Application ID

Supported Actions

Action Name Trigger on Audience Trigger on Streams
Push Message

Configure Settings

Go to the Connector Marketplace and add a new TUNE In-App Push connector. Read the Connector Overview article for general instructions on how to add a connector.

To configure the connector, follow these steps:

  • In the Configure tab, provide a title for the connector instance.

  • Provide your public API key, private API key and In-App Marketing Application ID.

For more information, see: Generating Keys.

Action Settings: Parameters and Options

Click Next or go to the Actions tab. It's where you'll set up actions to trigger.

This section describes how to set up parameters and options for each action.

Action: Push Message


  1. Audience User Type (Required): Select user type (see: Audience Model).
  2. Audience User (Required): Map user ID attribute to push message to. If user type is 'Segment ID' and you want to message all users, then enter 'everyone'.
  3. Message Options (Optional): Map attribute(s) to message option properties (see: Messages Model).
  4. Message Text (Required): Provide message text. Message text is a template and supports template variables (see: Templates Guide).
  5. Template Variables (Optional): Map attribute(s) to template variables to be used in message text (see: Template Variables Guide).
  6. On Push Open Options (Optional): Map attributes(s) to on push open option properties (see: OnPushOpen Model). Behavior property must be set to openApp, openDeepLink or executeDeepAction. If no options are provided, default Open App behavior is assumed.
  7. Extra Push Payload (Optional): Map attributes(s) to extra push payload properties.

Vendor Documentation

Version history
Revision #:
6 of 6
Last update:
‎01-23-2020 02:48 PM
Updated by: