Skip to main content

SAS CI 360 integration

This guide walks you through connecting SAS Customer Intelligence 360 to Better Email, choosing the export folder, and understanding how repeated exports create revisions.

Before you start​

To connect SAS CI 360, you will need:

  • an external gateway address for the SAS CI 360 access point
  • the access-point Tenant ID
  • the access-point Client Secret
  • an API User ID and API User Secret
  • an admin user in Better Email who can create and edit integrations

1. Gather the SAS CI 360 credentials​

From your SAS CI 360 setup, collect:

  • External Gateway Address
  • Tenant ID
  • Client Secret
  • API User ID
  • API User Secret

In practice, this usually means:

  • creating or confirming an access point / external gateway
  • adding access-point credentials to get the tenant ID and client secret
  • creating an API user for Better Email

2. Set up the integration in Better Email​

In Better Email:

  1. Go to Integrations.
  2. Create a new integration.
  3. Enter a clear name for the integration.
  4. Choose SAS Customer Intelligence 360 as the type.
  5. Optional: under Access, restrict the integration to specific users or groups.
  6. Save the integration.
  7. Enter the five SAS values.
  8. Enable the integration.
  9. Save the integration again.

Better Email handles the access-token refresh flow automatically after the integration is configured.

TODO: Add a screenshot of the SAS CI 360 integration settings with all required credential fields visible.

3. Choose the target folder at export time​

SAS CI 360 export includes a folder-selection step.

At export time:

  1. Open the export flow.
  2. Choose the SAS CI 360 integration.
  3. Select the target folder from the available SAS asset folders.
  4. Complete the export.

4. Understand how revisions work​

SAS CI 360 export is revision-aware.

Important to know:

  • The first export creates a digital asset in the selected folder.
  • Re-exporting to the same folder creates a new revision of that asset.
  • Exporting the same email to a different folder creates a new asset instead of another revision of the old one.
  • Better Email uploads the final HTML as a rendition on the selected revision.

This makes SAS CI 360 a good fit when your team wants clearer version history around repeated exports.

Troubleshooting​

If SAS CI 360 export fails, check:

  • the external gateway address is correct
  • the tenant ID and client secret came from the correct access point
  • the API user is still active
  • the integration is enabled in Better Email
  • the export folder is still available in SAS CI 360