About webhook connectors
This article describes the available webhook connectors.
- Tealium account enabled for EventStream (for event data)
- Tealium account enabled for AudienceStream (for visitor data)
How it works
The Webhook Connector allows you to send data to your vendor using customized HTTP requests and allows you to all aspects of an HTTP request, such as the URL, URL Parameters, Headers, Cookies, Body Content Type and Body Data. Webhook also supports a batching and 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 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.
|Action Name||Description||Webhook (BasicAuth)||Webhook OAuth2|
|Send Event Data via HTTP Request||Sends the entire event object, either as a URL-encoded JSON string or a JSON payload.||✓||✗|
|Send Visitor Data via HTTP Request||Sends the entire visitor profile object, either as a URL-encoded JSON string or a JSON payload.||✓||✗|
|Send Customized Data via HTTP Request (Advanced)||Sends individual event/visitor attributes specified via mappings||✓||✓|
|Send Batched Customized Data via HTTP Request (Advanced)||Sends batched event/visitor attributes specified via mappings.||✓||✓|
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.
Thank you for your feedback!
This page was last updated: June 23, 2022