Next release

For an EmailingTemplate en EmailingDocument it is possible to convert the stylesheet to inline styles or to keep the style blocks. This setting is useful for compatibility of the layout in several e-mail clients. This setting was only available in the user interface.

Since version 2.12 it is possible to change the setting for converting the stylesheet. This is a property is called useinlinestyles and is available in the objects EmailingTemplate and EmailingDocument. You can update the setting with the methods EmailingTemplate_update and EmailingDocument_update.

In the previous releases using the SOAP API it was only possible the create an import using an remote http or ftp location. starting with this release it is possible to add data to the import using the Import_addData method. Make sure your total SOAP request isn't larger then 128Mb because the server won't accept that.

Abuses and unsubscribes are important results for an e-mailing. Of course you want to have an indication whether this occurred and for how many destinations this occurred. Unfortunately there was not yet a clear indication how many unsubscribes you had and how many abuses.

To make this all much more clear we lifted the unsubscribes and abuses to the same level as clicks and impressions. This makes the overview easier to understand. To complete this we replaced the waterfall such that the abuses and unsubscribes are also visible in that overview.

If you load a content feed into your https website, you might have problems because https and http content are mixed. This will result in a warning in your internet browser.

In version 2.12 of the application we will serve the images in your content feed via an https connection, to make sure that you do not run in trouble when using the data on your website.

Some big e-mail providers like Hotmail have the possibility to register abuses. When you are registered with the feedback loop program, the application is able to process these abuses automatically. You are able to view the abuses from a single (bulk)mailing, but it was not possible to create a selection with abuses, thus you are not able to export them.

Since version 2.12 it is possible to make selection based on abuses. Now you have the possibility to select the (sub)profiles that have registered an abuse. You can export the data and use it for example to unsubscribe those e-mail addresses from another system.

It was already possible to set the properties of a email/pdf/web document using the *_setProperty method. If multiple properties had to be set multiple calls to this function had to be made. Now there's a new function *_setProperties() where you can set all the properties of a document using one call.When the SOAP server detects that the client supports gzip compression, the server will send the response compressed to the client. This will reduce the response size thus reducing the time needed to transfer the data to the client.

In the application you can use directories to store files in the profile. When one of profiles has the right directory structure, it is possible to copy this to all profiles of the database or selection. This was working correctly, but it was not very fast. Since version 2.12 we have improved the speed of copying the directory structure.

In the past the Profile_updateSubprofiles, Database_updateProfiles, View_updateProfiles, Collection_updateSubProfiles and MiniView_updateSubProfiles methods only returned the number of created or updated (sub)profiles. Quite often a search had to be done to get the updated/created (sub)profiles. To fix this these functions now return a Collection object with the ID's of the changed or created (sub)profiles. 

 

Because of the way the result is returned this change is backwards compatible and doen't need any changes to the client side code.

A database (and the same holds for collections and (mini)selections) has a setting for permitting the sending of bulk mailings, in the software known as intensions. It is a protection mechanism to make sure that you cannot send a bulk mailing to selection that holds the unsubscribers.

If for example you want to set the intension to permit e-mailings for a selection, a field in the database must be set to the type e-mail. When no field in the database is marked as e-mail field, the option bulk e-mailing is not clickable. This raised a lot of questions, because it was not explained why it is not clickable.

Since version 2.12 the dialog has been improved. When an option is not clickable, you will get a warning that explains the reason and you can click on a hyperlink to change the type of the field.

In the software it is possible to create or edit follow ups in a database or an e-mailing document. One of the possible follow up actions is to change the data of a (sub)profile. E.g. an interest can be changed as a result of an e-mailing. However it was not clear which value should entered to enable (or disable) a specific interest.

Since version 2.12 dropdown fields are used in the case of interests or multiple choice fields. For the multiple choice fields you can select any of the options and for an interest you have to choose "yes" or "no". In this way it is much easier to build a correct followup.

In the software it is possible to see or modify the delivery settings. The application contains a dialog with information about the IP-address used to send e-mailings and other delivery settings e.g., how many times we try to deliver a message. It is also possible to view and change the picserver (domain used for serving images) and envelope domain. All these functions were placed in the Extra menu of the E-mailings section of the software.

Since version 2.12 we moved those delivery settings to the Admin section of the software. We combined the settings in one dialog. Besides that it is now also possible to set a picserver domain or envelope domain per account instead of configuring it for a complete environment. Using this new settings, you can optimize your deliverability. Because you can use a subdomain of your own domain for the envelope and picserver domain. This make your message (headers) more consistent and it will help your e-mail to reach the inbox of the receiver.

In the software it is possible to add a DKIM key for your domain. When the key is added, you were redirected to the tab for editing the key. It was unclear what had to be done with this information.

Since version 2.12 we have improved the dialog. When the key is added, you will get a confirmation that the DKIM key has been created. We have added some instructions to explain what you have to do with this key. It is now also possible to send an e-mail with these instructions to someone who has to perform the necessary changes.

Until version 2.12 it is not possible to retrieve a personalized PDF document via the SOAP API. One of the properties of a PdfDocument object which was returned by the SOAP API is the source of the document.

Because the EmailingDocument_source and WebDocument_source functions already existed, we decided to include the function PdfDocument_source. With this change, the property source of the PdfDocument object is not available from version 2.12 and it is replaced by the method PdfDocument_source.

