Create a Triggered Bulk Push Notification Task
- About Triggered Push Notifications
- Create the Task
- Set Up Task Content
- Set Schedule Options
- Add a Trigger Event
- Add a Target Audience
- Set Metrics
- Set Task Properties
- Customize Task Permissions
- Submit Task for Approval
- Activate the Task
- Pause the Task
- End the Task
About Triggered Push Notifications
Triggered bulk push notifications are sent when an event that takes place outside the app that triggers the sending of a message. This is because push notifications are designed to invite the customer back into your mobile app. For example, if a coupon or an offer is generated for a customer, then that coupon system might trigger an event that sends the user a push notification that enables them to see their offer in the mobile app.
If you want to send a push notification based on specific criteria for the trigger event, supply a unique attribute value for the trigger event. The attribute value determines the which push notification to send to the customer. For example, you might create two push notification tasks that are triggered to deliver when a customer visits a page in the mobile app.
- When the customer clicks a television, you want to send a push notification that offers free delivery if they purchase the item today.
- When the customer clicks a laptop, you want to send a push notification that offers 10% off.
To enable the mobile app to send the applicable push notification, supply attribute values for the trigger events when you create the tasks. In this case, one task would have a trigger event attribute value of television and the other would have an attribute value of laptop. Based on those attribute values, the correct push notification is delivered when the customer clicks a television or a laptop. Separate push notifications are delivered in the order in which each notification is triggered.
Create the Task
- On the navigation bar, click
Tasks.
- Click
.
- Select Push Notification.
- Select Triggered as the delivery type.
- Select the mobile app where the
message will be delivered.
TipYou can edit the Send Options section if you need to change the mobile app later.
- Click Create Task.
Set Up Task Content
- Click Add
Content from the Content
section.
- Select New creative to design a new creative that is automatically added to the task. Enter the information and save the creative. When you are done updating the creative, select Ready from the list in Creative status.
- Select Existing creatives to select creatives to add to the task. You can select individual creatives or a message. You can also edit some of the creative content.
When you are done updating the creative, select Ready from the list in Creative status. The creatives must have a ready or active status to activate the task.
For more information, see Creating Mobile Push Notification Creatives.
Tip- If you add a creative that contains a personalization variable, update the variable by clicking Personalization. You can select a merge tag or substitute text for the personalization. To substitute text for the personalization variable, enter the text in the Default Value field without selecting a merge tag.
- Click iOS or Android to see a preview of the content. To ensure that the creative renders correctly, verify it across a variety of test devices.
- Use the Expanded view option to visualize the different ways that the message might appear on a mobile device.
- (Optional) Use generative AI (GenAI)
to suggest alternative messages. The suggestions match the tone of the original
message. Merge tags are supported.
TipReview the GenAI Best Practices for Generating Message Content when you are first using this option.
- Click Generate.
- Select the message that you want to use and click OK.
To generate a new list of suggestions, click Regenerate. You can refine the prompt or update the original message and regenerate suggestions.
IMPORTANT It is your responsibility to review any output generated with AI to ensure that the AI-generated content that you select is appropriate and accurate for its intended purpose. - If the task contains more than one
creative, you can configure distribution options for the creatives. Hover over
the Distribution section and click
Edit.
Select one of these methods:
- Select Frequency to specify how often a creative is displayed compared with the other creatives in this task. Next, set a percentage for each creative.
- Select
Sequential to set the order in which the
creatives are displayed. This option is not available for bulk push
tasks.
CAUTION
The order is reset every 24 hours. After 24 hours the order is reset, and the first creative in the sequence is selected again. If the content delivery schedule for your task is longer than 24 hours, the creatives might not be displayed in the order that you have specified.
- Select Rule-based to split a task’s target audience into subgroups and associate a creative with each subgroup, thereby personalizing the content that your target audience sees. You can assign different criteria to each creative so that you can decide which creatives are delivered to different subgroups of the target audience.
For more information, see Specify the Distribution of Content.
Note: This option is not available if audiences is used as the source type.
Set Schedule Options
Here are some things to consider when you schedule a bulk push notification task:
- Allow a minimum of five minutes between the time you activate the task and the scheduled start time for the task to be active. This time delay is needed by the system to process the request.
- Jobs are executed in parallel. The workload is distributed across servers for all customer requests in the region. Thus, if multiple jobs are scheduled to run at the same time, they can be processed simultaneously.
- It is recommended that you schedule jobs 10 minutes apart to ensure that large uploads of data are completed before the job starts.
- You can use on-premises data to create
an import list or transient file that contains information about the target
audience. It is recommended that you allow at least 30 minutes between the
upload of transient file data and when the bulk push notification tasks are
executed. Waiting for this time period ensures that SAS Customer Intelligence
360 has time to upload all the necessary data, including the data for
personalization, before the task begins to execute.
Note: If the transient file is not found when the task is executed, the task results in no (0) sent pushes.
- Set a schedule to specify the period
of time that a task is active. You can set the time zone, recurrence, start and
end dates and extend metric analysis.
To access scheduling options, hover over the Send Options section and click Edit. Enable Set a schedule and enter the schedule details.
- A scheduled task becomes active when the start date is reached.
- If the task is included in a real-time journey, the task uses the journey's schedule unless you enable the Set a schedule option.
- By default, the application continues collecting data for 7 days after the last occurrence of the task. However, you can select a different value for Extend metrics analysis to change how long data is collected after the last occurrence of the task.
For more information, see Set a Schedule.
- To add a trigger event, hover over the
Send Options section and click
Edit. Select an event that triggers the task to
send a push notification. Triggered push notifications can be triggered only by
an event that takes place outside the mobile app.
TipYou can click
add attribute conditions that must be present when the event occurs.
For example, you might create two push notification tasks that are triggered to deliver when a customer visits a page in the mobile app. When the customer clicks a television, you want to deliver a push notification that offers free delivery if they purchase the item today. When the customer clicks a laptop, you want to deliver a push notification that offers 10% off. To enable the mobile app to deliver the applicable push notification, supply attribute values for the trigger events when you create the tasks. In this case, one task would have a trigger event attribute value of television and the other would have an attribute value of laptop. Based on those attribute values, the correct push notification is delivered when the customer clicks a television or a laptop. Separate push notifications are delivered in the order in which each notification is triggered.
The push notification is sent when all of the conditions are met.
- (Optional) Change the mobile app that the notification goes to.
- Limit the number of times that a
customer sees the content that this task displays. Hover over the
Send Options section and click
Edit. Select one of these options:
- Limit total impressions per user defines the total number of times that a creative is displayed to a customer.
- Limit impressions per user by time period
Maximum impression defines the maximum number of times that a creative is
displayed to a customer. By default, Maximum
impression for spot and SMS tasks is set to 5. For push
notification and in-app message tasks, the default is set to
1. - Limit impressions per user by time period
Time period defines the maximum number of impressions that a user
sees during a specified time interval. By default, Time
period is set to 30 minutes.
For push notification tasks, if a customer has multiple valid devices, a push notification is sent to all the devices each time a push notification event is triggered until the impression limit is reached. For example, you might create a task that delivers a push notification each time a customer visits a page on your website in a browser. The impression limit is set to 2. Assume that a customer has two valid devices (both are known to SAS by their device IDs). Consider this scenario:
- The customer visits the page on the website, which triggers the event and delivers the mobile app push notification. The push notification is delivered to both devices. That is the first impression.
- Later, the customer visits the same page on the website. The push notification is delivered again to both devices. That is the second impression.
If the customer visits the same page yet again, no push notifications are delivered because the impression limit is reached. In total, four push notifications were delivered—two on each of the customer's devices.
For more information, see Set Impression Limits.
Add a Trigger Event
To add a trigger event, hover over the Send Options section and click Edit. Select an event that triggers the task to send a push notification. Triggered push notifications can be triggered only by an event that takes place outside the mobile app.
For example, you might create two push notification tasks that are triggered to deliver when a customer visits a page in the mobile app. When the customer clicks a television, you want to deliver a push notification that offers free delivery if they purchase the item today. When the customer clicks a laptop, you want to deliver a push notification that offers 10% off. To enable the mobile app to deliver the applicable push notification, supply attribute values for the trigger events when you create the tasks. In this case, one task would have a trigger event attribute value of television and the other would have an attribute value of laptop. Based on those attribute values, the correct push notification is delivered when the customer clicks a television or a laptop. Separate push notifications are delivered in the order in which each notification is triggered.
The push notification is sent when all of the conditions are met.
Add a Target Audience
To be included in the target audience of a triggered push notification task, a user must first complete the trigger event while the task is active. After the trigger event occurs, the user is evaluated against any targeting criteria in the task. To add criteria, hover over the Targeting section and click Edit.
- In the Eligible section, specify which people to include in your target audience.
- In the Exclusions section, specify which people to exclude from your target audience.
For more information, see Add a Target Audience to a Triggered Push Notification Task.
Set Metrics
Add metrics to track the progress of the task.
- A primary metric measures conversions to determine the success of a task. A task can have only one primary metric.
- Secondary metric can be used to track other user interactions that you are interested in.
- Hover over the Metrics section and click Edit.
- (Optional) Change the default primary
metric. Hover over the metric in the Primary Metric
section and click
.
The events and data views that you add to a primary metric determine the actions or behaviors that must be satisfied in order for a conversion to occur. If you include multiple events and data views in your primary metric, a conversion happens after the first occurrence of any of the events or data views.
(Optional) Select Classify this selection if you want the metric to be classified as either a contact or response.
- (Optional) Click Add
Secondary Metric to measure other benchmarks that you are
interested in. A task can have multiple secondary metrics. However, each
secondary metric can have only one data view or event.
(Optional) Select Classify this selection if you want the metric to be classified as either a contact or response.
- Select Stop delivery after conversion to stop delivering creatives when the primary metric for the task is met.
For more information, see Set Metrics.
Set Task Properties
To update the properties of the task, hover over the Properties section and click Edit. You can update the following types of properties:
- Standard properties, such as the task name, description, and code.
- Custom properties are specifically applicable to your goal or organization and must be added by your administrator.
You can select the Generate contact events based on the notification event if you want the task to generate notification send events each time that a message is sent.
To view or update planning properties,
click View
Plan to switch to the planning view.
For more information, see Add Properties to Your Task.
Customize Task Permissions
Customize permissions if you want to define which users and groups have access to view or edit the task.
- Click
and click Permissions.
- Enable Customize permissions.
- Click Edit and use the icons to reset permissions, add users or groups, remove users or groups, or restore default permissions.
For more information, see Customize Task Permissions.
Submit Task for Approval
If the Status
section of the task has an Approval status option, then
you must submit the task for approval before it can be activated. To submit it,
click and click Submit for
approval.
For more information, see Getting Approvals.
Activate the Task
When you are done updating the task and any required approvals are met, you can activate the task.
- Click Review and resolve any issues. Once the review completes successfully and you click OK, the task is ready to activate and the status of the task moves to Ready.
- Click
Activate.
Note: The task is activated unless it has a schedule. Scheduled tasks are activated when the start date is reached.
- When you activate a task, you are prompted to publish any dependent items that are marked Ready.
- A scheduled task becomes active when the start date is reached as long as the status of the task is either Scheduled or Active.
A job summary notification is sent when processing is complete.
After the task is activated, the default view changes to the Task insights view. From View, you can click Task design or Plan to see other views.
For more information, see Publish or Activate the Task.
Pause the Task
Open the task and click Pause.
You can pause an active task to temporarily stop delivery of a task. For example, you can pause a task if you to stop content from being delivered while you correct a mistake.
For more information, see Pause the Task.
End the Task
End the task when you no longer need the task to deliver content or when the scheduled end date is reached. Ending a task changes the status changes from Active to Complete. Completed tasks do not deliver content and cannot be modified. Any unsaved changes to the task are lost.
Click End to end the task.
For more information, see End the Task.