Creating a Recurring Broadcast Push Notification

Recurring broadcast push notifications are a great way to send the same message to a group of consumers on a daily basis.

Each time the recurring notification is to be sent, Plexure Campaigns reassesses the consumers based on the chosen tags, which is useful in instances where audiences and conditions change over time, such as birthdays, age bands, app opens, new consumers etc.


The following information is needed in order to set up a recurring broadcast push notification:

Setup Section 

Internal Name: The internal name of your recurring broadcast push message. This for naming purposes only within Plexure Campaigns and is not shown to the consumer.

Associated Campaign: A dropdown list of campaigns found within the Campaigns section of Plexure Campaigns. Selecting a campaign links the broadcast push message to the chosen campaign.

Recurring Type: Plexure currently supports daily recurring push notifications, which is the only option within the drop down menu.


Message Section

Message: The message content of the push notification. It is possible to use text as well as emojis within the message content to add more impact to your notifications. Keep the message simple and precise - try and say it within 10 words and make the call to action clear, e.g. "Visit us today and receive your birthday gift.", "Introducing our new value burger. Come take a look."

Plexure supports multiple languages for push notifications. If your instance has additional languages configured, you may enter them using the relevant tabs. 

Message Data Payload: Values entered here are sent along with the push notification as extended data. This can be used to take the consumer to a particular screen inside the app or deep linking to a particular offer, for example. The value must be entered using the JSON format.

Start Date and Time: The date and time at which the push message will be sent. For deployments with a large number of consumers the push messages will be sent out over several minutes from the start date and time.

Send Relative To: This is a dropdown containing two options: Consumer’s Device Time Zone and Server Time. The Consumer’s Device Time Zone option allows consumers to receive push notifications at their local time irrespective of the Plexure platform's configured time zone. The Server Time option will send the push notification to the consumers at the same time.

Offer: Links to an offer and includes the offer ID in the push message payload. Not ever seen by the consumer. 

Badge Number: iOS Only. Along with the push message Plexure can send a badge number to iOS devices. This appears as a number inside a small red circle on the app icon. The badge number can only be manually set and cannot reference exactly how many new offers any one consumer might have. 

Sound: The Plexure platform can send a sound that will play if the consumer has their device volume turned on when the push message is received.


Filter Section

Filter: Recurring broadcast push messages support consumer tags as filters. One or more consumer tags can be selected and only consumers with those tag(s) will be sent the recurring broadcast push message.

Each time the recurring notification is to be sent, Plexure Campaigns reassesses the consumers based on the chosen tags, which is useful in instances where audiences change over time, such as consumer birthdays, age bands, app opens, new consumers etc.

Reach Estimate: The Calculate Reach Estimate button estimates the number of consumers that meet the filter criteria, as above, for the selected tag(s). Adding new tags to the filter will narrow down the target consumer audience for the push message, therefore if a reach estimate is required after adding more tags, then the button will need to be clicked once more.


Activate Section

Get Approval and Activate: Once the direct push message has been set up, approval must be obtained before it is scheduled to send to the chosen consumers.

The Get Approval and Activate button sends an email to the person nominated to approve push notifications where they will be able to review its contents and criteria before approving it to be sent.




Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Please sign in to leave a comment.