Changelog

A new POST /campaigns/{id}/send‑test endpoint lets you send a test version of a draft campaign to specified email addresses (max. 5) with specific merge tag values. The test does not change the campaign status and is not counted in statistics. Partners and agencies integrating via API can test the final look of a campaign including personalisation without having to open the app.

You can now disable automatic alerts about approaching expiry and depleting coupon stock for each coupon folder. The Notify on low stock toggle is on by default and controls both email and in‑app notifications. When enabled, a notification is sent when stock drops below 15% or below a custom limit you set. The main folder now also supports a custom limit setting.

Previously the domain type (sending or transactional) would overwrite each other ‑ a domain could only ever have one type. A single domain can now be configured as both sending and transactional at the same time, with each type managed independently. The POST /domains API endpoint now requires a valid type parameter (sending or transactional) ‑ an invalid value returns 422 instead of being silently accepted. The domain listing may return two records with the same name differing by type for such domains. We recommend using a unique domain for both bulk sends and transactional emails.

We resolved potential issues with connecting the MCP server to third‑party AI tools, particularly Cursor. If you experienced connection problems, we recommend disconnecting and reconnecting the server following the updated help guide.

We released an updated version of the Magento 2 plugin on Adobe Marketplace. We compared the plugin against the current feature set of the PrestaShop and WordPress versions and added the missing options. The plugin's help documentation is updated.

For contacts whose email address contains a + character, all tracking code events (page views, add to cart, product views) stopped being recorded. The data only reached internal logs but never made it into the database or the frontend. The issue is fixed, and events are now recorded correctly regardless of the characters used in the address.

If a link from a data feed was inserted into a template as an HTML tag inside CDATA, it wasn't tracked ‑ clicking it was not recorded in campaign or automation statistics. Links inserted this way are now tracked the same as any other link in the template.

In CDP → Product Analytics you can now name and save a configured filter for repeated use. Saved filters can be selected, edited, or deleted at any time.

If a user deleted a Send email or SMS step after duplicating an automation, the step remained visible in the automation overview with no distinction from active steps, which made it harder to read the statistics. Deleted steps are now marked with a DELETED label in both the overview and the detail view (including A/B test variants). Automation statistics remain unchanged ‑ this is purely a clarity improvement for the list.

If an account had multiple product feeds connected and the same product had an ID differing only by a slash versus an underscore (e.g. 12345/67 and 12345_67), both products were inserted into the email instead of just one. Product IDs are now compared correctly and no longer produce duplicates.

Desktop pop‑up forms were displaying incorrectly on some websites ‑ either with an overly stretched image or excess white space below the form. Pop‑up form display is now fixed.

In the Google Analytics integration settings, pagination of the list of connected properties did not work ‑ clicking Next page kept showing the same list. Pagination is now fixed.