1. Select Push Campaign Type
To send a Push Notification campaign, click on New Campaign and choose Push Notification from the grid containing different types of campaigns.
2. Set up Campaign
The campaign name, primary goal, and secondary goal could be configured on this page. Additionally, it allows the administrator to enable a control group, a subset of the customers we are targeting with a particular campaign, who will not receive the campaign communication. Upon setting up the parameters click on “Save & Continue”.
Push Notification Options
Once you have chosen to send a Push Notification campaign, you need to give the campaign a name. For this example, we are going to send a push notification campaign to users of a coffee shop app and try to Re-Engage users who have stopped ordering lunch. We will call the campaign Re-Engage Lapsed, Lunch Users.
Insert the campaign name in the top navbar, choose a primary conversion goal "user opens the app" and click Continue button.
Now that the campaign has been named and conversion goal selected the next step is to begin to craft a Push Notification to Engage the app users and quickly communicate the message that you wish to send them. For more information on crafting engaging push notifications, please check out this Pulsate Academy guide for App Marketers on how to send better Push Notifications:
3. Insert Notification Content
Once you have decided on a strong push notification message that has a clear call to action, you can quickly type it out or copy into the Push Notification text box.
Pulsate also enables you to Insert a merge tag to your push notification to personalise the experience for your users. Adding a merge tag allows you to programatically insert personal details about a user such as their first name, last name or any other piece of custom data that Pulsate has on record for that user. Don't worry, if we don't have a merge tag for some of your users, we will leave the space, we won't insert anything for those users. To add a merge tag, click on the Insert button and choose the merge that that you want to insert.
You will also notice as you add text and merge tags to Pulsate that the phone simulator will update so that you can see what users will see when they receive the campaign. This is a great way to see exactly what your users will see and to make sure that your messages do not look too long and that all of your spelling and grammar is correct. If you want to see what the notification will look like on other iOS views or the Apple watch, you can use the arrows on either side of the simulator to scroll between those views. To find out how the campaign will look on Android, click the Android symbol and you can scroll between each Android view.
Now that you have entered your push notification text and chosen whether to add a merge tag, it is time to decide where the destination of this notification will be. This is the destination where users will be brought when they open your push notification and it should be directly linked to the Call to Action that you have included in your push notification. The following is the list of desitnations that you can choose for a Push Notification Campagn:
Destination | Description |
---|---|
Deeplink | Deeplinks enable you to link users directly to a specific section or page within your app. If you choose to send a deeplink, you will be presented with a choice of which deeplink to choose. To find out more about deeplinks and how to upload them to Pulsate, please click here. |
URL | Selecting URL allows you to link users directly to a web page. When you select this option you will be asked to enter a web page in the format of 'https://www.webpage.com' |
Opens Feed | This option allows you to link users directly to the top of their Message Center within your app. Users will be brought to the top of the Message Center and can scroll through the previous feed card campaigns that you sent them. |
Dismiss | If you select Dismiss, users will be directed to your app home page when they open the notification. |
3. Select Targeting
When you have created your push notification and chosen a destination for it, press the Next button to bring you into the Targeting section. Here you will be able to choose which groups of your users get your campaign. This is the audience for your push notification and as much as possible it should be chosen based on the group of users that you believe will be most interested in this campaign based on their previous transaction history, current proximity to a physical location and/ or in-app actions that the users will take within your app.
In the Targeting section you can choose from the following parameters:
- Segments
- Beacons
- Geofences
- In-App Events
When you choose any of these parameters, they will be displayed on the left-hand side of the screen in the Targeting simulator with an estimate of how many users the campaign will be sent to.
With Pulsate you can choose to target as many Segments, Beacons, Geofences and In App Events as you want. However, you should be trying to send each campaign to as well targeted a group of users as possible to ensure the highest open rates. You can send a campaign to multiple Segments of users and/ or send it to users who enter a Beacon, Geofence or carry out a specific in app action. Don't worry though, users will only receive the campaign once by default no matter how many of these parameters that they meet unless you specify otherwise whilst sending the campaign.
Pro Tip
Use the search functionality when you are looking for a Segment, Beacon, Geofence or In-App Event to quickly find the one that you are looking for.
You can also set up a Control Group in the Targeting section. For more information on Control Groups and how to set them up, please go here.
4. Select Delivery
Now that you have set up your push notification and chosen what users should receive it, the final step is to define when and how often users should receive your campaign. There are different scheduling options depending on whether you have chosen to send a campaign to a Segment or chosen to send it to any combination of Segments, Beacons, Geofences or In-App Events. The reason for the difference is that if you are sending a campaign to only a segment, you may want to just send the campaign to users already in the segment.
However, if you decide to send the campaign to users who enter or exit a beacon or geofence region or carry out an In-App Event (and possibly are also in a segment), you are relying on those users being in that location or carrying out that event in the future so you cannot just send it to users already in that segment.
Segment Only Campaigns
As mentioned above, if you send a campaign exclusively with a segment you will be given a choice whether to send the campaign only to users who are already in the segment or users in the segment combined with users who may enter the segment at some point in the future whilst the campaign is live.
People in the segment now
If you choose to send the campaign to only users who are currently in the segment, it will be sent to every user that is in the segment when the campaign is sent and the campaign will then end. However you can still choose whether the campaign should be sent now or at some point in the future.
There is no option for an end date when you are sending a campaign to People in the segment now because the campaign will be ended as soon as it is sent to all users in that segment.
People who enter the segment in the future
There are a number of different options if you want to send a campaign to users who enter the segment in the future too.
The first choice to be made is whether this campaign is send to each user once or multiple times if they remain eligible for it. Choosing One Time is useful would be useful if you were sending a campaign that every user in that segment should get but only once. An example might be a Welcome Campaign which you would like to send every user once they enter the segment but you only want to send it once even if the user leaves and re-enters the segment at some point in the future.
Conversely, you may want to send other campaigns multiple times to a user. An example might be a receipt for purchases the user makes, you may want to send that campaign to users every time they make a purchase and are added to that segment. If you choose to send a campaign Multiple Times, you can set Campaign Limits to ensure that users do not get overloaded by campaigns. Campaign Limits adds a delay between users receiving this campaign. For instance, if you set the campaign limit to five minutes, users will only receive this campaign once every five minutes even if they are eligible to receive it more often than that.
The final choice to make is to decide when the campaign should be scheduled. Choose Activate Immediately to send the campaign immediately or choose Schedule for the future to send the campaign at some point in the future. You can also choose here when the campaign should stop sending or whether it should continue until it is manually stopped. You can also choose to send your campaign in another timezone if you wish.
Pro Tip
If you would like to set your campaign to be delivered on certain times on specific days of the week, click Advanced Options and you can specify that by clicking the Deliver on certain days checkbox.
Delivery for Other Campaigns
If you wish to send a campaign based on the user entering or exiting a beacon or geofence or carrying out an in app event in your app and/ or combining those targeting types with a segment, you have slightly different targeting options. As users will be carrying out these actions in the future, you can only target people who will receive the campaign in the future.
The first choice to be made is whether this campaign is send to each user once or multiple times if they remain eligible for it. Choosing One Time is useful would be useful if you were sending a campaign that every user in that segment should get but only once. An example might be a Welcome Campaign which you would like to send every user once they enter a physical location but you only want to send it once even if the user leaves and re-enters the beacon or geofence region at some point in the future.
Conversely, you may want to send other campaigns multiple times to a user. An example might be a receipt for purchases the user makes, you may want to send that campaign to users every time they make a purchase and are added to that segment.
If you choose to send a campaign Multiple Times, you can set Campaign Limits to ensure that users do not get overloaded by campaigns. Campaign Limits adds a delay between users receiving this campaign. For instance, if you set the campaign limit to five minutes, users will only receive this campaign once every five minutes even if they are eligible to receive it more often than that.
The final choice to make is to decide when the campaign should be sent now or scheduled for some point in the future. Choose Activate Immediately to send the campaign immediately or choose Schedule for the future to send the campaign at some point in the future. You can also choose here when the campaign should stop sending or whether it should continue until it is manually stopped. You can also choose to send your campaign in another timezone if you wish.
Be Careful
Please ensure that you add an end date if you want this card to be removed from the feed at some point in the future. It will not be possible to change this after the campaign is sent.
Pro Tip
If you would like to set your campaign to be delivered on certain times on specific days of the week, click Advanced Options and you can specify that by clicking the Deliver on certain days checkbox.
Pro Tip
The Set campaign expiry from user's device functionality allows you to configure the duration up to which a campaign remains in the user's feed. Three choices are available:
Never - The campaign will never expire from the user's device unless an optional scheduled end date is selected
On a specific date - The campaign would expire the user's feed on this day
After a specific amount of time - Custom time range after which the campaign would expire from the user's feed.
5. Review and activate the campaign
Congratulations, your campaign is almost ready to be sent. Before you send it, Pulsate enable you to review everything that you have set up one last time so that you can make sure that everything is perfect.
The first thing you will notice on the Review page is the key parameters for this campaign which are what app the campaign is being sent for, the estimated reach of the campaign and when the campaign will be sent.
As you scroll down through the rest of the review page, you will be able to check the other details that you have set for that campaign including the Notification, Targeting and Delivery Options. If you see anything that you would like to change, you can quickly jump to that section by pressing the back button located at the bottom of the page.
Once you are happy with all of the parameters that you have set for the campaign, you are ready to send it. To send the campaign press the Activate Campaign button at the bottom of the screen. You will be asked to confirm that you wish to send the campaign. If you are ready to send, press Activate Campaign and your campaign will be activated and sent when you have specified.