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.
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 data being acted upon. A source can be an audience or a event feed.
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 configure the vendor service.
Click Next to go to the Actions tab
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. 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. For example, choosing an audience displays all visit- and visitor-scoped attributes but no event attributes.
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.
Select one of the following conditions:
WHEN conditions are applied to audiences only, not event feeds.
If the connector supports visitor segmentation (like Facebook Custom Audiences or Google Adwords Segments), these settings are configured in the Create tab.
Example Custom Audience for Facebook
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. A successful trigger will look something like this:
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.