ASP Releases

Inxmail Professional 4.7.0

The newly released Inxmail Professional 4.7.0 is specifically dedicated to meeting the requirements set out in the new EU General Data Protection Regulation (GDPR). Go to www.inxmail.com/gdpr to learn more about how these requirements affect email marketing.

Changes regarding conclusions about the behaviour of individual recipients

We’ve upgraded our email marketing solution to come in line with the requirements set out in the GDPR, helping you lay the groundwork for GDPR-compliant email marketing. The new version of Inxmail Professional allows you to obtain and manage person-based tracking permissions in your (standard) mailing lists on a recipient level.

Release 4.7.0 includes all of the standard features required for GDPR-compliant link tracking. The following update contains additional technical changes mandated in the GDPR as well as a new feature to meet the obligation to provide documented proof regarding tracking permission.

Dynamic lists can also be used with anonymised tracking in compliance with the GDPR. Conclusions about the behaviour of individual recipients are not possible using such lists. The standard key indicators will continue to be accurately captured to provide a reliable basis for measuring performance.

Please take a look at our GDPR Guidelines, which you can find at here, to learn more about how the GDPR will affect individual features of Inxmail Professional.

Please find below a list of sample applications for (standard) mailing lists in Inxmail Professional.

Practical examples: Tracking permission in Inxmail Professional

Obtaining tracking permission

Dynamic subscription page (JSPs) Obtaining tracking permission

You are looking to obtain permission to track an individual recipient when he/she subscribes to your newsletter on the dynamic subscription page (JSPs).

  • The template used to set up a dynamic subscription page (JSPs) offers the new element ‘Tracking Permission’.
  • Pressing the Update button allows you to add the ‘Tracking Permission’ element to existing dynamic subscription pages (JSPs).

HTML subscription pages (subscription servlet): Obtaining tracking permission

You are looking to obtain permission to track an individual recipient when he/she subscribes to your newsletter on the HTML subscription page.

  • You can add the system field ‘Tracking Permission’ to subscription pages generated as HTML pages using the subscription servlet.

Newsletter: Obtaining tracking permission

You are looking to obtain tracking permission via a link contained in your newsletter.

  • You can use a tracking permission link in the mailing to obtain your subscribers’ permission for person-based tracking.
  • Clicking the link takes the subscriber to a landing page. You will need to create or specify this page.

Withdrawing tracking permission

Newsletter: Withdrawing tracking permission

You are required to provide a link in your newsletter that allows subscribers to withdraw their consent to person-based tracking.

  • You can use a special type of link that enables subscribers to withdraw their consent to person-based tracking.
  • Clicking the link takes the subscriber to a landing page. You will need to create or specify this page.

Managing tracking permission

Setting the ‘Consent for person-based tracking’ advanced property

You want to configure the settings so that it is not possible to draw conclusions about the behaviour of individual recipients unless tracking permission has been given.

  • This can be done using a global default setting that is inherited by all lists. You can overwrite the default setting in any list.

Viewing and editing tracking permissions in the recipient table

You want to view and edit tracking permissions in the recipient table of mailing lists in order to respond quickly to enquiries and fulfil your duty of disclosure.

  • You can view and edit the status of tracking permissions in the recipient table of mailing lists.

Defining tracking permissions in actions in response to recipient reactions

You wish to carry out certain actions on the basis of a recipient reaction (e.g., a ‘Click on a certain link’ event) without permission to track the recipient. You are doing this in order to conduct another legal transaction (such as a purchase (product download) or unsubscribing a recipient from a list).

  • You can tick a box to specify that an action should be executed even if tracking permission has not been given.
  • Existing actions will continue to be executed without tracking permission. You will need to make configuration changes to ensure that existing actions are not carried out with respect to recipients who have not given tracking permission.

Transferring/synchronising tracking permissions between different lists

You wish to transfer a recipient’s tracking permission from one mailing list to another in order to synchronise the tracking permissions in the two lists.

  • There are two new events to trigger an action:
    • Grant tracking permission
    • Withdraw tracking permission
  • There are three new actions:
    • Grant tracking permission
    • Withdraw tracking permission
    • Apply tracking permission
  • You can only select one target list per action in which tracking permission will be given/withdrawn.
  • The ‘Import tracking permission’ action allows you to specify the source list from which tracking permission will be imported into the target list.
  • You can use copy and paste to transfer the tracking permission to other mailing lists.

Working with target groups

New target groups based on tracking permission

  • Recipient has given permission for person-based tracking (hasTrackingPermission)
  • Recipient has not given permission for person-based tracking (hasNoTrackingPermission)

