EMA with sharing, skills and memory, Webareal with automatic tracking and smart delivery API

The EMA assistant has gained five new features. A conversation can be exported ‑ in the conversation menu, choose Copy as Markdown or Download as Markdown. The Share option makes the conversation available to selected colleagues from the account (or you can copy a link): they can read the whole thread but cannot write in it. They will see everything EMA answered, including data their role does not normally have access to, and you are responsible for the content you share. Skills are ready‑made procedures that EMA runs with a single command ‑ you pick them in the menu under the plus button or by typing a slash in the message, for example abandoned‑cart (builds an abandoned cart automation), automation‑health (checks running automations), campaign‑preflight (checks a campaign draft before sending) or calendar‑review (goes through campaigns for the next 14 days). You can write your own skill from scratch, or with the create‑skill skill, where EMA asks you a few questions and builds the skill. Memory lets EMA remember, for example, how you address your customers ‑ the Memory switch in the conversation determines whether EMA may use and change it. EMA's answers now show sources: the numbers in the text refer to specific records, such as campaigns, that EMA drew on, and a list of them appears below the answer.

The Webareal integration now inserts the Ecomail tracking code into the e‑shop header on its own, so Google Tag Manager or any other external tool is no longer needed. The code tracks page views, viewed products and add‑to-cart events (it also works with templates that use an ajax popup cart), which makes it possible to run the Abandoned cart and Recently viewed products automations. A visitor is tracked only once identified ‑ by clicking a link from a campaign or automation, or by logging in to the e‑shop. When the integration is disconnected, the code is removed automatically. For new installations, tracking is active right away; existing customers enable it by saving the settings in the integration modal. To match products with the catalogue, a product feed must be uploaded in the account.

The GET, POST, PUT and DELETE /smart‑delivery/rules endpoints let you list, create, edit and delete smart delivery rules via the API, that is, the priority quarantine and frequency cap limits. The system rules standard and unlimited are always available ‑ the limits of standard can be changed, while unlimited can be neither edited nor deleted. A rule used by a campaign or automation cannot be deleted. A smart_delivery field has been added to POST /campaigns and PUT /campaigns/{id}, which lets you assign a rule to a campaign or set custom limits. If you omit the field, the campaign's existing settings stay unchanged, the same as when you edit recipients via recepient_lists. The settings are also returned in campaign responses in the smart_delivery field.

The new GET /coupons/folders endpoint returns a list of all discount coupon folders in the account, including the default one. For each folder it shows the number of remaining usable coupons (remaining) and the number of coupons with expired validity that have not yet been deleted (expired). Useful for automatically replenishing stock via POST /coupons/import before coupons run out and automations start sending emails without a coupon.

A "Disable click tracking" switch has been added to the button and link properties in the template editor. Ecomail normally wraps links in a tracking address, which could cause deep links to mobile apps to open in the browser instead of the app ‑ iOS and Android verify the link's domain, and the tracking domain does not host the app's verification files. For a link with tracking disabled, the original address stays unchanged, but clicks on it are not counted in statistics. Click tracking for other links in the template is not affected.

During the initial sync of customers from Ecwid into a list with double opt‑in enabled (after connecting the integration as well as on a manual customer refresh), customers who had given marketing consent were saved as unconfirmed, but no confirmation email was sent to them. They are now saved straight away as subscribed without a confirmation email, the same as with other e‑shop integrations. Contacts previously saved as unconfirmed remain unchanged.

If the product feed contained the same product ID more than once, an email with the last purchase merge tag for a specific feed (ECM_LAST_BOUGHT__<feedId>) was not rendered and not sent for a contact with an order of multiple products. This also affected the variant for purchases across the whole history. The issue is fixed, and products are rendered in the same order as before.

The online version of an automation email (the View online link) showed unprocessed merge tags instead of content for templates with a purchase category condition (ECM_BOUGHT_CATEGORY). The online version now evaluates the conditions the same way as the delivered email, including category names with spaces or diacritics. If the online version cannot be processed, the visitor sees a page asking them to contact the sender instead of unprocessed tags.