What this feature is used for
The integration lets Minoa read metric rows from an agreed table or view in your data platform on a recurring schedule. Rows are staged, matched to the right accounts and business case inputs, and written into value realization measurements—so teams see up-to-date actuals without manual entry. You can expose only a curated table or secure view and keep more sensitive data out of scope. Supported data platforms- Snowflake
- Google BigQuery
- Databricks
- ClickHouse
Metrics ingestion is rolled out per organization. Contact your Minoa account team to enable it and to align on
access during onboarding. Availability can vary by platform—your team will confirm what applies to your workspace.
Setup process
Note: Users with administrator (or integration) privileges in Minoa complete the in-product steps.Prepare your feed
Create or designate a table or view with the logical columns below, and a dedicated read-only principal for
Minoa.
Map the connection
Provide connection settings and map source column names to Minoa’s metric fields (including a cursor column
for incremental sync).
How it works
On each run, Minoa polls new or updated rows from the agreed object, maps columns to metric fields, and processes them through a short pipeline. Metric links map each external metric identifier and account to the correct business case input so values land in the right place automatically.Scheduled sync
Imports run on an interval you configure with Minoa (for example hourly or daily). Minoa tracks a cursor
column so each run only picks up new or changed rows where appropriate.
Metric linking
In Settings → Integrations, admins define metric links: which external metric ID and Minoa
account map to which opportunity and input. After linking, matching rows update those inputs without
extra routing data in every row.
What your data team prepares
Least-privilege access
Create a dedicated user or service principal for Minoa with read-only access to the target table or view (not the whole warehouse). Exact grants depend on the platform—for exampleUSAGE and SELECT where applicable. Authenticate using the method your security team requires (often key pair or short-lived credentials).
Network allowlisting
If your network policy requires IP allowlisting for Minoa, contact Support or your Minoa account contact. They can provide the appropriate addresses for your environment.Table or view shape
Focus on the metrics you want to pull into Minoa for value realization—your source does not need to line up one-to-one with every input or row in the product. Provide (or build a secure view over) a table that includes those measures. Compare what you plan to expose with your Value Framework (the use cases and inputs your team tracks on deals). If you want help deciding which metrics belong in the feed, contact Support or your Minoa account contact. Exact column names are flexible; during setup you map them to roles such as:| Logical field | Purpose |
|---|---|
| Account identifier | Stable ID that Minoa can align with a Minoa account (same identifier your team uses in CRM or Minoa). |
| External metric ID | Stable key for the metric (for example product.mtt_resolve). Used with metric links for routing. |
| Metric value | Numeric measurement. |
| Measurement time | When the measurement applies—typically a full timestamp with timezone. |
| Business interval (optional) | For example a month label (2026-02) if you track metrics by period. |
| Cursor column | Used for incremental polling: a monotonically increasing or watermark-style column (for example updated_at or an event time) so Minoa can fetch only new or changed rows. |
What you configure in Minoa
Enablement and connector setup
The Minoa support enables the capability and works with you to configure the warehouse connection (endpoint or account identifiers, database/schema, warehouse or compute where relevant, target table or view, credentials, sync interval, and column mapping including the cursor column).Ongoing operations
After the connector is live:- Test and sync — You can verify connectivity and trigger runs from Settings → Integrations (behavior depends on your workspace configuration).
- Metric links — Maintain metric links so each
externalMetricId+ account pair resolves to the intended business case input. This is how automation stays accurate as you add accounts or metrics. - Measurements — Accepted values appear on the relevant time-series inputs in the value realization scenario; see Measurements.
Related
- Measurements — Where ingested values surface on business cases.
- Data export — Scheduled export from Minoa to your warehouse or sheets. Warehouse metrics ingestion is the into Minoa direction for value realization.