For Data owners · Updated Oct 20, 2026
Choose how to connect your data
There are several ways to share CRM and analytics data with Scowtt. Your Scowtt team will help you pick the one that fits your environment best.
How we recommend a method
Scowtt prioritizes, in order: security, low effort for your team, standard well-supported architecture, and timely, reliable updates. Wherever possible, we recommend read-only access to data you already own and control, such as an S3 bucket or BigQuery dataset, rather than sharing credentials or granting write access into your systems.
Your options
| Method | Best when | Effort |
|---|---|---|
| Native CRM connector | You use Salesforce, HubSpot or Klaviyo | Fastest |
| BigQuery dataset share | Your data is in BigQuery or can be exported there, including GA4 | Low |
| SFTP | You want a simple way to get started quickly | Low |
| Amazon S3 | Your data is in AWS | Low |
| Google Cloud Storage | Your data is in Google Cloud | Low to medium |
| Snowflake export | Your data is in Snowflake | Moderate |
| Amazon Redshift export | Your data is in Redshift | Moderate |
| Databricks | Your data is in Databricks | Low to moderate |
| Amplitude export | Your product analytics are in Amplitude | Moderate |
| Twilio Segment delivery | Your customer data flows through Segment | Moderate |
| Push to Scowtt's API | Your team has developers and wants to send data in near real time | Higher |
| Scowtt pulls from your API | No other export path exists. Scowtt pulls hourly. | Highest |
If your data is in Snowflake
Snowflake customers export curated tables on a schedule to cloud storage that Scowtt can read.
- Preferred: a Google Cloud Storage bucket you own: Export your tables to a bucket in your own Google Cloud account, then give Scowtt read-only access. You keep full control over encryption, retention and access.
- Alternative: an Amazon S3 bucket you own: If exporting to Google Cloud Storage isn't practical, export to an S3 bucket in your AWS account and give Scowtt read-only access instead.
- If you don't have cloud storage: Scowtt can provide a destination bucket on request. Ask your Sales Rep or Account Manager before using this option.
Exports use Snowflake's standard COPY INTO command with an external stage. Share only the curated tables Scowtt needs, keep them in a folder used only for Scowtt, and follow the data format standards. Scowtt doesn't currently read from Azure storage, so if your Snowflake account runs on Azure, export to Google Cloud Storage or S3.
Other data platforms
Scowtt also works with these platforms. In each case, you keep ownership of your data and give Scowtt read-only access.
- Amazon Redshift: Schedule an export (Redshift's UNLOAD command) of the agreed tables to an S3 bucket you own, then give Scowtt read-only access.
- Databricks: If you already use Unity Catalog, share the agreed tables with Scowtt through Delta Sharing. Otherwise, export them to an S3 or Google Cloud Storage bucket you own. If your Databricks environment runs on Azure, ask your Sales Rep or Account Manager for the best option.
- Amplitude: Use Amplitude's built-in export to send data to a Google Cloud Storage bucket you own, or to an S3 bucket if that's easier for your team.
- Twilio Segment: Deliver data directly to BigQuery using Segment's BigQuery destination, or to an S3 bucket you own using Segment's AWS S3 destination.
Your Scowtt team will confirm the details for your setup, including which tables to share and how often to update them.
What we'll need from your team
| Item | Description |
|---|---|
| Datasets to share | The tables, schemas or event streams you'd like to connect |
| Historical backfill scope | For example, the last 90 days, 12 months or full history |
| Preferred refresh cadence | 15 minutes, 1 hour, 4 to 6 hours, or daily |
| Storage location or access details | S3 or GCS path, or BigQuery dataset details |
| Schema or data dictionary | Field definitions or links to your documentation |
| Technical contact | Who will support setup on your side |