Multi-Rooftop Reporting: How Dealer Groups Get One Version of the Truth

Multi-rooftop reporting is the practice of putting every store's sales, service, inventory and marketing results on one set of definitions, so a group executive can compare rooftops and vendors without a monthly reconciliation project. Getting there takes three things: metric definitions the whole group agrees on, marketing data tied to deals in the DMS, and a short scorecard built for decisions rather than for display. Software helps, but it comes third.

This guide covers what to standardize first, how to stop vendors from taking credit for the same sale, what a group scorecard should contain, and where reporting projects stall.

TL;DR

• Agree on metric definitions before you integrate anything. Stores that define "sold unit" or "days-supply" differently produce group numbers nobody can defend.
• Tie marketing results to closed deals in the DMS, not to leads, form fills or impressions. Vendor dashboards each claim credit for the same sale.
• Keep the group scorecard to a page: spend, cost per sold unit, and vendor performance by store, with the same definitions everywhere.
• Do not force every store onto one platform. A reporting layer that sits over your existing DMS and CRM stacks usually beats a migration.
• Have someone with no ad revenue at stake review the numbers at least once a year.

Table of Contents

• Why group reporting breaks as you add stores
• Step 1: Set canonical definitions at the group level
• Step 2: Tie marketing to deals, not to leads
• Step 3: Build a scorecard people read
• Step 4: Choose the reporting layer last
• Common mistakes in multi-rooftop reporting
• Our perspective: reporting is an accountability problem before it is a data problem
• How an independent review fits in
• A 90-day plan for a group starting from scratch
• FAQ
• Sources

Why group reporting breaks as you add stores

One store can get by with a handful of dashboards and a GM who knows the story behind each number. Add rooftops and the same habit stops working. Each store runs its own mix of vendors, its own CRM configuration, sometimes its own DMS. Each vendor sends its own monthly report, and each report says the program is working.

A data strategy write-up on what breaks at 10, 25 and 50 stores describes the pattern well: the same customer lives separately at several rooftops, integration costs grow per location, and group reporting turns into manual reconciliation. The core problem it names is not technical. Stores define basic terms such as "sold unit," F&I penetration and days-supply differently, so the group scorecard becomes a monthly reconciliation exercise instead of a management tool.

Marketing makes this worse because the money is large and the measurement is weak. Per the 2025 NADA data, the average franchised dealership spent $586,246 on advertising, or $739 per new vehicle sold. Multiply that by a group of eight or fifteen stores and the marketing line is one of the largest discretionary budgets you manage. Digital accounted for 74.9% of dealer ad spending, which is the part of the budget where vendor-supplied reporting is hardest to verify.

Step 1: Set canonical definitions at the group level

Do this before any dashboard project. A reporting tool will faithfully display whatever each store feeds it, including inconsistent definitions.

Write a one-page data dictionary, owned by a named person at the group level. At minimum, settle these:

Two rules keep the dictionary alive. First, the definitions are enforced by the group, not negotiated store by store. Second, changes are versioned, so a trend line does not silently shift when someone redefines a term.

Step 2: Tie marketing to deals, not to leads

Most multi-rooftop marketing reporting fails here. Every vendor measures from its own platform outward: its clicks, its form fills, its calls. Each one claims the customer who eventually bought. When you add the vendor reports together, the claimed sales exceed the units you actually delivered.

The fix is to reverse the direction. Start from the sold-unit list in the DMS and work backward to the source.

1. Export the deal log for each store for the period, with customer, VIN, sale date and gross.
2. Match deals to lead and contact records in the CRM and call tracking, using email, phone and name.
3. Assign each sale one source using a rule the group has agreed on in advance, for example first touch, last touch, or a documented split. Whatever you pick, a sale gets counted once.
4. Compare the result with what each vendor claims. The gap between claimed and verified sales is your vendor accountability number.
5. Require consistent UTM tagging on all digital campaigns so the match is possible at all.

We cover the mechanics of this match in our 90-day vendor-agnostic sales match analysis. The service side has its own version of the problem, since an appointment is not revenue until the repair order closes. See our piece on linking ads to RO value.

Watch for stores competing with each other

A group-level view shows something single-store reports hide: two rooftops bidding on the same shopper in the same metro market. If stores buy search ads and third-party listings independently, you can pay twice to reach one in-market customer. Search is the biggest single line, with search engine marketing taking 21.1% of every ad dollar according to the same NADA-based data. A shared view of keywords, geotargets and listing placements by store is often the quickest overlap check you can run.

Step 3: Build a scorecard people read

A group scorecard is not a data warehouse export. It exists so an executive can see where to act in about five minutes. Three layers work well.

Group level (one page).

• Total marketing spend, by channel and by vendor
• Verified sold units and cost per sold unit, new and used separately
• Marketing spend per vehicle retailed, which you can compare against the NADA figure of $739 per new vehicle as a rough outside reference, keeping in mind that brand, market and mix change what is reasonable
• Gap between vendor-claimed and verified sales

Store level.

• The same measures for each rooftop, ranked, with the prior period beside them
• Lead-to-appointment and appointment-to-show rates, so BDC problems are not mistaken for ad problems (our BDC conversion benchmarks explain the difference)

Vendor level.

• Spend, verified deals, cost per verified deal, contract end date and notice window
• A plain flag: renew, renegotiate, test, or cut

Leave out impressions, raw clicks and total lead counts unless they sit under a measure that connects to a sale. They are fine for diagnosing a problem, but they should not appear in the first page an executive reads.

Step 4: Choose the reporting layer last

Only after definitions and attribution rules exist does the tool question matter. The usual debate is all-in-one platform versus a reporting layer over what you already run.

