This article describes how to add and configure connectors for Tealium EventStream API Hub and Tealium AudienceStream CDP.
In this article:
A connector is an integration that transmits data between Tealium and another vendor in real-time. A connector offers actions that represent vendor-supported APIs. An action is triggered in real-time by an incoming event from a feed or a visitor joining or leaving an audience. An action sends data based on mappings that associate Tealium attributes to the expected vendor parameters.
Each connector in the marketplace has one or more consent categories assigned for each available action. To view the consent category for a specific connector, click the Information icon next to the connector action.
AudienceStream is categorized in the CDP consent category and DataAccess is categorized in the Big Data consent category. For additional information about server-side consent, see Consent Preferences Manager.
Use the following steps to add an EventStream or an AudienceStream connector:
To create an action, first select the type of data you want to send and configure the vendor service.
Connector actions that send audience data are controlled by triggers that determine when to fire the action.
Triggers can only be applied to an audiences and not to events.
In the Configuration step specify the credentials for your account with the vendor. This is usually an account ID, username and password, an API key, or other settings required by the vendor.
Use the following steps to add actions for this connector:
A connector action sends data according to the mapping configured. Some connectors offer the ability to map vendor parameters to Tealium attributes. This section describes how to map these attributes when this option is available.
Use the following steps to map Tealium attributes to the parameter expected by the vendor:
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:
This section describes how to turn a connector off or on, copy a connector and the associated configuration settings, and delete a connector.
Use the On/Off toggle to turn on or off a connector or action. If you turn off a connector, all associated actions for that connector are also turned off.
Use the following steps to duplicate a connector and the actions associated with the connector:
To delete a connector:
To get the connector ID:
To copy the action ID:
Connectors and actions can be deprecated, which means they may be unsupported or removed in the future. Deprecation typically occurs when a connector or an action has been replaced with a newer version or a new connector or action that should be used instead.
There are two types of deprecation, as follows:
When a connector or an action is deprecated, an icon is shown next to the connector or action in the connector list. When you hover over the icon, a message is displayed that specifies whether the deprecated connector or action still works.
The connector overview screen summary displays the following metrics as columns:
Expand the Add Action menu to quickly access the Edit, Duplicate, Get Connector ID, or Remove features.
The following sections describe how to view the reporting chart, view error details, and download error reports.
When you click on a connector action, the chart displays the number of times the action executed each day. You can view the graph for a rolling day, week, or month. Successful actions are shown in gray and errors are shown in red. Click any part of the chart to view a summary of the data for that display.
Use the following steps to view sampled errors for a connector:
Use the following steps to download sampled errors for a connector:
Connectors do not honor restricted data. This means that attributes marked as Restricted Data are always included, whether you are sending them through mappings or as part of the visitor profile. This cannot be changed. Learn more about Restricted Data.
If a connector you use has strict rules about which systems it accepts requests from, you can whitelist the IP addresses of the Customer Data Hub. The IP addresses that make connector requests can be found in the IP Addresses for Customer Data Hub.
When a connector action fails, it makes up to 2 additional attempts to trigger the action, which occur immediately.
A retry is attempted when the following responses are received:
A retry is not attempted when the following responses are received:
If the initial action fails, but a retry succeeds, it is logged as a success in the reporting chart.