In the area create -> push delivery you can selected the application to be contacted with the push (fig. 1).
You can send push only to applications that have at least one certificate/api key approved.
Click on “Create a new delivery” to proceed (fig. 2)
In the next step set the “delivery parameters” (fig. 3)
– Title of the delivery -> title is mandatory because push delivery, instead of the emails, do not have an object usable to identify the delivery.
– Filter of the delivery ->the preset filter is the one connected to the application (“Name application” that includes all the users of this application).
Select from the drop down menu the filter for the delivery or create a combined one.
- Charset -> encoding charset of the message. As default the charset of the DB connected to the application will be selected
Click on next to proceed.
In the next step you can define the content of the push message (fig. 4)
The message of the push is composed not only by the message but also by other parameters that can be send to the application to track the opens, clicks and eventually custom variables to shape the function of the application.
The sections composing the editor of the push message are:
- Custom data
- Apple options
- Google options
The message tab is composed by the following items highlighted in figure 4:
1. Switch that commands the type of preview in the Apple/Google devices
2. Preview of the message
3. Buttons that allows you to choose the notification type to be visualize in the preview based on the chosen device. E.g.: lock screen, banner, notification center. Notice: the visualization mode of the push depends on the recipient System and by the status of the application to which the push must be sent.
4. Text area where is inserted the push text.
5. Count of the characters in the text of the push. If a dynamic field is inserted in the text of the push message you can require the recount of the characters considering the longest value for the selected dynamic field.
6. List of the available dynamic field for the text of the push. By the icon “+” you can insert them in the text.
7. Here you can define if you want to insert in the push the link for the open tracking. If it is flagged you have to define also the key to be associated to the tracking link. Notice: the management of the open tracking link made by ContactLab is necessary but not sufficient to register the event.The cycle must be completed with the support and the cooperation of the recipient application.
8. Number of devices Google and Apple of the delivery by the selected filter.
The tab "Links" allows you to define "N" link to be inserted in the message of the push.
This section is composed by the following elements as you can see in figure 5:
1. Key -> variable to be assigned to the link to let the recipient app to manage it correctly (e.g. visualizing the web page in its own view).
2. Url -> url of the link.
3. Options of the link:
a. Track -> you can track the open of the link.
b. Short -> you can “short” the link style service bit.ly. This may be useful to decrease the wieght og the payload of the push message.
4. Button to add another link.
5. Button to delete the defined link.
The tab “Custom data” has the same functioning of the tab “Links”. Here you can define some personalized variables to be sent to the application composed by a key and a value.
This section is composed by the following elements as you can see in figure 6:
1. Key -> key to identify the custom value (usable, for example, to manage the deep link).
2. Value to be sent.
3. Button to add another custom data.
4. Button to delete the defined custom data.
Il tab "Options Apple" is composed by the following elements as you can see in figure 7:
1. Badge -> number to be shown on the icon of the application
2. Sound -> personalized sound for the reception of this push message.
In the tab “Opzioni Google” you can define the name of the variable that contains the text of the push in the payload sent to Google (fig. 8).
Once defined the message of the push the next step is a summary and preview of the delivery (fig.9).
In this step you can visualize a preview almost real for all the users depending on the device. You can scroll the previews using the button panel below.
In the last step "Delivery Method" you can define the sending type and get a test delivery (fig. 10)
More in details, the mentioned page is composed by the following elements:
1. Test delivery -> Here you can get a test delivery to a test filter configured on this DB.
2. Real delivery -> you can define if duplicates must be eliminated during the sending to avoid more then a sending for every user.
3. Unique delivery -> allows you to set some options:
a. Create a single delivery.
b. Create a split delivery.
c. Create a recurring delivery.
Click on Finish to end the delivery. ATTENTION: in this phase you are not sending, but you are just finishing the creations of the push delivery. The real sending must be executed in the area"Communicate -> Manage deliveries push"