Release Notes

This week's release includes: one account logs upgrade, the ability to send personalised test emails to specific contacts using their unique IDs, and two bug fixes: The reCAPTCHA tool on subscription forms now reflects correctly in Internet Explorer 9 and when you reuse your settings from previous imports, any additional columns now reflect correctly, not as 'undefined'.

This week's release includes one feature upgrade: A new type of start trigger on workflows that allows contacts only to enter via the API method. This ensures that the workflow is fully under your control and never triggers automatically.

This release includes one bug zap: Left and right scrolling works as it should in the Workflow reports display.

This release includes two bug zaps: The workflow name and message subject now only reflect once in the workflow composition, and the popup that enables you to log back into Everlytic when your session times out is working correctly.

This week’s release includes a notification about a solution we've submitted to Facebook to work around their policy changes and two improvements: Subject lines on transactional email bounce reports and multi-part transactional SMSes.

This week’s release includes: An improvement to email preheader text on test sends. Bugs zapped include: Fixed date-filter stats on transactional reports and corrected campaign sending times.

This week’s release includes an improvement to workflow processing speed. Bugs zapped include: a now-visible Everlytic-Grammarly incompatibility warning in our Classic email builder, and custom-field repairs on dynamic content for email.

This week’s release includes two bug fixes: An issue where custom fields weren’t saving a value of 0 and one where field mappings were undefined on recreated imports.

This week’s release includes: A new quick-launch communication modal, video-preview images in email, prepaid notifications, disabled Facebook posts, and one bug fix where images were sometimes misaligned in Outlook.

This week’s release includes one bug fix: Personalisation using custom fields now renders correctly in published landing pages.