Microsoft Azure Blob Storage Connector Setup Guide
This article describes how to set up the Microsoft Azure Blob Storage connector.
Batch Limits
This connector uses batched requests to support high-volume data transfers to the vendor. 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,000
- Max time since oldest request: 10 minutes
- Max size of requests: 100 MB
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:
- Tenant ID
- The unique identifier for your Azure Active Directory instance, representing your organization.
- Authentication type
- Select the authentication type. Available options are: Client credentials, Authorization Code flow (SSO) and Shared Access Signature (SAS).
- Client ID
- The unique identifier assigned to your application registered in Azure Active Directory.
- Client Secret
- The string that acts like a password, used by the application to authenticate with Azure Active Directory.
- Shared Access Signature
- Provide the special set of query parameters that indicate how the resources may be accessed by Tealium.
- Storage account name
- The unique name of your Azure Storage account, used to access storage services like Blob, File, Queue, and Table storage.
- API version
- The API version compatible with your Azure Storage instance. The default version is
2025-01-05
.
- The API version compatible with your Azure Storage instance. The default version is
Actions
Action Name | AudienceStream | EventStream |
---|---|---|
Send Entire Event Data | ✗ | ✓ |
Send Custom Event Data | ✗ | ✓ |
Send Entire Visitor Data | ✓ | ✗ |
Send Custom Visitor Data | ✓ | ✗ |
Enter a name for the action and select the action type from the drop-down menu.
The following section describes how to set up parameters and options for each action.
Send Entire Event Data
Parameters
Parameter | Description |
---|---|
Container | Select the container where you want to create the objects. This container represents the top-level storage unit within an account that organizes a set of blobs, similar to folders in a file system. |
Blob Path | Specify the path to the Blob object where you want the data to be appended. |
File Blob Suffix | If you want to dynamically add a suffix to the file name, for example, an attribute with the current timestamp, select it here. If multiple suffix values are provided, they will be separated by an underscore character. |
Record Suffix |
|
Overwrite Existing Blob | If the Blob object already exists, overwrite it with the current data. If unchecked, the data will be appended instead. When appending the data, each block will consist of a group of JSON objects containing the payload with the data being forwarded from Tealium. |
Print Attribute Names | By default, the attribute keys are used. If you want to use the attribute names as keys instead, enable this checkbox. Consider that the payload names will reflect the update if the attribute names are updated. |
Send Custom Event Data
Parameters
Parameter | Description |
---|---|
Container | Select the container where you want to create the objects. This container represents the top-level storage unit within an account that organizes a set of blobs, similar to folders in a file system. |
Blob Path | Specify the path to the Blob object where you want the data to be appended. |
File Blob Suffix | If you want to dynamically add a suffix to the file name, for example, an attribute with the current timestamp, select it here. If multiple suffix values are provided, they will be separated by an underscore character. |
Record Suffix |
|
Overwrite Existing Blob | If the Blob object already exists, overwrite it with the current data. If unchecked, the data will be appended instead. When appending the data, each block will consist of a group of JSON objects containing the payload with the data being forwarded from Tealium. |
Message Data
Parameter | Description |
---|---|
Template Variables |
|
Templates |
|
Send Entire Visitor Data
Parameters
Parameter | Description |
---|---|
Container | Select the container where you want to create the objects. This container represents the top-level storage unit within an account that organizes a set of blobs, similar to folders in a file system. |
Blob Path | Specify the path to the Blob object where you want the data to be appended. |
File Blob Suffix | If you want to dynamically add a suffix to the file name, for example, an attribute with the current timestamp, select it here. If multiple suffix values are provided, they will be separated by an underscore character. |
Record Suffix |
|
Overwrite Existing Blob | If the Blob object already exists, overwrite it with the current data. If unchecked, the data will be appended instead. When appending the data, each block will consist of a group of JSON objects containing the payload with the data being forwarded from Tealium. |
Print Attribute Names | By default, the attribute keys are used. If you want to use the attribute names as keys instead, enable this checkbox. Consider that the payload names will reflect the update if the attribute names are updated. |
Include Current Visit Data with Visitor Data | Select this option to include current visit data with visitor data. |
Send Custom Visitor Data
Parameters
Parameter | Description |
---|---|
Container | Select the container where you want to create the objects. This container represents the top-level storage unit within an account that organizes a set of blobs, similar to folders in a file system. |
Blob Path | Specify the path to the Blob object where you want the data to be appended. |
File Blob Suffix | If you want to dynamically add a suffix to the file name, for example, an attribute with the current timestamp, select it here. If multiple suffix values are provided, they will be separated by an underscore character. |
Record Suffix |
|
Overwrite Existing Blob | If the Blob object already exists, overwrite it with the current data. If unchecked, the data will be appended instead. When appending the data, each block will consist of a group of JSON objects containing the payload with the data being forwarded from Tealium. |
Message Data
Parameter | Description |
---|---|
Template Variables |
|
Templates |
|
This page was last updated: April 7, 2025