Who gets this? Data Warehouse Push is currently only available in beta for Postscript brands on the Enterprise plan. To begin using Data Warehouse Push, please be sure to first contact your Customer Success Manager.
Data Warehouse Push allows Postscript to automatically send both historical and new data stored in-app, including clicks, order attribution, and more, to your designated data warehouse.
In this article, we'll walk you through the three steps for configuring your Blob Storage container.
IMPORTANT! Once complete, share the credentials with Postscript and we'll handle the rest.
Prerequisites
An active Azure subscription with access to a Storage Account
Only Standard Azure accounts can use Azure Blob Storage Containers (Custom Filezones) with Data Integration. Ensure that you select Standard in the Performance section
Step 1: Create a Storage Account and Container
Log in to the Azure Portal.
Create or select an existing General-purpose v2 (Standard) Storage Account. When creating, ensure Standard is selected in the Performance section.
Navigate to Data storage > Containers and select + Container.
Give the container a name (e.g.
postscript-data)Select Create.
Step 2: Choose an Authentication Method
You can give Postscript access to your container in one of two ways. Pick whichever fits your security requirements.
Option A: Account Key (simplest)
In the Azure Portal, go to your Storage Account.
Navigate to Security + networking > Access keys.
Copy your Storage account name and either Key1 or Key2 — you'll share these with Postscript.
The account key grants full access to the storage account and does not expire until rotated.
Option B: Account SAS (scoped, time-bound)
A Shared Access Signature (SAS) gives time-bound, scoped access without sharing your account key. Generate the SAS in the Azure Portal under your Storage Account → Security + networking > Shared access signature.
The SAS must meet all of the following requirements:
Allowed services: Blob
Allowed resource types: Service, Container, and Object (all three are required — Service-level access is needed for our integration to enumerate containers during setup)
Allowed permissions: Read, Write, Create, Delete, List, Add (and Tag/Filter if available)
Allowed protocols: HTTPS only
Expiry: at least 6 months out (12+ months recommended)
IMPORTANT! A container-scoped SAS (sr=c) will not work — our integration requires Service-level access during Sync activation. You must generate an Account SAS.
NOTE: If your SAS is signed with Azure AD (a "user-delegation SAS"), Azure caps its lifetime at 7 days maximum. For ongoing data syncs this requires weekly rotation, which is operationally fragile. We recommend an account-key-signed Account SAS for longer expiries.
Step 3: Gather Your Connection Details
Send Postscript the following based on which authentication method you chose in Step 2.
Field | Required for | Description |
Account Name | Both | The name of your Azure Storage Account |
Container Name | Both | The name of the container you created in Step 1 (e.g. |
Sub-folder Path | Both | A path within the container where files should be written (e.g. |
Account Key | Option A only | Key1 or Key2 from the Access Keys page of your storage account |
SAS URL | Option B only | The full SAS URL including the token query string (e.g. |
Get Support
Have questions? Please feel free to reach out to our Support team at [email protected] or via live chat.
Need ongoing channel strategy guidance? Please fill out this form and we'll connect you to one of our certified partners.