# Azure Blob

> Configure automatic daily deposits of your event and dispatch data in parquet format to your Azure Blob Storage container

Source: https://docs.oursprivacy.com/docs/azure

## Azure Blob Integration

The Azure Blob integration provides a native solution for storing your event, dispatch, and visitor data in a scalable, cost-effective manner using Azure Blob Storage. Ours Privacy will automatically deposit daily data into your specified Azure Blob Storage container in parquet format, containing all events and dispatches that occurred on your account, plus visitor records that have been recently updated.

> **Note:** The Azure Blob destination is configured for your account by the Ours Privacy team. Contact [support@oursprivacy.com](mailto:support@oursprivacy.com) to set it up.

## How the Integration Works

* **Scheduled Deposits**: Events and dispatches are automatically collected and deposited into your Azure Blob Storage container daily by default, or hourly with the **Sync frequency** setting on the destination (see [Sync Frequency](https://docs.oursprivacy.com/docs/warehouse-destinations#sync-frequency)).
* **Visitor Updates**: Visitor data contains records where the last seen timestamp is greater than or equal to yesterday, requiring upsert processing
* **Parquet Format**: Data is stored in efficient parquet format, optimized for analytics and querying
* **Complete Data**: All events and dispatches from your account are included in the daily deposits
* **Flexible Access**: Once in your Azure Blob Storage container, you can process, analyze, or move the data as needed

## Data Organization

The data in your Azure Blob Storage container is organized in a partitioned structure:

```
https://your-storage-account.blob.core.windows.net/your-container/
  ├── events/
  │   └── YYYY/
  │       └── MM/
  │           └── DD/
  │               └── *.parquet
  ├── dispatches/
  │   └── YYYY/
  │       └── MM/
  │           └── DD/
  │               └── *.parquet
  └── visitors/
      └── YYYY/
          └── MM/
              └── DD/
                  └── *.parquet
```

This partitioning by year/month/day makes it easy to:

* Query specific time periods efficiently
* Manage data retention policies
* Process historical data in batches
* Use partition projections for optimized querying

## Data Processing Considerations

### Events and Dispatches

Events and dispatches are complete daily snapshots containing all data for that day. Each day's parquet files contain all events and dispatches that occurred on that specific date.

### Visitors

Visitor data contains records that have been recently updated. This means you'll need to implement an upsert process to merge this incremental data into your data lake, warehouse, or database:

1. **Read the parquet files** from the visitors directory for the current day
2. **Identify existing records** in your target system using visitor identifiers
3. **Update existing records** with new information from the parquet files
4. **Insert new records** for visitors that don't exist in your system
5. **Handle conflicts** based on your business logic (e.g., latest timestamp wins)

This incremental approach ensures you have the most up-to-date visitor information while maintaining data consistency across your analytics infrastructure.

## Azure Services Integration

You can leverage various Azure services with your exported data:

### Azure Data Lake Storage Gen2

* Hierarchical namespace support for efficient data organization
* Integration with Azure Databricks for advanced analytics
* Support for multiple data processing frameworks

### Azure Data Factory

* Automated data pipelines for processing and transformation
* Integration with other Azure services and external systems
* Data movement and orchestration capabilities

## Getting Started

To set up the Azure Blob destination:

1. Contact [support@oursprivacy.com](mailto:support@oursprivacy.com) to enable it for your account
2. Ensure you have an Azure subscription with Blob Storage capabilities
3. Prepare your Azure Blob Storage container and access policies
4. Consider your data processing and analytics requirements

Once configured, your event, dispatch, and visitor data is automatically deposited into your Azure Blob Storage container daily, ready for your use in analytics, reporting, or other data processing workflows. Remember to implement the appropriate upsert logic for visitor data to maintain data consistency in your target systems.

## Data Format

The parquet files deposited in your Azure Blob Storage container contain your complete data, including:

* Event names and properties
* Dispatch details and status
* Visitor information and updates
* User information
* Timestamps
* All associated metadata