Rule Templates
Browse all Apphud rule templates — Manual, Event-triggered, and Scheduled. Each template pre-fills a trigger, default push, and in-app action shape; the most common ones link to detailed guides with use cases.
Rule templates pre-fill a new Rule with a trigger, a default English push, and an in-app action shape. You can rename the rule, change triggers, edit the push, and swap audience after creation.
Open the Templates tab on the Rules page to browse them. Click any template card to open a Draft you can configure.
Manual templates
Fire only when you press Trigger now on the rule detail page.
| Template | What it does | Default push (English) |
|---|---|---|
| Manual rule | Generic blank Manual rule. Fully editable. | "Hello there! / We have an important update for you. Please take a look." |
| Auto-redirect to URL | When fired, opens the URL you set. No screen, no other action. | "We have an important update for you! / Please take a look." |
| Auto-redirect to App Store | When fired, redirects users to the App Store page you set. Useful for cross-marketing. | (no default — configure in the push tab) |
| Screen with URL button | Shows a screen with title, description, and an Open link button to your URL. | (no default — configure in the screen editor) |
| In-app message screen | Shows a custom in-app message. | "Hello there! / We have an important update for you. Please take a look." |
Event-triggered templates
Fire automatically when matching events occur for a user.
| Template | Trigger | Detailed guide |
|---|---|---|
| New subscriber welcome | trial_started, intro_started, subscription_started | — |
| Cancellation survey | trial_canceled, subscription_canceled | Get Cancellation Insights |
| Get cancellation feedbacks | trial_canceled, subscription_canceled | Get Cancellation Insights |
| Win back lost subscribers | trial_canceled, subscription_canceled | Win Back Lost Subscribers |
| Billing issue notification | billing_issue | Reduce Involuntary Churn |
| Refund requested feedback | refund_requested | — |
| App reinstalled welcome | app_reinstalled | — |
| Abandoned checkout | paywall_checkout_initiated | Abandoned checkout |
| Payment error notification | paywall_payment_error | Payment error notification |
Abandoned checkout
Offers a discount to a user who started a purchase on a paywall but didn't complete it.
- Trigger:
paywall_checkout_initiated. - Audience: Non-paying users.
- Timing: With delay =
3600seconds (1 hour). Limit: Just once per each user. - Push: Title: "Still thinking? 🎁" Text: "Finish your purchase today and save with a personal discount."
- Before you start: the push mentions a discount, but the template doesn't set one up. If you offer an Apple promotional offer, prepare the promotional offer and In-App Purchase Key first.
- In-app action: not present by default. The push promises a discount, so show one: choose a Built-in Screen with a promo offer screen (see Built-in Screens), or a Paywall model pointing to a paywall with discounted products.
Payment error notification
Asks a user to try again when a purchase fails on the paywall. Failed subscription renewals are not included: for those, use Billing issue notification.
- Trigger:
paywall_payment_error. - Audience: Non-paying users.
- Timing: With delay =
60seconds. Limit: Just once per each user. Choose Unlimited times per each user if you want a nudge after every failed payment. - Push: Title: "Let's try that again" Text: "Your purchase wasn't completed. Tap to finish it, it only takes a moment."
- In-app action: not present by default. Choose a Paywall model (for example, a Figma paywall) or a Built-in Screen. A paywall opens only with its screen attached in Apphud: without it, the rule only fires the SDK callback.
- Keep the price consistent: by default the push only asks the user to try again and doesn't mention a discount, so the user expects the same purchase at the same price. The paywall you attach is set in the rule and may offer a different set of products than the one the user saw (for example, in onboarding). Make sure its prices are comparable to what the user saw. If the price is lower, say so in the push text.
Scheduled templates
Fire on date / time. Schedule configured in the rule's Configuration tab.
| Template | What it does |
|---|---|
| Scheduled Rule (One time) | Sends a push at a specific date and time. |
| Scheduled Rule (Repeating) | Sends a push on selected days of the week at a specific time. |
When to pick a template
- Use a template when its trigger matches your need — it saves time on setting up triggers and the default push.
- Use Manual rule (under Manual templates) when none of the event-triggered templates fit and you want to fire the rule yourself.
- Use a Scheduled template for time-based campaigns (announcements, daily reminders).
For the mechanics shared across every rule — Configuration tabs, lifecycle, Test, Archive, push notification per locale, in-app action types — see Rules.
Updated 14 days ago
