About webhook connectors

Requirements

• Tealium account enabled for EventStream (for event data)
• Tealium account enabled for AudienceStream (for visitor data)

How it works

The Webhook Connector sends customized data to your vendor through HTTP requests, using all aspects of an HTTP request, including the URL, URL Parameters, Headers, Cookies, Body Content Type, and Body Data. Webhook also supports batching. Additionally, it includes a powerful templating feature designed to handle complex and dynamic data formats.

There are three Webhook connectors to choose from based on the authorization requirements of your vendor, as follows:

• Webhook (BasicAuth) – For services that do not require authentication or only require basic authentication with a username and password.
• Webhook (OAuth2 - 3-Legged) – Requires the user to login to the service to obtain an access token.
• Webhook (OAuth2 - 2-Legged) – Does not require the user to login to the service. The webhook is configured with the information required to authenticate.
• Webhook (JWT) – Uses JSON web token authentication. Does not require the user to log in to the service. The webhook is configured with the information required to authenticate.

Webhook OAuth2 is used for services that explicitly require OAuth 2.0 authentication.

To get started, go to the connector marketplace and add the Webhook instance you wish to use. For general instructions on how to add a connector, see Connector Overview

Connector actions

HTTP response cookies

While cookie-based session management is common in web browsers, it is generally discouraged in server-to-server environments that communicate with stateless APIs. For that reason, the Webhook connector does not track cookie-based sessions and effectively ignores Set-Cookie header values in HTTP responses.