Product events, metrics, and customer attributes help Cust understand adoption alongside conversations and CRM data. Admins manage these connections in Settings → Integrations.

Connecting a source and defining what to import are separate steps. Review the configured resources, queries, and identifiers with the person responsible for your product data.

Snowflake

Choose Snowflake and follow the connection wizard. It asks for the Snowflake account and the warehouse, database, and schema to use, and provides setup SQL for the OAuth security integration. A Snowflake administrator should review and run that setup, then complete authorization in Cust.

Check the connection's configured queries and sync status. If the connection shows an approaching authorization expiry, reconnect before it expires to keep scheduled imports running.

BigQuery

Choose BigQuery and follow the service-account setup instructions shown in Cust. The wizard calls for BigQuery Job User and BigQuery Data Viewer permissions and a service-account JSON key.

Upload the JSON key in the connection form. Cust validates it before saving the connection. Give the service account access to the projects and datasets needed by your configured queries, and treat the key as a credential.

Mixpanel

Create a service account with the Consumer role in the Mixpanel project's settings. In Cust, choose Mixpanel, enter its Username and Secret, and connect.

The sync uses the event selection and profile settings configured for the connection:

Selected product events sync on an hourly schedule. With no event whitelist configured, product-event import is off.
User profiles sync hourly when profile sync is enabled.
Configured JQL queries can provide aggregates on their own schedules.

Check these settings when a connection is healthy but an event or metric is missing. Contact Cust if the data selection you need is not editable on your connection page.

PostHog

Choose PostHog and enter the personal API key and project details requested by the form. Use the correct PostHog host for the project.

Cust imports the selected product events on an hourly schedule. Confirm the configured event selection and the identifiers used to match people to your contacts.

Verify the result

After the first successful sync, inspect a known company and contact:

Check imported attributes and metrics.
Check whether product activity is reflected in the contact's user status.
Compare a known source record and timestamp with what Cust received.

Missing data can come from a query or event filter, source permissions, unmatched identifiers, or a failed sync. A connected status alone does not confirm that every event or table is being imported.

For file-based metric imports, see Data import. For programmatic imports, see the Partner API.