For Data owners · Updated Nov 6, 2026
Choose how to connect your data
There are several ways to share data with Scowtt, in two groups: web analytics connections, for data about what visitors do on your site, and offline data (CRM) connections, for leads, bookings and revenue. Most customers use one of each: GA4 for web analytics, plus one option for CRM data. Pick the first option in each group that fits the systems you already use.
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 a BigQuery dataset or a storage bucket, rather than sharing credentials or granting write access into your systems.
Most options need no passwords or access keys from you. The two exceptions are Databricks Delta Sharing, which uses a sharing token, and the API pull, which uses read-only credentials you create. You can remove Scowtt's access at any time.
Your options
Web analytics connections
| Method | Best when | Your team's effort | Who sets it up |
|---|---|---|---|
| Google Analytics 4 (GA4) | You use GA4. Share your own BigQuery export, or let Scowtt host it | Low: turn on the export and connect the dataset, or add one Scowtt user | GA4 admin |
| Adobe Analytics Data Feed | You use Adobe Analytics | Moderate: create a location and an hourly data feed | Adobe Analytics admin |
Offline data (CRM) connections
Listed from least to most work for your team.
| Method | Best when | Your team's effort | Who sets it up |
|---|---|---|---|
| Native CRM connector: Salesforce, HubSpot, Klaviyo | You use Salesforce, HubSpot or Klaviyo | Minutes: an admin signs in and approves access | CRM admin |
| BigQuery dataset share | Your CRM or offline data is in BigQuery | Low: grant read access to a dataset | Google Cloud project owner |
| Databricks Delta Sharing | You use Databricks with Unity Catalog | Low: create a share and a recipient | Databricks admin |
| SFTP | You don't use cloud storage, or a tool or vendor can only send files | Moderate: create a key, then schedule an upload job | Data engineer, or your vendor |
| Google Cloud Storage | You're on Google Cloud | Moderate: create a bucket, grant read access, schedule exports | Google Cloud admin and data engineer |
| Scowtt-managed bucket | Your tool writes files out and you don't have cloud storage | Moderate: set up the destination in your tool | Data engineer |
| Amazon S3 | You're on AWS | Moderate: create a read-only role from our templates, schedule exports | AWS admin and data engineer |
| Push to Scowtt's API | Your developers want to send records as they happen | Higher: build and run a push job | Your engineering team |
| Scowtt pulls from your API | Your data is only reachable through an internal API. Scowtt pulls hourly | Highest: share API docs and credentials, then Scowtt builds a connector | Your API owner, with Scowtt engineering |
Before you start
- The data. CRM or offline data: lead and contact records, sales activity, funnel stages, and outcomes such as appointments, opportunities, purchases and revenue, each with a timestamp. Web analytics: raw, event-level data, from GA4 through its BigQuery export, or Adobe Analytics through a Data Feed. See Required fields and lifecycle stages for the full list.
- Click IDs. Each lead record should carry the ad click ID that produced it: GCLID, GBRAID or WBRAID for Google, and FBCLID for Meta. See Capturing click IDs on your forms.
- History. A one-time backfill of 24 months of CRM history, with 12 months as the minimum. GA4's BigQuery export only collects data from the day it's turned on, so turn it on as early as you can.
- Refresh cadence. Updates at least 4 times a day after the backfill, ideally hourly. See Data refresh schedule.
- Who to involve. Your CRM admin, whoever owns GA4 or Google Cloud, a data engineer for scheduled exports, and your security or legal reviewer. Start any security review at kickoff, since it's often the longest step.
How setup works
-
Sign in to the Scowtt app
The Account setup checklist walks you through seven steps: Connect your CRM, Map customer journey, Validate data, Connect ads, Connect Analytics, Review pilot goals, and Upload baseline metrics (optional). All connections live under Settings > Integrations, grouped into CRM, Analytics and Advertising.
-
Pick an option for each data source
Use the tables above, or the platform guides below.
-
Follow that option's article
Most options follow the same pattern: Scowtt sends you something, your team sends something back, and Scowtt confirms when data is flowing.
-
Send the backfill first
Scowtt validates it with you (row counts, schema and sample records) before turning on recurring updates.
Guides by platform
| Your data lives in | Use |
|---|---|
| Snowflake | Export data from Snowflake |
| Amazon Redshift | Export data from Amazon Redshift |
| Amplitude | Export data from Amplitude |
| Twilio Segment | Send data from Twilio Segment |
| Azure storage | Export to Google Cloud Storage or Amazon S3. Scowtt doesn't read Azure storage directly |
| Another CRM or a call-tracking tool | If you already copy it into a warehouse with a tool such as Fivetran or Airbyte, share it from there. Otherwise, schedule exports to SFTP, or ask about an API pull |
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 |
|---|---|
| Option and datasets | Which option you're using, and the tables, datasets, objects or event streams included |
| Access details | The path, dataset ID, share or connection details from that option's last step |
| Historical backfill scope | 24 months preferred, 12 months minimum |
| Refresh cadence | At least 4 times a day, ideally hourly, and whether updates are changes only or full copies |
| Schema or data dictionary | Field definitions or links to your documentation |
| Technical contact | Who will support setup and validation on your side |