Within the Quince (v4.7) Release, users can now be created and assigned granular rights to the different API endpoints. These users are called Service Accounts and are created through a dedicated entry in the Admin Configuration / Access Management tab. Service Accounts to not have access to the SMC application and can only be used by the API.
When a Service Account is created, an API key and secret are automatically generated. An expiration date can be set, either selected from a predefined list or specified as a custom expiration date.
API filtering can be defined for the Service Account, limiting access only from the listed IP addresses. Organization filtering can also be defined to limit the account’s access to specific organizations.
Once the general settings have been defined, specific operation rights can be assigned for each of the endpoints supported by the API.
When a Service Account is not authorized to use an endpoint, the API will return a ‘403 – Forbidden’ HTTP response code and message.
When using Smart Content algorithms there is a possibility that no products are returned, especially when using a personalization-based algorithm. To ensure a product is returned, the Quince (v4.7) Release introduces the ability to apply a fallback algorithm. Only statistics-based algorithms can be applied as a fallback, as these will always return products.
The fallback algorithm is selected from a drop-down field in the properties of the Smart Content and will automatically be applied when the primary algorithm doesn’t return any results.
Fallback algorithms are supported for email, web and API calls.
It is also now possible to limit the number of items returned in the configuration of a Smart Content of preview type Email. This option was previously only available for type Web.
This is an optional setting, and if not specified, defaults to maximum four items.
Users can now save a Content Block by using a keyboard shortcut of CTRL+S at any time while editing the code of the Content Block. Saving a Content Block this way keeps the editor window open, making it easier to perform intermediate saves. Saving your changes using the Save button closes the editor window and takes you back to the overview of all Content Blocks.
When Content Blocks are used in a message, the preview of the Content Block now displays the SG components defined in the Content Block. This includes SG components of type text, content, image, and button.
Several enhancements have been made to the Data Import capabilities which will allow marketers to:
To achieve the above, the following features have been introduced.
Inverse Lookups: This feature allows data coming from the source file to be transformed into values specified in SMC. This can be applied to:
Import into Custom Events: When importing an external file, the marker now has the option to import the data in a Custom Events list.
An additional option is available in the Import Options settings for this feature. When ‘Import into Custom Events’ is activated, a drop-down allows selecting the Custom Events list. Only Custom Events lists linked to the selected Audience list are available to choose from.
For an import into a Custom Events list, import options are limited and the import will always insert new records in the Custom Events list. Also, there are no settings for duplicate records.
Import into Multiple Lists: With this feature it is possible to import data from the source file into both an Audience list and any linked 1:1 list in a single import.
Three improvements have been made to Custom Events lists:
A field set as Data Selection filter Set in a Custom Events list can now be used as a look up field when defining a data selection used in a message.
Within this release, the data in this Custom Events field can used in the lookup configuration when defining a Data Selection in a message.
Within the Papaya (v4.6) Release, a detailed list of the failed records was added to give insight on the records that failed to sync and why they failed. In the Quince (v4.7) Release, the report can be exported in CSV format by clicking the Export button shown on the History tab of the sync configuration.
The Export button is not available when there are no failed records or when the cause for the failed record is unknown.
Previous releases introduced the ability to upload images, fonts, and JS files. Within the Quince (v4.7) Release, PDF and TXT files have been added to the list of file types that can be stored in the library. Once uploaded, they will be listed in the library and marked with a PDF or TXT icon.
PDF files stored in the Library can now also be selected when adding an attachment to an email.
A new method has been added to the SDK to allow APP developers to have access to the complete payload of the in-app messages. This way, app developers can handle in-app display and store content to build an inbox.
A Journey Overview page now displays details on the last or next planned execution. The current status of the journey is indicated with a color code and the date on which this status has been reached.
Swagger response examples for Tag List Structure and Data API’s have been updated with more relevant information.
A new version of the IOS SDK documentation is available.
The following Use Case videos have been added:
Use Case: Multi Channel Discount Custom Journey – A custom journey to provide a discount offer based on the communication channel preference of a contact.