📘
Public Beta
This feature is released in Public Beta. For more information about this feature, contact your Success Manager or the CleverTap support.

Overview

Microsoft Azure, a Microsoft cloud computing platform, offers access, management, and development of applications and services through global data centers. The Microsoft Azure data export feature provides the capability to bulk export your CleverTap event data to Azure Blob Storage. You can use this for analysis in BI tools or storage in your data warehouse for analysis in the future.

Setup

The following are the two major steps involved in enabling this feature for your account:

Create a Microsoft Azure Storage Account

To create a Microsoft Azure Storage Account:

Log in to your Microsoft Azure account and select Storage Accounts from the left menu.
Click + Create to create a new storage account.

Enter the Storage account name, and do not modify the default settings.

Click Review and click Create. The following screen displays once the storage account is created:

The storage account you just created now shows up under the Storage accounts page.

Create a Blob Service Container

To create a Blob Service Container:

Navigate to the Blobs menu under the Blob Service section of your storage account.
Create + Container to create a Blob Service Container within the storage account you created in the previous section.

Enter the Name of your Blob Service Container, and do not modify the other default settings.
Click Create.

Generate a SAS Token

A Shared Access Signature (SAS) Token is a Uniform Resource Identifier (URI) that provides limited access to an Azure Storage container. It is used when you want to authorize access to storage account assets within a defined time frame while keeping your storage account key confidential. For more information about SAS, refer to Delegate access by using a SAS Token.

To generate a SAS Token:

Select the Container and click the icon.
Select Generate SAS from the dropdown list. The Generate SAS window opens on the right side of the screen.

Enter the following details:

Field	Description
Signing method	Select Account key from the Signing method list. The Signing method provides secure delegated access to resources in your storage account. For more information, refer to Types of shared access signatures.
Signing key	Select any one key from the following options: Key 1 Key 2 .
Stored access policy	Select the Stored access policy you want to define for your storage. When defining a policy, you need to define the following: start time, expiry time, and permissions for the signature. To export data from CleverTap to Microsoft Azure, you need Read and Write permissions for the container. When defined on a container, it grants permissions to the container itself or to the blobs that it contains. For more information, refer to Define a stored access policy.
Permissions	This is a mandatory field. Select the permission for the request made with the service SAS. To export data from CleverTap to Microsoft Azure, you need Read and Write permissions for the container. If you have already assigned the required permissions to your stored access policy, the same permissions will be assigned to the request made with the service SAS. For more information, refer to Account SAS Permissions by Operation.
Start and expiry date/time	Indicates the start and end date/time during which the blob SAS is valid. CleverTap recommends setting the expiration time to the maximum duration available. This is because you will not be able to export any data to the container if the expiration date has passed. For more information, refer to Configure a SAS Expiration Policy.
Allowed IP address	CleverTap recommends not adding any IP address range in this field. It indicates that Microsoft will accept export requests only from the IP address or range of IP addresses defined under this field. If you still want to add the IP address(es), you must whitelist the IP addresses listed under CleverTap IP Ranges.
Allowed protocols	Allowing requests over HTTPS only is recommended. This field indicates the protocols permitted for a request made with the service SAS.

Click Generate SAS token and URL.

Copy the generated SAS token and URL, as you will not be able to access it later.

Configure Microsoft Azure Blob Container on CleverTap Dashboard

To add your Microsoft Azure Blob Container to Clevertap:

Navigate to Settings > Partners and click Integrate against Mircosoft Azure. The Integrate analytics partner - Microsoft Azure window displays on the right side of the screen.

Integrate analytics partner - Microsoft Azure

Click + Microsoft Azure to create a new bucket. The Integrate Microsoft Azure Bucket window opens on the right side of the screen.
Enter the Bucket Nickname.
Select the Azure Blob Storage Endpoint.
- Default: Enter the Blob Storage Account name.

Default Blob Storage Account on Microsoft Azure Portal

Custom: Add a custom domain mapped to your Azure Blob Storage Endpoint. For more information about defining a custom endpoint, refer to Map a Custom Domain.

Enter the name of the container that stores data on Azure and the SAS token that we obtained in Step 4 of the Generate a SAS Token section.

Create a New Data Export

To create a new data export, perform the following steps:

Navigate to Settings > Partners > Exports.
Click + Export and select Microsoft Azure from the Partners dropdown.

On clicking, the Export to Microsoft Azure popup displays on the right side of the screen.

Configure the following settings:
- Type: Select the events to export from the available options. For more information, refer to Export Details.
- Frequency: Select from one of the following options:
  - Once only: A single export for the selected export type. You can export data up to the last 60 days. You create an export for a specific day, date range, previous month, current month, and more.
  - Recurring: Set up a recurring export that exports all the new events captured in the last window. You can export data as frequently as every 4 hours and up to once every 24 hours.
Click Create export. On clicking, the popup closes, and the following message displays at the top of the Exports page:

CleverTap processes the export, and you can now see the newly created export for Microsoft Azure.

New Microsoft Azure Export Displays on Exports Page

The status for each export is displayed as Pending as soon as the export is created. The status changes to Running after the processing starts. And it changes to Done when the export is complete.

