Prerequisite knowledge
 
  • Knowledge of the Adobe Digital Publishing Suite and Adobe Analytics.

User level:
 
Beginner
 
Modified: 06/11/14 (Change log)
 
Required Adobe products
 
DPS allows publishers to send / schedule Text as well as Background Download Notifications. 
 
Using text notifications from DPS, publishers can reach their specific set of readers with a targeted message. A segment of readers can be created in Adobe Analytics based on various criteria like readers that have downloaded a specific issue, readers that have viewed a specific article, readers that have previewed a specific issue, etc. If DPS publishers are using Adobe Analytics for their analytics needs they can segment their readers, export the list of these readers and then upload this list in the Text Notifications section of the DPS Portal to target notifications to these specific segment of readers.
 
Publishers can schedule Background Download Notifications after they have published an issue. If publishers are scheduling a publish of an issue, then as a best practice they should put some buffer time between scheduled publish and scheduled Background Download Notification.
 
This article gives you an overview of Text notification and Background Download notification features. It also explains how to send Text Notifications to specific segment of readers.
 

 
Text Notification

Publishers can create text notifications:
 
Figure 1: Creating a new notification from the DPS Dashboard
Figure 1: Creating a new notification from the DPS Dashboard
 
The Text Notification service allows publishers to customize the reader experience when the reader taps on the Text Notification with these options:
 
Figure 2: Enter Text Notification message and specify tap action

Figure 2: Enter Text Notification message and specify tap action

 

  • Launch the app: When the reader taps on the Text Notification, the app is launched and the reader is taken to the last read location in the app.
  • Launch the app and go to the library (supported on viewer version 30 onwards): When the reader taps on the Text Notification, the app is launched and the reader is taken to the library (default library slot).
  • Launch the app and go to a custom slot (supported on viewer version 30 onwards): When the reader taps on the Text Notification, the app is launched and the reader is taken to a custom slot in the app.
  • Go to a link (supported on viewer version 30 onwards): When the reader taps on the Text Notification, the app is launched and the reader is taken to a http: / https: link specified by the publisher.
  • Launch the app and go to an article within a folio (supported on viewer version 31 onwards): Once publishers select the Product ID, iPad and/or iPhone articles will be listed in a dropdown. These articles dropdown will only list the Articles Names that are common across renditions for an iPad or iPhone. For example, if publishers have an iPad HD and SD rendition. Assuming all Articles Names are the same across iPad HD and SD renditions, then the iPad Article dropdown will list all Article Names. If there are no common Article Names across iPad SD and HD renditions, then the iPad Articles dropdown will not list any Articles.
Figure 3: Specifying an article to open upon tapping notification

Figure 3: Specifying an article to open upon tapping notification

 

Background download notifications
 
Publishers can create and schedule Background Download Notifications for published folios.  This notification informs the reader that a new issue is available, or it can trigger a background download of the new issue if the app is in the iOS Newsstand. The Background Download Notification feature is available only for multi-folio apps, not for single-folio apps.
 
Here is what the reader would see when their device receives a Background Download Notification:
 
  • For Non-Newsstand apps, readers see a red badge on the app icon.
  • For Newsstand apps, only subscribers see a red badge on the Newsstand icon that indicates the number of folios downloaded in background. In iOS7, a blue dot appears below the app cover in Newsstand until the subscriber opens the app. For both subscribers and non-subscribers, the cover image is updated to reflect the newest folio cover. 
Target and Schedule Text Notifications
 
A new Text Notification can be sent to targeted readers:
 
  • Readers on iPad
  • Readers on iPhone
  • Readers that have not logged in the past month
  • List of Devices (.csv) : A custom segment can be created in SiteCatalyst and a.csv file with list of device tokens exported from SiteCatalyst can be uploaded. More details on this is avaiable in sections – “Push Notification tokens” and “Create reports in Sitecatalyst and send Text Notifications” sections.
As a best practice, if in the prior step a publisher has specified that a reader should be taken to an iPad specific article after the Text Notification is tapped; then the targeted readers in this step should be "Readers on iPad" only. In this case, if "Readers on iPhone" or "All Readers" or "Readers that have not logged in the past month" is selected as a target reader and the Article name does not exist for an iPhone reader then the reader will get an error when the Text Notification is tapped by the reader. This is not a good reader experience. A new Text Notification can be created to be sent immediately or can be scheduled to be sent in future. The service also allows for scheduled Text Notifications (that are not started) to be cancelled. The timezone used for scheduling is extracted from the timezone set on the local machine.
 
 
Figure 4: Target and schedule Text Notifications

Figure 4: Target and schedule Text Notifications

 

View Notifications history
 
Publishers can create new Text / Background download Notification and view history of previous notifications that were scheduled/sent. Background Download Notification sent via Folio Producer will be shown in the history. When a new Text / Background download Notification is created / sent , a Text Notification could have various statuses as follows:
 
  • Created: A notification has been created. It is not yet queued or sent.
  • Queued: A notification has been added to the queue. The devices are chunked before the notification could be sent to the devices. So the push notification could be going through chunking. 
  • Started: A notification is being processed.
  • All_sent: All notifications sent to Apple’s APNS.
  • Finished: All notifications sent to the devices.
  • Failed: A notification has failed due to some reason. The reason for failure would be listed.
     
