Export data to Azure Blob Storage
Sync your model profiles and attributes into an Azure Blob Storage container to enable personalization and rapid data retrieval in your apps and websites.
Overview
This destination service allows DinMo to insert new files or update existing ones in an Azure Blob Storage Container, based on your DinMo models or segments.
To use this service, follow these three steps:
Create an Azure Storage destination. Follow the step-by-step guide above to establish this connection using a SAS Token.
Create your DinMo model or segment representing the data you want to send to your Azure Blob Storage container.
Activate your model or segment with the Azure Storage destination to start synchronization.
Every time the activation runs:
If the file does not yet exist: DinMo will create it with all the rows in the query results.
If the file already exists: DinMo will overwrite it, with all the rows in the query results.
Activation Setup
Once the Azure Storage destination is configured, create an activation to begin syncing your data.
To do so:
Go to the Activations tab.
Click on New activation.
Select the model or segment you want to export.
Choose your Azure Storage destination from the list.
You’ll then configure the activation:
File Name: Indicate the desired name for your file.
If you don't want to override existing files, we recommend including timestamp variables in the filename. To do so, you just need to surround each variable with {}. DinMo supports these timestamp variables:
{YYYY}: Full year (e.g., 2025){YY}: Last two digits of the year (e.g., 25){MM}: Month (01-12){DD}: Day of the month (01-31){HH}: Hour (00-23){mm}: Minute (00-59){ss}: Second (00-59){ms}: Millisecond (000-999){X}: Unix timestamp in seconds{x}: Unix timestamp in milliseconds
For example: {YY}-{MM}-{DD}_export will be 25-04-14_export.csv for the upload of April 14th 2025.
All placeholder values are set on Coordinated Universal Time (UTC)
File Format: Choose between CSV, JSON, XML, or Apache Parquet.
For CSV only: select a delimiter and whether to include headers.
Indicate the type of run you would like to do, based on the result you would like to see in your file.
Attribute Mapping: Map any fields from your model/segment to custom column names in the destination file. You can rename fields freely.
The example above shows how to export the age, name, phone_number and boolean is_active. These columns are mapped to new fields in the destination file as age, last name , phone and is_active.
DinMo ignores all other columns from your model/segment.
Run Types and Sync Modes
When configuring your sync, you will be asked to choose the Run Type and the Sync Mode. For Azure activations, here are the available options:
FULL ONLY
Every sync processes all records from the source and exports a complete file (or several, if size limit is reached).
When the exported file must always contain a full extract, and incremental updates are not required.
No delta logic
Every sync rebuilds the full export
Recommended for Snapshot mode
FULL THEN DELTA
The first sync exports all records. All following syncs export only changed records, based on DinMo’s delta detection logic.
When exporting large datasets frequently and wanting to reduce file size or processing time.
Sync 1 → Full export
Next syncs → Only changed records (new, updated).
Compatible with INSERT, UPSERT, and DIFFERENCE modes
Sync modes determine how data is synchronized between your data source and destination. They control whether to insert new records, update existing ones, or both, and how to handle the synchronization process.
For the Azure destination, here are the available options:
SNAPSHOT
Exports a complete snapshot of all records at the time of sync. Each sync can generate a new file with a timestamped name.
Useful for backups or systems expecting full “point-in-time” extracts.
Always exports the full segment / model
Creates a new file with timestamp
No incremental logic
UPSERT
Writes all updated or new records into the exported file.
Keeps files up-to-date with the latest source data.
New records → included in the exported file
Existing records → included if, and only if, there are updated values
Deleted records → simply not present in the file
INSERT
Adds only new records to the exported file. Existing records are never modified.
Useful for append-only files, such as historical logs or event tracking.
New records → added to file
Existing records → ignored
Missing records → no action
DIFFERENCE
Generates separate files for added, updated, and removed records between syncs.
For audit trails, incremental processing, or systems needing change-specific files.
Creates
_added.csv,_updated.csv,_removed.csv(or other extensions)Each file contains only the relevant change type
Scheduling
Define how frequently your data is exported to your Azure Blob Storage Container.
For each run, DinMo performs a full run, meaning that 100% of the people in the model/segment will be present in the file (even if they were already in the previous one).
Warnings
In this section, specify if you want to receive warning for your Azure Storage activation.
Last updated