简体中文
English
Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is Aimtell?
Aimtell is a web push notification platform for reaching people who have already visited a website, without collecting an email address. A visitor grants permission in one click, and from then on Aimtell can send browser notifications to their desktop or mobile browser — the page evidence names Chrome, Safari and Firefox. It is aimed at ecommerce stores, SaaS products and publishers that want to bring casual visitors back rather than build a mailing list.
What it actually does
The core idea is that a subscriber is more than a browser token. According to the page, Aimtell records each subscriber's pageviews, geolocation (country, region, city), device and browser, plus custom attributes you pass in (for example plan or cart value) and custom events (purchase, form completed, video watched). Those become the basis for segments — the page's own example is "Country is United States and Viewed /pricing within 7 days and No purchase event."
Sending comes in two modes:
- One-off campaigns — a flash sale, launch or announcement, sent immediately or scheduled to an exact date and time.
- Automations — a welcome series for new subscribers, event-triggered messages (abandoned cart, abandoned form), RSS-triggered sends for every new post, and API-triggered sends for things like back-in-stock or shipping updates.
The claimed reach is 30,000+ sites, and there is a 14-day free trial with no credit card required.
Who it suits, and the trade-off
Aimtell fits a store or content site that gets traffic but converts little of it, and wants a re-engagement channel that does not depend on email capture. A concrete case: someone browses a product, adds it to cart, and leaves. An event-triggered push can follow up hours later with a reminder, and the page shows exactly that pattern.
The trade-off is permission. Push notifications are opt-in at the browser level, so your audience is only as large as the number of people who click "allow" — and browsers and users can revoke it. It is a complement to email, not a replacement, because you cannot reach someone who never subscribed.
If you want to judge fit quickly, check the pricing page for subscriber-tier limits against your current traffic, then run the free trial on one high-intent flow — cart recovery or a welcome push — and measure click-through before rolling it out site-wide.
How does Aimtell collect subscribers without requiring an email address?
Aimtell collects subscribers through browser-level push permission, not through email capture. When a visitor lands on your site, they see a prompt asking them to allow notifications. If they click "Allow," they become a subscriber immediately — no form, no email field, no name. From that point, Aimtell can identify that browser and associate activity with it.
What gets attached to a subscriber
Once permission is granted, the subscriber record can include:
- Pageviews — every page seen, how recently, and how often
- Geolocation — country, region, and city, refreshed on each return visit
- Device information — mobile or desktop, operating system, browser type
- Custom attributes — traits you already track, such as plan name or cart value
- Custom events — actions like purchase, form completed, or video watched
The page evidence illustrates this with a sample subscriber: a visitor in Austin, Texas on desktop macOS/Chrome, with 14 pageviews across 3 visits, events for added_to_cart and viewed_pricing, and attributes for plan: trial and cart_value: 148 — all collected without an email address.
Why this matters in practice
Email capture creates friction: the visitor has to type something, trust you with it, and often confirm. Push permission is one click. That lower barrier means you can build a larger list faster, but the trade-off is that the relationship lives in the browser. If someone clears their browser data, switches devices, or uses a different browser, that subscriber identity does not follow them the way an email address would.
A concrete scenario
Imagine a SaaS site with a pricing page. A visitor browses three pages, views /pricing, then leaves without signing up. With email-only capture, you have nothing. With Aimtell, if they granted permission, you can segment them as "Viewed /pricing within 7 days and No purchase event" and send a follow-up push later — as the page evidence shows with its example segment of 18,402 subscribers.
Next step
Decide whether your audience is more likely to accept a browser prompt than fill out a form. If you run a content site, ecommerce store, or web app where visitors return often, push can complement email rather than replace it. Set up a test: add the permission prompt, let it run for two weeks, and compare subscriber growth against your email capture rate. If you want to see how the platform handles segmentation and automation, review the setup flow at Aimtell.
What can I do with the custom attributes and events that Aimtell tracks?
Custom attributes and custom events are the two ways you turn anonymous push subscribers into segments you can actually act on. Attributes describe a subscriber as a person or account; events record something they did. Together they let you target by state rather than by guesswork.
Custom attributes
Attributes are traits you already store elsewhere — the page lists examples such as name, plan and lifetime value. Once attached to a subscriber, they become filter conditions: everyone on a trial plan, everyone above a certain cart value, everyone whose plan changed this month. The practical value is that a push can reference the trait, so a message can speak to plan level or spend tier without you maintaining separate lists.
Custom events
Events are actions worth responding to — purchase, form completed, video watched, and similar. Aimtell also records standard browsing data automatically (pages viewed, geolocation, device and browser), so custom events are for the things only your own tracking knows about.
What this looks like in practice
A segment can combine both, for example: country is United States and viewed a pricing page within 7 days and no purchase event. That is the same logic the page shows in its segment example. From there:
- One-off sends — a flash sale or launch aimed only at subscribers who viewed a product in the last 30 days.
- Event-triggered automations — an abandoned cart or abandoned form message; the page notes Aimtell re-checks that the subscriber still qualifies before sending, which avoids firing at someone who already converted.
- Attribute-driven personalisation — plan, cart value or lifetime value used to pick who gets which offer.
Trade-offs to weigh
The more attributes and events you push in, the sharper the targeting — but also the more your site's tracking has to be correct, and the more segments you have to maintain. Start with two or three events that map to real revenue moments (cart abandonment, pricing page visits, purchases) and a couple of attributes you already trust, rather than mirroring your entire data model.
A concrete next step: list the five actions on your site that most often precede a sale, check which of them you can already fire as events, and build one segment around the strongest one. If you want to see how this fits alongside other channels, Aimtell covers the mechanics, and it is worth comparing against a broader engagement tool such as Klaviyo if email and SMS are also in your stack.
How do I set up an automated push notification campaign in Aimtell?
Aimtell's automation is built around a trigger plus a message. You pick what should start the campaign — a new subscriber, a site event, an RSS post or an API call — then define who qualifies and what they receive. The page describes this as "send a promo today, or automate it for good," and lists four automation types: welcome series, event triggered, RSS triggered and API triggered.
The four automation types
| Type | Fires when | Typical use |
|---|---|---|
| Welcome series | Someone opts in | Greet new subscribers while attention is fresh |
| Event triggered | A tracked event occurs, such as added_to_cart or a form submission |
Cart or form abandonment recovery |
| RSS triggered | A new item appears in your feed | Publish every new post automatically |
| API triggered | Your own systems call the API | Back-in-stock, price drop, shipment updates |
For event-triggered campaigns, the page notes that Aimtell re-checks whether the subscriber still qualifies before sending. That matters for cart recovery: a four-hour wait followed by a qualification check avoids nudging someone who already bought.
A practical cart-recovery setup
The page's own illustrated example is a useful template:
- Trigger: event is
added_to_cart - Wait: 4 hours
- Message: a reminder about the item left behind
- Audience filter: viewed a product in the last 30 days, or no purchase event
The same pattern works for a welcome series with no wait, or an RSS campaign with no audience build at all.
What you need before you start
Automation quality depends on the data you collect. Aimtell captures pageviews, geolocation, device and browser, plus custom attributes and custom events you already track — plan, cart value, lifetime value. Segments combine these with AND logic, for example: country is United States, viewed /pricing within 7 days, and no purchase event.
Two setup decisions follow from that:
- Define your events first. Cart recovery only works if
added_to_cartand a purchase event are both firing. Decide what counts as conversion before you build the automation. - Keep segments narrow enough to be relevant. A welcome push to everyone is fine; a price-drop push should target people who viewed that product.
Next step
Start with one automation, not four. A welcome series is the easiest to verify end to end: opt in on your own site, confirm the push arrives, then check that the subscriber shows the expected attributes. Once that loop works, add event-triggered cart recovery using the wait-and-qualify pattern above.
If you want the mechanics of permission and browser coverage before building, Aimtell's own site covers the opt-in flow at Aimtell. For general background on how web push works across browsers, the MDN documentation at MDN Web Docs is a reliable reference.
What are the pricing options and free trial terms for Aimtell?
Aimtell advertises a 14-day free trial with no credit card required, and it publishes a dedicated pricing page rather than only a sales-contact form. The page's own framing is "Start free trial / Talk to us," which suggests the trial is the standard entry point and that higher-volume or custom needs are handled through a conversation. Specific plan tiers and rates are not stated in the supplied page material, so check Aimtell directly for current numbers before budgeting.
How to evaluate the trial against your actual use
A 14-day window is enough to test the core loop — permission prompt, segmentation, and one automated send — but usually not enough to judge long-run deliverability or subscriber growth. Treat it as a functional test, not a revenue test.
- Confirm what counts as a subscriber. Push pricing commonly scales with audience size, so ask whether unsubscribed or expired-permission browsers still count.
- Check campaign or send limits. If one-off and automated pushes draw on the same allowance, a welcome series plus an RSS feed can consume it faster than expected.
- Verify the trial's end behavior. "No credit card required" implies no automatic charge, but confirm whether data and segments survive if you don't convert.
A concrete first-week test
Pick one segment you can already identify — for example, visitors who viewed a product page in the last 30 days but never purchased — and run a single scheduled campaign plus one event-triggered cart recovery. That exercises both the manual and automated paths the product describes, and tells you whether the segment builder matches the attributes you actually track. If your stack already fires events like added_to_cart, the API-triggered option is the one worth stress-testing, since it depends on your systems rather than Aimtell's scheduler.
If your goal is simply comparing entry costs, look at Aimtell's pricing page alongside one or two comparable web push tools and compare the subscriber-count bands, not the headline trial length.
Can Aimtell send notifications triggered by RSS feeds or external APIs?
Yes. Aimtell supports both RSS-triggered and API-triggered notifications, alongside one-off campaigns and event-based automations. That means you can let a new blog post go out on its own, or fire a push from an existing system when something changes.
What each trigger is good for
| Trigger | Fires when | Typical use |
|---|---|---|
| One-off campaign | You send or schedule it | Flash sale, launch, announcement |
| Welcome series | A visitor subscribes | Greeting new subscribers immediately |
| Event triggered | A tracked event occurs | Abandoned cart or form, with a qualification check before sending |
| RSS triggered | A new item appears in your feed | Publishing every new post with no campaign to build |
| API triggered | Your own system calls the API | Back in stock, price drop, shipment out for delivery |
Choosing between them
RSS is the low-effort option: point Aimtell at a feed and every new item sends automatically, which suits blogs, news and content sites where the publishing rhythm is already the trigger. The trade-off is limited control — you are sending whatever the feed produces, so a draft, a minor edit or a feed glitch can become a notification unless you gate the feed.
API triggering is the opposite: more setup, but you decide exactly what deserves a push. It fits teams that already run commerce or logistics systems, because the event that matters (a restock, a price change, a dispatch) already exists in their own software. Event-triggered automations sit between the two, since Aimtell checks the subscriber still qualifies before sending — useful for cart recovery, where a purchase in the meantime should cancel the message.
A practical sequence for a small store: start with an RSS feed for the blog and one event automation for abandoned carts, then add API triggers only for the events your team already tracks reliably. Aimtell's own page describes a 14-day free trial with no credit card required, so a pilot can be run on real traffic before committing.
Amazon Route 53
Vercel
Google Workspace
User reviews (0)