Every week we summarize what happened in Ecomail. New features, minor and major improvements or bug fixes.
Expanded CDP product analytics filtering as new features, two integration improvements and three fixes.
In CDP → Product analytics you can now filter data not only by time period but also by specific e‑shops, categories, products or customers. Filter values can be both included and excluded from the selection. This makes it easy to remove discounts from analysis, focus on seasonal goods or separate B2B customers.
The new version of the PrestaShop module for Ecomail integration brings both fixes and improvements. Fixed: synchronisation with the Newsletter Subscription module, shop name storage logic (removed http:///https:// prefix) and Nginx compatibility (legacy routes, JS loading, AJAX URL, CORS). Autoupdate support has also been added. Customer group tags from PrestaShop now sync to Ecomail in real time ‑ without any additional contact editing in PrestaShop.
We updated the method for exchanging the authorisation code for OAuth login to Ecwid. Ecwid disabled the old GET method and Ecomail now uses a standard POST request in line with the current Ecwid documentation.
The ability to bulk edit product attributes in a block (button text, style) has been restored in the template editor. Product image display on mobile devices in two‑ and three‑column layouts has also been fixed ‑ images now respect column width.
The condition was finding contacts who had never purchased the product ‑ instead of contacts who had not purchased it within the specified time window. The condition now correctly respects the specified time range.
When setting a specific start date for recurrence, the trigger displayed an incorrect first run date. The calculation is fixed and the displayed date matches the actual first scheduled run of the automation.
Five new API endpoints and product categories as JSON as new features, CLV segmentation improvement and four fixes in automations and Shopify integration.
Product categories are now stored as a JSON array instead of a delimiter‑separated string (e.g. Alcohol|Wine|Red). In segmentation, entering just Wine is enough ‑ without needing to know the full category tree. Integrations have been updated: Shoptet now sends all categories (previously max. 1), Upgates all (previously max. 3), Webareal adds category transfer for the first time. Existing segments remain functional and can gradually be re‑saved in the new format. The API and tracking code accept both the new format and the original string ‑ backward compatibility is maintained.
Improved product blocks with a reworked approach to products from feeds are now available in the template editor. A detailed guide is available in help.
A new GET /templates endpoint returns the list of templates in the account with their IDs and names. Useful for example for agencies that manage templates programmatically.
A new PUT /templates/{id} endpoint allows updating the HTML content of a template via API. Editing is also permitted for templates linked to a campaign, but the campaign must be in Draft status.
A new PUT /lists/{list_id}/update‑subscribers-bulk endpoint allows updating up to 3,000 contacts in a single call. Clients who previously synchronised contacts one by one now have a cleaner alternative without needing to use subscribe‑bulk.
Conditions for segmenting by CLV are now available in segments ‑ customers can be filtered by CLV amount or distribution group (Low, Mid, High, VIP). Available on the CDP plan.
After reconnecting the Shopify integration to a different Ecomail account, it remained shown as active in the original account. The integration now automatically deactivates in the original account after being reconnected to another.
The automation test run displayed the time shifted two hours ahead of the actual trigger time. The time in the test overview now matches the actual record.
When exporting automation activities, records from all emails were exported regardless of the selected filter. At the same time, the export did not include the name of the email that triggered the activity. Both issues are fixed.
The GET /campaigns/{campaignId}/log endpoint returns campaign activity records (sends, opens, clicks, unsubscribes and more) with filtering and pagination support. The endpoint was fixed and added to the API documentation.
Custom conversion attribution window, pre‑built RFM automations and HTTPS for tracking domains as new features. Webhook with custom fields and three fixes.
In account settings (Marketer+ and CDP plans) you can now configure the attribution window length separately for opens and for clicks. Default values (10 days from open, 30 days from click) remain unchanged. The setting is in Account management → Settings → Global variables → Conversions.
Pre‑built segments and automations based on RFM analysis are now available on the CDP plan ‑ for contacts at risk of churning, most valuable customers, potentially valuable contacts and contacts suitable for discount campaigns. Segments are in CDP → Pre‑built segments. Pre‑built automations are available when creating them in Automations → New automation.
Tracking domains can now be secured with HTTPS by pointing the CNAME record to v2.spgo.io. The certificate is issued automatically and renews itself every 3 months. Existing HTTP domains are unaffected, the switch is optional. The setting is in Account management → Domains.
The Send to webhook step in automations now includes a custom_fields object in the payload with the values of the contact's custom fields. Previously the payload did not include custom fields.
Translated text in a template changed to garbled characters after any subsequent edit (indentation change, button link swap, product replacement). Translation text now remains intact regardless of further template edits.
Segment export was missing custom preference values for contacts, even though the full list export included them. At the same time, diacritics in the export were displayed as unicode escape sequences (e.g. Ko\u010dka instead of Kočka). Both issues are fixed.
The automation overview with API trigger showed 0 entries even when contacts had actually passed through the automation. The entry count now reflects the actual state.