Agillic Recipients Connector Setup Guide | Server-Side Connectors |Preview of Tealium Docs

Connector actions

Action Name	AudienceStream	EventStream
Add or Update Recipient	✓	✓
Add or Update Recipient (Batched)	✓	✓
Update Recipient Table Records	✓	✓
Achieve Event	✓	✓

Configure settings

Navigate to the Connector Marketplace and add a new connector. For general instructions on how to add a connector, see the About Connectors article.

After adding the connector, configure the following settings:

Client ID
- Required.
- Provide your web application client ID.
- For more information, see Getting Started with APIs: Authentication.
Client Secret
- Required.
- Provide your web application client secret.
Date Format
- Set the date format for the connector.
- If not specified, the default format dd.MM.yyyy is used.
- The date and timestamp format is unique to each Agillic account instance.
- Formats are defined in the Agillic Administration interface.
- For more information, see Getting Started with APIs: Dates and Time.
Timestamp Format
- Set the timestamp format for the connector.
- If not specified, the default format dd.MM.yyyy is used.

Actions

Click Next or go to the Actions tab. Enter a name for the action and select the action type from the drop-down menu.

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

Add or Update Recipient

Parameters

Parameter	Description
Recipient ID	Required. Map any unique Person Data, such as EMAIL or MOBILE. Use Recipient ID for general purpose. For more information, see APIs: Recipient API.
Recipient Data	Required. Map values to the Person Data fields.

Add or Update Recipient (Batched)

Batch limits

This connector uses batched requests to support high-volume data transfers to the vendor. For more information, see Batched Actions. Requests are queued until one of the following thresholds is met or the profile is published:

Max number of requests: 1000
Max time since oldest request: 10 minutes
Max size of requests: 5 MB

Parameters

Parameter	Description
Recipient ID	Required. Map any unique Person Data, such as EMAIL or MOBILE. Use Recipient ID for general purpose. For more information, see APIs: Recipient API.
Recipient Data	Required. Map values to the Person Data fields.
Recipient ID Attribute Name	Optional. Overwrites which Person Data value is used to match with existing recipients. Map any unique Person Data, such as EMAIL or MOBILE. For more information, see APIs: Recipient API.

Update Recipient Table Records

Parameters

Parameter	Description
Recipient ID	Required. Map any unique Person Data, such as EMAIL or MOBILE. Use Recipient ID for general purpose. For more information, see APIs: Recipient API.
Table	Required. Table ID of the records that will be batch updated.
Table Record	Required. Map one or more values to each table record field. ID or Primary Key must be specified.

Achieve Event

Parameters

Parameter	Description
Recipient ID	Required. Map any unique Person Data, such as EMAIL or MOBILE. Use Recipient ID for general purpose. For more information, see APIs: Recipient API.
Event ID	Required. Event ID to be achieved.