Skip to main content
Skip table of contents

LuxSci Email

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

General Tab

Re-subscribe contacts: as per SFMC email channel.

Channel Specific Tab

Recipient email: as per SFMC email channel.

The following properties are exposed within the Service Credentials section:

  • Host: this mandatory text property defaults to the value 'rest.luxsci.com'. It accepts a maximum of 1000 characters. It represents the API host URL used to connect to the LuxSci service.

  • Username: this mandatory text property accepts a maximum of 100 characters. It allows you to specify the username to be used to connect to the LuxSci service.

  • Password: this password-masked text property accepts a maximum of 100 characters. It is used in conjunction with Username when connecting to the LuxSci service.

  • API token: this mandatory text property accepts a maximum of 100 characters. It allows you to specify a user API token, which is also used when connecting to the LuxSci service.

  • Secret key: this password-masked text property accepts a maximum of 100 characters. It is also used when connecting to LuxSci.

  • Secure message: this checkbox allows you to specify that message recipients who receive emails via the channel will need to log into the LuxSci SecureSend Portal to view the message. Note that use of this feature is intended only for low-volume sends.

The following properties are exposed within the Suppressions section:

  • Auto-suppress: as per SFMC email channel.

  • Custom suppression table: as per SFMC email channel.

  • Suppression table name: as per SFMC email channel.

The following property is exposed within the Miscellaneous section:

  • BCC email address: as per SFMC email channel.

  • Max send batch size: this numerical property defaults to 1000, and accepts a range of values from 10 to 10,000. It allows you to specify the maximum number of recipients to be sent at a time to LuxSci.

  • Max send threshold: this numerical property defaults to 10, and accepts a range of values from 1 to 30. It allows you to specify the maximum number of concurrent connections to be used when sending emails.

  • Max events batch size: this mandatory numeric property allows you to define the maximum number of email events that can be processed at a time. It defaults to 10,000 and accepts a maximum value of 20,000,000.

  • Data sync time limit: this numeric property accepts values from 10 to 1000. It defaults to 60. It represents the time limit in minutes for which the data sync task will be able to get available email event details.

  • Import event threshold: this numeric property accepts values from 1 (the default) to 10. It represents the maximum number of concurrent connections to be used when importing event data

  • Max mail merge batch size: Max mail merge batch size: this numeric property defaults to 1000, and accepts a range of values from 1000 to 5000. It represents the maximum number of contact records to process within a mail merge batch.

  • Template retention period: this numeric property defaults to 7, and accepts a range of values from 1 to 60. It allows you to specify the number of days after which LuxSci templates will be deleted (RPI-created LuxSci template are deleted by Housekeeping).

  • Custom headers: this property allows you define custom headers to attach to emails sent using the channel. It consists of a toolbar and a list.

    • Toolbar: exposing the following buttons:

      • Add: clicking this button adds a new custom header to the list.

      • Remove: this button is enabled when a custom header is selected within the list. Clicking it removes the header without displaying an 'Are You Sure?' dialog.

    • List: each row within the list contains the following:

      • Use attribute: this checkbox is unchecked by default. When checked, the value of the custom header for a given target will be sourced from an attribute; accordingly, the Custom header value field is replaced by an attribute file property.

      • Custom header name: this mandatory text field accepts a maximum of 100 characters. It accepts alphanumeric and underscore ('_') characters.

      • Custom header value: this text field, which is shown when Use attribute is unchecked, is mandatory when displayed and accepts a maximum of 100 characters.

      • Attribute: this file property is shown when Use attribute is checked and is mandatory when displayed. You can populate the property with a database column attribute using drag and drop, or by browsing the RPI file system. Having populated the property, inline View File Information and Clear buttons are shown.

      • Remove: this inline button is shown on hovering over a custom header. Clicking it removes the header without displaying an 'Are You Sure?' dialog.

Note that a maximum of 2 custom headers can be provided, and they must match the email headers configured in the LuxSci portal's 'SMTP Header Tracking' section.

  • Import via file: this checkbox allows you to specify that importation of email state information will be carried out using an RPDM file import job instead of using the LuxSci API directly. It is unchecked by default. When checked, the Import table suffix and Report destination properties are enabled.

  • Import table suffix: this optional text property is enabled when Import via file is checked. It accepts a maximum of 50 characters. It allows you to specify a suffix that will be applied to the import table's name, to handle multiple channels sharing the same import job.

  • Report destination: this property is enabled when Import via file is checked. It allows you to select an SFTP-only external folder to which report CSV files will be uploaded.

  • State results folder path: this text property is disabled when Import via file is unchecked. It accepts a maximum of 1000 characters. It allows you to specify the server folder path or share where state results data will be placed for processing by the channel's import job.

  • Async report retry: this numeric property accepts a range of values from 1 to 100, and defaults to 10. It allows you to specify the maximum number of retries that will occur when making an asynchronous report request.

  • Convert report date: when this checkbox is checked, any email reports associated with the channel will be converted from UTC to local time. Dates from the same will be recorded in Offer History States.

Web Adapters Tab

All types of web adapters are supported.

Advanced Tab

  • External folder: as per Acoustic email channel.

  • Request timeout: as per SendGrid email channel.

  • Enable trace: as per SendGrid email channel.

  • API call max. re-try: this integer property defaults to 10, and accepts a range of values from 5 to 60. It represents the number of retry attempts to be undertaken if a call to the provider's API fails.

  • Move hashtags to end of URL: as per SFMC email channel.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.