All-in-one systems can work for a single store. Groups often have brand-specific processes, different OEM requirements and DMS contracts that end on different dates. Forcing one stack on all of them means a long migration and a lot of disruption to the people actually selling cars. An enterprise reporting or BI layer that reads from your existing DMS, CRM and marketing sources usually gets you a group view sooner, and you can improve it incrementally.

Whatever you evaluate, ask these questions in the demo:

• Can I see the field-level definition behind every number on the screen?
• How does the system handle the same customer appearing at two stores?
• How are duplicate leads from multiple sources handled before they are counted?
• Can it show sold units from the DMS next to marketing cost, store by store?
• Who owns the data model when a store changes DMS or CRM?

A vendor that cannot show you how it deduplicates leads across sources is probably counting overlapping leads as separate conversions, which makes its own ROI look better than reality.

Common mistakes in multi-rooftop reporting

Letting vendors define success. A vendor report is a sales document for that vendor. It may be accurate, but it is not independent, and no vendor will show you how it overlaps with the others.

Averaging across stores. A group average hides the rooftop that is wasting money and the one that is carrying the result. Always show the distribution by store.

Mixing new, used and service. These have different margins, cycles and sources. A blended cost per sale tells you very little.

Reporting monthly only. Month-end is too late to move a budget. Review pacing weekly, and keep the deeper vendor review monthly or quarterly.

Skipping the cost side. If agency fees, platform fees and creative are not in marketing cost, every store looks better than it is, and unevenly so.

Waiting for perfect data. A sales match on 85% of deals, with the gap documented, is more useful than no match at all. Our list of signs your dealership is wasting marketing dollars can help you prioritize which gaps matter first.

Our perspective: reporting is an accountability problem before it is a data problem

We have seen the same pattern in group after group. Leadership has plenty of reports. What it lacks is a report nobody has a stake in. The agency's dashboard supports the agency's retainer. The platform's dashboard supports the platform's renewal. Each can be internally consistent, and together they still do not add up to the sales on the floor.

That is why we do not sell advertising, manage campaigns or take vendor commissions. Our role is to take the vendor claims, the DMS deal log and the spend records, put them on one set of definitions, and tell executives where the money is and is not producing sales. The output is an executive-level scorecard and a recommendation that the GM, the dealer principal and the vendor can all see the basis for.

For multi-rooftop groups, our advice is to fix the definitions first, build the deal-level match second, and treat any tool purchase as a decision that follows from those two, not one that replaces them. If a reporting project begins with a software demo, the definitions problem is usually still sitting there afterward.

— AutoROIQ

How an independent review fits in

Many groups can build parts of this internally, especially the data dictionary. The difficult part is neutrality: the people who manage the vendors are often the same people asked to grade them. Our Marketing Intelligence Review gives group leadership an outside analysis of vendor performance and channel efficiency, with executive-level recommendations on where to reallocate spend. Groups that want continuing oversight can add ongoing strategic advisory. You can read how each works on our Marketing Intelligence Review and advisory page, or start from the AutoROIQ home page. If you want to see how we think about reallocation first, our marketing spend audit guide is a good place to start.

A 90-day plan for a group starting from scratch

Days 1 to 30: definitions and inventory. Publish the data dictionary. List every marketing vendor by store, with contract terms, monthly cost and the report each one sends. Confirm that every store can export its deal log in a consistent format.

Days 31 to 60: the first match. Run the deal-to-source match for the last full quarter at every store. Calculate verified cost per sold unit and the gap against vendor claims. Do not act on the first pass alone. Use it to find data holes, such as missing UTMs, untracked phone calls or CRM fields left blank.

Days 61 to 90: decisions. Build the one-page group scorecard. Pick two or three budget moves that the data clearly supports, such as cutting a vendor with a large claimed-versus-verified gap or consolidating overlapping search spend between nearby stores. Set review dates so the scorecard becomes a routine instead of a project. For budget logic, see our ad budget allocation framework and the dealership marketing budget playbook.

FAQ

What is multi-rooftop reporting in a dealership group?

It is the consolidated reporting of sales, service, inventory and marketing performance across every store in a group, using shared definitions. The goal is that a number means the same thing at every rooftop, so leadership can compare stores and vendors directly.

How many stores does it take before this becomes a problem?

There is no fixed threshold, but strain shows up as soon as stores use different vendors, CRMs or definitions. The multi-rooftop data strategy piece describes reporting at 25 or more stores as closer to reconciliation than reporting. Smaller groups feel it too, usually first in marketing.

Do we need to move every store to the same DMS or CRM?

Not necessarily. Many groups get a usable group view by standardizing definitions and adding a reporting layer over existing systems. A platform migration is a large operational change, so treat it as a separate decision with its own business case.

Which marketing metrics matter most at the group level?

Verified sold units, cost per sold unit and the gap between vendor-claimed and verified sales matter most. Lead volume, impressions and clicks are useful diagnostics, but they should not be the headline numbers. Show them by store so stronger and weaker rooftops are visible.

Who should check the vendor numbers?

Someone who gains nothing from the result. That can be a finance lead or controller with access to the deal log, or an independent firm that sells no advertising and takes no vendor commissions. Whoever does it, the match should start from the DMS sold-unit list.

Sources

• Multi-Rooftop Data Strategy: What Breaks at 10, 25, and 50 Stores
• Turning Data Into Dollars: Key Insights From 2025 NADA DATA (Inside Radio)
• Dealer ad spend nears $10 billion as digital marketing dominates (Dealership Guy)

Recommended

• Dealership ROI Reporting: Prove Profit Beyond Lead Counts
• Get a Working Marketing Reporting Cadence for Dealerships in 30 Days
• Vendor Report Reconciliation for Dealers: Demand Raw Exports
• Up to 40% More Dealership Marketing ROI With Outcome Based Measurement