FeaturesHow it worksPricingDocsBlog
Sign inGet started

Win back the shoppers who almost bought.

Get startedChat on WhatsApp

Product

  • Features
  • How it works
  • Pricing

Resources

  • Docs
  • Blog
  • Recovery guide

Company

  • Careers
  • Support

Legal

  • Privacy
  • Terms
  • Data Deletion

© 2026 Nerja AI · Customer Intent & Retention

support@nerja.ai·+880 1886-157091

Chat on WhatsApp
  • Nerja AI documentation
  • Quick start
  • How Nerja works
  • Install the Nerja Tag
  • Events the tag detects
  • Tag JavaScript API
  • Privacy & consent
  • Mobile SDK overview
  • Get the SDK
  • Android SDK
  • iOS SDK
  • Push notifications setup
  • Push templates
  • Deep links: app or website
  • Connect email (AutoSend, Resend, Amazon SES)
  • Connect SMS (Twilio, BulkSMSBD)
  • Connect WhatsApp (WAAPI, Meta, Twilio)
  • Connect push (Firebase)
  • Campaign types
  • Delivery, open and click tracking
  • Signed user ids
  • Permissions explained
  • API reference
  • Store integrations
  • Troubleshooting
  • FAQ

Campaigns

Campaign types

Audience-based and event-based campaigns: when each runs, who receives it and how channels are chosen.

Audience based#

You choose one or more saved audiences (e.g. Cart Abandoned) or describe one in words. On launch, every reachable member gets the first step; the campaign is complete when the workflow has run for everyone.

// what

A fixed group at a point in time.

// why

Best for announcements, win-backs and promotions where you decide who and when.

Event based#

You choose one or more trigger events (Add To Cart, Checkout Abandonment, Purchase…). Whenever a shopper does that, they are enrolled and the workflow starts — an ongoing automation with no end date. A shopper is enrolled at most once every 7 days per campaign.

// what

A reaction to behaviour, as it happens.

// why

Best for recovery: the closer the message is to the moment of intent, the better it converts.

Channels and reachability#

ChannelNeedsIf the contact lacks it
EmailAn email address and a connected email providerSkipped for that person
SMS / WhatsAppA phone number and a connected providerSkipped for that person
PushAn active FCM token and Firebase connectedSkipped; a push-only audience with no tokens is refused at launch with an explanation

Workflow steps#

A workflow is a chain of send, wait and condition steps. The default for recovery is: send → wait (6 hours) → “customer engaged?” → if not, send a reminder. Wait durations are editable.

What happens at launch#

// Launch checks, in order
  1. 1Copy check

    every variable can be filled

  2. 2Providers

    each channel is connected

  3. 3Enrol

    reachable members only

  4. 4Safeguards

    daily cap · quiet hours · do-not-contact

  5. 5Send + track

    receipts, clicks, revenue

  1. Copy is checked — a variable Nerja cannot fill blocks the launch.
  2. Each selected channel must have a provider connected.
  3. Reachable members are enrolled; daily caps, quiet hours and do-not-contact lists apply at send time.

Prefer to talk it through? Book a 30-minute call with the Nerja team.

PreviousConnect push (Firebase)Next Delivery, open and click tracking

Something unclear or missing? Email support@nerja.ai and we will improve this page.

on this page

  • Audience based
  • Event based
  • Channels and reachability
  • Workflow steps
  • What happens at launch