Acoustic Email

Acoustic is a third-party email execution engine used by RPI to deliver interaction emails.

The following channel-specific fields are shown for Acoustic email channels:

•      Re-subscribe contacts: as per Salesforce Marketing Cloud email channel.

•      Recipient email: as per Salesforce Marketing Cloud email channel.

•      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: as per Salesforce Marketing Cloud email channel.

•      Remove default text footer: as per Salesforce Marketing Cloud email channel.

•      Custom suppression table: as per Salesforce Marketing Cloud email channel.

•      Suppression table name: as per Salesforce Marketing Cloud email channel.

•      Save data files: this checkbox is unchecked by default.  It allows you to specify whether Acoustic mail merge data files are to be moved to a 'C:\temp\RPI\Acoustic\[Client ID]\Processed\[ChannelExecutionID]' folder after email offer execution.

Note that, if checked, this means that PII will potentially be stored on an RPI server; accordingly, a warning is shown to this effect at the property's being checked.

•      Content templates shared folder: as per CheetahMail email channel.

•      Save XML files: this checkbox is unchecked by default .  If checked, Acoustic XML files will be saved to a network path

•      XML files shared folder: this text property is enabled and mandatory when Save XML files is checked.  It allows you to specify the path of a network folder where Acoustic XML files will be saved.  At channel execution, the generated XML files will be saved to the following path:

‘[XML files shared folder]\[clientid]\[channelexecutionid]’

The following properties are exposed at the Advanced tab:

•      External folder: this optional Button allows you to specify an external folder to which embedded image will be uploaded. The button initially displays the text ‘Choose external folder’.  Clicking the button displays the External Folders dialog.

A treeview lists all instances of existing external content providers, with the exception of SharePoint Online and OneDrive.  You can expand an external content provider in order to select a single folder.  Having selected a folder, you can click OK to choose it.  You can also click Cancel to remove the dialog from display.

On invocation of OK, the name of the selected external provider and folder is displayed at the property.  Having specified an external folder, you can clear it.

•      Import via file: as per Salesforce Marketing Cloud email channel.

•      Import table suffix: as per Salesforce Marketing Cloud email channel.

•      Import FTP location: as per Salesforce Marketing Cloud email channel.

•      Request timeout: as per SendGrid email channel.

•      Enable trace: as per SendGrid email channel.

•      Move hashtags to end of URL: as per Salesforce Marketing Cloud email channel.

Note that Web Adapters are supported at the channel.

A Validate channels job is created and executed on saving a new Acoustic email channel, or on saving following a change to an existing Acoustic email channel's Recipient email address field.  Full details are as per the Salesforce Marketing Cloud email channel documentation.