Help CenterThis feature requires the latest BETA Player enabled.
In the blog post Engage users through automated in-app drip campaigns with walkthroughs we talk about drip campaigns and how businesses often use drip marketing to keep up with their audiences in a timely manner based on their audience’s behavior, how autolaunchers can help you automate your content for different use cases and ways to improve your product experience by adding more rules and conditions. The next step to create your own drip campaign with Inline Manual is to make use of the autolauncher campaign feature.
An autolauncher campaign will give you more flexibility and control over time delays. For example, if you have five new features to showcase, you might want to space out the announcements to let your users learn of each feature separately, this way they will have time to focus on one feature at a time, try it out and get confident using it, before learning about another feature. By adding the autolaunchers for each feature announcement to the campaign you can set up time restrictions to only display one announcement per day and login, with this set up a user will see an announcement the first time they login today, after 24h if that user logs in again the second announcement will be shown to them and so on.
How it works?
Autolaunchers that are part of a campaign allow setting an interval between the autolauncher and the previous autolauncher.
The Autolauncher in a campaign always plays only once after the set interval. This interval relates to the previous Autolauncher that is also part of a campaign. The interval is ignored if there is no previous Autolauncher in a campaign.
Let's see it in a few scenarios:
Scenario 1
Autolauncher 1 - part of Campaign - interval 24 hours - rules are matching
Autolauncher 2 - part of Campaign - interval 12 hours - rules are matching
Autolauncher 3 - part of Campaign - interval 24 hours - rules are matching
Users will first see Autolauncher 1 when they visit our application because the rules match. There is no Autolauncher in a campaign above it; therefore, the interval of 24 hours is ignored.
If they come back after 32 hours, the user will see Autolauncher 2; rules are matching, and 12 hours have already passed (we launched Autolauncher 1 32 hours ago).
If they visit again in 12 hours, nothing will launch for them because the interval between Autolauncher 2 and Autolauncher 3 was set to 24 hours.
Scenario 2 - not matching rules for Autolauncher 2
Autolauncher 1 - part of Campaign - interval 24 hours - rules are matching
Autolauncher 2 - part of Campaign - interval 12 hours - rules not matching
Autolauncher 3 - part of Campaign - interval 24 hours - rules are matching
Users will first see Autolauncher 1 when they visit our application because the rules match. There is no Autolauncher in a campaign above Autolauncher 1; therefore, the interval of 24 hours is ignored.
If they come back after 32 hours, the user will not see Autolauncher 2, as the rules are not matching. Inline Manual will stop evaluating any following Autolaunchers in a Campaign.
If they visit again in 12 hours and the rules still do not match, nothing will launch.
Scenario 3 - combination of normal Autolaunchers and Autolaunchers in a Campaign
Autolauncher 1 - part of Campaign - interval 24 hours - rules are matching
Autolauncher 2 - normal - rules are not matching
Autolauncher 3 - part of Campaign - interval 12 hours - rules not matching
Autolauncher 4 - normal - rules are matching
Autolauncher 5 - part of Campaign - interval 24 hours - rules are matching
As you have complete control over the order of the Autolaunchers, you can combine the normal Autolauncher with those in the Campaign.
Users will first see Autolauncher 1 when they visit our application because the rules match. There is no Autolauncher in a campaign above it; therefore, the interval of 24 hours is ignored.
If they visit another page after seeing Autolauncher 1, which triggers the check for Autolaunchers again, the Autolauncher 2 won't launch as it does not match the rules. The Autolauncher 3 won't launch either, as the interval between Autolauncher 1 and Autolauncher 2 is not yet 12 hours. The Autolauncher 4 will launch, as it is a normal Autolauncher, and the rules match. Lastly, Autolauncher 5 won't launch either because Autolauncher 3 has not yet launched.
Conclusion
The Autolaunchers that are part of a Campaign are "connected" to each other with the intervals, which allows you to distribute the content in time. For example, not bombarding your users with features announcement with every page load. But you can still combine the other Autolaunchers, giving it a priority based on the order you set in Site > Automation and rules.