Changelog

The GET /campaigns/{id}/stats and GET /pipelines/{id}/stats endpoints now support optional from_date and to_date parameters in YYYY‑MM-DD format. The same parameters were also added to the stats‑detail endpoints, where previously only from_date worked. Filtering lets you retrieve statistics day by day without loading the full history.

The merge tag for the validity date of the last sent discount coupon was not displayed in automation emails ‑ fixed. The export of sent coupons in a folder was not sent after clicking the button ‑ fixed, the export is now delivered reliably. Importing coupons from a CSV file could fail in certain cases ‑ fixed.

If a template in an automation contained a product condition (e.g. last purchased product) that was not available in the feed or did not meet the specified condition, the email was not sent and the automation failed without an error message. The template is now sent even when the product condition is not met ‑ the product is omitted from the email, but the rest of the template is delivered.

The Ecwid integration was loading the contact name from an API field that Ecwid stopped populating. We switched to the current field per Ecwid's corrected documentation.

The GET /pipelines/{id}/actions and GET /pipelines/{id}/actions/{actionId} endpoints now return a next field for each step containing the IDs of the following steps, so the full automation graph can be reconstructed from the response. For most step types, next is an array of IDs (usually one, or empty/null at the end of a branch). For branching steps, next is an object with one array of IDs per output ‑ yes / no for the Condition step, the variant keys for the Split test step, and default / quarantine_skip for the Send email step.

A new GET /feeds endpoint returns the list of all product feeds in the account, including the feed type, URL, number of loaded products, and any error from the last processing run. The id field from the response can be used as feed_id for the feed refresh endpoint.

The POST /templates endpoint now accepts an mjml field in addition to html, using the same JSON format as the Ecomail template editor. A template created from an MJML definition is fully editable in the drag‑and-drop editor ‑ Ecomail compiles the definition to HTML automatically. A template created from raw HTML remains editable only in the code editor. The html and mjml fields cannot be combined ‑ exactly one must be sent.

Alongside the existing CURDATE() function, NOW() is now available, returning the current date and time in the format YYYY‑MM-DD HH:MM:SS. The Date field type now accepts this extended format with time in addition to the plain date ‑ useful for more precise logging, for example the exact time of a registration or purchase.

Agency admins can now transfer EMA credits between the agency account and sub‑accounts the same way it already works for email and SMS credits ‑ in both directions, in the Manage sub‑account section. A transfer cannot be made if the agency or the affected sub‑account currently has an unsettled EMA session in progress (chat or a scheduled checkup) ‑ in that case you need to wait for it to finish.

When a segment with an Exclude from segment condition was used as a parent segment, the resulting segment ignored that exclusion and returned contacts that should have been excluded. Exclusion from a parent segment is now respected.

The time of the last sent campaign in the Overview section was displayed in UTC, while the Campaigns section showed the same moment in local time (CET/CEST). Time display in the Overview is now unified with the rest of the app.

For some orders from the Eshop‑rychle integration, the product code stored with the order differed from the code in the product catalogue, so the product could not be matched in the data feed. Codes are now stored consistently and matching against the catalogue works reliably.

Exporting an automation with a large number of steps and contacts could fail or take an unreasonably long time. Export processing is now optimised and handles large automations reliably.

Segmentation and automation triggers now understand custom event property data types. The platform automatically detects the property type from account data (number, date, boolean, array, text) and adapts the available condition operators ‑ instead of plain text comparison, ranges, dates, numeric operators and array comparisons are now available. The Category, Action, Label, Property and Value fields offer autosuggest directly from account data ‑ start typing and the platform suggests existing values. Works in segmentation and in the Custom event trigger.

The template preview mode now has a Dark mode toggle. When enabled, background and text colours in the preview are transformed following Gmail's logic ‑ dark backgrounds lighten, light ones darken, and text is recoloured for contrast. Images remain unchanged. This is purely a display mode in the editor ‑ nothing is written to the saved template or the sent campaign. The toggle resets to light mode on each entry to the preview.

For A/B campaigns in the Evaluating state, a new Evaluate now action is available. The campaign no longer needs to wait for the full evaluation period to elapse ‑ the system evaluates the current variant results and sends the winning variant to the remaining recipients. The action is irreversible and requires confirmation in a dialog. It is also possible to cancel the evaluation ‑ the winning variant will not be sent.

Accounts with a correctly connected GA4 integration were incorrectly shown a message about unsupported Google Analytics Universal in campaign reports. The message now only appears for accounts that genuinely do not have GA4 connected.

In some automations, sending an email and progressing the contact to the next step took considerably longer than the usual seconds. Automation step processing is fixed and now runs in the expected time.

In the HTML template editor, preview scrolling did not work in Firefox, Safari or after expanding the preview to full width. In some cases the scrollbar could not be released or the preview could not be shrunk back. Preview scrolling now works correctly in all supported browsers.

When adding a tag to a contact, confirming with a comma did not clear the input and the new tag did not immediately appear as checked in the contact detail. Both are fixed.