Push: Response tracking

The Unica Campaign and Acoustic Campaign integration performs response tracking, so marketers can retarget responders and non-responders.

Prerequisites to support response tracking

  • The UBX Toolkit was installed and configured.
  • The UBX Toolkit user created the necessary response tracking tables.
  • A Unica Campaign administrator configured the tables as a user data source.

How does tracking work?

Acoustic Campaign records information about mobile push transmission, delivery, and responses. It makes this information available to UBX.

To get the information from UBX to Unica Campaign, run UBX Toolkit scripts to download event data and import it into response tracking tables.

Unica Campaign flowcharts can then access those tables as a user data source.

In some organizations, the routing of response data is automated through scripts that administrators set up. If the scripts are on the Unica Campaign listener (Analytics) server, you can create a flowchart that calls a trigger to run the scripts and use the Unica Marketing Platform Scheduler to schedule the trigger. The Scheduler also allows you to run external scripts, so you can use that method as well.

If response routing has not been automated, you must run the scripts manually, periodically.

Attributing responses to a particular mailing and Unica Campaign is handled by the integration: Unica Campaign assigns a unique name to each push. That unique name is included in Acoustic Campaign events, for correlation back to Unica Campaign. The unique name is generated based on the Push name that is assigned in the process box on the flowchart.

What events are tracked?

Information about the following Push events can be imported into the response tracking tables, so it is available to Unica Campaign:

  • Application Install (appInstalled): Information that relates to an individual installing a mobile app on a mobile device. The app is installed and the app registration information is received.
  • Application Uninstall (appUninstalled): Information that relates to an individual removing an app from a mobile device. Apple or Google informs IBM that the app is no longer reachable by push. This might be due to uninstalling the mobile app.
  • Application Opened (appOpened): Information to describe what happens when a mobile user clicks in a simple notification to open an app.
  • Application Click (urlClicked): Information to describe what happens when a mobile user clicks a button in a simple notification, providing the mobile OS with a URL to be handled. This typically happens when the user opens a browser on a mobile device.
  • Application Notification Push Enabled (uiPushEnabled): Information that describes what happens when an APNS user uses a mobile app to opt in to receiving push notifications.
  • Application Notification Push Disabled (uiPushDisabled): Information that describes what happens when an APNS user has used the application settings to opt out of receiving push notifications.
  • Application Session Start (sessionStarted): Information that describes what happens when the mobile user opens the application for the first time in a configurable number of minutes.
  • Application Session End (sessionEnded): Information to describe when the mobile user session ends.

As a marketing user, how do I populate and use these tables?

You must periodically download events from UBX and import them into your local response tracking tables. You can run the scripts manually or as a scheduled job:
  1. To download events, run the eventsDownload script that is provided with the UBX Toolkit.
    Note: The eventsDownload script downloads tracking data related to email, SMS messages, and mobile push notifications. You may or may not be using all of those features.
  2. To import the downloaded events into the response tracking tables, run the eventsImport script that is provided with the UBX Toolkit.
  3. Be sure to follow all of the instructions that are provided in the UBX Toolkit documentation. Specifically, see Chapter 3. Event destination endpoints.
  4. Once the tables are populated, you can access the tables in Unica Campaign flowcharts to retarget responders and non-responders.

    Typically, you design a response flowchart and configure the process boxes to read data from the response tracking tables. For example, you can configure Select or Extract process boxes to target users who opened an application.

  5. For additional information, see Response tracking tables for the integration.