Triggers & Orchestration
Triggers extend AXO beyond the browser. When a behavioral condition is met – an abandoned cart, a first identification event, or a segment transition – AXO can fire a dynamic payload to any endpoint: an ESP (Klaviyo, Braze), an ad platform, a webhook, or a Slack channel.
Plays Catalog
Start from a pre-built play – Abandoned Cart Email, Browse Abandonment, Welcome New Customer, Conversion Pixel Fire, Segment Entry Notification – or build from scratch. Each play comes pre-wired with sensible defaults for timing, cooldown periods, and destination integrations.
Trigger Criteria
Trigger conditions use the same predicate tree model as custom Segments. You can combine behavioral events (add_to_cart, form_submit, conversion), session properties (page count, dwell, device), and CRM attributes. Set a cooldown (24h, 7d) to prevent over-messaging, and an ID type (email, external_id) to gate firing until a profile is identified.
Payload Templates
Each trigger has a dynamic payload template. Variables like {{profile.email}}, {{session.last_product_viewed}}, and {{segment.name}} are resolved at fire-time from the live profile and session context. The payload is sent to your configured destination integration (e.g., Klaviyo track event, Braze custom event, or a raw webhook URL).
Test Fire & History
Before enabling a trigger in production, use Test Fire to send a simulated payload with a real profile. Each trigger maintains a full fire history – timestamp, profile, payload sent, destination response code – accessible from the History button on the trigger row. Triggers evaluate every 1 minute on Vercel cron.
Chatbots & Agents
Triggers can also fire on-site: Admin → Chatbots & Agents configures floating conversational AI agents that appear on your storefront when their behavioral conditions are met. Agents adapt to your site theme, support full style customization, and are saved as web_agent triggers – so they share the same criteria, cooldown, and fire-history model as every other trigger.