
dbt integration with Ocean.io
Your data team trusts dbt. Put fit where they can check it.
Whether a segment actually performs is a question for the data team, and it needs fit next to revenue and usage. Ocean's tier, segment and firmographics reach dbt through the API and your existing pipeline tooling, keyed on domain.
Ways to connect dbt
What lands in dbt
- Fit score, tier and segment per company, as a table in dbt
- Firmographics and buying signals alongside them
- A refresh whenever scores change
Who it's for
- Data teams: fit as a joinable table, no custom pipe
- Leadership: retention and expansion by segment
Ocean acts as a context layer on dbt
Run Ocean's MCP server and dbt's on one agent. Ocean supplies fit and segments. dbt supplies what actually happened.
“Ask Ocean for our segments and tiers, then query dbt for revenue and usage by account and tell me which segment performs best.”
Needs dbt's MCP server, which depends on your plan and setup. Searches and exports spend Ocean credits.
Frequently asked questions
Does Ocean.io integrate with dbt?
Yes, through the Ocean API, a CSV or spreadsheet and an HTTP request step. It can also be done with MCP: dbt publishes an MCP server, so one agent can use Ocean's server and dbt's together, if your plan includes it.
How does Ocean data get into dbt today?
Through the Ocean API and whatever loads data into your warehouse now, or as a CSV for a first look.
A worked example (illustrative)
An analyst joins Ocean tiers to net revenue retention by account in dbt and splits it by segment. The question is concrete: which segments keep and expand customers, and does the tier predict it?
- Pull tier, segment and firmographics with the Ocean API.
- Load them next to revenue and usage tables in dbt.
- Join on domain.
- Compare retention and expansion by tier and segment.
Related integrations
Put Ocean to work in your stack
- Ranked accounts and the reason each one fits
- Scores, segments and signals written to the fields you choose