Last updated November 13, 2026.
Push notification automation means your web push messages send themselves, based on a rule, a schedule or something a visitor does, instead of someone writing and sending each one by hand. In Aimtell there are three ways to set it up: welcome notifications that go out the moment someone subscribes, triggered notifications that respond to behavior like an abandoned cart, and API notifications that your own systems send. This guide covers how each one works as of November 2026, when to use it and how to set it up.
What is push notification automation?
Push notification automation is the practice of sending web push messages automatically, from rules, timing or push subscriber activity. You set a campaign up once, and it keeps sending to every push subscriber who meets the condition.
Automated notifications save your team from repeating the same sends every day. They also reach people at the moment that matters, like a few minutes after they leave a full cart, which a manual campaign cannot do.
1. Welcome notifications
Your welcome notification is often the first push a new push subscriber gets from you. It goes out automatically the moment a visitor opts in.
To set one up, open Welcome Notifications in your Aimtell dashboard. Enter the title, body, icon and destination URL, then switch the status on. Every new push subscriber gets it from then on, and it has its own conversion reporting so you can see what it earns.
A simple “Thanks for subscribing” works, but you can also use the welcome push to:
- Introduce your brand and say what kind of pushes to expect
- Offer a first order discount or another incentive
- Point new push subscribers to popular content or products
- Add up to two action buttons, each with its own link
Learn more in our welcome notification documentation.
2. Triggered notifications
Triggered notifications send a push when a push subscriber does something specific. Unlike a welcome push, which fires once, a triggered campaign can respond to almost any behavior you track.
Common triggers include:
- Cart abandonment. A shopper adds items and leaves without buying.
- Browse abandonment. A shopper spends time on a product page and leaves without adding it to the cart.
- Abandoned funnels. Someone reaches step one of a sequence, like a quote form, but never step two.
- Page views. A visitor views a specific page, such as a pricing or plan page.
- Custom events. Anything you track through our Custom Events API, from your site, your server, Zapier or ActiveCampaign.
On Shopify, WooCommerce and BigCommerce, Aimtell tracks add to cart, purchase, cart abandonment and browse abandonment for you, with no code.
Controls for triggered campaigns
- Time delay. Wait minutes, hours or days before the push sends.
- Multi-step drips. List several delays, such as 5 minutes, 25 minutes and 2 hours, and send a whole sequence from one trigger.
- Expire On Conversion. Cancel any steps still waiting as soon as the push subscriber converts.
- Segment targeting. Only send to people who are, or are not, in a segment.
- Event details in the message. Carry details like the plan name or the city they searched into the push.
- A/B testing. Test two versions of any step to see which performs better.
To track a custom event with JavaScript, add a call like this to your site:
_at.track("event", {
"category": "product",
"action": "viewed",
"label": "Premium Plan",
"value": 99
});
Then open Triggered Notifications in your dashboard and click New Triggered Notification. Enter the event category and action that should trigger it, matching what your code tracks. Fill in the title, body, destination URL, icon and optional action buttons, just as you would for a manual campaign.
See our triggered campaigns documentation for full setup steps.
3. API notifications
API notifications let your own systems send pushes, from your backend, your app or a third-party tool. They suit order updates, account alerts and anything else your code already knows about.
You can send an API notification to:
- One push subscriber by their subscriber UID
- Several push subscribers by passing up to 1,000 subscriber UIDs
- A whole segment by its segment ID
- A subscriber by alias, using your own username, user ID or email
Aliases link your existing user data to push subscribers. Add a tracking call like this to your site:
_at.track("alias", {
"user": "user_12345",
"email": "customer@example.com"
});
Once aliases are set, you can send to a user ID or email address through the API, and Aimtell finds the matching push subscriber. Here is a shipping update sent by alias:
curl -XPOST -H 'X-Authorization: YOUR_API_KEY' \
-H 'Content-type: application/json' \
-d '{
"idSite": "1234",
"title": "Your order has shipped",
"body": "Track your package now.",
"link": "https://yoursite.com/track/12345",
"alias": "user==user_12345"
}' \
'https://api.aimtell.com/prod/push'
Your backend, CRM or marketing tools can then send personal pushes without storing Aimtell subscriber UIDs. Learn more in our subscriber aliases documentation.
You can also send to a whole segment, which is useful for promotions and announcements:
curl -XPOST -H 'X-Authorization: YOUR_API_KEY' \
-H 'Content-type: application/json' \
-d '{
"idSite": "1234",
"title": "Flash sale",
"body": "50% off for the next 2 hours.",
"link": "https://yoursite.com/sale",
"segmentId": 5678
}' \
'https://api.aimtell.com/prod/push'
API notifications can be scheduled for a later time instead of sending right away. You can also send pushes from Zapier without writing code. Visit our API documentation to get started.
More automated notifications in Aimtell
Beyond the three main methods, a few other campaign types run on their own once you set them up.
- RSS campaigns. Point a campaign at your feed and every new post becomes a push. You can cap RSS pushes per hour or per day so a busy feed never floods anyone.
- Repeating campaigns. Send daily, weekly or monthly, with an optional end date.
- Shared campaigns. Share a manual, triggered or RSS campaign across all your sites. Each copy stays linked and reports its own results.
Delivery controls for automated notifications
Automated notifications work best when they arrive at a good time and not too often. These settings help:
- Timezone delivery. Send at the same local time in every push subscriber’s time zone.
- AI optimized delivery. Let Aimtell pick each push subscriber’s best time from their engagement history.
- Daily frequency cap. Limit how many pushes one person gets per day across manual, triggered and API sends.
- Expiring notifications. Let a time sensitive push expire after minutes, hours or days.
See the full list on our automation features page.
Choosing the right push notification automation method
- Welcome notifications: best for a good first impression with every new push subscriber.
- Triggered notifications: best for behavior-based messages, like abandoned cart drips and browse abandonment.
- API notifications: best for transactional messages and custom integrations.
Most stores start with a welcome push and an abandoned cart drip, then add the rest over time. For more campaign ideas, see our list of 10 ways to automate your web push notifications.
Get started
Log in to your Aimtell dashboard to set up welcome and triggered campaigns, or visit our developer portal to start with the API.
New to Aimtell? Start a free 14-day trial with no credit card required and set up your first automated notification today.



