Event connectors give you the ability to leverage Event Feeds for taking action on events such as product page views, add to cart actions, or newsletter signups, etc. These actions occur in a cloud-based delivery service instead of client-side (ie. in your mobile app or website).

In this article:

Table of Contents Placeholder


  • EventStream - Contact your Tealium account manager to activate.
  • Event Feed - An event feed with incoming data.
  • Supported Vendor Account - An active vendor account that supports cloud delivery.

Trigger Actions Using Feeds

Step 1: Add an Event Connector

  1. Navigate to the EventStream > Connectors
  2. In the side bar, select a category filter.
  3. Select a connector and click Add Connector

Step 2: Configure an Action

  1. On the Configure tab enter required fields and click Next
  2. From the Actions list, select the desired action and click Add Action
  3. Enter a name for the action
  4. From the Source list, select the desired feed 
  5. Map data values to be sent to the vendor. The mapping destinations will vary depending on the Connector.
  6. Click Save

Step 3: Save/Publish your profile 

The action will trigger as data flows into the feed selected.

Validating Event Connector Actions

You have set up your desired actions and now it's time to test them. With the help of the Trace tool you can monitor which streams are activated by the Tealium Collect tag, which actions are triggered, and what data is collected in the process. Let's walk through a simple exercise to trigger a GET action in Webhook and have it triggered by a sample stream.

Step1: Add a new feed and title it 'Test Event A'.

Add the condition: "customer_email" is assigned.

Test Event A.png

Step 2: Add the Webhook Connector and create a GET Action. Select 'Test Event A' as the trigger source.

Get Source.png

Step 3: Save/publish your profile.

Step 4: Start a new Trace in AudienceStream and navigate to your site.

Trace will start displaying all the configurations and processes that are being evaluated behind the scenes.

Step 5: In the reporting screen, check if your target Stream 'Test Event A' was picked up by the Collect Tag.

stream in trace.png


Step 6: Check to see if the GET Action was triggered successfully.

action in trace.png

Sending Array Data

  • Some Connectors will support a data layer Array of items in a URI-Encoded JSON format
  • The expected format for a list of items (Array) would be as follows:
    • &product_id=%5B%22prod1%22%2C%22prod2%22%2C%22prod3%22%5D
    • This sends an array of ["prod1","prod2","prod3"]
  • A product with a comma as part of the product name would need to be double-encoded in a form such as:&product_id=%5B%22pro%252Cd1%22%2C%22prod2%22%2C%22prod3%22%5D
    • Notice the %252C in prod1which double-encodes the comma which is regularly %2C
    • This sends an array of ["pro%2Cd1","prod2","prod3"]

IP Whitelist for Connectors

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.