Push subscription workflow

Case of use

For this case, we'll use a workflow with the following structure:



As you can see, any kind of contact can be part of the workflow, from those already in the data base to the ones that are added after the workflow is activated. When these contacts visit a page on our site, a popup will appear. It will contain a button to subscribe to push notifications. If the contact subscribes, Connectif will wait 5 minutes before showing the first push notification, which serves as a welcome.

Node "Start"

This node establishes which contacts will enter the flow. We'll only change the data source from the default setting, since the preferred option is "All existing and new".



Node "On page visit"

We'll only modify the limitation settings from this node. The configuration settings remain as they are by default, since the goal is to make the popup appear in any page of our site. Once we're in the limitations tab, we'll uncheck the "inactivate after trigger" option. Instead, we'll establish an inactivation for a interval of 1 day after the popup is shown. This way, we won't be intrusive in case the contact doesn't subscribe, but the popup won't disappear completely. 



Node "Send web content"

This node establishes the popup that will be use to attract the contacts to the subscription. The first step is to chose which popup we'll utilize.



In case we don't have any previous popup, we'll go to "create new content" and select "popup". In the next image, we'll see how to notify a subscription. You just have to add a "button link" element to the edit section, go to that element's settings and chose "ask for push subscription" in the highlighted part of the image. 



Since we don't have variables in this example, the last step will be to choose the moment in which the popup will appear. There are various options:

  • Immediate: the content appears as soon as the page gets loaded.
  • On leave page: the content appears when the cursor goes beyond the page limits. For example, the URL area or the tabs.
  • On scroll: the content appears when the contact scrolls down the page a specified percentage (20%, 50%).
  • On timeout: the content appears after the selected seconds have passed.
  • On activity timeout: the content appears if the contact doesn't register any activity (cursor movement or scroll) during the span of the seconds chosen.

It's also important to check the option "Show only if contact has not accepted or blocked Push Notifications yet". This means that the content will only appear to those who have never interacted with push notifications. That way, the content doesn't have to be shown to people who have already subscribed, which would be redundant.



Node "On push notification subscribed"

This node automatically triggers once the system detects that a contact has subscribed. It doesn't have any settings options since it's function is simple and it usually activates just one time, unlike other trigger nodes like "On page visit".


Node "Wait"

This node is optional, since it's purpose is just to not send the first push the moment the contact clicks the subscribe button. One of the main concerns of contacts about push notifications is receiving too many in short intervals. With a wait period, in this case 5 minutes, we reassure the contact about it. To set this node up, we mark the "A period of time" option and select 5 minutes. 


Node "Show push notification"

Finally, this node will send the first push notification to the contact. In this case, we'll assume that the contact will go through this workflow just once, so we'll establish a limitation of one activation for each contact. It doesn't have to be that way all the time, since it's possible that a contact unsubscribes and goes back to being subscribe in the future. But, for consistency's sake in regards to all the previously discussed nodes, we'll keep said limitation.

The setting of this node only has two steps. First, we'll select or create the push with Connectif's editor. After that, we can do mappings if any variable is in the push. In this example, our first push has the name variable, so we'll do the mapping accordingly to customize the push for each contact. 




Every node includes a tab named "Data" alongside "Configuration" and "Limitations". 



In this tab we can see the data that was compiled from all the previous nodes ("Incoming data"), and the data that the system will get from that particular node ("Outgoing data"). That means that, if we go to the "Start" node in any workflow, the incoming data section will be empty, since it's the first node of the workflow. All the other nodes will have incoming data, since at least that first node will provide information. 

This option is useful for whenever a user wants to check which data is coming through in the workflow.


Was this article helpful?
0 out of 0 found this helpful