Four ways to get a head start
Work that can begin before the nightly batch cycle delivers its first load — across data, operations, gamification and creative.
Real time events & customer registration
Register customers and stream their activity the moment it happens — fully independent of the nightly batch cycle.
Admin & permissions
Every site launches with role-based access, controlled from Settings → Access Management.
System notifications & the status page
Two operational must-dos before go-live: proactive alerts on daily processes, and visibility into system health.
MiniGames — launch your first campaign
Wheel of Fortune, match-3, prediction games, and more — built and published in seven steps.
Loyalty — turn every touchpoint into an engine
Design and launch gamified loyalty programs independently of batch data.
Templates for native channels
Build and validate creative across every channel — independent of when batch data starts flowing.
Real time events & customer registration
Register customers and stream their activity the moment it happens — fully independent of the nightly batch cycle.
1Upsert API — register customers
A single Upsert API call registers a customer in Optimove.
2Real-time events — stream activity instantly
Register event definitions in Events Settings, then fire them from site or app. Events land immediately and are available to triggers.
3No dependency on the batch cycle
Both paths run outside the nightly load — the site can hold live customers and activity on day one.
Next story 1 of 6
Upsert API — cURL request and response, straight from the Developer Hub console.
Events Settings — event definitions registered per site, ready to receive real-time activity.
Admin & permissions
Every site launches with role-based access, controlled from Settings → Access Management.
1User accounts
Invite the team, set each account's status, and manage sign-in from one tab.
2Role permissions
Four roles ship out of the box — Admin, Analyst, Manager, Marketer — each with its own scope.
3API keys
Issue and rotate keys for the integration work happening in parallel.
Access Management — user accounts, role permissions, and API keys in one place.
System notifications & the status page
Two operational must-dos before go-live: proactive alerts on daily processes, and visibility into system health.
1Site system notifications
Email alerts on the daily data and campaign processes — configured by the site admin only.
2Status page
Live status for core product, API, batch process, Real-Time Triggers, and campaign channels.
3Set both up before launch
Alerts and status together mean a failed load is noticed by the team, not by the client.
System Notifications — pick the daily processes the admin should be alerted on.
Status page — all systems operational, per service.
MiniGames — launch your first campaign
Wheel of Fortune, match-3, prediction games, and more — built and published in seven steps.
1Choose your campaign type
Start from the game that fits the moment.
2Add content & design the game
Copy, artwork, and brand styling on the game itself.
3Build the surrounding landing page
The page the game lives in, built in the same editor.
4Decide the campaign screen flow
What the player sees before, during, and after play.
5Decide on prize distribution
Prizes, odds, and inventory.
6Decide how users will interact
Entry rules, attempts, and eligibility.
7Publish your campaign
Go live — no batch data required.
A published Wheel of Fortune MiniGame, spinning in the player's browser.
Loyalty — turn every touchpoint into an engine
Design and launch gamified loyalty programs independently of batch data.
1Gamified economies
Points, coins, and currencies players actually chase.
2Recognize achievements
Missions, badges, and levels that mark progress.
3Drive repeat visits
Streaks and recurring rewards that pull players back.
4Brand every element
Every surface styled to the client's brand.
A branded loyalty hub — missions, currencies, and achievements in the player view.
Templates for native channels
Build and validate creative across every channel — independent of when batch data starts flowing.
1Email
Drag-and-drop templates, previewed and tested before the first send.
2Mobile
Push and in-app messages, drafted against real personalization tags.
3SMS & WhatsApp
Short-form templates ready for approval lead times.
4Web
On-site messages and pop-ups, staged and validated.
Previous 6 of 6
The template library — creative organized per channel, ready to validate.