Author a Real-Time Trigger Without a Developer
Describe the moment you want to react to — an event, a balance, a page visit within a window — and have the connector wire the real-time trigger that launches your program, no developer required.
Real-time triggers — react the instant a customer does something — are usually a developer job: defining the events, the conditions, the time window, and wiring it to a program. With the Optimove MCP, a marketer describes the trigger in plain language and the connector builds it: a sequence of events, attribute conditions, and a time window, attached to the campaign or journey it should launch.
This turns “I wish we could catch players right after X” into something a marketer ships the same day — sequencing events (for example, a bet finished with balance at zero, then a page visit within a few hours), layering attribute filters, and pointing the trigger at a program that's already built.
What you need to run this use case.
| Ingredient | What to use |
|---|---|
| AI assistant | Any MCP-compatible AI assistant (Claude, ChatGPT, Copilot, and others) |
| Connector | Optimove MCP |
| Optimove data | Real-time events, customer attributes, triggered campaigns/journeys |
| Optimove products | Optimove real-time triggers (triggered campaigns) |
These prompts are a baseline — a starting point to copy and adapt to your own brand, data, and goals, not a fixed script. Paste one into your assistant with the Optimove connector on, and replace anything in [brackets].
Using the Optimove MCP, help me author a real-time trigger. 1. Fire when [event A, e.g. a bet finishes with balance at zero and risk score under 70], then [event B, e.g. a page visit] within [3 hours] 2. Add the attribute conditions and the time window between the two events 3. Attach it to launch [my existing program, e.g. the churn journey I built], and show me the logic to confirm
A clickthrough where a marketer describes a two-event real-time trigger with a time window and attaches it to an existing program.
The flow, step by step:
Describe the moment. Tell the assistant the events you want to react to and the order — for example, a bet finished at zero balance, then a page visit soon after. It sets up the sequenced trigger.
Add conditions and the window. Layer the attribute filters (balance, risk score, and so on) and the time window between the events. the assistant encodes them into the trigger logic.
Point it at a program. Attach the trigger to the campaign or journey it should launch — typically one you've already built, like a churn or reactivation program.
Review the logic. Have the assistant show the trigger definition — events, conditions, window — so you can confirm it fires exactly when you intend before it goes live.
Activate in Optimove. The trigger is drafted for review; you activate it in Optimove when you're satisfied.
A marketer wired a two-event sequenced real-time trigger without a developer — a Bet Finished event with balance at zero and a risk score under 70, followed by a Page Visit within three hours — to launch the 45-email churn programme they had built the day before. The whole trigger was authored conversationally, from events and conditions to the three-hour window.
sequenced into one real-time trigger
between the two events, set in chat
authored by the marketer, in one session
Do I need a developer to build a real-time trigger?
No — that's the point. You describe the events, conditions, and window in plain language and the connector wires the trigger. You review the logic before it goes live.
Can it chain more than one event?
Yes. You can sequence events with a time window between them, plus attribute conditions on each, so the trigger fires only on the exact pattern you want.
Does the trigger go live automatically?
No. It's drafted for review; you activate it in Optimove once you've confirmed the logic fires as intended.