- TLC Home Home
- Discussions & Ideas Discussions & Ideas
- Product Guides Product Guides
- Knowledge Base Knowledge Base
- Developer Docs Developer Docs
- Education Education
- Blog Blog
- Support Desk Support Desk
This article describes how to set up the AWS Kinesis Streams (Tealium-Provided Credentials) connector.
In this article:
Action Name | AudienceStream | EventStream |
---|---|---|
Send Event Data to Kinesis Stream | ✗ | ✓ |
Send Visitor Data to Kinesis Stream | ✓ | ✗ |
Send Customized Data to Kinesis Stream (Advanced) | ✓ | ✓ |
Navigate to the Connector Marketplace and add a new connector. For general instructions on how to add a connector, see the About Connectors article.
After adding the connector, configure the following settings:
Click Done when you are finished configuring the connector.
Click Continue to configure the connector actions. Enter in a name for the action and then select the action type from the drop-down menu.
The following section describes how to set up parameters and options for each action.
Parameter | Description |
---|---|
Stream Name | Select stream to send data to If your IAM policy does not grant 'kinesis:ListStreams' permission, you will need to manually enter a Custom Value |
Partition Key | (Required) |
Sequence Number For Ordering | |
Explicit Hash Key | |
Print Attribute Names | If attribute names get updated, the names in the payload will reflect the update. |
Parameter | Description |
---|---|
Stream Name | Select stream to send data to If your IAM policy does not grant 'kinesis:ListStreams' permission, you will need to manually enter a Custom Value |
Partition Key | (Required) |
Sequence Number For Ordering | |
Explicit Hash Key | |
Include Current Visit Data | |
Print Attribute Names | If attribute names get updated, the names in the payload will reflect the update. |
Parameter | Description |
---|---|
Stream Name | Select stream to send data to If your IAM policy does not grant 'kinesis:ListStreams' permission, you will need to manually enter a Custom Value |
Partition Key | (Required) |
Sequence Number For Ordering | |
Explicit Hash Key | |
Custom Message Definition | |
Template Variables | Optional Provide template variables as data input for templates (see: Template Variables Guide) Name nested template variables with the dot notation (Example: items.name) Nested template variables are typically built from data layer list attributes |
Templates | Optional Provide templates to be referenced in message data (see: Templates Guide) Templates are injected by name with double curly braces into supported fields (Example: {{SomeTemplateName}}) |
Copyright All Rights Reserved © 2008-2022