The Owner's Screen ServiceTitan Can't Draw Alone: Jobs, Revenue, Calls and Ad Spend Together

Monday, 7:15 a.m., and four tabs that refuse to agree

The ritual is familiar. ServiceTitan in one tab, Google Ads in another, the call tracking account in a third, and a spreadsheet in the fourth where someone copies numbers from the first three. The spreadsheet has a column called ROI that nobody remembers defining. The agency's monthly PDF reports clicks, impressions and a cost per lead calculated on leads ServiceTitan has never heard of.

None of these tools is wrong. Each one is right about its own slice. The trouble is that the owner's real questions cut across all of them: which campaign produced paid jobs, how fast the office answered the web leads it got, how many estimates are still open from the spring. That cross-cut is what a custom dashboard is for, and also the only good reason to build one. Everything else ServiceTitan may already do. The rest of the website connections are mapped on the ServiceTitan integration hub.

Before you pay for a dashboard, open the ones you already own

ServiceTitan's reporting is broader than most owners use. Here is what its help center documents as of November 2026.

• Built-in reports, which ServiceTitan describes as "pre-built reports included with ServiceTitan that track commonly used business metrics."
• Custom reports, built from report templates (ServiceTitan's word for datasets) with the columns, filters and layout you choose. The help center says creating them "is available only to customers on the Works package or Legacy/Non-Packaged customers."
• Legacy reports, the originals, which are "filterable but not customizable."
• Scheduled and exported reports, so the numbers arrive on a schedule instead of waiting to be looked up.
• Custom dashboards made of report modules, KPI modules that "Display up to six key performance indicators" from a report template, and visualization modules. Whether you can build them "is dependent on the ServiceTitan package you have."
• Rollup Reporting for Enterprise Hub customers, across every location's business units.

There is also Atlas, ServiceTitan's AI assistant. ServiceTitan's October 2026 blog says it "pulls from your existing reports, including custom reports," and its press release says owners can ask it "about sales performance, revenue or why a number moved." The same blog says Atlas is "in closed alpha for admins only" with pricing not yet set. Worth watching; not yet something to plan a quarter around.

The numbers that live outside ServiceTitan's walls

ServiceTitan knows the job, the invoice, the technician and, with Marketing Pro and call tracking in place, a good deal about the campaign. It does not know what happened before the customer became a record. That is the data a custom dashboard adds, and the table shows where each piece comes from.

If the click IDs never reached ServiceTitan in the first place, no dashboard can join them afterward. That plumbing is on the marketing attribution guide and the call tracking guide, and it comes first.

Reading ServiceTitan's data without breaking its rules or its limits

ServiceTitan publishes a Reporting API, and its OpenAPI document is specific. It lists report categories and the reports in each, describes a report's input parameters and output fields, and returns its data. Since July 2026 the long-running version is the one to use: a query returns inline if it finishes in about 10 seconds, or a token to poll if not, with up to 25,000 rows a page. Report columns may change, so field names come back with the data for checking. Reporting allows "1 of the same report per minute per tenant," while other APIs allow 600 calls per 10 seconds.

Two more facts shape the design. Export APIs, which page through jobs and invoices in bulk, show a change 15 minutes after it happens unless recent changes are requested. And ServiceTitan's API Terms of Use, last updated April 15, 2026, say in section 5.2 that you "must not store or cache any Content obtained from the APIs for longer than 24 hours, except to the extent expressly permitted by these Terms or the Documentation," and section 5.4 requires deleting it when a customer disconnects.

A sample owner's dashboard, tile by tile

This is an illustration of the tiles we start with for an HVAC or plumbing shop. The numbers are yours to fill in; the point is which questions each tile answers and where the data comes from.

For an HVAC company we usually add a membership tile: active members, renewals due and tune-ups booked, read from the memberships API. Our memberships guide covers that side, and the HVAC website guide explains how the site sells the plan in the first place.

HomeService WebApp: a command center built on ServiceTitan data

Our proof is a product, not a promise. HomeService WebApp is a contractor command center we redesigned. It pulls every open estimate, customer and overdue follow-up onto one screen, and its API layer "syncs jobs and estimates bidirectionally with ServiceTitan." Stripe runs its subscription billing, and an automated follow-up engine works the unsold estimates while the crew is out. The HomeService WebApp case study shows the screens.

The lesson we took from it applies to every dashboard: a screen that only displays numbers gets opened twice. A screen that lists the five estimates to call today, with a button to do it, gets opened every morning. Where it fits, we build the second kind. It is a web app, not a chart.

How a dashboard build runs, from questions to first Monday

1. 1

   Write the five questions

   Not metrics: questions. Which campaign paid? Which hours do we lose leads? Each tile has to answer one of them.

2. 2

   Check what ServiceTitan already answers

   Built-in and custom reports first. Anything they answer stays in ServiceTitan, and the dashboard links to it.

3. 3

   Map every outside source

   Ad accounts, call tracking, the website, Search Console: who owns each login, and what each one can export.

4. 4

   Request read-only scopes

   Your admin approves the app in Settings > Integrations > API Application Access. A dashboard needs to read, so we ask only to read.

5. 5

   Build against the integration environment

   ServiceTitan customers can request an integration environment that holds a copy of their production data, so testing never touches live records.

6. 6

   Agree retention before launch

   Which ServiceTitan figures are read fresh, which are kept and for how long, in writing, with section 5.2 of the API terms in view.

7. 7

   Review it together after a month

   Tiles nobody used come off. Questions nobody asked at the start usually go on.

Honest limits, prices, and when to skip the custom build

• It is never perfectly live. Exports lag 15 minutes by default and a given report runs at most once a minute. For an owner's screen, that is plenty.
• It cannot attribute what was never captured. Calls without tracked numbers and forms without click IDs stay unattributed, however good the chart.
• Your package still matters. Custom reports and dashboards inside ServiceTitan depend on it, and API access is approved in your account.
• Report shapes can change. ServiceTitan says report columns may change, so a careful build checks field names on every run and alerts a person when one moves.

Portals, dashboards and web apps start at $575, depending on complexity, and are quoted after a free review; a two-system connection typically takes one to three weeks per our API integrations page. If the attribution plumbing is missing, conversion tracking setup comes first, and the Google Ads conversion guide explains why. New sites start at $1,500 on the web design pricing page. Not sure the data is even there? A free site audit answers that before anyone quotes a dashboard.