Figure 5: View Notifications history

Figure 5: View Notifications history

 

 
Push notification tokens

Each publication app on a device that recieves push notification has a unique Push Notification Token associated with it. If a reader has opted-in to receiving push notifications, the Push Notification Token associated with the reader is available in a DPS SiteCatalyst report suite. Refer to fig. 1 to understand how to access these tokens. These Push Notification Tokens in SiteCatalyst are Base64 encoded.
 
Figure 6: How to access push notification token in SiteCatalyst

Figure 6: How to access push notification token in SiteCatalyst

 

 
Create reports in Adobe Analytics and send text notifications

Here are three basic reports that publishers can begin with:
 
  1. Readers that have downloaded a specific issue
  • Step 1: Create an "Issue Name" Report in Adobe Analytics and select the "Issues Downloaded" metric.
  • Step 2: This report should be broken down by "Push Notification Token" so that you can identify readers that have downloaded a specific issue. Below is a screenshot of how this report looks. You will see "None" values for Push Notification Token because not every device opts-in to receiving push notification; therefore these devices do not have a Push Notification Token associated with them.
Figure 7: Issues Downloaded report

Figure 7: Issues Downloaded report

 

  • Step 3: Download the report in csv format 
Figure 8: Download report menu

Figure 8: Download report menu

 

  • Step 4: Open the csv file in a spreadsheet application such as Microsoft Excel and keep only the Push Notification Tokens in the file.
Figure 9: Cleansed csv file

Figure 9: Cleansed csv file

 

  • Step 5: Log in to the DPS Portal and click on “Notifications” in the left navigation. Select “List of devices” and upload the csv file. Enter the Text Message and click “Notify”.   Text notification will now be sent to all readers that have downloaded a specific issue.
Figure 10: Push Notification UI on the DPS Portal

Figure 10: Push Notification UI on the DPS Portal

 

  1. Readers that have viewed an Article of a specific issue
  • Step 1: In Adobe Analytics, add a segment to include analytics hits from a specific issue. Add the segment definition and save the segment.
Figure 11: Add a segment

Figure 11: Add a segment

 

Figure 12: Segment definition

Figure 12: Segment definition

 

  • Step 2: Create an “Article Title” report broken down by “Push Notification Token” with “Content Views” metric selected.  Please note, the segment created in Step 1 should be selected.
Figure 13: Push Notification Token associated with readers that have viewed an article.

Figure 13: Push Notification Token associated with readers that have viewed an article.

 

  • Step 3: Download the report in csv format
Figure 14: Download report menu

Figure 14: Download report menu

 

  • Step 4: Edit the csv file and keep only the Push Notification Tokens in the file.
Figure 15: Cleansed csv file

Figure 15: Cleansed csv file

 

  • Step 5: Log in to the DPS Portal and click on “Notifications” in the left navigation. Select “List of devices” and upload the csv file. Enter the Text Message and click “Notify”.  Text notification will now be sent to all readers that have viewed an article of a specific issue.
Figure 16: Push Notification UI on DPS Portal

Figure 16: Push Notification UI on DPS Portal

 

  1. Readers that have previewed an issue
  • Step 1: Create a "Issue Name" Report in Adobe Analytics and select "Issues Previews" metric.
  • Step 2: This report should be broken down by "Push Notification Token" so that you can identify readers that have previewed a specific issue. Below is a screenshot of how this report looks. You will see "None" values for Push Notification Token because not every device opts-in to receiving push notification; therefore these devices do not have a Push Notification Token associated with them.
Figure 17: Push Notification Token associated with readers that have previewed a specific issue

Figure 17: Push Notification Token associated with readers that have previewed a specific issue

 

  • Step 3: Download the report in csv format
Figure 18: Download report menu

Figure 18: Download report menu

 

  • Step 4: Edit the csv file and keep only the Push Notification Tokens in the file.
Figure 19: Cleansed csv file

Figure 19: Cleansed csv file

 

  • Step 5: Log in to the DPS Portal and click on “Notifications” in the left navigation. Select “List of devices” and upload the csv file. Enter the Text Message and click “Notify”.  Text notification will now be sent to all readers that have previewed a specific issue.
Figure 20: Push Notification UI on DPS Portal

Figure 20: Push Notification UI on DPS Portal

 

 
Where to go from here

To learn more about tracking these Text Push Notifications sent, please refer to DPS Analytics Report Guide.
 
Change log
 
06/11/14: Updated to reflect new features added in the June 2014 DPS release, including push notification deep linking options and scheduled background downloads.
 
03/14/14: Updated to reflect new features added in the March 2014 DPS release, including addition text notification features, scheduling notifications, and viewing notification history.