AI understands the meaning.
Names, descriptions and data structures tell AI how to connect your campaign: it reads the structure of your events, never their values. At send time, the approved code runs without the model.
Orchestrator AI · Made for marketing
Launch campaigns.Without waiting for developers.
AI connects each new campaign to your existing events and data sources. Your marketing team creates, personalizes and goes live, without another development ticket.
14-day free trial · No credit card required
- No manual field mapping
- No template syntax
- No contact database to sync
You describe the outcome
Start with whatyour customer needs.
Choose the signup event and create the message. Give each variable a name and describe what it contains. Your section says what it needs, in your words.
Your campaign
A helpful onboarding reminder.
“One day after signup, remind people of the steps they still need to complete.”
- Selected event
- User signed up
- Variable name
- Next steps
- What it contains
- The onboarding steps this person has not completed yet.
AI handles the connections
You say what.AI finds the how.
Orchestrator reads your campaign, understands what each section needs and connects it to your chosen event and available data sources.
No field paths. No manual mapping.
Connected by Orchestrator AI
A helpful onboarding reminder.
Event · User signed up
- RecipientThe person who signed up
- Signup event
- First nameWhat to call this person
- Account profile
- Next stepsWhat they still need to do
- Onboarding progress
You keep the final say
Know what will happen.Then go live.
Read the campaign’s logic in plain language. Ask AI for adjustments, review with your team and publish when you’re ready.
Campaign summary · Ready for review
A helpful onboarding reminder.
- Start with signup.
Use the person identified by the event.
- Wait one day.
Get their name and remaining onboarding steps.
- Send a useful reminder.
Check the campaign’s conditions and their preferences before sending.
One campaign, from your intent to its connections. Select a step to explore this example.
Example · An onboarding reminder
Remind them ofwhat’s still to do.
Right before sending, Notifizz checks Camille’s latest progress in your app. The reminder includes only the steps still left to complete.
One campaign. Personalization from your current data.
From your app · At send time
- Create a projectNot yet
- Invite your teamNot yet
The reminder Camille receives
Let’s finish your setup.
Hi Camille, here’s what’s left:
- Create a project
- Invite your team
Both steps are unfinished. Both appear in the email.
From your app · At send time
- Create a projectDone
- Invite your teamNot yet
The reminder Camille receives
Let’s finish your setup.
Hi Camille, here’s what’s left:
- Invite your team
Project already created. Only the invitation remains.
On-demand personalization · Your data stays yours
Personalized on demand.AI never runs at send time.
Use the context your customers need, from the systems you already trust. The sending workflow requests the required information from your connected sources. Your customer database stays in your systems.
Personalization, at send time.
No customer database to sync. AI never runs at send time.
No customer database to sync.
Your product, billing system and CRM remain the source of truth. Request the information a campaign needs from the sources you have connected.
Personalization, with boundaries.
EU-hosted orchestration brings the message together. The sending workflow checks user preferences before delivery.
A closer look at data and connections
Each section declares typed inputs with a name and description. Orchestrator AI reads those needs, the selected event’s schema and the available source definitions, then generates the code that connects them.
The on-demand connections are called enrichers in the technical documentation. These functions in your systems return the requested information. The approved workflow calls them according to their cache policy (1 hour by default, configurable per source), which determines freshness. Delivery history and operational records have their own retention.
More campaigns. Fewer development tickets.
The best dev experienceis the one you don’t need.
Engineering connects your events and data sources. Marketing creates and launches campaigns using those connections, directly in Notifizz. Your product team keeps building your product.
- 1×Connect an event.
Reuse it across campaigns. - 0App redeploys for campaigns
using available connections. - ∞New ways to use
the same foundation.
Versioned campaigns
Change with confidence.
Publish a new version when you’re ready. In-flight sends finish on the version they started with.
Campaign health
See what needs care.
Inspect each execution, from data requests to delivery results. Campaign health highlights connections that need attention.
Sequences and conditions
Make the next step useful.
Add a delay or a condition, and stop the follow-ups as soon as someone reaches the campaign goal.
Your team has the final say
AI does the wiring.You give the go-ahead.
See how the campaign will work in plain language: the event, the data, the recipients and the delivery. Refine it with AI, review it with your team and publish when it’s ready.
A final look before it reaches your users.
Preview the rendered email and check spam risks during review. Consent, unsubscribe handling and reputation safeguards support delivery once the campaign goes live.
A few things to know
Good questions.Clear answers.
How does Orchestrator know which data a section needs?
A section’s variables have names and plain-language descriptions. Orchestrator uses those meanings to connect the section to your chosen event and available data sources. Marketing does not write field paths, map technical properties or manipulate template expressions.
What if the information is not in the event?
Orchestrator can retrieve it through a connected data source. If the source or a required field is not yet available, it creates a specific implementation task for your technical team. Once connected, the source can be reused across campaigns.
Do I need a developer for every new campaign?
Once the required events and sources are connected, marketing can create, adjust, review and publish campaigns from Notifizz without an application redeploy. A new source or a change to the data exposed by your app may need engineering work.
Does AI run every time a message is sent?
No. AI generates and refines the campaign’s connections before publication. At send time, the approved code resolves the required data and the sending workflow applies the configured rules and preferences.
Does on-demand personalization store a copy of my customer database?
No customer database import or ongoing contact synchronization is required. Connected sources provide information when a campaign needs it. They use a short cache, 1 hour by default and configurable per source, so freshness depends on that policy and the source. Delivery history and operational records have their own retention, as described in the privacy policy.
Your team. Your messages. Your control.
Your next campaign.On your schedule.
14-day free trial · No credit card required