Webhook JDBC Connector Setup Guide

To use a webhook to send data to an HTTP API endpoint, see About webhook connectors.

Batch limits

This connector uses batched requests to support high-volume data transfers to the vendor. Requests are queued until one of the following three (3) thresholds is met:

• Max number of requests: 1,000
• Max time since oldest request: 60 minutes
• Max size of requests: 100 MB

Configuration

Navigate to the connector marketplace and add a new connector. For general instructions on how to add a connector, see About Connectors.

After adding the connector, configure the following settings:

• Username: The username to log into your database from Tealium. For security reasons, allow this user to connect only from these IP addresses.

• Password: The password for the username provided.

• JDBC URL: The fully qualified JDBC URL to establish the connection (for example, jdbc:postgresql://host:5432/dbname?p1=a&p2=b).

• Additional properties: A set of comma-separated pairs to pass as properties when establishing the connection. For example, prop1=a,prop2=b results in the following adjustment to the connection:

  props.setProperty("prop1", "a");
  props.setProperty("prop2", "b");
  Connection conn = DriverManager.getConnection(url, props);
  

Column data types

To make it easier to map attributes to table columns, the columns appear with their data type appended to the name. For example, if you have a column named customer_id of type VARCHAR, it appears in the mapping list as customer_id//VARCHAR.

Batch configuration

All actions that support batch processing support the following parameters:

Actions

Send Entire Event Data

Use this action to send the entire event JSON object to a single table column.

For more information, see Event Data JSON.

Parameters

Send Custom Event Data

Use this action to send specific event attributes to specific table columns.

Parameters

Send Entire Log event

For more information, see Connector error logging.

Parameters

Send Log Event

For more information, see Connector error logging.

Parameters

Log event resource attributes

These fields capture information about the entity for which telemetry is recorded.

Log event HTTP attributes

These fields log the HTTP requests and responses within the logging system.

If you want to map the entire HTTP array to a single column, map the http attribute. If the target column is of type VARIANT, the raw array is sent; otherwise, it is converted to a string.

Log event result attributes

These fields log the outcome of the operation, detailing whether it was successful or if it encountered errors.

Log event other attributes

These fields provide additional metadata about the logged events.

Send Entire Visitor Data

Use this action to send the entire visitor JSON object to a single table column.

For more information, see Visitor Data JSON.

Parameters

Send Custom Visitor Data

Use this action to send specific visitor attributes to specific table columns.

Parameters

Execute Custom Query

Use this action to run custom SQL statements.

Only INSERT, UPDATE or MERGE statements are allowed, but they can include SELECT sub-queries. Including multiple INSERT, UPDATE or MERGE statements within the same query causes an error.

To use this feature, map your attributes to named placeholders, that you reference in your SQL using the :MY_PLACEHOLDER format. For example, if you map a boolean attribute to a placeholder named :my_bool_param, then reference :my_bool_param in the query where you want that value to be replaced by the mapped attribute’s value.

Examples:

-- Example
INSERT INTO redshift_table
(col1, col2) VALUES (:col1Value, :col2Value)

-- Example
UPDATE redshift_table
SET col1 = :col1Value, col2 = :col2Value
WHERE col3 = :col3Value

-- Example
UPDATE redshift_table
SET col2 = (
  SELECT new_col2 FROM source_table WHERE source_table.col1 = redshift_table.col1
)
WHERE EXISTS (
  SELECT 1 FROM source_table WHERE source_table.col1 LIKE :col1Value
);

Parameters