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, you'll learn how Postscript securely connects to your Redshift destination using Prequel, where you simply provide an initial detail, use a secure setup link to configure your bucket and permissions, and submit your credentials directly to Prequel so Postscript never accesses them.
NOTE: If your Redshift cluster is behind a security group with IP restrictions, you'll need to allowlist Postscript's IP addresses (provided by your Postscript contact) before connecting.
What We Need From You
To get started, share the following with your Postscript contact:
Field | Description |
Cluster / Workgroup Endpoint | Your Redshift cluster endpoint, found on the cluster's General Information page. If you're on Redshift Serverless, use the Workgroup Endpoint. |
S3 Bucket Name | An S3 bucket used to stage data before it's loaded into Redshift |
What Happens Next
Once we have your endpoint and staging bucket, we'll send you a secure Prequel connection link.
Open the link and follow Prequel's guided setup for Redshift. Prequel will walk you through creating the database user and schema and granting the permissions required for access.
Enter your credentials directly and securely in Prequel. Postscript never sees them.
Once connected, your historical data is pushed first, followed by new data every hour.
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.