Add a connector (legacy)

This is the legacy version of the connectors interface and will soon be deprecated. For the new interface, see About connectors.

Use the following steps to add an EventStream or an AudienceStream connector:

1. Navigate to EventStream > Event Connectors or to AudienceStream > Audience Connectors.
2. Click + Add Connector.
3. Browse or search for a connector, then click the connector to add.
   The connector summary, including links to vendor documentation, and configuration instructions appears.
4. Click Continue.
   The Select Source screen appears.

Select a source

The source for a connector is either an event feed or an audience, depending on the type of connector.

Select a data source for event connectors

1. Select a Data Source.
2. Select an Event Feed, then click Continue.
   

   

Select a data source for audience connectors

Connector actions that send audience data are controlled by triggers that determine when to fire the action.

Triggers can only be applied to audiences, not to events.

1. Select an Audience.
2. For Trigger, select one of the following:
   • Joined Audience - Trigger the action if a visitor joined the audience during this visit. For example, when a Cart Abandoner or Frequent Shopper joins an audience.
   • Left Audience - Trigger the action if a visitor left the audience during this visit.
   • In Audience at start of visit - Trigger the action at the beginning of the visit if the visitor is already in the audience.
   • In Audience at end of visit - Trigger the action if the visitor is in the audience at the end of the visit.
3. To limit how often this action triggers, toggle Frequency Cap to On, then select an Action Priority and an Action Cooldown Group.
   For more information, see Action Frequency Capping and Prioritization.

Configuration

Use the following steps to enter a name and the authentication information required for this connector:

1. In the Name field, enter a meaningful name for this instance of the selected connector.
2. Under Authentication, provide your login credentials, token or password, Account ID, and any other information required for establishing a connection with the vendor service.
3. Click Done.
4. Click Continue to add a connector action.
   The Add Action dialog appears.

Action settings

If you use a Send Visitor Data action with the Include Current Visit Data option selected, the events array in the visitor data only includes event attributes that are also defined in AudienceStream (as an attribute or an enrichment). It is a best practice to only select the Include Current Visit Data option when the connector needs the visit data. For more information, see the AudienceStore Data Guide.

Use the following steps to add actions for this connector:

1. In the Action Name field, enter a unique name for this action.
2. Select an Action Type. This list varies, depending on the connector. Big Data connectors, such as AWS Kinesis or Google Pub/Sub, typically have a Send Visitor Data action.
3. Complete the required fields for the action selected, using pre-populated drop-down lists where available. If any required fields are missing data, an error message is displayed in red text.

   

   When a value is selected or entered for all required fields, COMPLETED is shown.
4. Expand each section to complete any optional fields, as needed.
5. If the connector supports visitor segmentation, click Create Custom Audience to create a custom audience.
6. Click Finish.
7. Save and Publish your profile.
   The actions you configured will now fire when the trigger conditions are met.

Map attributes (Optional)

A connector action sends data according to the mapping configured. Some connectors offer the ability to map vendor parameters to Tealium attributes.

Use the following steps to map Tealium attributes to the parameter expected by the vendor:

1. Scroll to the bottom of the connector Actions list and click Custom Attributes to expand.
2. Click + Add Mapping.
3. In the Map field, select an attribute.
   This list is populated based on the Source you select. For example, choosing an audience displays all visit and visitor-scoped attributes but does not display event attributes.
4. In the To field, select a vendor parameter to map the attribute data to.
   If the To option is preselected, you are required to send data to that endpoint. You can optionally enter a custom name if the vendor supports custom parameters.
5. Click Back to modify, or click Finish.
6. Save and Publish your profile.

Test your connector

After you have added and configured a connector, you need to test it. The easiest way to test your connector is by using the Trace Tool, as follows:

1. Start a new trace.
2. Examine the real-time log.
3. Check for the action you want to validate by clicking the Actions Triggered entry to expand.
4. Find the action you want to validate and view the log status.

EventStream and AudienceStream pass only valid Trace IDs. Invalid Trace IDs are removed from the payload.