Click on Map Input link in Configure Activity section displayed below the orchestration.
The mandatory parameters for this Activity vary depending on the custom fields of the database.
Select Contact Activity
Name | Type | Required | Description |
String | No | The contact email address to look up. Note: When using a Non-Email Key or No-Key database, this element is not required | |
RECIPIENT_ID | String | No | The Recipient Id may be provided with a LIST_ID to look up a contact. No key fields are required when passing the Recipient Id. |
ENCODED_RECIPIENT_ID | String | No | The encoded Recipient Id may be provided with a LIST_ID to look up a contact. No key fields are required when passing the encoded Recipient Id. |
VISITOR_KEY | String | No | The Silverpop Web Tracking visitor key may be provided with a LIST_ID to look up a contact. No key fields are required when passing the Silverpop Web Tracking Visitor key. The Silverpop Web Tracking Visitor key is available in the Web Tracking cookie stored in a contact’s browser settings. |
RETURN_CONTACT_LISTS | Boolean | No | Indicates whether to return all Contact Lists which the contact belongs to. Valid values are: true false |
COLUMN | Depends on Each column name type. | Yes | Required if the database has a key other than Email or no Unique Identifier. XML nodes defining the column name and value used to look up a contact in a database. Ignored for regular email key databases. Note: Unique key columns must be part of the submission with column names and values. Note: If more than one contact is found matching the lookup columns, the oldest contact will be returned. Name Specifies the field name of the unique key for the database. Value Specifies the field value for the field name of the unique key for the database. |