Changelog

The templates overview now has an Unassigned item in the dropdown menu. It shows only templates that are not assigned to any folder. The item displays the count of such templates and the selection stays active even after refreshing the page. Users with many templates can easily find and organise templates outside the folder structure.

For individual subscribe and unsubscribe contact notifications, the notification was only sent when both addresses were filled in at once. Now it's enough to fill in just one of them ‑ the subscribe notification address separately, the unsubscribe one separately, or both together. The notification is sent based on which addresses are filled in.

Plan‑based accounts whose sending was blocked due to exceeding the contact limit were incorrectly shown a message about insufficient email credits in the bell notification. Now the correct information is shown ‑ that the number of contacts exceeds the plan limit, with a recommendation to upgrade the plan or reduce the number of active contacts.

We've released a new version of the Ecomail tag for server‑side Google Tag Manager. We fixed the data assembly when unsubscribing a contact. For unsubscribing to work correctly, the Update existing option must be enabled in the Data about user section of the tag template.

The POST /domains endpoint returned a generic 500 error with an HTML response when attempting to create a domain that already exists in the account. It now returns status code 422 with a readable JSON body that clearly states the domain already exists.

The web events endpoint (tracker/events) could fail if an incoming parameter exceeded the length allowed by the database. The value is now automatically trimmed to the allowed length and returned in that form in the response, so the request completes without an error.

For products with variants, the product code contains a slash or a space (e.g. 12345/ABC). Different feeds stored the same product with a slash in one and an underscore in another, so the code from the order did not match the product in the feed. As a result, automated emails (last purchased products) showed the price and name, but the description, product link and image were missing. Product codes are now normalised before comparison, so the product is found in the feed regardless of whether it's stored with a slash, a space, or an underscore.

Coupons with an expired validity date were imported into the account via the Eshop‑rychle and Upgates integrations even after expiring, which then got deleted and re‑imported day after day. Only coupons valid today or in the future are now imported; a coupon without a validity date is treated as permanently valid. The change only affects future synchronisations and does not touch coupons already in accounts.

When using the "All in list" option, the export ignored the applied filters (date range, type, name) and exported the entire campaign list. The export now matches what the user actually sees after filtering. If a user selects all records and then manually deselects some, the export only includes the records that remain selected.

The campaign log endpoint always returned an empty result when filtering by the not_opened event, even for campaigns with demonstrably unopened emails. The filter now returns the correct list of contacts who did not open the campaign.

If a client had the same domain set up as both sending and tracking, the tracking domain could not be deleted ‑ the application considered it in use because of the sending domain. Using a domain as the sending domain no longer blocks deletion of the tracking domain with the same name.

The custom permissions settings were missing the option to grant a user access to RSS feeds. As a result, the user could not see RSS feeds in the menu and received a 403 error when accessing the page directly. Permission for RSS feeds is now part of the custom permissions configuration.

On some accounts, the notification about a new contact subscribing to a list was not sent despite correct settings.