The following considerations relate to specific ESPs. Note that additional considerations and limitations are documented in the RPI Plugin Features Matrix – please see that document for further information.
•Salesforce Marketing Cloud:
o When executing an email offer containing an embedded table asset in an Oracle environment, and when the channel's Import via file setting is checked, please ensure the channel's Disable field quote wrapping property is also checked.
o The email’s Sender address must be validated at the SFMC Portal.
o At execution of a Salesforce Marketing Cloud email offer, the data extension and email objects' names thus created are preceded with the following:
‘[Interaction name]-[Activity name]-‘
If the interaction name is the same as the activity name, the objects are preceded with:
‘[Interaction name]’
o If Encrypt exported file was checked at the channel, the export file generated at email offer execution will be encrypted in accordance with the specified public key and encryption type. Execution will fail if the key is not valid. If encryption is successful, the encrypted file is uploaded to SFMC with the following file naming conventions:
[GUID].csv.pgp/gpg
If the channel's File transfer activity name property is valid, the file is decrypted and data loaded into the SFMC data extension.
o At channel synchronization Task execution, if the channel's Decrypt imported file property is checked, the supplied Tracking extract activity name is used to generate disposition data. The supplied File transfer activity name is used to encrypt disposition data which is saved in accordance with the channel's configuration. Saved files are downloaded and decrypted using specified the Encryption private key, in accordance with the selected Encryption type. If the specified key is not valid, the file import process fails.
•SendGrid:
o On clicking an unsubscribe link in a SendGrid-delivered email, the recipient is redirected to the URL configured in the SendGrid account’s Apps Subscription Tracking Settings Custom Landing Page URL property.
o No image hosting is supported. At email offer execution, if the offer contains an RPI image asset or private external content provider-supplied asset, a warning is displayed:
‘The channel must be configured with an external content provider in order to use image assets within the email content'
At this point, you can proceed with or cancel execution of the email offer.
o When utilizing a table smart asset within a Text email offer, spaces within table content may be truncated upon receipt of the email message. This issue does not appear within the Offer Designer and only occurs upon email execution using SendGrid's SMTP API v2 service.
o If configuration setting SendGridSaveEventFiles is set to False, any SendGrid JSON files are deleted after successful processing by the SendGrid callback service. If the setting is True, JSON files are moved to the ‘SendGridEmailResults\[Tenant ID]\Processed folder’ after successful processing by the SendGrid callback service.
•CheetahMail:
o No image hosting is supported. At email offer execution, if the offer contains an RPI image asset or private external content provider-supplied asset, a warning is displayed:
‘The channel must be configured with an external content provider in order to use image assets within the email content'
At this point, you can proceed with or cancel execution of the email offer.
o Email offer execution through a CheetahMail channel can take longer than other email providers – a 15-minute delay in fulfillment is not uncommon.
o Note that a delay of up to a day can occur prior to the availability of CheetahMail results.
o Use of rule smart assets in email content is supported. Doing so utilizes one of the channel's data fields. If no available data fields exist, execution will fail.
•Acoustic:
o No image hosting is supported. At email offer execution, if the offer contains an RPI image asset or private external content provider-supplied asset, a warning is displayed:
‘The channel must be configured with an external content provider in order to use image assets within the email content'
At this point, you can proceed with or cancel execution of the email offer.
o Links that contain a hashtag will result in link click tracking not capturing any portion of the link that precedes the hashtag.
•SparkPost:
o The following HTTP headers are added to emails sent using SparkPost:
§ x-userid: the SparkPost account Customer ID.
§ x-rpdateofcommunication: timestamp at which the email was sent.
§ x-rpclientid: the Redpoint client ID.
§ x-rpchannelexecutionId: the Redpoint channel execution ID.
•Instiller:
o During email offer execution using an Instiller channel, any existing email profile parameters remain as stet, and are not updated.
•Responsys
o Only 500 profile extensions are allowed per profile list.
o Dynamic attributes in links are not supported.
•Dotdigital
o External dynamic content is supported, up to 20 placeholders per email body.
o External dynamic content and dynamic content are not allowed in plain text emails.
o It is necessary to create new Address Book for each 5000 subscribers per account.
o New custom fields of the following type can be created:
§ Boolean allowed up to 50 per account.
§ Date/time allowed up to 49 per account.
§ Numeric allowed up to 50 per account.
§ String allowed up to 245 per account.
o String or text based custom fields can only hold up to 255 characters
o The Sender address at email offers is not used, as Dotdigital uses the default From Address for all campaigns configured at a given account.
•Listrak
o Scheduled campaign delivery is not supported
o The Purpose property has no effect at delivered emails
•Mailchimp
o Maximum number of characters in a text field limited to 255
o Maximum number of merge or custom fields 30
o Table smart assets not supported
o Attribute formatting not supported
o Smart asset inclusion in Subject line not supported
o Dynamic sender details not supported
•Paubox
o No unsubscribe option is available.
o Link tracking is not supported.
o Personalized content is generated by RPI on a recipient-by-recipient basis, which has the potential to detrimentally impact performance.
o A known issue exists, where Open events are raised incorrectly in respect of unopened emails delivered to Gmail addresses.
•Cordial
o If a Cordial channel's Account list setting is blank, a new list will be created with the following name format:
'RPI_<Channel Name>_<ChannelExecutionID>'
Uploaded contacts will be grouped within this list.
If the setting is not blank, contacts will be grouped within the account list matching the provided name.
o The following retryable error codes are supported:
§ Timeout
§ ConnectFailure
§ SecureChannelFailure
§ ConnectionClosed
§ ProtocolError
§ ReceiveFailure
§ NameResolutionFailure
§ SendFailure
§ ServerProtocolViolation
§ KeepAliveFailure
§ GatewayTimeout
§ BadGateway
§ ExpectationFailed
§ RequestTimeout
§ NotFound
§ ServiceUnavailable
§ TooManyRequest
o If the Cordial channel's Custom subscriber key property is configured, Cordial sends emails using the supplied key. Deduplication has no effect on the same. Execution will fail if the Custom subscriber key's name does not exactly match that configured in Cordial.
o Text merge data fields' lengths are defined in accordance with RPI Catalog settings.
o Records are batched in accordance with Batch export and Max export batch size channel configuration settings.
•LuxSci
o Unsubscribe is not supported at the LuxSci email channel. The following states are added automatically to the email suppression table:
§ Failed (unsubscribe method = Failed)
§ Hard Fail (unsubscribe method = Failed)
§ Soft Bounce (unsubscribe method = Bounce)
§ Spam (unsubscribe method = Spam)
o Offer execution will only fail when all of a batch of emails fails to send.
o A tracking record will be inserted into the RPI_LuxSciTracking table when at least 1 email is successfully sent.
o Luxsci supports execution in 'sandbox mode'. Sandbox mode is enabled in the Execution Service configuration file (Resonance.ExecutionService.exe.config) as per the following example:
<sectionGroup name="applicationSettings" type="System.Configuration.ApplicationSettingsGroup, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" >
<section name="RedPoint.Resonance.ChannelPlugins.LuxSci.LuxsciSilentSettings" type="System.Configuration.ClientSettingsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false" />
</sectionGroup>
<applicationSettings>
<RedPoint.Resonance.ChannelPlugins.LuxSci.LuxsciSilentSettings>
<setting name="EnableSandBoxMode" serializeAs="String">
<value>True</value>
</setting>
</RedPoint.Resonance.ChannelPlugins.LuxSci.LuxsciSilentSettings>
</applicationSettings>
When enabled, messages are validated, accepted, and queued for sending within LuxSci but are not sent to recipients.
•Amazon Simple Email Service (SES)
o When an email offer's purpose is set to 'Operational', AWS SES sends emails using the Bulk method.
o When an email offer's purpose is set to 'Marketing':
§ If no contact list is available, AWS SES creates a contact list with the selected Topic. Only one contact list is allowed per account.
§ If a contact list is available, but the supplied topic name is not available, the topic is added to the contact list (the contact list is required so AWS can determine recipients' opt-in or opt-out status by topic).
§ AWS SES send emails using Serial Sends. Serial sends are used to facilitate the insertion of unsubscribe links (AWS SES doesn't support unsubscribe links when using the bulk method). Performance is likely to be slow when using serial sends (a single API call is made per send).
§ When 20 topics already exist, and the provided topic does not, a runtime validation error advises to use an existing topic instead.
§ BCC is not supported.
o The following states are added automatically to the email suppression table:
§ Bounced (unsubscribe method = Bounce)
§ Complaint (unsubscribe method = Complaint)
o Web versions of emails are not supported.
o The Facebook Like button is not supported.
o Sharing of email content is not supported.
o Forward to Friend functionality is not supported.
o Image hosting is not supported.
o SES does not publish an 'Unsubscribe' event when a recipient unsubscribes.
o It is not possible to determine the specific email from which a recipient unsubscribed.
o If a reply-to name is enclosed in parentheses, it is not displayed. E.g. '[John] Doe' will be displayed as 'Doe'.
•Amazon Pinpoint Email
o During execution of an email offer using an Amazon Pinpoint channel, one or more CSV files are uploaded into the specified AWS S3 bucket. Each file contains up to a maximum number of records defined by the channel's Max. recipients per file property. Each file is named 'RPI_[Channel name]_[ChannelExecutionID]_Export_[yyyyMMdd]_[GUID].csv', where [Channel name] is the first 6 characters of the channel's name, and GUID is the first 6 characters of a GUID (excluding hyphens). An Amazon Pinpoint segment is created and named '[Channel name]_[ChannelExecutionID]_Segment'. Segment import jobs are initiated to load files from the defined AWS S3 CSV bucket, with files being deleted once import is complete. An email campaign is created at Amazon Pinpoint, named '[Channel name]_[ChannelExecutionID]_Campaign'. Finally, Amazon Pinpoint sends the emails.
o A record will be counted as invalid when one or more of its attributes contains a value exceeding 100 characters.
o A maximum of 40 custom attributes can be created.
o Each custom attribute's value must not exceed 100 characters.
o BCC is not supported.
o Dynamic sender address is not supported.
o Reply-to address is not supported.
o Share Content is not supported.
o Forward to Friend is not supported.
o The use of table smart assets in email content is not supported.
o Number formatting withing email content is not supported.
o URL shorteners are not supported.
o URLs are not trackable when personalized.