This article describes what connectors are and how they are used.
In this article:
A connector is an integration between Tealium and another vendor to transmit data. Connectors have actions that represent the API's supported by the vendor. Each connector is fueled by an event feed or an audience. That data is passed to an action based on mappings that translate your attributes into the format expected by the vendor.
Use the following steps to add a connector:
Before creating actions, you must configure the vendor service.
Feeds are only available in EventStream enabled connectors.
You are all set! The action will fire when the trigger conditions are fulfilled.
A connector action sends data according to the configured mappings. Mappings serve as a translation between your attribute names and the parameter names expected by the vendor.
Use the following steps to map an attribute:
Connectors actions that send audience data are controlled by WHEN conditions related to the behavior of the audience that determine when to fire the action.
WHEN conditions are applied to audiences only, not event feeds.
Select one of the following conditions:
If the connector supports visitor segmentation, such as Facebook Custom Audiences or Google Adwords segments), these settings are configured in the Create tab. Enter the required information, click Save, and then Save and Publish your changes.
Example Custom Audience for Google AdWords
Connectors do not honor Restricted Data. This means any 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.
Now that your connector is up and running, it's time to test it. The easiest way to do this is by using the Trace Tool. Start a new trace and examine the real-time log, checking for the action you wish to validate. Expand the "Actions Triggered" entry and check its status.
If a connector you use has strict rules about which systems it accepts requests from, you might need to whitelist the IP addresses of the UDH. The IP addresses that make connector requests can be found in the IP Addresses for Universal Data Hub.