Confluent Kafka Connect Connector Setup Guide
This article describes how to set up the Confluent Kafka Connect connector.
Configuration
Go 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:
- API Key: (Required) The Confluent API Key.
- API Secret: (Required) The Confluent API Secret.
- Bootstrap Server: (Required) The Confluent Bootstrap Server. Do not include the protocol or path. For example,
https://confluent.bootstrap.server:443should beconfluent.bootstrap.server. - Cluster ID: (Required) The Kafka Cluster ID.
Actions
| Action Name | AudienceStream | EventStream |
|---|---|---|
| Send Entire Event Data | ✗ | ✓ |
| Send Custom Event Data | ✗ | ✓ |
| Send Entire Visitor Data | ✓ | ✗ |
| Send Custom Visitor Data | ✓ | ✗ |
| Send Log Event | ✗ | ✓ |
| Send Entire Log Event | ✗ | ✓ |
Enter a name for the action and select the action type.
The following section describes how to set up parameters and options for each action.
Send Entire Event Data
Batch Limits
This connector uses batched requests to support high-volume data transfers to the vendor. Parallel processing may result in events reaching the vendor out of sequence. Add a sequence value to events if ordering is important. For more information, see Batched actions. Requests are queued until one of the following thresholds is met or the profile is published:
- Max number of requests: 100
- Max time since oldest request: 60 minutes
- Max size of requests: 10 MB
Parameters
| Parameter | Description |
|---|---|
| Topic ID | Select the topic or enter the Topic ID. |
| Partition ID | Select the Partition ID. |
| Data format | Specify the format for data delivery. Possible values: JSON, STRING, or BINARY. |
| Headers | Optional parameters. A set of key-value pairs listing the header properties and values. |
| Message key | Specify the raw message key. If you chose BINARY as the data format, Tealium encodes this value before sending it. |
| Timestamp | The topic timestamp in ISO 8601 UTC format. For example, YYYY-MM-DDThh:mm:ssZ. If no timestamp is provided, the current timestamp will be used. |
| Batch Time To Live | Set the time to live (TTL) to specify how often batch actions are sent. Enter a value between 1 and 60 minutes. The default value is 60 minutes. |
| Print Attribute Names | By default, the attribute IDs are used as key names. If you want to use the attribute names as key names instead, enable this checkbox. If the attribute names are updated, the key names in the payload will be updated. |
| Enable Streaming Mode | Enable this option to send each event immediately instead of batching events. Disabling this option allows events to be batched according to the batch limits specified above. |
Send Custom Event Data
Batch Limits
This connector uses batched requests to support high-volume data transfers to the vendor. Parallel processing may result in events reaching the vendor out of sequence. Add a sequence value to events if ordering is important. For more information, see Batched actions. Requests are queued until one of the following thresholds is met or the profile is published:
- Max number of requests: 100
- Max time since oldest request: 60 minutes
- Max size of requests: 10 MB
Parameters
| Parameter | Description |
|---|---|
| Topic ID | Select the topic or enter the Topic ID. |
| Partition ID | Select the Partition ID. |
| Data format | Specify the format for data delivery. Possible values: JSON, STRING, or BINARY. |
| Headers | Optional parameters. A set of key-value pairs listing the header properties and values. |
| Message key | Specify the raw message key. If you chose BINARY as the data format, Tealium encodes this value before sending it. |
| Timestamp | The topic timestamp in ISO 8601 UTC format. For example, YYYY-MM-DDThh:mm:ssZ. If no timestamp is provided, the current timestamp will be used. |
Message data
| Parameter | Description |
|---|---|
| Template Variables | Provide template variables as data input for templates. For more information and usage examples, see Template Variables Guide. Name nested template variables with the dot notation. For example: items.name.Nested template variables are typically built from data layer list attributes. |
| Templates | Provide templates to be referenced in message data. For more information, see Templates Guide. Templates are injected by name with double curly braces into supported fields. For example: {{SomeTemplateName}}. |
| Batch Time To Live | Set the time to live (TTL) to specify how often batch actions are sent. Enter a value between 1 and 60 minutes. The default value is 60 minutes. |
| Enable Streaming Mode | Enable this option to send each event immediately instead of batching events. Disabling this option allows events to be batched according to the batch limits specified above. |
Send Entire Visitor Data
Batch Limits
This connector uses batched requests to support high-volume data transfers to the vendor. Parallel processing may result in events reaching the vendor out of sequence. Add a sequence value to events if ordering is important. For more information, see Batched actions. Requests are queued until one of the following thresholds is met or the profile is published:
- Max number of requests: 100
- Max time since oldest request: 60 minutes
- Max size of requests: 10 MB
Parameters
| Parameter | Description |
|---|---|
| Topic ID | Select the topic or enter the Topic ID. |
| Partition ID | Select the Partition ID. |
| Data format | Specify the format for data delivery. Possible values: JSON, STRING, or BINARY. |
| Headers | Optional parameters. A set of key-value pairs listing the header properties and values. |
| Message key | Specify the raw message key. If you chose BINARY as the data format, Tealium encodes this value before sending it. |
| Timestamp | The topic timestamp in ISO 8601 UTC format. For example, YYYY-MM-DDThh:mm:ssZ. If no timestamp is provided, the current timestamp will be used. |
| Print Attribute Names | By default, the attribute IDs are used as key names. If you want to use the attribute names as key names instead, enable this checkbox. If the attribute names are updated, the key names in the payload will be updated. |
| Include Current Visit Data With Visitor Data | Add the current visit data to the payload. This includes event visit data, unless Exclude Current Visit Event Data is checked. |
| Exclude Current Visit Event Data | Exclude event data from the current visit data. |
| Batch Time To Live | Set the time to live (TTL) to specify how often batch actions are sent. Enter a value between 1 and 60 minutes. The default value is 60 minutes. |
Send Custom Visitor Data
Batch Limits
This connector uses batched requests to support high-volume data transfers to the vendor. Parallel processing may result in events reaching the vendor out of sequence. Add a sequence value to events if ordering is important. For more information, see Batched actions. Requests are queued until one of the following thresholds is met or the profile is published:
- Max number of requests: 100
- Max time since oldest request: 60 minutes
- Max size of requests: 10 MB
Parameters
| Parameter | Description |
|---|---|
| Topic ID | Select the topic or enter the Topic ID. |
| Partition ID | Select the Partition ID. |
| Data format | Specify the format for data delivery. Possible values: JSON, STRING, or BINARY. |
| Headers | Optional parameters. A set of key-value pairs listing the header properties and values. |
| Message key | Specify the raw message key. If you chose BINARY as the data format, Tealium encodes this value before sending it. |
| Timestamp | The topic timestamp in ISO 8601 UTC format. For example, YYYY-MM-DDThh:mm:ssZ. If no timestamp is provided, the current timestamp will be used. |
Message data
| Parameter | Description |
|---|---|
| Template Variables | Provide template variables as data input for templates. For more information and usage examples, see Template Variables Guide. Name nested template variables with the dot notation. For example: items.name.Nested template variables are typically built from data layer list attributes. |
| Templates | Provide templates to be referenced in message data. For more information, see Templates Guide. Templates are injected by name with double curly braces into supported fields. For example: {{SomeTemplateName}}. |
| Batch Time To Live | Set the time to live (TTL) to specify how often batch actions are sent. Enter a value between 1 and 60 minutes. The default value is 60 minutes. |
Send Log Event
Parameters
| Parameter | Description |
|---|---|
| Topic ID | Select the topic or enter the Topic ID. |
| Partition ID | Select the Partition ID. |
| Data format | Specify the format for data delivery. Possible values: JSON, STRING, or BINARY. |
| Headers | Optional parameters. A set of key-value pairs listing the header properties and values. |
| Message key | Specify the raw message key. If you chose BINARY as the data format, Tealium encodes this value before sending it. |
| Timestamp | The topic timestamp in ISO 8601 UTC format. For example, YYYY-MM-DDThh:mm:ssZ. If no timestamp is provided, the current timestamp will be used. |
Message data
| Parameter | Description |
|---|---|
| Template Variables | Provide template variables as data input for templates. For more information and usage examples, see Template Variables Guide. Name nested template variables with the dot notation. For example: items.name.Nested template variables are typically built from data layer list attributes. |
| Templates | Provide templates to be referenced in message data. For more information, see Templates Guide. Templates are injected by name with double curly braces into supported fields. For example: {{SomeTemplateName}}. |
Send Entire Log Event
Parameters
| Parameter | Description |
|---|---|
| Topic ID | Select the topic or enter the Topic ID. |
| Partition ID | Select the Partition ID. |
| Data format | Specify the format for data delivery. Possible values: JSON, STRING, or BINARY. |
| Headers | Optional parameters. A set of key-value pairs listing the header properties and values. |
| Message key | Specify the raw message key. If you chose BINARY as the data format, Tealium encodes this value before sending it. |
| Timestamp | The topic timestamp in ISO 8601 UTC format. For example, YYYY-MM-DDThh:mm:ssZ. If no timestamp is provided, the current timestamp will be used. |
This page was last updated: January 21, 2026