Last modified January 29, 2019 by Shelly Wolfe

Managing push notifications

Swrve’s new centralized campaign center has two options for viewing your push notification campaign results. To display only your push notification campaigns, filter your campaign view by State and Channel.

  • To expand the campaign card and view high-level metrics of a specific campaign, select View metrics.
  • To view a more detailed campaign report, on the Actions  menu, select View Campaign.

Push campaign summary card

You can perform the following actions in the Campaign center:

  • Create a new push notification. For more information, see Creating push notifications.
  • Create a Transactional Push API campaign. For more information, see Transactional push API campaigns.
  • Create a quick push notification targeted at a predefined audience. For more information, see Quick push notifications.
  • Delete a push notification in Draft status by selecting Delete campaign from the Actions   menu on the push notification summary.
  • Archive a push notification in Finished or Inactive status by selecting Archive on the campaign report.
  • Create a copy of a push notification by selecting Duplicate campaign from the Actions  menu on the push notification summary.
  • Create and download a CSV file of the results for all of your campaigns. For more information, see Downloading campaign reports.

Push notification status

The push notification status can be one of the following:

  • Draft – the push notification was created but not launched.
  • Pending/Scheduled – the push notification was launched but has not yet reached its scheduled activation time or launched campaigns that are in the process of being sent.
  • Active – the ongoing campaign is either active (transactional push) or the scheduled date/time of a recurring push notification has passed and the campaign has at least started its first iteration.
  • Inactive – the ongoing campaign has either ended or was stopped manually. The individual push notification report continues to display campaign results and message details.
  • Finished/Sent – the one time push notification was delivered.
  • Archived – the push notification is archived.
  • Failed – the push notification failed being sent to Apple or Google due to an error.
It is now possible to stop a campaign in Sending state that hasn’t completely finished being sent. When you select Stop, the system attempts to stop sending the campaign. If successful, a confirmation message is displayed and the campaign status returns to Draft. If the system cannot stop the campaign, a message is displayed with the reasons it wasn’t possible to stop the campaign.

Managing your push campaigns

To view the detailed report for a particular push notification, on the Actions  menu, select View Campaign.

Push campaign report

Depending on the message type and status, you can perform the following actions on the push campaign report screen:

  • Edit, schedule, and launch a campaign in Draft status.
  • Unschedule a Scheduled push notification, and then edit and reschedule or launch it.
  • Duplicate push notification to create a copy of a campaign.
  • Stop an Active ongoing campaign or a one time campaign that is in Sending status.
  • Archive a FailedInactive, or Sent campaign.
  • Edit an Inactive transactional push API campaign.
  • Restart an Inactive transactional push API campaign.

Viewing campaign details

For push notifications in any other status than Draft or Pending, the individual push notification screen displays a detailed report of your push notification campaign results (Campaign Report tab) and an overview of your push notification content and delivery status (Campaign Details tab). If your push notification includes multiple variants, the graphs display the results for each variant in the corresponding color. On the Campaign Details tab, select a variant tab to display the overview of the message content.

Campaign report

The Campaign Report tab displays the default tracking metrics as well as any custom goals you selected when creating the push notification. The top of the report displays overall totals for the following performance indicators:

  • Recipients – the total number of users who received the push notification.
  • Engaged – the number of recipients who opened your app by accepting the push notification.
  • Engagement Rate – the percentage of recipients who opened your app by accepting the push notification.
  • Total Influenced – the total number of users that opened the app without engaging directly with the push notification in a window of 12 hours after the push notification was sent. (Note: Influenced tracking is available with Swrve SDK version 4.11 and higher.)
  • Influence Rate – the percentage of recipients who were influenced by the push notification out of the total number of push notifications sent.
  • Total Button Clicks – the total number of users who engaged with the push notification via the custom buttons.

Below the campaign totals, the Engagement and Influenced Metrics section displays a bar graph of the default and custom metrics for engaged and influenced users, broken down by message variant or locale, if applicable. The engagement and influenced metrics are:

  • Engagement or Influence Rate – Same as above.
  • Subsequent Time in App – The average number of minutes spent in app by users after engaging with the push notification or after being influenced by the campaign.
  • Subsequent Number of Sessions – The average number of individual sessions of users after engaging with the push notification or after being influenced by the campaign.
  • Revenue – The average revenue generated per user after engaging with the push notification or after being influenced by the campaign.
  • Primary and secondary campaign goals – If set, displays the average number of goals triggered per user after engaging with the push notification or after being influence by the campaign. These goals are typically specific events or purchases.

The Button Metrics section displays the number of users who selected each button and the percentage based on the total number of notifications sent.

The Metrics Over Time section displays a line graph of various KPIs for the push notification campaign, including the default metrics, custom goals and standard KPIs. The graph includes the following features:

  • View results for a selection of KPIs. Select an option from the KPI list to display the related graph.
  • View the results for Last week, Last month or All time by selecting the related link.
  • Download a CSV file of the selected KPI results by selecting the Download CSV button.
  • If your push notification includes multiple variants, each variant displays as a separate line on the graph. Select the variant letter to remove the line from graph view.

Campaign details

The Campaign Details tab displays an overview of the push notification content, target criteria, campaign goals, and delivery results.

For one time and ongoing push campaigns, the Push Results section of the tab displays the following information:

  • N devices were targeted for the push – the number of user devices that qualified for the push notification (that is, the number of devices with a device token for the platform of your app).
  • N devices were not sent push due to absence of required user property, where no default value was specified – the number of devices that could not be sent a personalized push message, since the message included a user property reference with no fallback option, and the user did not have a value set for that user property.
  • N push notifications were sent – the number of user devices that qualified for the push notification and were processed by Swrve’s push notification batch job.
  • The last push was sent on [date and time] – the date and time of the last push notification that was sent for this campaign.
  • N devices were not sent push due to app uninstalls – the number of devices that were not sent the push notification because the app was uninstalled prior to the push.
  • N push notifications failed to send – the number of device tokens for which an error occurred in the push notification batch job, preventing them from being sent to Apple or Google.
  • N batches failed – push notifications are sent in batches of 10,000 users at a time. If something goes wrong when sending a batch and the entire batch fails, displays the number of failed batches.
  • Apple/Google rejected N notifications immediately – the number of device tokens immediately rejected by Apple or Google (due to token invalidity, for example). You can view the error message returned by Apple or Google for each rejected device token by selecting the View Causes of Rejection link.

For Transactional Push API campaigns, the Campaign Summary includes the Push API key and URL for that campaign. The Push Results section also displays:

  • The number of Push API requests.
  • The number of failed requests due to various reasons.
  • The number of push notifications sent.
  • The time and date of the last sent push.
  • The number of notifications that failed to send.
  • The number of notifications rejected by Apple or Google.

Next steps