by Trivas.aiTrivas.ai documentation isn't sitting on one tidy page. It's spread across a handful of dedicated sections, each built for a different job: API reference material lives separately from integration how-tos, and the data dictionary is its own beast entirely. That's by design, but it means people often can't find the specific doc they need on the first try.
This page fixes that. It maps every documentation resource Trivas maintains, in one place, so you're not guessing which section covers what.
Three groups tend to land here. Developers wiring up the API and need endpoint specs. Data analysts trying to figure out why a metric in Trivas doesn't match their own Redshift query. And ops teams staring at a broken sync at 8am, trying to fix it before the daily standup. Below, each doc category gets a one-line summary before you click through.
Developer docs is the index for anything API-related: authentication, endpoint references, rate limits, and request/response schemas. If you're building a custom integration or pulling raw data into your own BI stack, this is the reference material you want open in a second tab.
It's worth separating this from /resources/help/api-integrations, which is task-based rather than reference-based. The developer docs tell you what an endpoint accepts and returns. The API integrations help section walks you through connecting a specific platform end to end, with the actual clicks involved. Different job, different doc.
If you need someone on Trivas's engineering side rather than a page to read, /solutions/api-developer-support is where that support lives. Worth using when you're mid-build and stuck on something the docs don't address directly, not as a first stop.
First-timers usually hit three things right away: generating an API key, figuring out sandbox versus production environments, and setting up webhooks for event-driven syncs. Get those three sorted before you touch anything else. Most integration headaches trace back to someone testing in the wrong environment or missing a webhook scope.
For connecting Trivas to your actual data sources, /resources/help/data-integration has step-by-step guides for Amazon, Shopify, Meta, Google Ads, and GA4. Each guide covers the same three things: required permissions for the connection, how often the sync runs, and how fields map from the source platform into Trivas's schema.
Field mapping is the part people skip and regret. If your Shopify product tags don't match what you expect in a dashboard, it's almost always a mapping issue documented right there in the guide, not a bug.
One distinction worth knowing: the solution pages like /solutions/shopify and /solutions/amazon explain why you'd connect that platform and what you get out of it. The help docs are where you actually do it. If you're pitching Trivas internally, read the solution page. If you're the one plugging in API credentials, go straight to the help doc.
/resources/data-dictionary defines every metric that shows up on a Trivas dashboard: blended ROAS, contribution margin, MER, and everything else. This is the index, and it's the one page in this whole guide worth bookmarking if you're an analyst.
Here's why it matters more than it sounds like it should. If a number in Trivas doesn't match what your own Redshift query spits out, the fix usually isn't a bug report, it's checking whether Trivas's definition of that metric matches yours. Contribution margin alone has enough variants (with or without shipping cost, with or without returns) that mismatches are common and rarely anyone's fault.
The individual metric pages live under this index, but don't try to guess their URLs. Browse from the data dictionary itself and click through, since child page slugs aren't predictable and change as new metrics get added.
/resources/help/dashboards-analytics covers building custom reports, setting filters, and configuring the Wingman AI insights layer. This is where you'll find dashboard permission settings, how to schedule report exports so they land in someone's inbox automatically, and how the forecasting models pull from underlying sync data.
Keep this separate in your head from the data dictionary. The data dictionary tells you what a metric means. This section tells you how to build the view that displays it, filter it, and share it. Different question entirely, and conflating the two is the most common way people end up on the wrong page.
When something's actually broken, /resources/help/troubleshooting covers the usual suspects: sync errors, data lag, and connector re-authentication steps for when a platform token expires. Most sync issues resolve with a re-auth, not a support ticket, so check here first.
For anything account-related, /resources/help/billing-plans documents plan limits, seat management, and how to pull past invoices.
If your question doesn't fit neatly into either bucket, /resources/help-center is the general support hub. Think of it as the catch-all for questions that aren't technical enough to need the developer docs but aren't quite a billing issue either.
If you haven't set up an account yet, none of the above is where you start. /resources/getting-started covers onboarding: initial account setup, connecting your first data source, and the basics of navigating the platform.
The scope difference matters here. Getting-started is a one-time walkthrough for first-time setup. Everything else on this page is ongoing technical reference you'll come back to for months. If you're still evaluating Trivas and haven't gone live yet, this is genuinely the right place to start, not the API docs or the data dictionary.
To recap: developer and API reference, data integration guides, the data dictionary, dashboards and analytics configuration, troubleshooting, and billing all live in their own dedicated sections, and now you know which is which.
If you've gone through the relevant docs and something's still unanswered, particularly if you're a technical team evaluating Trivas and weighing it against something like Triple Whale or Northbeam, /talk-to-a-founder is a reasonable next step. No pressure to commit to anything, it's just a faster way to get a specific technical question answered than digging through another doc page.
And if you just want to keep tabs on new features and doc updates as they roll out, the Trivas newsletter is a low-effort way to stay current without checking back here every week.
explore more insights
3 min read
3 min read
3 min read
.d53b12e5.png&w=3840&q=75 "Trivas.ai")