Adestra Release Notes

Here you will find the most recent Adestra release notes.

For older releases, refer to our historical release notes.

Release	Features and fixes
3.100	Campaigns - UI
3.99	API, bug fixes
3.98	API
3.97	API, Automation program builder, SFD links
3.96	Shopify integration, Salesforce integration
3.95	Bug fixes
3.94	SMS processing - message status, API, Unsub - false positives, bug fix - non-latin form elements
3.93	API, bug fixes
3.92	API - event stream query, Two-click unsub - hide/remove from campaign options, bug fixes
3.91	User permissions - hidden workspaces, AI subject lines - option selections, SMS links - domains, bug fixes
3.90	AI subject lines, SMS - reporting, bug fixes
3.89	AI subject lines - UI, API, DKIM - key length, bug fix - staggered launch

Adestra 3.100

Campaigns - compose UI

Cards on the compose step updated to make it easier to get started with a new campaign using a template.

Screen capture showing an example of the cards present when first opening the compose step of a campaign.

Adestra 3.99

API

You can now update and test both delegated and authenticated domains via both APIs.

Bug fixes

Personal delivery time - you can now fully delete a PDT campaign that hasn’t started.

Unsub handling - the Variant Options page no longer displays an outdated error message about an invalid configuration.

CampaignSendMultiple REST API now returns suppression information.

Adestra 3.98

API

Create/validate delegated and authenticated domains via the API.

Adestra 3.97

API

Domain API search/all functionality added.

Automation program builder

UI updated with improved error notifications, e.g. for when attempting to activate an unpublished campaign.

SFD links

Improved handling of SFD links to prevent 404 errors.

Adestra 3.96

Shopify integration

Abandoned basket - the Adestra-Shopify app now allows you to sync your Shopify abandoned cart with Adestra's conversion capture feature.

Unsub support - improved unsub support for syncing unsubs via Shopify with Adestra so that you now define an unsub list when connecting your Shopify store to Adestra.

Salesforce integration

Workspace selection - workspaces are no longer assigned when mapping your core table and fields, allowing you to choose any workspace linked to your core table when syncing a Salesforce campaign to Adestra.

Remote lists - you can now connect remote lists with the latest version of the Adestra-Salesforce app.

Adestra 3.95

Bug fixes

Updated Promo Codes UI to add quotations for clarity on template code usage.

Removed unsub handling section in campaign options UI for split-test and persona variants as unsub handling is determined by the main campaign options.

Removed an incorrect error message for login attempt limits (associated with non-UCM users) when using UCM.

Filters with 'Fixed Date' date properties are now inclusive of end date when timezone set, similar to the filtering without timezone set.

Updated help documentation link for transaction imports.

Updated error text when attempting to save source_info for a remote list and the deduplication field name is not set.

Adestra 3.94

SMS processing - message status

Improved the SMS processing for SMS sends using Adestra's Upland Waterfall integration to better allocate messages to the 'Pending' and 'Bad Record' statuses.

API

To better support the Adestra-Salesforce integration, the workspace.search API call now allows you to specify a core table and return all workspaces available to that core table.

Remote List API only requires a dedupe_field if that pref is set, otherwise it defaults (to email).

Unsub - false positives

Improved unsub monitoring to avoid false positives in reporting as a result of ISP link scans.

Bug fix - non-latin form elements

Corrected the labels form element to allow and display non-latin, e.g. Arabic, characters.

Adestra 3.93

API

Added account_id to user.self results.

Updated the one-click list unsubscribe header to only unsub the contact when the url receives a POST request.

Added a feature setting to enable hiding of dedicated lists from the API (i.e. lists that are only intended to be used for one campaign or has a campaign ID).

Bug fixes

Resolved a conflict between the Spam Filter Detector and Remote XML with xmlns tags.

When copying a campaign with presets, you are now asked to confirm the campaign options in the new campaign.

List-Unsubscribe-Post header nor List-Unsubscribe header do not feature in emails sent where the unsub feature is not enabled at the workspace or project level.

Adestra 3.92

API - event stream query

New query parameter added to export exact event types for Event Stream API Endpoint. When options are present, only events of those types are passed back.

Existing white lists are applied. Events not white listed are ignored.

Searching for non-existing types and types on the “skip” list will be ignored and therefore return no record.

Two-click unsub - hide/remove from campaign options

Preference options added to hide/remove the two-click unsub menu in the campaign options and use only the default (also set in preferences).

Bug fixes

Long running filters no longer result in a launch failure warning while the filters are still running. Status is updated after filters have run.

Setting an event export data source to a workspace no longer removes all sms_launch events

Adestra 3.91

User permissions - hidden workspaces

When assigning user permissions, inactive workspaces are now hidden by default.

AI subject lines - option selections

When using the subject line generator, the tool remembers your settings/selections, i.e. if you want to get more subject line suggestions, you do not have to reselect the persona, etc.

SMS links - domains

The unsub link now uses the same domain configured for the tracking links, if configured.

If there is no domain configured for the tracking links, then the unsub link will use what’s set in the preference.

Bug fixes

UnsubList API no longer identifies the workspace id as a string.

Using the hints code to select the from address when DKIM is configured now also updates the DKIM settings to match.

UCM login permissions updated.

Unicode characters in transaction tags no longer break filters.

PGP keys can now be saved in the export screen.

Adestra 3.90

AI subject lines

When using previous campaigns for subject line suggestions, the AI assistant now uses the top performing 25 campaigns in the last 6 months, ordered by best to worst CTOR, instead of the 25 most recent subject lines.

Repositioned the Generate button and disclaimer text.

SMS - reporting

Metrics for messages targeting customers with bad record data, e.g. missing a mobile number in the database, changed from 'Rejected' to 'Not Attempted' with the reason being listed as 'Bad Record'.

Side-by-side image of the reporting screen before and after the change to illustrate the move of 'rejected' to 'bad record'.

Bug fixes

Staggered split test manual launch - manually launching using the 'Send this variant' button no longer results in the staggered launches selecting another variant.

Save as template preview - campaign previews now reflect edits made to the content if using a template created using the Save as Template feature.

Incremental list exports - contacts with a NULL value in their 'created' column no longer appear in incremental list exports.

Adestra 3.89

AI subject lines - UI

Removed the Use persona checkbox from the persona variant AI subject lines as the persona is always applied when editing a variant.

API

List core tables can no longer be changed by the API during an update to prevent accidental list corruption.

If the table_id in the PUT request is different from the current table_id, you will now receive an error message.
You can still omit the table_id when performing an update to a list.

Remote source and field mapping can be updated and retrieved via the API for a remote list.

DKIM - key length

Adestra now supports DKIM keys longer than 1024-bit. Should you require longer keys, i.e. 2048 or 4096-bit, please contact your customer success manager to discuss options.

Bug fix - staggered launch

Deselecting all of the days in a staggered launch (i.e. excluding every day of the week) would result in the staggered launch defaulting to the launch time and ignoring exclusions.

For a staggered launch to work, you now have to include a minimum of one day in the staggered launch days, i.e. you cannot deselect all launch days and still launch the campaign.