Acoustic Email
Overview
The following channel-specific fields are shown for Acoustic email channels:
Recipient email: Provision of the attribute that contains recipients’ email addresses is optional; however, you must supply an email address attribute if the channel is to be used for delivering emails to outbound targets sourced from an RPI audience.
Recipient email is optional if the channel will be used exclusively for the sending of emails from a queue activity. Please see the Interaction Designer documentation for further information.
You can browse for an email address attribute using the recent items chooser or File System Dialog, or you can drag an attribute from the toolbox and drop it onto the field. You can select an attribute from an auxiliary database (including a PII vault). Having done so, you can clear the selected attribute. You can also view details of the attribute in the File Information dialog.
Model project, exists in table, and parameter attributes are not supported in this context.
Web service address: mandatory, and a maximum of 100 characters. The Acoustic web service address.
Host server URL: mandatory, and a maximum of 100 characters. The host server is used for tracking links clicked within delivered emails. Defaults to
http://sdm3.rm04.net.Client ID: this mandatory text property allows you to specify the client ID to be used when connecting to the Acoustic service. It accepts a maximum of 100 characters.
Client secret: this password-masked mandatory text property allows you to specify the client secret to be used when connecting to the Acoustic service. It accepts a maximum of 100 characters.
Refresh token: this password-masked mandatory text property allows you to specify the refresh token to be used when connecting to the Acoustic service. It accepts a maximum of 256 characters.
Export FTP location: this mandatory property allows you to choose an existing FTP location to which exported files will be uploaded.
Group ID: mandatory, and a maximum 100 characters. This setting must reflect the value configured at the Acoustic website.
Opt out URL: optional, and a maximum of 1000 characters. Facilitates navigation to an Acoustic landing page, where opt-out from communications can be requested.
Max send batch size: an integer property that defines the maximum number of records that can be sent to Acoustic at a time. The property’s value defaults to 1000.
Auto-suppress: this checkbox, checked by default, controls whether the system should automatically suppress (i.e., not send mail to) any individual whose email address is registered in the email suppression table (as defined by system config setting
EmailUnsubscribersTable).Remove default text footer: checkbox, checked by default. When you check Remove default text footer, the footer appended automatically by SFMC at email execution is not added to the end of delivered emails. When unchecked, the field is added.
Custom suppression table: checkbox, default unchecked. This field allows you to specify that the email channel is to use its own custom suppression table, rather than the default email suppression table (defined by system configuration setting
EmailUnsubscribersTable). Checking the field toggles on Suppression table name.Suppression table name: this text field is available and mandatory when Custom suppression table is checked and can be a maximum of 50 characters. Any characters entered must be database-valid. When a contact elects to unsubscribe from email communications received via a channel using a custom suppression table, his or her email address is stored in that table. Any other email channels remain unaffected, so emails could still be sent using those mechanisms.
Save XML files: this checkbox is unchecked by default. If checked, Acoustic XML files will be saved to a network path.
XML files external folder: this property is enabled and mandatory when Save XML files is checked. You can select an external folder to which to save XML files generated during execution using the channel.
Outbound upload folder: this mandatory text property accepts a maximum of 1000 characters. It defaults to the value
transact/inbound, and allows you to specify the remote folder location where XML files are to be uploaded during execution.
Advanced tab
The following Advanced fields are shown for Acoustic email channels:
External folder
This optional button allows you to specify an external folder to which embedded image will be uploaded.
Import via file
A checkbox, unchecked by default. Checking this option means that a Redpoint Data Management (RPDM) job needs to be configured at the RPI server to manage the receipt of email results data (in lieu of the standard email results reporting mechanism). This approach is best suited to high volume email environments. If system configuration setting DataManagementDataConnection is set, Data Management will use its value as the connection string when executing Data Management jobs. If the setting is not set, Data Management will use the default Data Connection as configured in the RPDM project.
Setup and configuration of the RPDM job is beyond the scope of this documentation.
In order for Import via file to be used, values must be provided for the following system configuration settings:
DataManagementCredentialsDataManagementServerNameDataManagementServerPortDataManagementUploadDirectory
When Import via file is checked, the following results are returned via the RPDM job:
Opened
Unsubscribed
Click Through
Forward to Social
Forwarded
Hard Bounce
Soft Bounce
Other Bounce
Import table suffix
This optional field is available when Import via file is checked. It is appended to the name of the import table used by the RPDM job, in situations where more than one channel makes use thereof. If provided, the value entered must be database-compatible and can be a maximum of 16 characters in length.
Import FTP location
This property is available when Import via file is checked. It allows you to specify a specific FTP location from which email results are to be sourced when RPDM is used to gather channel results. If no FTP location is specified, the default is used.
A dropdown list, the property is populated with FTP locations configured at the current RPI tenant. No value is selected by default. On selecting an FTP location, a Clear button is displayed; selecting it clears the chosen FTP location.
Request timeout
This property is set to a default value of 60 and accepts a minimum value of 3. It represents, in minutes, the amount of time for which an activity will wait for API requests to complete. At execution of an email offer in an interaction workflow, or a channel synchronization job, RPI will continue to send requests to SendGrid until a successful response is received or timeout period elapses.
Enable trace
This checkbox is unchecked by default. When checked, API requests and corresponding replies from the email service provider are logged. At execution of an email offer in an interaction workflow, or a channel synchronization job, if checked, all requests made to SendGrid are logged.
This feature should be used only when troubleshooting to avoid logging an excessive amount of data to the database. A message displays when Enable trace is selected, which states “Enabling this option can impact performance and potentially persist PII data within the trace data”.
When Enable trace is checked at a SendGrid channel, copies of any related MailMerge files will be created and stored at
C:\temp\RPI\Emails\SendGrid\.
Move hashtags to end of URL
This checkbox, unchecked by default, allows you to specify that any hashtags (#) within email links are to be moved to the end of the URL in which they occur.
This property will only be applied if a Google Analytics or PURL web adapter is attached to the channel.
Upon receipt of the email, any link URLs containing hashtags URL will be reformatted as per the following example:http://www.redpoint.net/products/#interaction would be reformatted as https://www.redpoint.net/products/?utm_source=RPI&utm_medium=Email&utm_content=0&utm_campaign=Test#interaction.
Personalized content queue
This property allows you to select a queue provider from a list of the currently-configured Realtime Queue Providers, to which personalized content will be sent. Its provision is mandatory.
Personalized content queue path
Having selected a queue provider, you must specify the path of the queue to be used at the same.
Web Adapters are supported at the channel.