Changelog

changelog

Every week we summarize what happened in Ecomail. New features, minor and major improvements or bug fixes.

Contact update trigger with new modes and new button text alignment options

Contact update trigger expanded with two new modes ‑ has value and is empty, fix for the IdoSell integration, fix for the mobile pop‑up form, improved button text alignment options, and fix for incorrectly evaluated Wait step in automations.

IMPROVEMENT

Contact update trigger: new has value and is empty modes

The Contact update trigger now offers two additional modes ‑ has value (field changes from empty to filled in) and is empty (field changes from filled in to empty). Both react to the field's value transition, not just the resulting value ‑ a regular change between two filled‑in values (e.g. CZ → SK) will not trigger these modes; the existing any change and matches modes are used for that.

FIX

IdoSell: subscribe and unsubscribe information is sent back to the platform

After contacts were unsubscribed via a segment or via the unsubscribe link in a campaign, the unsubscribe information was not sent back to IdoSell. Contacts could incorrectly appear as active in IdoSell even after being unsubscribed in Ecomail.

FIX

Automations: the Wait step evaluates correctly

In certain scenarios, the Wait step incorrectly evaluated the elapsed time, which could cause the automation to continue too early or too late.

IMPROVEMENT

Editor: button text alignment respects the setting

When a button contained multi‑line text (entered via shift + enter), the text alignment in the template preview and in the sent email always displayed as centred. You can now set the text alignment to right, centre, or left.

FIX

Mobile pop‑up form displays in the correct position

The mobile version of the pop‑up form was in some cases displayed shifted towards the right edge of the screen instead of centred. The form's position has been fixed.

Fixes for Shoper integration, API and segmentation

The Shoper integration now safely merges contact tags and fixes newsletter subscription, fix for segmentation by purchased item price, fix for SMS campaigns and transactional emails in the Polish version, fix for the data feed and three API endpoints.

FIX

Shoper: safe tag merging and fixed newsletter subscription

The Shoper integration overwrote all tags with the current set from Shoper on every contact update ‑ a contact could lose tags assigned by an automation or another source. Tags are now safely merged with the existing ones, without data loss. We also fixed adding the newsletter consent tag ‑ it previously wasn't added when consent was given in an order, during registration, or via a form. An unsubscribed contact who gives new consent in Shoper is now resubscribed in Ecomail.

FIX

Segmentation: the Purchased item price condition calculates correctly

The condition for segmenting by purchased item price calculated the total order value instead of the price of the specific item set by the client. The calculation is now fixed and matches the specified criterion. A new condition, "Order value", has also been added.

FIX

Data feed: emails with large feeds are now sent

When using a data feed with very extensive content (e.g. long HTML text in one of the keys), a campaign got stuck in the Sending state and the email was not sent ‑ without showing an error message. During a data feed update, the maximum value size of 64kB is now strictly enforced.

FIX

Automations: the Repeat trigger always saves with the set time

The Repeat trigger could in some cases be saved without a filled‑in trigger time, meaning the automation never fired ‑ without this being obvious at first glance. Saving the trigger without a valid time is now blocked.

FIX

API: deleting a tracking domain accepts the ID in the URL path

The endpoint for deleting a tracking domain did not accept the domain ID as part of the URL path, even though the documentation described it that way. The endpoint now works as documented ‑ DELETE on /domains/{domain_id}.

FIX

API: custom fields handled case sensitivity inconsistently

Custom fields submitted via API with different letter casing (e.g. Phone and phone) were stored as separate fields instead of being matched to the existing one. A new custom field is now created in lowercase and matched regardless of the casing used in the request.

Shopify: on‑site behaviour tracking and improved data sync

The Shopify integration now tracks viewed pages and viewed products, lets you choose the source of product categories, and syncs tags and contact subscription status in real time.

IMPROVEMENT

Shopify: on‑site behaviour tracking and improved data sync

We added support for tracking viewed pages and viewed products to the Shopify add‑on. In the integration settings, you can now choose the source of product categories between Shopify Tags and Shopify Categories. The transferred data also includes the customer's note. Tag synchronisation now happens in real time, without needing any further contact edits in Shopify. We also expanded the data sent back to Shopify to include contact subscription.