An app function can send users to a custom URL, send the iOS Push Registration message, or run another custom function you have set in your code. You'll generally use these immediately after a message or another action in a campaign.
For example, you might have a message asking the user to update their profile. When the user selects the OK button, an Open URL app function would deeplink them directly to their profile.
To use an app function, add a new action to your campaign and select App Function as the channel. You can also create an app function immediately after a user engages with a push, in-app, or app inbox message using the Open or Accept Actions in the message.
Next, you'll move to a new page where you can select a template. You can choose Open URL, Push Registration, App review request, or a custom function depending on what is set up in your app.
Select "Register for push" to create a push registration prompt for your iOS users.
The Push Registration prompt can only be sent to users once, so make sure you send it at the right time in your onboarding process or app experience. You can A/B test the timing of this message to see what is most effective.
Select Open URL to create an action that sends users to a specific URL. You can use this feature with deep links, and links can be customized with handlebars to include custom values like user attributes and events. See Personalize a message for more.
Determines when your App function will send. This is where you set your Action delivery and Display when trigger.
For chains of actions, you must receive the previous action to receive all following actions in a chain.
For app functions, this means that only users who interact with the app function (by tapping a push or accepting a message) can receive any following actions. To send another action regardless of whether the user clicked the push or message, create a new branch from the message above the App Function, not from the App Function itself.
See Sub-Delivery for more.
Updated 23 days ago