Trigger-based emails fire the instant a subscriber takes action — browse abandonment, cart abandonment, purchase, link click, birthday, inactivity — sending the most relevant message at the exact moment of highest intent, automatically.
Trigger-based emails outperform broadcast campaigns by 8× because they are sent at the exact moment a subscriber is thinking about your product. Migomail fires these emails within 90 seconds of the triggering event — before the moment passes.
When a subscriber's triggering event fires — a cart abandonment, a link click, a purchase, a form submission — Migomail processes the event and dispatches the triggered email within 90 seconds. There is no batch processing, no scheduled job, and no manual review. Events fire instantly, emails follow in under two minutes.
Fire triggered emails when a subscriber adds items to a cart and leaves without completing purchase, or browses a product page without adding to cart. Native Shopify and WooCommerce integrations push these events in real time — no pixel, no custom code required. The triggered email contains the exact products from the cart or browse session.
Send a triggered email when a subscriber clicks a specific link in any email campaign — pricing page, feature comparison, signup CTA — or when they visit a specific page on your website via the Migomail tracking pixel. High-intent clicks are the strongest purchase signals in email marketing; trigger emails on them within 90 seconds.
Fire triggered sequences on any ecommerce purchase event — first order, repeat order, high-value order, specific product purchase, or order from a specific category. Post-purchase triggers include order confirmation, shipping notification, delivery confirmation, review request, and cross-sell recommendation — each fired at the right time in the fulfilment flow.
Trigger re-engagement emails when a subscriber has not opened or clicked in a defined window — 30 days, 60 days, 90 days — or when a previously active subscriber goes quiet after a purchase. Inactivity triggers catch subscribers before they permanently churn, reaching them at the inflection point when a win-back attempt is most likely to succeed.
Trigger emails on changes to subscriber profile data or lifecycle stage — subscription upgrade, plan downgrade, trial expiry approaching, annual renewal due, loyalty tier change, or any custom field value change synced from your CRM. These lifecycle moment triggers deliver the exact right message at the exact right business moment.
Fire triggered emails on subscriber-specific dates — birthday, join anniversary, product purchase anniversary, custom date fields, and subscription renewal dates. Date triggers calculate the send date per subscriber individually and fire at the optimal time in the subscriber's local timezone — not at a fixed global time.
Fire any trigger email from your own application by sending a custom event to the Migomail Events API — a payment processed, a support ticket resolved, a feature milestone reached, a contract signed, or any application-specific event that represents a moment worth responding to. Triggered emails from custom events support full merge variable personalisation from the event payload.
Every trigger-based email tells a real-time story — a subscriber takes an action, Migomail detects it, the right email fires, and revenue follows. Here is how three of the highest-performing triggers work in practice.
Every subscriber action worth responding to is available as a trigger. Browse the full catalogue of trigger events below — each one can activate an instant single email, a multi-step triggered sequence, or a branch in a larger automation workflow.
Real-time events from your Shopify or WooCommerce store.
Actions subscribers take with your emails and website.
Triggers that fire when subscribers stop engaging.
Calendar-based and lifecycle date triggers.
Triggers on changes to subscriber profile and account status.
Fire any trigger from your own application via the Events API.
The most common mistake with trigger emails is not building them at all. The second most common is building them and sending them too late. This is what timing actually does to performance.
Purchase intent is a perishable asset. When a subscriber abandons their cart, their intent to buy peaks at the moment of abandonment and declines rapidly over the following hours — they get distracted, find a competitor, or simply forget. An email sent 1 hour after abandonment intercepts that intent while it is still at 80–90% of peak. The same email sent 24 hours later arrives when intent has already declined to 30–40%.
Setting up a trigger email in Migomail takes under 30 minutes for most trigger types. The system runs automatically from that point — no ongoing management required.
Not all trigger types are equal. These are the 8 highest-revenue trigger email types ranked by average revenue per send across Migomail ecommerce and SaaS accounts — so you know exactly where to start.
Data from Migomail customer accounts · ecommerce and SaaS · 2024–2025 · averages across accounts with 3+ months of trigger email data.
Feedback from ecommerce operators, SaaS marketers, and growth leads who use Migomail trigger emails to respond to subscriber actions in real time.
We were sending cart abandonment emails manually — someone on the team would check abandoned carts at the end of each day and batch-send a reminder. The emails were going out 18–24 hours after abandonment. Our recovery rate was 2.1%. When we switched to Migomail's 1-hour trigger, our recovery rate jumped to 13.8% in the first month. Same email, same offer, same product — just sent at the moment when the subscriber still cared. The timing difference alone was worth changing platforms.
The pricing page visitor trigger changed our entire sales process. When a trial user visits our pricing page, Migomail fires an email within 90 minutes from their assigned account manager — not from a generic sales@ address, a personalised email from a real person's name — saying "I noticed you were looking at our pricing plans. Happy to answer any questions." Our trial-to-paid conversion from pricing page visitors went from 8% to 34% after we set this up. The technical setup took 45 minutes. The business impact was immediate.
The back-in-stock trigger was something I did not realise we needed until I saw the revenue numbers. We had a popular product that went out of stock for 3 weeks. We added a "notify me" form on the product page and collected 847 email addresses from interested buyers. When it came back in stock, Migomail fired the trigger email immediately to all 847 subscribers. Within 6 hours, 423 of them had purchased. ₹18 lakh in revenue from a single trigger that took our team 20 minutes to set up. I have been explaining this to every brand founder I know.
“Rackwave Technologies has significantly improved our marketing performance while providing reliable cloud services. We’ve been using their solutions for a while now, and the experience has been seamless, scalable, and results-driven.”
David Larry
Founder & CEO
Common questions about Migomail's trigger-based email capabilities.
Migomail processes trigger events and dispatches triggered emails within 90 seconds of receiving the event signal — for immediate trigger configurations. For delay-based triggers (for example, cart abandonment after a 55-minute wait, or browse abandonment after a 4-hour window), the timer starts the moment the event is received and the email dispatches exactly at the configured delay. There is no batch window, no scheduled job, and no manual action required between the event and the email.
Migomail detects cart abandonment via native Shopify and WooCommerce integrations, which push real-time webhook events when a subscriber creates a checkout and does not complete it within your configured window (default: 15 minutes). The triggered email receives the full cart contents — product names, images, prices, and quantities — as merge variables, so the email dynamically shows the exact products the subscriber left behind. No pixel or custom code is required for Shopify or WooCommerce users.
Cart abandonment fires when a subscriber adds items to a cart and does not complete the purchase. Browse abandonment fires when a subscriber views a product page — typically 3 or more times, or for a configurable duration — without adding to cart. Browse abandonment emails capture intent earlier in the purchase journey and typically include the browsed product, a short social proof element, and a gentle nudge to return. Browse abandonment requires the Migomail tracking pixel on your product pages.
Yes. Every trigger configuration includes a delay setting — you can send immediately (within 90 seconds of the event), or add a fixed delay (15 minutes, 1 hour, 4 hours, 24 hours, 7 days, or a custom duration). For cart abandonment, a 45–60 minute delay is the most common configuration — long enough to exclude subscribers who were simply interrupted but returned to complete the purchase on their own, short enough to catch them while the cart contents are still fresh.
Yes. Suppression conditions let you cancel a queued trigger email if the subscriber takes a qualifying action between the trigger firing and the email sending. The most common suppression is "do not send the cart abandonment email if the subscriber completes a purchase before the 1-hour delay expires." This prevents sending a recovery email to someone who already bought — which confuses subscribers and damages trust.
Yes. Trigger events can activate a full multi-step workflow rather than just a single email. A cart abandonment trigger can activate a 3-email recovery sequence (1 hour: reminder, 24 hours: social proof, 72 hours: discount offer) with each step suppressed if the subscriber converts between emails. This is configured in the Migomail workflow builder — the trigger fires the workflow, and the workflow handles the sequence, delays, and conditional branching.
Send a POST request to the Migomail Events API endpoint with your account API key, the event name (a string you define — e.g., "payment_failed", "contract_signed", "feature_milestone_reached"), and an event properties object containing any merge variable data you want available in the triggered email. The event name maps to a trigger configuration in your Migomail account. API documentation, request examples, and SDK support are available in the Migomail developer documentation.
Yes. The trigger analytics dashboard shows per-trigger-type performance: emails sent, open rate, click rate, and revenue attributed (when ecommerce tracking is connected). Revenue attribution for trigger emails uses a 7-day click attribution window and a 1-day open attribution window — a subscriber who clicks a triggered email and purchases within 7 days has that revenue attributed to that trigger. You can also export trigger analytics per-event for use in your own BI tools.