📘
Stop Export
You can also stop the export that you have created. To do so, click the icon for the export request you want to stop, and then click Stop to confirm your action.

Confirm if your event data was successfully exported. To do so:
a. Log in to your Microsoft Azure account and select the Storage account under Resources.
b. Click the Blob service link under the Properties tab.
c. Select the Container where you exported the data.
d. (Optional) Click the Switch to Acces Key link if you encounter any authorization error after selecting the Container.

New Export Displays on Microsoft Azure Dashboard

Export Details

Export Type

All user events: This exports data for all events that have been defined, which include System and Custom events.
Select events: This exports specific events you want to export.
All user profiles: This exports all your user profile data.

Export Frequency

One time: Single export for the export type selected. You can export data up to the last 60 days.
Recurring: Set up a recurring export that exports all the new events/user profiles captured in the last window. You can export as frequently as every 4 hours and up to once every 24 hours.

Export Format

JSON
XML
CSV
Parquet

For more information, refer to the following section.

Export Format

This section provides information about the file format and the name format of the files exported to the S3 bucket.

File Name Format

File Name Format for Event Export
The example below shows the file name format for event export:
- Export request ID: Indicates the export request ID generated when you create a request in the CleverTap dashboard.
- Timestamp of export run: Indicates when the export was run.
- Event name: Indicates the event type that is included in the file.
- File index: We chunk the data across multiple files for larger exports. We limit file sizes to 100 MB chunks to make them more consumable. The file index indicates the file number in the file series.
- Database ID: Indicates the database ID of the CleverTap from where the file was exported.
- File format: Indicates the format of the file exported to the S3 bucket.

<export request id>-<timestamp of the export run>-<event name>-<yyyymmdd>-<file index>-<database-id>.json

File Name Format for User Profile Export:
The example below shows the file name format for user profile export:
- Account ID: Indicates the integer value for your CleverTap project ID.
- Request ID: Indicates the export request ID generated when you create a request in the CleverTap dashboard.
- Timestamp of export run: Indicates when the export was run.
- Database ID: Indicates the database ID of the CleverTap from where the file was exported.
- File format: Indicates the format of the file exported to the S3 bucket.

<account id>-<request id>-<timestamp of the export run>-<database-id>-<file format>.gz

File Data Format

Files are split by event names for event exports and each file will have all event data for the given period for the event.

JSON

The first line of the file contains the event name. After the first line, each line in JSON describes the timestamp, object id, and event properties.

{
	"profile": {
		"identity": "dqsndckfk234"
	},
	"ts": 20171109000015,
	"eventProps": {
		"ct_connected_to_wifi": "false",
		"ct_bluetooth_version": "ble",
		"ct_bluetooth_enabled": "false",
		"ct_sdk_version": 30107,
		"ct_latitude": -6.1975594,
		"ct_longitude": 106.52913,
		"ct_os_version": "5.1.1",
		"ct_app_version": "2.30.1",
		"ct_network_carrier": "3",
		"ct_network_type": "4G"
	}
}

CSV

CSV files are comma-delimited and have each event in separate rows.

XML

XML has the timeStamp, eventName, followed by eventProperties.

<Event>
    <ts>20200220130735</ts>
    <eventName>Export Custom Event</eventName>
    <profile>
        <all_identities>[email protected]</all_identities>
        <platform>Web</platform>
        <email>[email protected]</email>
    </profile>
    <deviceInfo>
        <browser>Others</browser>
    </deviceInfo>
    <eventProps>
        <entry>
            <key>CT Source</key>
            <value>API</value>
        </entry>
        <entry>
            <key>Category</key>
            <value>Mens Watch</value>
        </entry>
        <entry>
            <key>Product name</key>
            <value>Casio Chronograph Watch</value>
        </entry>
        <entry>
            <key>Price</key>
            <value>59.99</value>
        </entry>
        <entry>
            <key>Currency</key>
            <value>USD</value>
        </entry>
    </eventProps>
</Event>

Parquet

Parquet has a timestamp, eventName, and eventProperties for each event.

📘
Parquet File Format
Parquet is an open-source file format for Hadoop. Parquet stores nested data structures in a flat columnar format.

FAQ

Q. How to secure the data exports from CleverTap to Microsoft Azure?

A. You can whitelist IPs to ensure that CleverTap will only have access to push data to your Microsoft Azure bucket. To get the list of whitelisted IP ranges, refer to the CleverTap IP Ranges documentation.

Q. Do CleverTap data exports allow special characters?

A. Yes, CleverTap data exports allow the following special characters:

CleverTap's export system supports Unicode (UTF-8) character encoding. It facilitates the accurate representation of text in various languages and scripts. For example, Indian regional languages, Arabic, Korean, Russian, Japanese, Chinese, Spanish, Greek, Indonesian, etc.
It replaces the following characters with a hyphen to avoid issues in output file generation:
- Whitespace
- Tab
- Slash
- null (\0)
Control characters are replaced with ?. For more information, refer to Control Character.
Supports emoji characters; however, some emojis (UTF-16) may not render properly.