This article describes how to set up the Silverpop Transact connector.

Connector Actions

Action Name AudienceStream EventStream
Send Transactional Email

Configure Settings

Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector.

After adding the connector, configure the following settings:

  • API OAuth2 Client ID: Required: OAuth2 Client ID, please contact Silverpop for assistance.
  • API OAuth2 Client Secret: Required: OAuth2 Client Secret, please contact Silverpop for assistance.
  • API OAuth2 Refresh Token: Required: OAuth2 Client Refresh Token, please contact Silverpop for assistance.
  • Transact API Server Endpoint: Required: your transact server number usually matches your Silverpop Engage Organization Pod Number Please contact Silverpop for assistance.

Action Settings - Parameters and Options

Click Next or go to the Actions tab to configure connector actions.

This section describes how to set up parameters and options for each action.

Action - Send Transactional Email


Parameter Description
Campaign ID (Required)
Recipient Email (Required)
Transaction ID  
Save Column(s)
  • Optional: Optional list of column names from the recipient elements to save to the database in Engage.
  • The column names are case sensitive and have to match what was specified in Engage.
  • if you do not use this element, Engage does not save any column names.
Content/Body Type
  • Required: Parameter to define if this is HTML only or TEXT only.
Content Personalization (Map TAG Value to TAG Name)
  • Required: At least one personalization block is required to provide the content for the email to be sent. Each Personalization element contains one Name/Value pair.
  • Map Tag Value to Tag Name where Tag Name specifies the name of the personalization string used in the body of the mailing template for the mailing, and Tag Value specifies the value of the corresponding TAG_NAME element
  • Tag Names must exactly match the fields used in Engage. Booleans (true, false) must be in lowercase.
  • The Transact server does not process any code (logic or transformation) placed in text or CDATA content, including anything inserted by Template fields.
  • If the text contains angle brackets (< or >), you must enclose it within a CDATA section.