We are adding a 'context' feature to our Flows API that will allow a flow to be triggered with personalised data. This substitutes the previous method of achieving events for target groups by being far more efficient and simpler.
For more detail on the API see: https://developers.agillic.com/apis/flows-api
For more detail on Contextual detail see: https://developers.agillic.com/apis/getting-started#contextual-data
New Version of the App Push Channel
With release 23.0 we are happy to announce our new and improved version of the App Push Channel. With this improved version of our App Push Channel customers can now faster than ever send push notifications out to their recipients. Furthermore it offers quick integration, better flexibility and improved time to market. The channel will be enabled for all instances.
Read more here: Understanding App Push
Firebase Data Notifications
Customers can now choose to send notifications to Firebase using the Data Message format rather than the default Notification Message format. The Data Message format allows customers to update content in the app without notifying the recipients, which means that app developers can build the app so that it responds to content from Agillic, without pushing anything visible to the recipients, or use locally stored data.
Read more here: Configuring the App Push channel
For more info on Firebase messaging concepts see here: https://firebase.google.com/docs/cloud-messaging/concept-options
It is not a given that recipients receive an App Push Notification. The Fallback Condition allows customers to let their recipients fall back receiving messages through other channels in case they do not receive the push notification.
Copy Changes for App Push
Early user feedback has indicated that when we refer to Android and iOS on the platform and our knowledge base, we are really talking about Firebase and APNS. Changes have been made to the UI to indicate whether the push provider is either Firebase or Android.