Marketing automation
Define what to send, when and on which channel, then let user actions or segment membership start the flow. Anti-spam rules and grace periods keep every user from being over-messaged.
Reviewed:
AppBoost Marketing Automation is the rules and journeys engine for marketing and product teams who want behavior-based messages without manual sends. You define messages, channels and grace periods once, then start them from an SDK trigger point, a REST API call or automatic segment membership, across push, email, SMS and web push.
The problem
Abandoned carts, missed onboarding and lapsed buyers need a message within hours, not at the next campaign meeting. Marketing Automation sends them from rules you define once, and stops when the user acts.
Capabilities
Send behavior-based communication when a user performs an action in your app, over push, web push, email or SMS, using rules created in the dashboard.
A rule lists each message with its title, channel, content, URL and grace period. Send a push after one hour and an email after 24 hours in the same sequence.
Set the delay between messages in hours, and use different delays for different channels so each message arrives at the point where it is most likely to convert.
When a user taps the call to action in the first message received on any channel, the automation stops sending the same content on the other channels.
The same message is never sent to the same user twice per day for the same event, even if the trigger fires repeatedly, and this applies across channels.
Users enter and leave a journey automatically when they match a customer segment. Use it for onboarding, first-purchase nudges, purchase rewards and birthday offers.
Call fireAutomator() from the AppBoost SDK with a trigger point name and optional personalization data, or start automation from your backend through the REST API.
Follow delivery, open, click-through and conversion results for each automation, with automator events recorded for each user.
How it works
For journeys, define the user criteria that should start the flow, such as installed for N days with no purchase.
In the dashboard, list each message with its channel, content, destination URL and grace period in hours.
Fire the rule from the SDK with fireAutomator(), from your backend through the REST API, or let segment membership start a journey.
Pass key-value data with the trigger so messages carry the cart, product or offer details for that user.
Review delivery, open, click-through and conversion for each automation, then adjust content and grace periods.
Who it is for
Build lifecycle programs once and let them run, while the anti-spam and stop-on-click rules protect the customer experience.
Connect in-app moments to messages with a single SDK call, and keep server-side logic in your own backend when you need it.
Use cases
Fire a trigger point when a cart is left, send a push after one hour and an email after 24 hours, and stop if the user opens the cart.
Send welcome messages over push, email and SMS with 2, 24 and 48 hour gaps to teach new users the key features.
Target users who installed the app N days ago and have not purchased, and nudge them toward the first order.
Send an automated discount code to customers on their birthday through a journey.
Frequently asked questions
Learn more
Step-by-step guides on docs.appgain.io
Articles from the Appgain blog
Related products
Talk to the AppBoost team about which lifecycle journeys to launch first.