In the past some users accidentally entered a complete HTML document in their textversion, this was most likely not what the user tried to achieve.

In version 2.11 of the application we added a warning for this problem. Now when you try to store a text version which contains HTML tags a warning is given and the text version is not saved.

Phishing (see wikipedia) becomes a bigger problem everyday, because of that spamfilters and even e-mail clients get more strict about validation of hyperlinks. One of the problems that occurs is that links in an e-mail have a label which contains the link to which it points eg:

<a href="http://www.mastercard.com/">www.mastercard.com</a>

However to measure clicks the underlying links are replaced by our system, this tranforms the link in for example.

<a href="http://www.example.org/892035820398/register">www.mastercard.com</a>

To a spamfilter the above example looks like a phishing attempt so this mail is likely to be moved to the junk-email or a warning might be given will the links remain disabled.

To help our users to get their e-mail delivered we added a check for this to version 2.12 of the software. This problem will be reported in our normal spam report, so please review your e-mailing and its spam report.

The PxWidgets library will now use a HTML5 header instead of a XHTML strict header. XHTML is not developed any further and the HTML5 header is more compliant with our software.

When you are an application admin, you can change the envelope address which is used as the underlying sender of the e-mails. This address is used to receive bounces, process abuses and unsubscribes. So its very important that you setup this domain correctly.

To aid our users in settings this up correctly we now (from version 2.12) check the envelope address before storing it. This to make sure that e-mail which are sent by you are always sent from a correct envelope address. A correct envelope address has a MX record pointing to one of our servers.

Sometimes users make mistakes will configuring their account, their e-mailing, their dns or they accidently added content which is not supported by e-mail clients or gets a high spam score. Problems like this influence the deliverability and thus the chance that your e-mail reaches the inbox of the receiver becomes smaller.

You want your e-mail to arrive in the inbox, so we added some extra steps to help you to improve your e-mail and your settings. We warn you when you use unsupported techniques, or when you have an incorrect SPF record set-up. If there are errors which will damage your reputation too much, we do not allow you to send this message this to make sure that you do not send mails directly to the spamfolders.

Sometimes it is desirable to use the parameter from the URL. For example: if you want to display a specific image based on a parameter. However this was only possible when you had extensive knowledge of JavaScript.

From version 2.12 it is possible to use the parameters from the URL within smarty. This can be done with {$smarty.get.<parametername>}. In this way it is much easier to use the parameters from the URL in your webdocuments.

In the past some customers had problems with e-mailings not arriving. Unfortunately most of the time this is caused by the receiving side. Most of the time extra information was available at our servers but could not be viewed by our users.

In this version (2.12) we already included the time at which the e-mailing was delivered, we decided to give our users all the information we have. We now also show attempts to deliver an e-mailing and much more details about errors that occurred.

In some cases we perform multiple attempts to deliver an e-mailing, these attempt are now visible in the application and can be used to find the reason for certain delays or other potential problems.

Besides that we also show as much information as possible whenever an error occurs. We show the address to which the e-mail was sent, the current e-mail address (if it changed). And if the domain contains a certain misspelling which we have seen before we suggest a correction of the e-mail address. And of course the message we got back from the receiving, the error code and its meaning.

We hope this helps our users to enjoy and use the software.

Up to version 2.11 of the software the language in which the software is displayed is based on a list of priorities in our application. However this is not always the desired solution.

Starting from version 2.12 we always pick the language which is supported by our platform and has the preference of the user. We hope that this will the make application more user friendly.

Added emailing setting “Cache external images”. When checked all externally hosted images are stored and hosted by Copernica. Also when the cache option is enabled you can even use it in combination with the embed option, then the images will be embedded in the email, previously externally hosted images where not embedded.

The advantage of caching the images are that the image will always be available, because they are stored by Copernica. In other words when the server which hosts the external images is not available or the images gets removed from the server, they will still display in the emails when the cache option is enabled. 

Until version 2.12, it was possible to see when the e-mail was sent to the profile. This was not the timestamp that the message was really sent, but this was the timestamp that the message was compiled.

In version 2.12 we added the timestamp of delivery. This is the timestamp when the message is really delivered. In the user interface, it is also possible to see the response of the server when holding your mouse cursor on the delivery timestamp. When it is not the first attempt, the attempt will be displayed.

When editing the content of a text block, two different text editors can be used: the Rich Text Editor (which has a MS Word look and feel), and the plain HTML editor (more similar to good old Notepad). However when the HTML editor was used to edit the content under E-mailings and then stored, the editor view would always switch to the Rich Text Editor. We considered this as unwanted behaviour.

From version 2.12 this has changed. You will stay in the editor view where you already were. This has been changed in both the E-mailings and Websites section. We wish you happy editing. 

Since the first version of the software it is possible to set the access right 'style admin'. This right allows the user to send mailings, or give permission to send a mailing to a user that is not a style admin.

When a regular user without style admin rights created a new document, he or she was allowed to set the access rights of mailings and overruled the function of not being a style admin. This is undesirable behavior.

From version 2.12, only style admins are allowed to set access rights for mailings. When the user is not a style admin, the options are not clickable. By default, newly created users are style admins, so most users are still able to set the access rights just like now.