Azure Blob Storage

Airbridge supports Azure Blob Storage integration. Once set up, you can access raw event data collected by Airbridge SDKs and tracking links in Azure Blob Storage. You can select specific events and properties to send to Azure Blob Storage, and data collected the previous day is sent daily around 7:00 PM UTC.

Attention

For connections created or modified after June 10, 2026, ${VERSION} in the folder path is fixed at 3.0. Existing connections keep their current version as long as you don't change them.

You need Owner or Contributor IAM permissions to create and view storage accounts, access keys, and containers in the Azure Portal.

Azure Blob Storage integration takes 4 steps.

1. Connection setup: Enter integration details and test the connection.

2. Event selection: Choose events to send to Azure Blob Storage.

3. Property selection: Choose properties for those events.

4. Review and add: Review your selections and add the connection.

To create a connection, find the following information in the Azure Portal.

• Storage account name

• Access key

• Container name

Create a storage account in the Azure Portal and find its name.

1. Sign in to the Azure Portal and select [Storage accounts].

2. Click Create and enter the basic information.

3. Click Review + create.

4. Once the automated validation passes, click the activated Create button to finish.

5. Find the storage account name you created.

Find the access key to enter in the Airbridge dashboard.

1. In [Storage accounts], select the storage account to connect with Airbridge.

2. Go to [Security + networking]>[Access keys].

3. Between key1 and key2, use only the Key value under key1 for the integration. key2 is a backup and isn't used. Click Show next to Key under key1.

4. When the key1 value appears, click the copy icon to copy it.

Create a container to receive data from Airbridge. The name used to create the container is also used in the Airbridge dashboard.

1. In [Storage accounts], select the storage account to connect with Airbridge.

2. In [Data storage]>[Containers], click + Container.

3. In the right panel, enter a container name and click Create. See the Azure Blob Storage guide for container naming rules.

Enter the details you found in the Azure Portal into the Airbridge dashboard.

1. In the Airbridge dashboard, go to [Integrations]>[Third-party Integration] and click Azure Blob Storage.

2. Click Add connection.

3. Enter the storage account name, access key, and container name from the Azure Portal.

4. Choose CSV or Parquet as the integration format and click Submit.

Test whether the information you entered can connect to Azure Blob Storage.

1. In the Airbridge dashboard, click Test connection.

2. If the test succeeds, click Next in the bottom right to move to event selection.

If the test fails, check the information you entered and try again. If you leave the page before completing the test, you'll need to restart the entire integration process.

Select events to send to Azure Blob Storage. You can only select events that Airbridge has collected at least once.

1. Select events from app, web, tracking link categories.

2. Click Next in the bottom right.

Note

Events newly collected after you create the connection won't be sent until you add them manually.

Select properties to send to Azure Blob Storage for the events you chose.

1. Select properties by category.

2. Click Next in the bottom right.

Note

Required properties cannot be deselected.

Review your selected events and properties, then add the connection.

1. Review [Events to send] and [Properties to send]. To make changes, click Edit on the right.

2. Under [Data transfer status], check the transfer status by data source.

3. Click Save connection in the bottom right to create the connection.

You can check data sending status on the following pages in the Airbridge dashboard.

See the table below for the specific meaning of each status message.

Airbridge always sends the previous day's data based on your app's time zone around 7:00 PM UTC. Once you complete the Azure Blob Storage integration, data is delivered to the following paths in your container starting the next day.

• App events:

  ${YOUR-CONTAINER-NAME}/${YOUR-APP-NAME}/app/${VERSION}/date=${year}-${month}-${day}/

• Web events:

  ${YOUR-CONTAINER-NAME}/${YOUR-APP-NAME}/web/${VERSION}/date=${year}-${month}-${day}/

• Tracking link events:

  ${YOUR-CONTAINER-NAME}/${YOUR-APP-NAME}/tracking-link/${VERSION}/date=${year}-${month}-${day}/

Sent files contain only the properties you selected. Property changes can reorder columns in the file, so always use column names to identify data.

Attention

For connections created or modified after June 10, 2026, ${VERSION} in the folder path is fixed at 3.0. Existing connections keep their current version as long as you don't change them.

Refer to the sections below to edit or delete your integration.

If your Azure Blob Storage integration details change, follow these steps to update them.

1. In the Airbridge dashboard, go to [Integrations]>[Third-party Integration] and click Azure Blob Storage.

2. Click the connection you want to update.

3. Click the field you want to edit and enter the new value.

4. When done, click Save.

If you change the storage account name, access key, container name, or integration format, you need to test the connection again.

1. In the Airbridge dashboard, go to [Integrations]>[Third-party Integration] and click Azure Blob Storage.

2. Click the delete icon for the connection you want to remove.

3. Enter the confirmation phrase and click Delete.

Deleting a connection stops data transfer immediately. However, data already sent to Azure Blob Storage stays in your container.

You can check integration setup status under [Integrations]>[Integration Overview] in the Airbridge dashboard. If an error occurs, see the Check Integration Status guide for resolution steps.

Airbridge supports one cloud storage integration by default. Integrating with more than one storage requires additional charges.

Editing the connection details such as events or properties updates the ${VERSION} in your Azure Blob Storage path to 3.0. Once updated, data can no longer be retrieved from the previous folder path. Check with your internal Azure Blob Storage administrator before switching to the 3.0 path.