As you may know, through the dashboard of the Marketing Suite you can configure the so-called sender domains. In this feature we made a small change.
Log files for Marketing Suite mailings
About each mailing that is sent with Copernica we keep log files. These log files contain information about the number of clicks, bounces, delivery attempts et cetera. Users of SMTPeter already had access to these log files. As of now they are also available and downloadable for users of the Marketing Suite. The log files can also be accessed through our REST service.
To lookup and download the log files in the Marketing Suite, click the Operation logs link in the side menu.
For more information about how to retrieve the log files via our API, please visit our documentation.
Feedback Loops for Marketing Suite
Since this week it is possible for users of the Marketing Suite to set up feedback loops. Feedbackloops allow you to receive real-time notifications when a click, open or error is recorded in a mailing. To get the notifications you place a script on your own server. In the dashboard of the Marketing Suite you then configure where we can find your script, and how often and in which scenarios the script should be called.
For now, people who want to learn more about our feedback loops can hover to the documentation for SMTPeter (the working is 99% the same). The Marketing Suite documentation will of course also be extended with this subject later.
Publisher follow-up actions
A number of improvements have been made in the follow-up actions module of Publisher.
Follow up with Marketing Suite templates.
It is now possible to send Marketing Suite (MS) templates in Publisher follow-ups. Previously, you could only choose templates and documents created in Publisher. To associate a Publisher follow-up action with an MS template, you simply choose the template from the list in the dialog box to set up follow-up actions in Publisher.
More information in the overview
In the familiar overview of follow-up actions in Publisher it was previously almost impossible to distinguish different follow-up actions from another. To remedy this problem, we now display the associated conditions at each follow up in the overview. Later we'll also add to this the number of triggered and executed follow-up actions.