Azure Blob Storage is a storage service under Azure Cloud Platform. Azure Blob storage is Microsoft’s object storage solution for the cloud. Blob storage is optimized for storing massive amounts of unstructured data, such as text or binary data.
The event data will be forwarded as plain text files containing new-line delimited JSON objects. The file cannot be parsed as JSON in its entirety. Instead, each line in the file will correspond with a single event batch formatted as a JSON object. Please refer to the mParticle JSON documentation for a detailed description of the data format used for each batch.
For example, if two batches are forwarded at once, the blob will contain something similar to the following (note some fields were removed for brevity):
Each blob should be named using the following format:
<App Name>_<UTC timestamp set as message is forwarded>_<Random 5 digit number>.txt.
Optionally, you can store blobs in a folder within your Azure container by providing a Folder Name in mParticle’s Azure Blob Storage Integration Connection Settings.
You can further organize blobs into date-based folders, with the name format:
Files can be sorted into folders in several ways according to how you set Store Data in Folders By Date in the mParticle’s Azure Blob Storage Integration Connection Settings:
|Setting Name||Data Type||Default Value||Description|
||The name of your Azure Storage account.|
||One of the keys for your Azure Storage account. Microsoft recommends using the first key, but either may be used.|
|Setting Name||Data Type||Default Value||Platform||Description|
|Blob Container Name||
||All||The name of the Azure container that mParticle will use to store event data.|
||All||An optional folder name in your Azure container to store the event data.|
|Store Data in folders by Date||
||None||All||If enabled, your data will be stored in a folder according to the chosen method.|
||All||An optional string identifier for your app that will be forwarded with each event batch. Standard app identifiers (Apple OS Bundle ID, Android Package Name) will be forwarded regardless of this setting.|
|Metadata Field Exclusion||Custom Field||All||A way to exclude specific fields of metadata properties in the output.|
||True||All||If enabled, the following metadata - application_info, device_info and source_info will be forwarded.|
||False||All||If enabled, data will be compressed in gzip format.|
|Include MP DeviceId||
||False||All||If enabled, MP DeviceId (Device Application Stamp) will be forwarded with event batches.|
|Send as Batch||
||True||All||If enabled, this setting will cause your app’s events to be sent in (roughly) 10-minute batches per device. If disabled, mParticle will send each event individually as it’s received.|
|Send Batches without Events||
||True||All||If enabled, an event batch that contains no events will be forwarded.|
|Send Profile Change Events||
||True||All||Deprecated, do not use. Instead, log a custom event at
|Include User Attribute Change Events||
||False||All||If enabled, User Attribute Change Events will be forwarded.|
|Include User Identity Change Events||
||False||All||If enabled, User Identity Change Events will be forwarded.|
Was this page helpful?