Success and Failure Actions
Configure custom behaviors after purchase or restore actions complete.
Overview
Success and Failure Actions allow you to define custom behaviors that occur after a purchase or restore action completes in your No-Code screens.
By default:
- On Success: The screen closes (
Close All) - On Failure: Nothing happens, the user stays on the screen (
None)
With custom Success/Failure Actions, you can override these defaults to create more engaging user experiences.
Available Actions
The following actions can be configured as Success or Failure handlers:
| Action | Description |
|---|---|
| None | Do nothing, stay on the current screen |
| Close | Close the current screen only |
| Close All | Close all No-Code screens |
| Navigate | Navigate to another No-Code screen |
| Open URL | Open a URL in the browser |
| Deep Link | Open a deep link in your app |
| Go to Page | Navigate to another page within a multi-page screen |
Supported Actions
Success and Failure handlers can be configured for the following actions:
- Make Purchase β triggered when a user initiates a product purchase
- Restore β triggered when a user restores previous purchases
Platform-Specific Configuration
When Platform-Specific Actions is enabled, you can configure different Success/Failure behaviors for iOS and Android platforms independently.
Minimum SDK Versions
Success and Failure Actions require the following minimum SDK versions:
| Platform | Minimum Version |
|---|---|
| iOS | 6.5.0 |
| Android | No-Codes 1.5.0 |
| Flutter | coming soon |
| React Native | coming soon |
| Unity | coming soon |
| Cordova | coming soon |
| Capacitor | coming soon |
NoteIf you're using an older SDK version, the default behavior will be applied:
- Success: Close all screens
- Failure: Stay on the screen
Configuration
To configure Success/Failure Actions in the No-Code Builder:
- Select a component with a Make Purchase or Restore action
- In the Action section of the right sidebar, you'll see:
- On Success β action to execute after successful completion
- On Failure β action to execute after failure
- Select the desired action for each case
- If the action requires a value (e.g., URL, screen ID), enter it in the corresponding field
Best Practices
- Success Actions: Consider navigating to a thank-you screen or closing all screens to return users to your app
- Failure Actions: Keep users on the screen (
None) so they can retry, or navigate to a help/support screen - Platform Differences: Use platform-specific actions when iOS and Android require different post-purchase flows
Updated about 2 hours ago
