🚧 Testing Automation Make sure you have set the environment to Sandbox when testing Automated Push Notifications.
Do not forget to remove this setting for the production build.
Automation Delegate
Using the Automation Delegate, you can handle callbacks from Qonversion No-code Screens or Automated Notifications and adjust their behaviour.Set Automation delegate
To override default logic or handle callbacks, call thesetDelegate SDK method and implement the following functions.
Flutter
React Native
Unity
Implement AutomationsDelegate functions
1. Controller for navigation (optional to implement)
This function will return a controller for IOS navigation and context for Android screen intent.Flutter
React Native
Unity
2. Automation callbacks (optional to implement)
You can handle the function that notifies you that a No-code screen is shown. You can do additional logic or track an event here:Flutter
React Native
Unity
2.1. Start:
Flutter
React Native
Unity
2.2. Fail
Flutter
React Native
Unity
2.3. Finish
You can use this function to get information if a user launches a purchase within the No-code screens flow. In this case, you need to check the user’s entitlements (‘checkEntitlements’) to unlock access to your app’s premium content.Flutter
React Native
Unity
2.4. Automations finished
This function is called after a No-code screen is closed.Flutter
React Native
Unity
3. Automated push notifications events (optional to implement)
This function lets you identify the event type that triggered the push notification. Override this method and return false if you want to handle the corresponding push notification click by yourself. Otherwise, Qonversion handles the event and shows linked No-code screen (if configured). If you want to handle push notification’s click result and show your screen, you need to process the Automation event, check the event type, and show the required screen. Learn more with Handling Qonversion Notifications guide.Swift
Objective-C
Kotlin
Java
Flutter
React Native
Unity