Skip to content
Features · 5 min read

Push automations: welcome series and follow-ups

The moment someone subscribes is when they’re most interested. An automation says hello right away and follows up at the right time — while you do nothing.

Updated By the Pusharoo team
In short
  • Pusharoo automations can start when someone subscribes, does a custom event, gets a tag, clicks a notification or goes quiet for N days.
  • Add a welcome (0 delay) plus as many follow-ups as you like — minutes, hours or days later.
  • Pause or edit any time; each step shows sent, expired and clicked.
  • Unlimited automations, no plan gate.

A simple, effective sequence

A welcome automation timelineSubscribe at minute zero triggers a welcome message immediately, a follow-up after one day and another after seven days.Subscribes · 0 min🎉 Thanks for subscribing!Follow-up · +1 day⭐ Our most-loved picksNudge · +7 days🎁 A little something for you…add as many steps as you likeA welcome automation timelineSubscribe at minute zero triggers a welcome message immediately, a follow-up after one day and another after seven days.Subscribes · 0 min🎉 Thanks for subscribing!Follow-up · +1 day⭐ Our most-loved picksNudge · +7 days🎁 A little something for you
Triggered by a new subscription. Pause or edit the sequence any time.
  1. Welcome (immediately) — confirm they’re in and what to expect.
  2. Day 1 — your best content or bestsellers.
  3. Day 7 — a small thank-you: an offer, a guide, early access.

Welcome copy that sets expectations

nowYou’re in! 🎉We’ll ping you about deals 1–2× a week. Tap to see this week’s picks.

A welcome also proves delivery works on that device — a useful test for you.

Rules of thumb

  • Keep sequences short: three to five steps.
  • Every step needs a link worth tapping.
  • Don’t stack an automation step and a big campaign on the same hour.
  • Review click rates per step after a few weeks and cut the weakest.

Beyond the welcome series

Need other triggers (an order, a form, a cart)? Use webhooks and the JavaScript API to connect Pusharoo to your own systems, and pair with segments like “joined in the last 7 days”.

Sequences by site type

SiteWelcomeDay 1–3Day 7+
Online store“You’re in — here’s what’s new”BestsellersSmall subscriber-only offer
Blog / publisher“Thanks! Start with our top 3 posts”Most-read articleNewsletter or series
SaaS / app“Notifications are on”Getting-started tipFeature you’re proud of
Local business“Thanks for following”Hours, booking linkSeasonal special

All five triggers, with ideas

TriggerExample automation
Someone subscribesWelcome → bestsellers on day 1 → small thank-you on day 7 (welcome guide)
A custom event happensadded_to_cart → wait 1 hour → reminder, stop if purchase
A tag is setplan=trial → day 3 tip → day 10 “trial ends soon”
A click on any notificationClicked a sale alert → 2 days later, related collection
Subscriber goes quiet for N days45 days inactive → “new since your last visit” (win-back guide)

Stop conditions keep automations polite

The most common automation mistake is sending a reminder to someone who already did the thing. Add Stop if event to any sequence where that can happen: purchase for cart reminders, subscribed_paid for trial nudges, registered for event reminders. Events can come from the page (Pusharoo.track('purchase')) or your server (POST /api/v1/events), and events sent before someone subscribes are queued in the browser, so nothing is lost.

Automations and campaigns together

Automations run continuously in the background while you send regular campaigns. To avoid double-messaging, exclude people who are mid-sequence from big campaigns using a segment such as “joined in the last 7 days”, and don’t schedule a campaign in the same hour as a common automation step. Review each step’s targeted, delivered, clicks and CTR monthly and cut steps that underperform.

How to judge an automation

Look at click-through per step. If a step’s clicks fall well below your campaign average, rewrite it or remove it. Expired counts tell you how many subscriptions died between steps — usually small for short sequences.

Questions

What triggers a Pusharoo automation?

Five triggers: someone subscribes, a custom event happens (Pusharoo.track or the REST API), a tag is set, a click on any notification, or a subscriber going quiet for N days. Each step can wait minutes, hours or days, and a “stop if event” condition cancels waiting steps.

Can I pause an automation?

Yes. Pause or edit any time from the dashboard.

Can automations send at a subscriber’s local time?

Steps run after the wait you set; for local-time sends use timezone-filtered segments with scheduled campaigns, or choose waits that land at reasonable hours.

What is a “stop if event” condition?

A rule that cancels the remaining steps for a subscriber when a chosen event arrives — for example purchase cancels a waiting cart reminder.

More in Features: White-label push notifications: your brand, not ours · Rich push notifications: images, icons and buttons · All guides

Free for life. No limits.

Unlimited subscribers, campaigns and automations. No badges. About five minutes to install.