A Connector is a technical integration to transmit data between Tealium and another vendor. Each Connector has a Source of data, either visitor or event, that fuels its behavior. That data is passed to an Action based on Mappings that translate the Tealium data into the format expected by the vendor.
This article explains more about Connectors and provides general instructions for configuration.
The following topics are covered:
An Action is a vendor operation, like triggering an email, building a custom audience, or managing leads. Actions vary depending on the vendor service. Many Actions can be associated with a single Connector.
Source indicates the origin of the visitor data being acted upon. You can set it to be an Audience or a Stream (aka Live Events; requires EventStream service)
A Connector Action performs in real-time, but some Actions are designed to have a wait period before they are triggered. The Frequency Cap allows you to set a downtime period for Actions so they don't trigger immediately. Learn more about Frequency Capping and Prioritization.
Before creating Actions, you must hook up Tealium to the vendor service.
Click Next to go to the Actions tab
Stream targeting is possible in EventStream enabled Connectors only.
You are all set! The Action(s) will fire when the trigger conditions are fulfilled.
A Connector sends data to a vendor according to the configured Mappings. Mappings serve as a translation between the Tealium Attribute names and the parameter names expected by the vendor. To map an Attribute,
Often times, the To option is preselected, which means you are required to send data to that endpoint.
The Map dropdown is populated based on the Source you select. Choosing an Audience source, for example, displays all visit- and visitor-scoped Attributes but no event Attributes.
Connectors that send Audience data are controlled by WHEN conditions related to the behavior of the Audience that determine when to fire an Action.
Select one of the following conditions:
WHEN conditions are applied to Audiences only, not Streams.
If the Connector supports visitor segmentation (like Facebook Custom Audiences or Google Adwords Segments), these settings are configured in the Create tab. This tab is available to select Connectors only.
Example Custom Audience for Facebook
Connectors do not honor Restricted Data. That 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 put it to test. The easiest way to do this is by using the Trace Tool. Start a new Trace and examine the realtime log, checking for the Action you wish to validate. Expand the "Actions Triggered" entry and check its status. A successful trigger will look something like this: