Skip to main content

Documentation Index

Fetch the complete documentation index at: https://help.statisfy.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Connect Redshift with Statisfy

The Redshift integration lets you import data from your Amazon Redshift cluster into Statisfy. Sync product usage metrics, account-level custom fields, and custom objects from the same warehouse you use for analytics. Redshift is PostgreSQL wire-compatible, so the connection model and configuration UX mirror the PostgreSQL integration — the differences are around schema introspection and the SQL dialect Statisfy uses to validate your queries. Prerequisites:
  • Admin access to Statisfy
  • A Redshift cluster reachable from Statisfy’s egress IPs (see Network Access below)
  • A Redshift database user with SELECT access on the schemas/tables you want to sync

​
What You Can Import

Data TypeDescriptionUse Case
Product UsageUsage metrics and adoption dataTrack MAU, API calls, feature usage
Custom FieldsAccount-level attributesSync industry, segment, scores from BI
Custom ObjectsDomain-specific recordsSync subscriptions, orders, deployments

​
Steps to Connect

  1. Log in to Statisfy.
  2. Navigate to: Integrations → Admin Apps → Redshift → Connect
  3. Enter your Redshift credentials:
    • Host — Cluster endpoint (e.g., my-cluster.abc123.us-east-1.redshift.amazonaws.com)
    • Port — Default 5439
    • Database — Target database name
    • Username — Service account username
    • Password — Service account password
  4. Click Test Connection to confirm Statisfy can reach the cluster and authenticate.
  5. Once connected, Redshift will appear as Connected on the Integrations page.

​
Configure Queries

Redshift uses the same self-serve configuration UI as the other warehouse integrations. Open Integrations → Redshift → Settings to:
  • Browse schemas and tables in your cluster
  • Author queries with autocomplete and a preview pane
  • Map results to Statisfy entities — accounts (via Statisfy account ID, CRM ID, organization ID, email domain, account name, or any custom field), product usage metrics, custom fields, or custom objects
  • Set the schedule — daily, weekly, or monthly cadence with an optional week-start-day override
Each saved query can be one of three types:
Query TypeOutput
product_usageTime-series metrics per account
custom_fieldAccount-level attribute values
custom_objectRecords of a custom object type
Queries are validated against the Redshift dialect before they run, and a preview against your cluster lets you confirm the result shape before scheduling.

​
Account Matching

Each query specifies how its rows map to Statisfy accounts via an account resolver:
ResolverDescription
Statisfy Account IDNative Statisfy account identifier
CRM Account IDSalesforce or HubSpot account identifier
Organization IDExternal org identifier
Email DomainCompany website domain
Account NameCompany name (fuzzy matching)
Custom FieldAny custom field defined on accounts
Rows that don’t resolve to an existing Statisfy account are skipped. Make sure the resolver column matches values already present in Statisfy.

​
Sync Behavior

Scheduled Jobs:
  • Each query runs on the cadence you configure (daily / weekly / monthly).
  • Self-serve configuration is read first; if no self-serve config is found for a query type, Statisfy falls back to any hardcoded mapping previously set up by support.
Error Handling:
  • Per-query errors are logged but do not block other queries from running.
  • Invalid rows within a query are skipped and reported in the job audit log.

​
Network Access

If your Redshift cluster is in a private VPC or has IP allowlisting enabled, allow Statisfy’s egress IPs: 
35.203.185.27
35.197.52.231

​
Security

  • Credentials are stored encrypted in Google Cloud Secret Manager.
  • All connections use SSL.
  • Queries authored in the Settings page are validated and parameterized — they cannot mutate your warehouse.
  • Access is scoped to the database user you provide — grant SELECT only on the schemas you want Statisfy to read.

​
Troubleshooting

Check network access:
  • Verify the cluster is reachable from the Statisfy egress IPs above
  • Confirm the security group allows inbound traffic on the Redshift port (default 5439)
Check credentials:
  • Verify host, port, database, username, and password
  • Confirm the user has CONNECT privilege on the database
  • Confirm the database user has USAGE on the schema and SELECT on the tables
  • System schemas (pg_catalog, information_schema, pg_toast, pg_internal) are intentionally hidden
  • Statisfy validates queries against the Redshift dialect before saving — Postgres-specific syntax that Redshift doesn’t support will be flagged
  • Check the validation error for the offending function or syntax and adjust to a Redshift-supported equivalent
  • Verify the resolver column contains values that exist in Statisfy
  • For CRM ID resolvers, confirm your CRM integration has synced the matching accounts
  • Try a different resolver (for example, switch from account name to email domain) if matching is unreliable

​
Need Help?

For initial setup, query design, or troubleshooting, contact support@statisfy.com.