You wish to create two target groups:  One target group will contain recipients who have given tracking permission, while the other will include recipients who have not provided tracking permission.

  • There are two new target group functions:
    • Recipient has given permission for person-based tracking (hasTrackingPermission)
    • Recipient has not given permission for person-based tracking (hasNoTrackingPermission)
  • You can use the target groups in all target group agents.
  • You will need to assign the relevant target to a mailing list.

Changes to existing target groups based on recipient reactions

You want to create a target group on the basis of recipient reactions. This will only contain recipients who have (not) opened or clicked on the mailing. In this example, you can only select recipients who have given tracking permission.

  • If you have enabled the ‘Include setting for person-based tracking’ property, target groups that are based on recipient reactions only contain recipients who have given tracking permission.

Importing and exporting tracking permissions

Setting tracking permission via manual recipient import

You would like to update and manually import tracking permissions.

  • You can manage the import of tracking permissions in the Import wizard for manual import.

Setting tracking permissions via Import Automation

You would like to set and update tracking permission via Import Automation.

  • The workflow steps for Import Automation allow you to manage the import of tracking permission.
  • Existing automated imports will continue to function without the need for changes.
  • If you import tracking permissions, the existing settings for tracking permissions will be overwritten.

Exporting tracking permissions

You want to export tracking permissions together with the other user data from a list so that you can further edit the attribute working outside of Inxmail Professional.

  • You can select tracking permission as an additional export attribute in the Export dialogue box.

Managing tracking permissions via the REST API

Setting tracking permissions with the import of recipient data via the REST API

You wish to import large volumes of recipient data (including tracking permissions) from another system into Inxmail Professional via the REST API.

  • You can set tracking permission via the REST API when importing recipient data in the CSV format.
  • You can change the tracking permission when re-importing data.

Accessing tracking permissions with recipient data via the REST API

You want to access any number of lists page by page (including certain recipient attributes and tracking permissions) via the REST API in order to synchronise the recipient data from Inxmail Professional with the data in another system.

  • Tracking permission is documented in every list.

Setting tracking permissions during the subscription process via the REST API

You want to set tracking permission during the subscription process via the REST API. This will allow your subscribers to provide their consent to person-based tracking.

  • You can set tracking permission via the REST API when they subscribe.

Accessing data of recipients with tracking permission filtered by change data via the REST API

You wish to filter the data of recipients who have given tracking permission by change date. As a result, you will only be able to access recipients who have made changes.

  • You can enter a start date for integration (date format: ISO-8601).
  • Once you have entered a start date, all recipient data that has been modified will be shown starting from the specified date.

Managing tracking permissions via RPC API

(These functions are available from API version 1.16.)

RPC API: Subscription with tracking permission (SubscriptionManager)

You want to set tracking permission during the subscription process via the RPC API. This will allow your recipients to provide their consent to person-based tracking.

  • You can use a new method available in SubscriptionManager to set tracking permission when the recipient subscribes.

RPC API: Importing tracking permission (BatchChannel)

You wish to import large volumes of recipient data (including tracking permission) from another system into Inxmail Professional via the RPC API.

  • You can set tracking permission in a list via BatchChannel.

RPC API: Setting, modifying and accessing tracking permission (RecipientRowSet)

You wish to set, modify and access tracking permissions via the RPC API in order to synchronise your recipient data with other information.

  • You can set, modify and access tracking permissions via RecipientRowSet.

Upgrades

  • All relevant API methods now deliver consistently sorted collections (RowSets and BOResultSets). 
    Up until now, certain methods would return RPC API collections whose elements were not consistently sorted (for example, the final results could be sorted first by list and then by attribute.) As a result, it was not possible to develop reliable synchronisation mechanisms.
  • The process of identifying the address to which the email was originally sent as a bounce was improved.
  • Release information is available directly in the Inxmail Professional cockpit.
  • It is possible to sort JSPs by type (subscription type, profile type, etc.).

Bug fixes

  • Recipients tagged as ‘unavailable’ can re-subscribe to a list. The ‘Hard bounce’ tag is removed once a recipient has subscribed to any list using the double opt-in (DOI) procedure and the confirmation email did not generate a hard bounce again.
  • Email attachments containing (special) characters that are not found in the ASCII table in their file name are correctly encoded and can be opened by the recipient; starting with Inxmail Professional 4.6.2, these characters were incorrectly encoded and the attachment could not be opened by the recipient.
  • Revised error message for webspace connection error.
  • Bug that occurred occasionally during colour selection has been fixed.
  • Import Automation option ‘Import file again next time’ did not function because file name has been changed. This option has been removed.

REST API:

  • Access tracking permissions with recipient data via the REST API. This is possible with or without recipient attributes. You can also filter by change date.
  • Set tracking permission when recipient subscribes.
  • Set tracking permission via CSV import.

Updates