This article describes how to add and configure connectors for the Tealium EventStream API Hub and AudienceStream Customer Data Platform (CDP).
In this article:
A connector is an integration between Tealium and another vendor used to transmit data. Tealium users spend a large portion of their time working with connectors. The Customer Data Hub (CDH) interface offers feature-rich tools to add and configure connectors that make your day-to-day experience faster, more logical, and dynamic.
Here's how it works:
Each EventStream 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 consent preferences, see Consent Preferences Manager.
Use the following steps to add an EventStream or AudienceStream connector:
Before creating actions, you must first select the type of data you want to send and configure the vendor service.
To add actions for this connector:
A connector action sends data according to the mapping configured. Some connectors offer a the ability to map the vendor attribute to Tealium attribute names. This section describes how to map these attributes when this choice is available.
Use the following steps to map Tealium attribute names to the parameter names expected by the vendor:
After your connector is up and running, you need to test it. The easiest way to test your connector is by using the Trace Tool, as follows:
Use the following steps to make a copy (duplicate) of a connector and the actions associated with the connector:
Use the following steps to delete or remove a connector:
Use the following steps to revert back to a previous version of a connector instance:
This section describes additional configuration options that can be used with some connectors.
Connector actions that send audience data are controlled by WHEN conditions related to the behavior of the audience. The WHEN condition determines when to fire the action.
WHEN conditions can only be applied to audiences and not event feeds.
Select one of the following conditions:
If the connector supports visitor segmentation, such as Facebook Audiences or Google Adwords, these settings are configured in the Create tab. Enter the required information in the setup screens, click Continue > Finish and then Save and Publish your changes.
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.