Databricks + Outcome
Databricks already holds the numbers your teams model. Outcome makes them the measure of a goal. Together, a saved query or metric view becomes a goal's number with its full history, and Databricks' own spend lands on the goals it served.
Databricks brings the facts. Outcome turns them into decisions.
| Use | From Databricks | What Outcome does with it |
|---|---|---|
| Measures |
| A goal's number is read on a schedule, with its history. |
| Financial |
| Cost lands on the goals it served, and spend that served none shows too. |
Databricks + Atlassian + TeamForm + Salesforce + Outcome
What it never reads
- Jobs, notebooks and secrets
- Anything but one SELECT
- Tables the service principal cannot see
- Writes of any kind to Databricks
Status
Preview Data and BI
Live In the product today. Preview Working, refined with customers.
Connected in minutes, by an admin.
- 01Open
An owner or admin opens Settings, Integrations, Databricks.
- 02Connect
Paste: Service principal client ID, OAuth secret.
- 03Choose
Pick the number for a goal. It is read on the schedule you set.
- 04Done
Nothing is ever written to Databricks.
Connect Databricks and see what it brings in on the first sync.
Also in data and bi Power BI · Tableau · Google BigQuery · Snowflake