Skip to main content
EngageEngage Updates

Engage Update – 1.73 – November 2nd 2013

By October 22, 2013June 4th, 2019No Comments

1.73 – November 2nd 2013

Table of Contents

  1. Overview of 1.73
  2. Transactional Databases
  4. Other Enhancements
  5. Tweaks and Bug Fixes

1. Overview of 1.73

1.73 is scheduled for release on 2 November 2013.

In this release Ubiquity introduce Transactional Databases.

They have also included a few new features, more performance improvements and bug fixes.

2. Transactional Databases

You can now store transactional data in your Engage Database.

Transactional data is the information about what goods or services a person has purchased. So when a contact purchases something from your store or website, you can log this information within Engage.

Storing transactions in Engage will allow you to segment contacts based on what they purchased, when, and how much was spent. Use this for personalised messaging, automated marketing programmes and loyalty systems.

Not only can you store purchase data in Engage but you can use transactional databases to store any data where there is a one-to-many relationship between contacts and the data, for example, logging multiple phone conversations against a single contact.

Transactional Data

This release includes the ability to create a transactional database as well as to view and edit transactional data within Engage. Imports, merging and filtering are scheduled for the December release.

You can create transactional databases and view transactions via the “Manage Transactional Data” link on the Database dashboard.

External databases and CRM systems can be integrated with Transactional Databases in Engage via the Engage API. Using the Engage API makes it easy to keep Engage in sync with your database automatically.


CAPTCHAs have been given a revamp in this release.CAPTCHA stands for “Completely Automated Public Turing test to tell Computers and Humans Apart”. They can be used to ensure that the user completing the form, survey or event is human and not an automated bot.

It is recommended to add a CAPTCHA if you’re getting strange data that was obviously not typed in by a person or if you want to stop automated submissions on competition entry forms.

Rather than adding CAPTCHAs via the settings page it is now added via the field dropdown as you would add any other field.

Add CAPTCHA field

This means that you now have control over the question text. Ubiquity have also added additional options for type and description.

CAPTCHA options

Type includes the standard Character option, but also includes a new Math option where users must solve a basic math problem before submitting the form.


The description appears below the CAPTCHA and can be useful in providing instructions as to what CAPTCHAs are and what users need to do in order to fill them out.

CAPTCHAs are now processed alongside the other fields when submitting the form. Previously they were processed first so you would have to successfully complete the CAPTCHA before it would tell you that mandatory fields were not completed, now it will return errors for the CAPTCHA and other fields at the same time.

If you have an existing CAPTCHA on a form, survey or event we recommend that you migrate this over to the new format – simply uncheck the CAPTCHA checkbox on the settings page and add a new CAPTCHA field via the add field dropdown. The old CAPTCHA system will be deprecated and removed in a future release.

4. Other Enhancements

Other Enhancements:
When adding new fields in imports previously Engage would show you the design database screen. With lots of fields it could be painful to scroll all the way to the bottom of the page to add your new fields. Now adding fields occurs on the same page as mapping fields.When you choose [New Field] against one of the fields you’re mapping then a new section will appear for you to define your new field.

Adding new fields via imports

Articles in emails with URL field types now have an Insert Engage link button alongside the media manager button. This makes it easy to add a link to your Engage Form, Survey or Event to your email.

EasyEdit URL field

If a contact has participated in a TXT programme, the contact history will now show the whole conversation instead of just the initial inbound message.

Event options

5. Tweaks and Bug Fixes

Tweaks and Bug Fixes:
EasyEdit template share field types would hang when trying to add a share to social in Firefox. This has been fixed.
Triggered email EasyEdit article filters were missing the disable toggle. This has now been added.
Mobile number field types are less strict now to account for new mobile number formats. The field will now accept any New Zealand number so long as it starts with 02, or any international number with an area code other than +64.
In imports you can now map fields containing TRUE/FALSE/0/1 to yes/no fields in Engage.
If you leave a space at the end of a URL then it can break in some email clients e.g. Hotmail. Engage will now strip spaces off.
The View Recipients link on the Mailout dashboard could throw an error if the Mailout had not yet started sending.
If you insert images via the Media Manager into an editable section and your account has a custom host header on it, then the images would sometimes not display. This has now been fixed.
International mobile numbers now work correctly throughout Engage.
You can view the edit history of nearly all items in Engage from their details/settings page. This has now been tidied up to be more consistent.
When viewing recipients of an automated mailout you’d sometimes get the same row duplicated a number of times. This has now been fixed. We’ve also added the ability to filter by send date for an automated mailout, and added this to the filter when you click through from the report to view the recipients.
You will now be able to interact with Insight charts while other charts on the page are still loading – you no longer have to wait for them all to finish.
Automated Mailout link clicks were not showing up in contact history. They will now.
On Form confirmation and inactive pages, changing from a redirect to showing copy would have the input box disabled. This now works correctly.
We have fixed an issue where copying an email template from one account to another account would sometimes not change in the new links you specify.
API tokens can no longer be copied between accounts using the create user dialog.
Automated TXT Out history now no longer shows the send history in the history section on the details screen. You can see the send history on the Send History page on the automated TXT Out dashboard.
Can now download more than 1,000 TXT messages at a time.
In a TXT programme the Send TXT step now defaults to the correct mobile number merge field.
Previously there could sometimes be quite a bit of a delay between when an email was actually delivered or read, and when the widget would update to show that. We have sped this up considerably.
Automated TXT Outs now have an activate dialog at end of the wizard, just like automated Mailouts have.
You can now use the same opt in field for multiple TXT programmes.

Leave a Reply