What types of push campaigns can you run with Aimtell?

Updated

Aimtell supports two broad categories of web push campaigns: one-off campaigns you write and send (or schedule) yourself, and automated campaigns that fire on their own from a trigger — a new subscriber, a site event, an RSS post, or an API call. Which one you use depends on whether the message is tied to a moment in time (a sale, a launch) or to something a visitor does (abandoning a cart, subscribing, reading a new post).

One-off campaigns

Use these when the message is about you — a flash sale, a product launch, a big announcement.

  • Write the push, choose the audience segment, then send immediately or schedule it for an exact date and time.
  • Scheduling respects each subscriber's time zone, so a "Fri, Nov 27 at 9:00 AM" send arrives at 9:00 AM locally rather than at one global moment.
  • Example from Aimtell's own demo: a weekend flash sale scheduled for Friday morning, sent only to subscribers who viewed a product in the last 30 days, with the message "40% off everything, this weekend only."

This is the right choice when the trigger is a calendar date or a business decision, not visitor behavior.

Automated campaigns

Use these when the message should be tied to what a subscriber does or what your systems produce. Aimtell lists four automation types:

Automation Trigger Typical use
Welcome series A visitor grants push permission Greet every new subscriber while you're still on their mind
Event triggered A tracked event occurs, e.g. added_to_cart or an abandoned form Cart recovery, form-completion nudges
RSS triggered A new post appears in your feed Every new article goes out with no campaign to build
API triggered A call from a system you already run Back in stock, price drop, shipment out for delivery

Two details matter for the event-triggered type. First, Aimtell re-checks that the subscriber still qualifies before sending — so a cart-recovery push doesn't go out to someone who already completed the purchase in the meantime. Second, automations can include a wait step: the demo flow is "Event is added_to_cart → wait 4 hours → send," which is what makes it a recovery message rather than an instant reaction.

How to choose

  • Time-based message, decided by you → one-off campaign, sent now or scheduled.
  • Behavior-based message, decided by the subscriber → event-triggered automation.
  • Onboarding a new subscriber → welcome series.
  • Publishing on a regular cadence → RSS-triggered.
  • Message originates in another system (inventory, shipping, pricing) → API-triggered.

The two categories aren't exclusive — most accounts run scheduled promos alongside at least one automation, since the automation keeps working between one-off sends.

What you need before either works

Both campaign types depend on the same audience data, collected after a visitor grants permission in a single click — no email or form required. Aimtell records pageviews, geolocation (country, region, city), device and browser, plus any custom attributes and custom events you track. Segments are built from these: for example, "Country is United States AND viewed /pricing within 7 days AND no purchase event," which in Aimtell's demo resolves to 18,402 subscribers. A one-off campaign and an automation draw on the same segment builder, so the targeting work carries over between them.

Aimtell offers a 14-day free trial with no credit card required; check the pricing page for current plan details before committing to a send volume.