Web push campaigns

How to get started?

Web pushes are an effective method of communication, especially in the context of Real Time Marketing. These are nothing but notifications in the browser.

In order to receive web push, a user has to agree to receive notifications in the browser. The consent box is located near the address bar and may look like this:

The appearance of the consent and the notification itself depends on the browser.

Once you accept the notification, iPresso saves the token. If the contact is not present in the contact manager, it will be an anonymous token. If a contact is present in the manager and is monitored, the token will be associated with it. 

NOTE: a contact can have multiple tokens because they can 
use multiple browsers.

 

In the case of mobile push notifications, the form and appearance of the notification depends on the mobile application in which the notification appears.

 

Monitored site and service worker

In order to start collecting tokens and sending web pushes, it is necessary to add the site to monitoring and upload the service worker file to the server of the monitored site. Below are the access paths:

System > Monitoring > Site monitoring

 

System >campaigns settings > Web push settings

To get started, go to the send section and select the web push or mobile push communication channel:

Configuration - Settings

Let's start with the settings:

• Give the created campaign a Campaign Name, which is visible only to the system's users.
• We recommend assigning an appropriate Tag to a created creative, thanks to which you will mark your mailing in the system. This will make it easier to find it e.g. in statistics. Remember that mailing Tags do not limit the group of recipients. They are used only for reporting purposes.
• If you want the push can be used in MA scenarios, select "For scenarios" as the Campaign type. Once you have finished editing the content, it will automatically be saved in the Campaigns -> For Scenarios section. Using this option bypasses the Recipients configuration as they are selected based on the criteria selected when creating the scenario.
• API triggered campaign is an option that allows you to trigger a push using our API. When selecting this option, you must enter an API key that will allow you to identify the dispatch. You can find more information in our documentation: web push API
• Link monitoring makes iPresso will collect data about the links the user clicked in the notification.
• Monitored page - from the dropdown list, select the page(s) for which you want to send web pushes. This setting determines more the tokens collected from the page/s you choose.
• Contact kind determines the recipients of the push. This is important because, in the case of monitored contacts, you can choose a segmented group of recipients. In the case of anonymous, you send the message to all tokens (permissions granted in browsers, saved in browsers).
• Push message key - the key by which dispatches are identified. Use gives you the ability to override previous dispatches that have not yet been delivered to the recipient.
• Message validity period specifies the maximum time that a notification will display to users.
• Devices on which the notification is to be displayed - similar for Operating System
• Browsers - selection of browsers on which the push should be displayed

 

Configuration - Recipients

In the next step, configure the recipients:

As recipients of your message you can choose:

• all tokens
• a selected segment, i.e. a selected group of recipients

Once creating a segment, we have three options to choose from:

• Create a new segment: this option allows you to create a new segment based on the contact information stored in the system.
• Create a new segment based on the selected one: that option allows you to create a new segment, built by editing the segment created earlier. The contacts belonging to the created segment will be recalculated.
• Select a segment from the archive: this option allows you to select a previously created segment from the archive. That gives you the possibility to reuse a predefined set of criteria. In this case, it is not possible to edit the segmentation criteria. Contacts belonging to the created segment will be recalculated.

Remember that the number of recipients can be different from the number of contacts in the segment (one contact can have multiple tokens). The final group of recipients will include only:

• correct tokens
• tokens assigned to contacts you can access
• tokens that meet the criteria defined in the settings

NOTE: segment can only be selected once it is sent to monitored contacts

 

Configuration - Content

You can configure web push accordingly to the example below:

Hints:

• the title should be a maximum of 32 characters, and the content should be 64
• it is worth personalizing the content by adding attributes to the title and/or subject, such as the name:You can also add call to action buttons

Once the content is ready, you can send a test push. To do this, you need to have a test contact in the contact manager that has a token (agreed to receive notifications on the monitored site that is defined in the settings of this push).

That will allow you to test the appearance of the notification. We suggest doing this in multiple browsers because the final appearance depends on your system and browser.

 

Summary

Move to the summary. If all items are green, the message can be approved. If there are red elements, they need to be corrected. There may also be yellow elements - they require attention, but will not prevent sending.