This article describes what connectors are and how they are used.

In this article:

Table of Contents Placeholder

How it Works

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.


  • Action
    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.
  •  Frequency Cap
    A connector action performs in real-time, but some actions are designed to have a wait period before they are triggered.
    WhiteUI_EventStream_About Connectors_FrequencyCapToggle.png
    The frequency cap allows you to set a downtime period for actions so that they do not trigger immediately. Learn more about Frequency Capping and Prioritization
  • Source
    Source indicates the origin of the data being acted upon. A source can be an audience or a event feed.

Adding a Connector

Use the following steps to add a connector:

  1. In the sidebar, go to Event Stream > Event Connectors.
    For visitor data connectors go to AudienceStream > Audience Connectors.
  2. Browse for your vendor or use the global search to search for a name.
  3. Click Add Connector.
    The connector setup screen displays.

Configure Settings

Before creating actions, you must configure the vendor service. 

  1. Enter a meaningful title for this instance of the selected connector.
  2. Provide your login credentials/token, account ID, and other information required for establishing a connection with the vendor service. WhiteUI_EventStream_AboutConnectors_Configure ClickSend Connector.png
  3. (Optional) Provide additional notes about this configuration.
  4. Click Next to go to the Actions tab

Action Settings

  1. In the Actions tab, select the desired action from the drop-down list and click + Create Action.
    This list will vary depending on connector.
  2. Action Name: Provide a name for the action instance.
  3. Frequency Cap: Turn ON this toggle if you wish to set cooldown hours for the action instance. Learn more about Frequency Capping and Action Prioritization.
  4. Source: Use the drop-down list to select the audience or event feed to take action on.

    Feeds are only available in EventStream enabled connectors.

  5. Complete the remaining settings as applicable.
  6. Repeat to add more actions.
  7. Click Save.
  8. When complete, save and publish your profile.

You are all set! The action will fire when the trigger conditions are fulfilled.

Mapping Attributes

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:

  1. Scroll to the bottom of the connector Actions list and click Custom Attributes to expand.
  2. Select an attribute from the Map drop-down list.
    The Map drop-down list is populated based on the Source you select. For example, choosing an audience displays all visit- and visitor-scoped attributes but no event attributes.
  3. Select an parameter from the To drop-down list.
    The To option is sometimes preselected, which means you are required to send data to that endpoint. You can optionally enter a custom name if the vendor supports custom parameters. 
    WhiteUI_EventStream_AboutConnectors_MappingAttributes_Predefined and Custom.png
  4. Click Save.
  5. Save and Publish your changes.

WHEN Condition

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:

  • Joined Audience
    Trigger the Action whenever a visitor joins the Audience, for example Cart Abandoners or Frequent Shoppers.
  • In Audience at Start of Visit
    Trigger the Action at the beginning of the visit if the visitor is already in the Audience.
  • In Audience at End of Visit
    Trigger the Action if the visitor is in the Audience by the end of the visit.
  • Left Audience
    Trigger the Action whenever a visitor leaves the Audience.

Creating Visitor Segments

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

WhiteUI_EventStream_AboutConnectors_Create Visitor Segments_Google Adwords Example.png

Connectors and Restricted Data

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.

IP Whitelist

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 Customer Data Hub.  The IP addresses that make connector requests can be found in the IP Addresses for Customer Data Hub.