What's new
What's new in Optima v1.2.0
Contact attributes, your own mail server for notifications, safer sign-in, large batch campaigns that resume, and many fixes.
Released 16 November 2026.
Signing in and access
- Change a password someone else chose. When an administrator creates your user, you must
choose your own password at the first sign-in. Until then the console opens only the
change-password screen and the API answers 403
password_change_required. You can change your password yourself at any time; doing so ends your other sessions. Passwords longer than 72 bytes are refused. - Clearer sign-in answers. Sign-in says "invalid credentials" until the password is right, and only then tells you that the account is locked, disabled or unverified.
- No log-out during an outage. When Optima's sign-in service is briefly unavailable, the API answers 503 instead of 401 and the console keeps your session and shows a notice.
- Read-only editors. If you may view a page but not change it, the fields are read-only and say why, instead of offering a Save that does nothing.
- Role names in your language. Built-in role names are shown in the console language on the Team, Users, invite and role pages.
- Licence notices. When a feature is switched off for an account that already holds its package, the notice says so and points you to your account administrator.
Privacy
- Contact attributes. Privacy settings has a new Contact attributes tab where you declare which profile attributes hold an email address or a phone number. Unsubscribes and erasures now also suppress the addresses in these attributes, and campaigns, journey send steps and one-off sends can only send to a declared attribute of the right kind. An attribute that a live campaign or journey uses cannot be removed without confirming.
- Hosted preference page. The preference link in an email now opens a small page with a switch per purpose and a Save button. Only the purposes the person changes are recorded. One-click unsubscribe also withdraws the purpose the email was sent under.
- Audit trail. A read that withheld attributes or identifiers is recorded as
redactedwith the withheld keys; exports record the same per row. An erasure request records who asked for it. - Retention policies. A policy created without
is_activeis active. Check scripts that create policies without the field. - Profile filters.
GET /profileswith a filter, profile export and the bulk profile routes needentity_type(400 without it). Remove-by-filter refuses more than 100,000 matches.
Profiles and data
- Identifier conflicts.
/profiles/setand its batch form answer 409identifier_conflictwhen the identifiers you send belong to different existing profiles, instead of writing to the first match. - New identifiers are kept. A write that matches an existing profile and carries an identifier nobody owns yet now adds it to that profile. Before, it was dropped.
- Event types with a dot. Segments, profile filters and journey conditions work on event types
such as
lead.qualified. - Datasets from SQL transforms. A transform that writes a dataset removes the records that vanished from its report. It removes nothing when the report was cut at its row limit, and when more than half would go it waits for you to confirm with Run and remove N records. The Transforms tab shows the outcome of each run.
- One-time connectors show Completed after their run, in the list and on the detail page.
- Catalogues in use. Renaming or deleting a recommendation catalogue that templates, content or journeys still use is refused with the list of users, unless you force it.
- Recommendations explain each item in the console language (trending, recently viewed, often
bought together, matches a profile value, pinned). The API returns the same as
reason_code.
Campaigns and delivery
- Large batch campaigns resume. A one-off batch to a large audience saves its progress every 100 profiles. After a temporary failure it continues from there; if it cannot continue, the campaign is paused and activating it again resumes the run. The fixed limit of 10,000 profiles is replaced by an operator setting (default 1,000,000).
- Provider rate limits. Every channel provider type takes a rate limit. When a provider answers "too many requests", Optima waits and sends later instead of counting a failed attempt.
- No duplicate sends from slow batches, and a resumed run does not queue the same person twice.
- Campaign statistics. Funnel rates use a clear base (delivered, opened and clicked are measured against sent), so rates no longer exceed 100% by mistake. Statistics, lift and predictions say when a result was cut at a read limit.
- Email. Messages are encoded so long lines and non-English text survive strict mail servers,
and carry a
Dateheader. Pre-flight fails early when the chosen provider cannot carry attachments. - Template preview uses the profile's preferred language when you give a Profile ID and choose no language, as a real send does, and names the language it used.
- Templates in use cannot be renamed. Saving a template that clears approvals tells you so.
- Journeys. Winner tests count every run of the saved version. A journey whose customer was erased exits cleanly. An on-site hold condition must be complete before the journey can be saved.
- Test connection on a webhook provider or external system checks that the address can be reached through the same network guard as real sends, without sending a request.
- Segments in use. Deleting a segment that campaigns, offers or audience syncs use is refused with the counts.
- Email builder. Insert merge tag is back in the text editor, and inserting a tag while the cursor is inside another one no longer loses it.
- File links support resumable downloads.
Notifications and usage
- Your own mail server. Notifications has a Providers tab: a workspace can send its notifications through its own SMTP server, with a connection test and a test mail. Sign-in and invitation mails still use the instance's server.
- Webhook signatures. Notification webhooks are signed only with the subscription's own secret. A webhook subscription without a secret no longer receives deliveries: rotate its secret in Settings > Notifications. A subscription with a User receiver cannot use the webhook channel; use an Application receiver.
- Usage alerts belong to the account. Subscribers of usage threshold alerts are managed on the account's Usage page, and the alerts arrive by email.
- Annual contracts. Usage of events and operations is compared with the allowance for the months so far, and the projection uses the same basis. Earlier it could show figures far above 100%.
Optima Agents
- New versions of the built-in agents: the campaign evaluator adds a journey drop-off section and always evaluates a stopped campaign; the weekly digest covers the eight largest campaigns and lists up to five it left out; the privacy digest says in the Erasure section when its counts may be incomplete; the data quality watchdog words its findings more carefully; the lead qualifier reads only the form's attributes. Existing instances keep their version until you upgrade them.
- An instance reacts to events about 5 seconds after it starts (it was 30).
- Each budget field of an instance shows its own error.
Forms and web content
- A required form field left empty, or a required checkbox left unticked, is refused.
- Double opt-in confirmation mail is limited to one per form and address every 10 minutes.
- On-site content with a hold condition is served again, and inline content no longer prints
<no value>for a missing attribute. - A hosted landing page body is limited to 192 KiB.
For API users
X-Idempotency-Keyis scoped to the caller, method and path. A key of the wrong length answers 400.- Failures between Optima's services answer 502
CDP unavailableor 503 withRetry-Afterinstead of a misleading 400, 401 or 500. - A filter with a malformed id answers 400 and names the column.
- New fields:
package_licensedon licence refusals,reason_codeon recommendation items,audience_capon the audience count,sweepon transform runs,user_idon account team members. - The requests-per-minute limit per IP address now defaults to 6,000 when the operator sets none.
SDKs
No SDK has a new release. These versions go with Optima v1.2.0:
- Web SDK 1.4.0
- iOS SDK 1.4.0
- Android SDK 1.4.0
- React Native SDK 1.2.0