AccuLynx Reporting Meets the Ad Account: Custom Roofing Dashboards Built From the Records

Monday morning, three tabs and a spreadsheet nobody trusts

Roofing owners do not lack reports. They lack one that answers the questions they actually ask on Monday: what did we spend, what did it bring in, who is sitting on leads, and how full is the storm pipeline. Those answers live in different buildings. AccuLynx holds the jobs, milestones, reps and approved values. Google and Meta hold the click-level ad data. The call tracking service holds the calls. The website holds the form timestamps and the click IDs.

So the answer gets assembled by hand, which means it arrives late, or it arrives from an agency whose report counts clicks, multiplies by a hopeful average ticket and calls the product revenue. Then there is the dashboard with fourteen charts that someone built in a burst of enthusiasm and nobody has opened since. A useful dashboard is smaller than that, and it says where every number came from. If your web leads still arrive by email and get retyped, fix that first with AccuLynx lead forms; a dashboard can only count what reaches AccuLynx. The whole section starts at our AccuLynx integration hub.

What AccuLynx already measures, as of October 2026

Start with what you already pay for. AccuLynx is a serious reporting tool in its own right, and plenty of contractors never need anything more. Here is what its own pages describe.

If a scheduled ReportsPlus email already answers your Monday questions, stop reading and enjoy the coffee. The case for a custom dashboard begins where AccuLynx's data ends: click-level ad data, calls by tracking number, and the minutes between a web form and the first human reply. Those numbers live in other systems, and AccuLynx was never meant to hold them.

Why a custom dashboard cannot simply copy an AccuLynx report

One technical fact shapes every AccuLynx dashboard project. The API's reports group covers scheduled reports only: schedule runs, report instances and their recipients. Get Latest Report Instance returns metadata, namely a reportId, a date, a runInstanceId and a recipientsCount. It does not return the rows. As of October 2026, report data itself is not available through the API.

So a dashboard outside AccuLynx is built one level down, from the records the reports are made of. That is more work. It is also the more honest way to do it, because every figure traces back to a job someone can open. The API documentation is public at apidocs.acculynx.com, and our AccuLynx API guide explains access and keys in plain English.

Larger operations have a second route. DataMart puts AccuLynx data in Snowflake, where a warehouse or a BI tool can query it directly. AccuLynx publishes neither its price nor its refresh interval, so we ask before planning around it. For a company with a handful of reps, the API and a nightly sync are usually plenty.

The numbers that live outside AccuLynx

Custom dashboards earn their cost by joining AccuLynx data with ad, call and website data AccuLynx does not hold. As of October 2026, AccuLynx's integrations page lists no Google Ads, Meta or analytics connection. Its one call tracking partner is CallRail, whose AppConnection opens an unassigned lead and copies the caller's source, the form, the tracking line and the campaign into its notes. Useful, but notes are prose, and prose has to be parsed before it can be charted.

• Ad spend and clicks come from Google Ads and Meta, by campaign and by day. The bridge to a job is the click ID the website saved with the lead, which our marketing attribution guide sets up step by step.
• Calls come from the call tracking account: which number rang, how long the call ran, and whether it turned into a lead.
• Form submissions come from the website's own log, with the moment the homeowner pressed send, the page they were on and the source tags. That timestamp starts every speed-to-lead figure.
• Texts come from the messaging provider when the website texts back, logged to the contact as our AccuLynx SMS page describes.
• Storm dates come from wherever your team tracks hail, so the pipeline can be read against the weather. The intake side of that week is in our storm lead guide.

None of this replaces AccuLynx. It sits beside it. The jobs remain the record of what was sold; the other systems explain why it was sold, and what it cost to find.

A sample owner's screen, tile by tile

Here is the first screen we would sketch for a residential roofer with two sales reps and a storm season. The figures are invented for illustration. They show the shape, not anyone's results. Each tile names the records it reads, so nobody has to take a chart on faith.

A dashboard that cannot show its work is just a mood with a color scheme.

Notice what is missing: page views, impressions, likes. They have a place in a marketing review. They do not belong on the screen that decides whether to hire a third rep. Our roofing marketing page covers the channels; this screen only judges them.

How we build it without leaning on the API too hard

1. 1

   Write down the Monday questions

   The owner and sales manager list what the screen must answer. Every tile traces to one of those questions, or it goes.

2. 2

   Get a key from your administrator

   API keys need the AppConnections add-on, and a Location or Company Administrator creates them in AccuLynx. Each location connects separately. Your own admin makes the key, and no AccuLynx password ever comes to us.

3. 3

   Agree what each number means

   Which milestone counts as sold, which lead sources roll up together, which job categories count as storm work. Written down and signed off before any code.

4. 4

   Sync nightly, listen during the day

   A nightly pull pages through jobs by ModifiedDate. Webhooks such as Job Created and Job Milestone Current Changed keep the screen current between pulls. AccuLynx gives listeners 10 seconds to respond and warns of duplicate events, so each event is stored once and processed after the reply.

5. 5

   Stay under the published limits

   AccuLynx publishes two sets of rate limits that do not match each other. We do not gamble on either: requests are queued and back off on a 429.

6. 6

   Join the outside data

   Ad spend, call records and form timestamps land in the same database, keyed by date, campaign and click ID.

7. 7

   Check it against AccuLynx by hand

   The sales manager opens five jobs and compares them with the screen. When the two disagree, AccuLynx wins and we find out why. A health check also alerts us if webhooks stop, since AccuLynx disables subscriptions that return too many errors.

Proof, prices, and when ReportsPlus is enough

We have built this kind of screen before. HomeService WebApp is a contractor command center we redesigned that pulls every open estimate, customer and overdue follow-up onto one screen, with Stripe subscription billing and an automated follow-up engine. It is not an AccuLynx product. It is proof that we build working dashboards on top of field-service data, and it sits with our other projects on our work page.

Building a dashboard beside an existing site counts as integration work, priced after a free review. Most two-system connections take one to three weeks, according to our API integrations page, and the tracking underneath comes from our conversion tracking setup. When the site itself is due for replacement, fixed prices begin at $1,500 with booking included, and portals and web apps begin at $575, depending on complexity, on our web design pricing page. Financing for websites is 0% with a quarter of the price down.

DataCram is a web studio in San Antonio, Texas, building on Next.js with our own Athena CMS and running PPC advertising for contractors across the US. See how we approach roofing websites, run the AccuLynx website checklist before go-live, or call (210) 346-0848.