Export sequence performance data for deeper analysis¶
You can export detailed sequence performance data from your Revenue Grid environment into CSV files for use in your business intelligence (BI) tools. This allows you to have full visibility into engagement performance over time.
The export process is fully automated and securely delivers data to Azure Blob Storage, where it is accessible via a shared access signature (SAS) URL.
This article explains how the export works and how to access the exported files.
How the export process works¶
The export feature provides a reliable, automated way to access sequence performance data for reporting and analysis. Once enabled for your account, the system begins collecting data from the Sequence database and delivering it in CSV format to your secure Azure Blob Storage folder.
Daily data export¶
Every day at 5:00 a.m. UTC, the system gathers all available data from the start of the current month up to the time of export. For example, on December 25, the system collects data from December 1 at 00:00:00 through December 25 at 05:00:00 UTC, the time the report is generated.
Each daily export creates a full month-to-date CSV file, which is saved to your dedicated storage folder.
Once the file is uploaded, it is never modified. This ensures that the file’s “last modified” timestamp always reflects the export date and can be used to identify the most complete version.
On the first day of each new month, the system runs an additional export to generate a complete file for the previous month. This ensures that events recorded late on the final day of the month are included.
File naming and folder structure¶
Each exported file follows the format: customer_{guid}.csv .
- For example:
contoso_123456a7-b89c-123d-45ef-g6789h0i123j.csv.
Files are stored in folders based on the reporting period, using the format: YYYYMM01–YYYYMMDD.
- For example, exports for December 2025 are stored in the folder
20251201–20251231.
Each monthly folder contains one CSV file for each day of the month, showing the cumulative data from the 1st up to that day.
- For example:
20251101-20251130/
contoso_{guid-for-day1-only}.csv
contoso_{guid-for-days1-2}.csv
...
contoso_{guid-for-days1-30}.csv
20251201-20251231/
contoso_{guid-for-day1-only}.csv
...
contoso_{guid-for-days1-31}.csv
This structure ensures that each daily file reflects a complete snapshot of the sequence data up to that point. As a result, you only need to select the most recently modified file from each folder to retrieve the latest data for that month.
Data security and access control¶
You will receive a secure, read-only SAS URL that allows access to your storage folder. This link can be used for manual downloads (via tools like Azure Storage Explorer) or automated access through supported BI tools.
The SAS URL is sent securely to your team using Bitwarden Send, a one-time, encrypted sharing method that ensures the link is not exposed through unsecured channels.
Security measures in place¶
- Read-only access: SAS URLs allow only read and list permissions. Write, update, and delete actions are blocked.
- HTTPS-only: All access is restricted to HTTPS connections.
- Data isolation: Each customer’s data is stored in a dedicated folder, accessible only via their unique SAS URL.
- No public access: Blob storage is configured to block public access by default.
- Access duration: SAS URLs are valid five years from the creation date.
Note
If your organization requires regular SAS URL rotation or has specific security requirements, contact your Customer Success Manager to coordinate a custom setup.
Data retention¶
Exported files are retained for three years. After that, they are automatically deleted according to the retention policy configured in your storage container.
Exported data¶
The exported CSV file contains raw, structured data from multiple parts of the engagement workflow. It includes campaign details, step activity, contact information, email and call records, and more—providing a complete dataset suitable for deep analysis in BI tools.
Exported CSV field reference
Note: The table below reflects the export format as of June 10, 2025. We may add new fields in the future, but the format will stay compatible, so it doesn’t break your import setup. When new fields are added, we’ll clearly indicate the date from which they are available.
| Field name | Field description | Value example |
|---|---|---|
| Campaign_Id | Unique identifier of the sequence | b7bac9c8-3835-4456-872c-f559f2f98e29 |
| Campaign_Name | Name of the sequence | Testing many clicks and opens |
| Campaign_CrmCampaignId | ID of the connected Salesforce campaign (if applicable) | |
| Campaign_CreatedOn | Date and time the sequence was created | 2025-05-27T15:42:19.5158656 |
| Campaign_CreatorEmail | Email address of the user who created the sequence | [email protected] |
| Campaign_SharingMode | Sharing mode of the sequence (e.g., private, shared) | shared |
| Campaign_Status | Current status of the sequence | running |
| Campaign_Priority | Priority assigned to the sequence | normal |
| Campaign_Tags | Tags assigned to the sequence | |
| Campaign_ClickedContactsCount | Number of contacts who clicked at least one link in the sequence | 1 |
| Campaign_RepliedContactsCount | Number of contacts who replied to the sequence | 0 |
| Campaign_SucceededContactsCount | Number of contacts who reached a successful outcome in the sequence | 0 |
| CampaignStep_Id | Unique identifier of the step within the sequence | 3b7cb8a7-7f38-4884-9bbc-dad063af604d |
| CampaignStep_Type | Type of sequence step (e.g., mail, call, misc.) | |
| CampaignStep_Name | Name or subject of the step | Step 1 – Email (Automated) |
| CampaignStep_Order | Order number of the step in the sequence | 1 |
| CampaignStepSchedule_Id | Identifier of the schedule used for this step | 5d1731ca-98cb-4f3c-931f-449a356ad5c7 |
| CampaignStepSchedule_Name | Name of the schedule assigned to this step | New schedule 24/7 ON |
| CampaignStepSchedule_ExcludeHolidays | Indicates whether holidays are excluded from the schedule | FALSE |
| CampaignStepSchedule_Periods | Weekly schedule windows when the step is allowed to execute | Mon–Sat [00:00 - 23:59] |
| CampaignStepTemplate_Id | ID of the step template used | 5d1731ca-98cb-4f3c-931f-449a356ad5c7 |
| CampaignStepTemplate_Name | Name of the step template | Thanks for joining the webinar |
| Contact_Id | Unique identifier of the contact | 6994f98e-0cda-4c12-a173-0c509c4f401a |
| Contact_Email | Contact’s email address | [email protected] |
| Contact_FullName | Full name of the contact | [email protected] |
| Contact_CompanyName | Company name associated with the contact | ACME Inc. |
| Contact_OwnerEmail | Email of the user who owns the contact | [email protected] |
| Contact_SourceType | Source system the contact came from | salesforce |
| Contact_SourceKey | External ID of the contact from the source system | 0030q00000VRzcoAAD |
| Contact_InternalStatus | Internal system status of the contact | unresponsive |
| Contact_Tags | Tags assigned to the contact | |
| Contact_CreatedOn | Date and time the contact was added to the system | 2023-11-22T09:43:34.2358944 |
| CampaignContact_CreatedOn | Date the contact was enrolled in the sequence | 2025-05-27T15:43:46.8029217 |
| CampaignContact_State | Current execution state of the contact in the sequence | failed |
| CampaignContact_Status | Status of the contact within the sequence | unresponsive |
| CampaignContact_CreatorEmail | Email of the user who added the contact to the sequence | [email protected] |
| CampaignContact_TimeZone | Time zone used for scheduling steps for this contact | (UTC-06:00) Central Time (Chicago) |
| CampaignContact_StatusChangedOn | Last date and time the contact’s status changed in the sequence | 2025-06-10T15:46:18.0830375 |
| CampaignContactStep_PlannedStartDate | Scheduled start time of the sequence step for this contact | 2025-05-27T15:44:31.2701832 |
| CampaignContactStep_Status | Status of the step execution for this contact | actionsucceeded |
| CampaignContactStep_UserStatus | User-defined status of the step for this contact | failed |
| CampaignContactStep_CompletedDate | Completion date and time of the step for this contact | 2025-05-27T15:45:13.2740639 |
| CampaignContactStep_ExecuteOnBehalfOf | User who executed the step on behalf of someone else (if applicable) | [email protected] |
| CampaignContactStepActivity_Type | Type of activity recorded for the step (e.g., emailOpen, linkClick) | emailOpen |
| CampaignContactStepActivity_RecordedOn | Date and time when the activity was recorded | 2025-05-27T10:55:36 |
| Mail_Type | Type of email communication | outbound |
| Mail_Class | Class of the message | ordinary |
| Mail_ReceivedOrSentOn | Timestamp when the email was sent or received | 2025-05-27T15:45:02 |
| Mail_Subject | Subject line of the email message | How to test many clicks and opens? |
| Mail_Sender | Email address of the sender | [email protected] |
| Mail_RecipientsTo | Primary recipients of the email | [email protected] |
| Mail_RecipientsCc | CC recipients of the email | |
| Sms_Type | Type of SMS communication | |
| Sms_Status | Delivery or read status of the SMS | |
| Call_ProviderType | Call provider used | |
| Call_ContactPhoneNumber | Phone number of the contact | |
| Call_UserPhoneNumber | User’s phone number used in the call | |
| Call_Direction | Direction of the call (inbound or outbound) | |
| Call_Status | Call outcome or status (e.g., answered, missed) | |
| Call_StartedOn | Start time of the call | |
| Call_EndedOn | End time of the call |
How to access and use the exported data¶
You will receive a secure SAS URL that provides read-only access to your exported data in Azure Blob Storage. You can download files manually using Azure Storage Explorer or connect directly to the storage from your BI tool.
Please select your preferred access method below to follow step-by-step instructions: one for manual download and one for connecting through Power BI.
To download files using Azure Storage Explorer:
- Download and install Azure Storage Explorer.
-
Open the app and select the plug icon to open the Connect dialog.
-
Select Blob container or directory.
-
Select Shared access signature URL (SAS), then click Next.
-
Paste the full SAS URL provided to you and select Next, then Connect.
-
In the left pane, browse to your dedicated folder, then open the folder for the reporting period you need (e.g.,
20251201–20251231).
-
Identify the most recently modified file in the folder and select it.
-
Click the Download button in the top toolbar.
-
Choose a local folder on your device to save the file, then select Select Folder to start the download.
Once downloaded, you can open the CSV file or import it into your BI tool for analysis.
To connect directly to your exported data in Power BI Desktop:
- Download and install Power BI Desktop, then open it.
-
On the Home tab, select Get Data.
-
In the Get Data window, select Azure Blob Storage, then click Connect.
-
In the Azure Blob Storage dialog, paste the container URL without the SAS token (everything before the
?in your SAS URL, for example:https://yourstorageaccount.blob.core.windows.net/yourcontainer) and click OK.
Note
Power BI does not support full SAS URLs in the “Web” connector. You must split the SAS URL into two parts: the base container URL and the SAS token string.
-
When prompted for authentication:
- Choose SAS.
- Paste the SAS token string (everything after the
?in your SAS URL). - Click Connect.
Power BI displays a table containing all accessible files in the container, with metadata such as file name, folder path, and last modified date.
-
Click Transform Data to open the file list in Power Query Editor.
-
In Power Query:
- Filter by folder path or file name to narrow down to the folder you want (for example,
20251201–20251231). - Sort by the Date modified column and keep only the most recent file.
- If analyzing multiple months, select one file per folder and use Append Queries to combine them into a single dataset.
- Filter by folder path or file name to narrow down to the folder you want (for example,
-
When you’re done, click Close & Apply to import the data into Power BI.
Your selected file(s) are now available as a dataset, ready for reporting, filtering, or visualization.
Request access to the export feature¶
The sequence data export feature is available upon request. To enable it for your organization, contact your Customer Success Manager or Revenue Grid Support.
After your request is approved, our team will:
- Provision secure storage for your tenant.
- Configure export automation.
- Send your SAS URL securely via Bitwarden Send.
Summary¶
The sequence data export feature provides secure, automated access to raw engagement data for use in reporting and analytics. Files are exported daily, organized by month, and stored in Azure Blob Storage with long-term retention and strict access controls.
You can access the data manually or connect directly through your BI tools, such as Power BI. To enable this feature, contact your Customer Success Manager or Revenue Grid Support. Once set up, you can immediately begin analyzing your sequence data with your preferred tools.