Optimove vs Craft CMS

Optimove's developer changelog is API surface work, and the pace is steady rather than dramatic. The Gamify API gains an endpoint capping how many times a player can play a campaign. The Preference Center API adds smart-campaign preference endpoints for topics hidden from the UI. Data Share now documents three schema generations side by side with version tabs so customers migrate on their own schedule. Around them sits documentation correction work — parameter types, response behaviour, error handling on the conditional execution endpoints.

Two things are happening at once. The platform is being exposed programmatically across every module — gamification, preferences, SMS, overlay messaging, conditional execution — which shifts Optimove from a campaign UI toward something other systems drive. And the AI Minigame Creator, which generates and publishes playable minigames from natural language through the Optimove MCP, points at where that leads: the API surface exists partly so an AI client can operate it. Side-by-side schema versioning suggests a customer base large enough that forced migrations are not an option.

Given the Gamify API is accumulating operational controls alongside the MCP-driven creation path, expect more guardrail endpoints — limits, eligibility, spend — since generated campaigns need bounds. The volume of documentation corrections suggests the API reference is still catching up to the implementation.