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}.
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.
Once in a while, we will send a summary of new features, improvements, and fixes to your inbox. No spam, no marketing – just product updates from Ecomail.
