Industry: Auto dealer groups

Compare sales and service demand across every rooftop in your dealer group

Dealer group digital marketing reporting goes wrong when it blends the two funnels on a rooftop's site: inventory pages that sell cars and scheduling pages that fill bays. Add a different website provider at each store, each wiring GA4 its own way, and the group table ends up ranking tag setups instead of stores.

Continue with Google

Free for 2 sites · No credit card

Or have your agent set it up

Set up DuckDive for my website. Follow https://analytics.duckdive.ai/agents.md

Updated 16 min read

The short answer

Set up one DuckDive website per rooftop, carrying that store's GA4 property and Search Console site. Then have your AI agent sort every store's landing pages into inventory pages and service pages, and compare rooftops inside each funnel. Check which key events each property counts first: stores built to the same ASC standard still count differently.

  • Never rank rooftops on one blended conversion rate. Sales pages and service pages convert for different reasons.
  • List the key events each rooftop's property counts before a single number goes into the group report.
  • Treat vehicle detail pages as search landing pages that expire the day the car sells.

Two funnels on every rooftop's website

A rooftop's website has two jobs: move metal and fill service bays. The sales path runs from a search results page of inventory to a vehicle detail page, then to a lead form, a call, a chat or a digital retailing tool. The service path runs from a service page or a service special to the scheduler. They share a domain and a GA4 property, and little else.

Service is not the side show. NADA Data for 2025 counts 16,990 franchised light-vehicle dealers, more than 276 million repair orders and service and parts sales above $164 billion, next to 16.2 million light-duty vehicles sold (as of November 2026). That works out to about 17 repair orders for every vehicle sold.

Blend the two and the group report misleads you. A store with a busy service drive and a thin used lot posts a strong site-wide rate and passes for your best sales store. A store whose scheduler broke looks fine while inventory leads hold.

Inventory pages
Search results pages (SRPs) that list vehicles, and vehicle detail pages (VDPs) for one unit. Paths usually hold new, used, inventory, a VIN or a stock number.
Service pages
Service, parts, service specials and schedule-service pages, plus the scheduler when it runs on the rooftop's own domain.
Conversions
The total of every event a rooftop's GA4 property has flagged as a key event; DuckDive's tools report that total under this name. Google Ads can create a conversion from a GA4 key event (About key events).

DuckDive imports each rooftop's GA4 and Search Console history when you link it and keeps it, so your agent reads seven stores from stored data instead of waiting on seven live pulls from Google. The agent does the sorting: it lists each rooftop's landing pages, buckets them by path and hands you one table per funnel.

It reads what each property records. It does not repair tags, which is why the counting rules come next.

Ask your agent
Group each rooftop's GA4 landing pages into service pages and inventory pages and compare conversions for each group over the last 30 days.

Tools it calls list_websites get_ga4_landing_pages

Give the agent your URL patterns when providers use odd ones: one platform puts VDPs under /used/, another under /vehicle-details/. Each call returns a rooftop's top 100 landing pages by sessions. Many single VDPs sit below that line, so the inventory bucket is mostly SRPs plus your busiest units. Tell it to leave the homepage out of both buckets.

The ASC event standard and why rooftops still disagree

The Automotive Standards Council for Google Analytics 4 (GA4), or ASC, describes itself as automotive dealers, vendors and manufacturers that have joined forces to set shared rules for GA4. It publishes an event specification for car retail. Its member benefits page says the spec "supports conversions by department (sales, service, parts) and conversion outcomes", such as whether a click to call actually connected to the store's phone system. Vendors send the events from their own code, not tag manager containers.

The same page speaks to your situation by name: "Dealership groups, who have to support multiple website platforms due to OEM mandates" can build roll-up reporting more easily and reliably. As of November 2026, the council's certified products list names seven website platforms, plus certified digital retailing, trade-in, credit and chat tools.

So why do two certified rooftops still disagree? Five reasons, each checkable:

  1. Key events are a property setting. The spec names the events. Whoever runs each GA4 property picks which ones count as key events. A store that also counts button clicks looks twice as good as one that counts only forms and connected calls.
  2. Vendors add their own events. The spec allows it, so a digital retailing tool's extra events inflate the count only at stores that run it.
  3. Not every tool sends every event. The certified list itself notes that one certified tool does not yet send a few minor calls to action and parameters, and that another needs each dealer's GA4 Measurement Protocol API secret to support all events.
  4. Versions move. As of November 2026, the spec download page offers Spec 1.2 while its body text still announces version 1.1. Ask each provider which version its build sends.
  5. Scheduling often leaves the domain. When the scheduler lives on a vendor's domain, GA4 creates new cookies and IDs on each domain unless cross-domain measurement is set up with the same tag ID on both.

What the agent cannot see

DuckDive's GA4 tools return sessions and conversions by date, by channel and by landing page, with conversions added up across every key event. Event names and the ASC department parameter are not in the tools. Bucketing pages by path approximates the sales and service split.

Worked example: service scheduling across seven rooftops

Here is the first prompt run on a fictional group: five Graystone stores plus two acquired rooftops that kept their names.

EXAMPLE DATAFictional business: Graystone Auto Group

Split all seven rooftops into inventory pages and service pages for the last 30 days. I want to know which service drives get website traffic but no bookings.

  1. list_websitesreturns seven rooftop websites, all named with a Graystone prefix
  2. get_ga4_landing_pageseach rooftop's 100 leading entry pages, split by URL path
  3. get_ga4_channelstraffic sources for Graystone Motors Corwin Valley, the outlier

Group-wide, service pages convert at 4.0% (430 conversions from 10,830 sessions) and inventory pages at 2.1% (897 from 43,050). Two stores break the pattern.

RooftopInventory rateService rateService share of conversions
Graystone Motors North2.0%4.5%34%
Graystone Motors Eastgate1.8%5.0%37%
Graystone Motors Corwin Valley2.1%0.6%9%
Graystone Pre-Owned Hollins Road1.3%2.9%12%
Graystone Imports Westbury4.0%4.1%21%
Lakeshore Imports1.8%4.9%54%
Pinecrest Truck Center1.9%5.5%44%

Corwin Valley: 1,940 sessions on service pages and 12 conversions. Its traffic sources show the scheduling vendor's domain as a referrer with 260 sessions, the signature of a scheduler on another domain without cross-domain measurement. Customers may be booking; this property never hears about it. Book a test appointment first.

Westbury: inventory pages convert at about twice the group rate while its service pages sit in line. That points at counting, not selling. Check whether Westbury marks payment-calculator clicks as key events.

Hollins Road is a pre-owned store with a small service lane. Nine conversions is too few to rank. Lakeshore Imports takes more than half its conversions from service. Judge stores on site-wide rate and Lakeshore's sales desk gets credit for its service drive.

Google Analytics 4

Run that traffic-source check across the group monthly. The GA4 connection page explains when to ask for source rather than channel group.

Split your own rooftops into two funnels

Link one rooftop free and ask whether its service pages draw visits without bookings.

Continue with Google

Free for 2 sites · No credit card

Inventory pages as landing pages

A VDP is a product page with a short life. It goes up when the unit hits the lot and comes down, or changes, when the unit sells. While live, a search for an exact year, model and trim can land on it. That makes VDPs a search channel of their own.

Google changed how these pages appear. In June 2025 it said Vehicle Listing structured data would no longer be supported in Search results, and added "This update won't affect how pages are ranked" (Simplifying the search results page). From September 9, 2025, Search Console dropped Vehicle Listing from its rich result reports and search appearance filters. VDPs now compete as ordinary results.

Search Console also keeps score per URL. Its performance report totals the chart by property, but data grouped by page is aggregated by page. A VDP's clicks belong to its own address. When the unit sells, that history stays with a dead URL.

When the car sells

Google's crawl budget guide tells site owners to return 404 or 410 for permanently removed pages, and warns that soft 404 pages "will continue to be crawled". The same guide says it is mainly for sites with 1 million or more pages that change about weekly, or 10,000 or more that change daily. Ask each provider instead: does a sold VDP return a 404, redirect to the matching SRP, or load a normal page saying the vehicle is gone?

Ask your agent
Which rooftops get the most Search Console clicks to vehicle detail pages, and how do those pages convert in GA4 compared with each rooftop's service pages?

Tools it calls list_websites get_search_console_pages get_ga4_landing_pages

The page list stops at each store's top 100 URLs by clicks. Dozens of VDPs in it means inventory pulls search demand by itself. If your service specials show the same pattern as some VDPs, plenty of clicks and few leads, the guide to pages that rank but don't convert has a scoring method for them.

Worked example: vehicle detail pages that earn search clicks

Both acquired stores claim search is their best source of used-car shoppers. The agent checks.

EXAMPLE DATAFictional business: Lakeshore Imports and Pinecrest Truck Center

Lakeshore and Pinecrest both swear search sells their used units. Whose VDPs really get Google clicks this month, and do those visitors convert anything like their service visitors?

  1. list_websitespicks Lakeshore Imports and Pinecrest Truck Center from the group's sites
  2. get_search_console_pageseach store's 100 most-clicked URLs this month; VIN and stock-number paths kept
  3. get_ga4_landing_pageslines those VIN paths, and each store's service paths, up with sessions and conversions
  4. get_search_console_keywordswhat Pinecrest's truck buyers typed before clicking

Lakeshore has 38 VDPs in its top 100 search pages; Pinecrest has 12. Lakeshore wins on clicks and loses on conversion.

RooftopVDP clicksVDP rateService conv. rate
Lakeshore Imports1,2401.4%4.9%
Pinecrest Truck Center6103.8%5.5%

The GA4 rates cover the VDPs that also appear in each store's top 100 landing pages: 22 of Lakeshore's 38 and 9 of Pinecrest's 12.

Lakeshore: 7 of its 15 most-clicked VDPs had sessions and zero conversions. Open those seven. If the units are sold and the pages still load with a "no longer available" note, searchers are arriving for cars that are gone.

Pinecrest: fewer clicks, but its truck VDPs convert at 3.8%. Its top queries name cab style, bed length and upfit, so searchers land on the one unit that matches.

Search Console Google Analytics 4

The clicks column is Google's tally of results people chose; the rate column comes from GA4 sessions, which every traffic source feeds. Use the pairing to rank VDPs against each other, never to reconcile totals. How page, query and summary data come out of Search Console is set out on the Search Console connection page.

Service searches that never mention your name

Service demand shows up in search in two kinds. Branded queries such as "graystone eastgate service hours" are your own customers finding the door. Unbranded ones such as "oil change near me" or "brake inspection" plus a town are drivers who have not picked a shop yet. The second kind is where service department SEO pays.

Ask your agent
Show Search Console clicks for queries containing 'oil change' or 'service' for each rooftop over the last 90 days.

Tools it calls list_websites get_search_console_keywords

EXAMPLE DATAHow many of each store's 100 top queries carry service intent, and the clicks they drew over 90 days
RooftopQueriesClicksUnbranded clicks
Lakeshore Imports171,610690
Graystone Motors North141,320410
Graystone Motors Eastgate11960350
Graystone Imports Westbury9702260
Pinecrest Truck Center8540300
Graystone Motors Corwin Valley641040
Graystone Pre-Owned Hollins Road2850

Corwin Valley gets almost all its service clicks from people who already know its name, so it barely competes for new service customers. The word "service" also catches "customer service" and "service department phone number", so have the agent drop those, plus any query with a rooftop name in it, before you compare.

When website providers tag GA4 differently

Provider differences arrive as patterns in the agent's answers, never as error messages. Trace them back here.

Tracing a strange rooftop number back to the tagging
What the agent showsLikely causeWhere to fix it
Conversion rate double its peers on similar trafficMore events marked as key eventsGA4 Admin, key events list
Busy service pages, next to no bookingsScheduler on another domainCross-domain settings, with the scheduler vendor
A vendor's domain among top traffic sourcesVisits restart when shoppers return from a toolGA4 tag settings for that rooftop's data stream
Conversions fall off a cliff on one dateProvider switch or rebuild dropped eventsNew provider's ASC event setup
Chat leads missing at one store onlyChat tool not sending to that propertyChat vendor's GA4 connection
Ask your agent
For every rooftop, pull GA4 sessions by traffic source for the last 30 days and flag any store where a scheduling, chat or financing vendor's domain is one of the top sources.

Tools it calls list_websites get_ga4_channels

A provider switch is the other classic. Traffic holds and conversions jump or sink overnight because the new build counts differently. Compare against a store that did not switch.

Ask your agent
Eastgate moved to a new website provider in early September. Put its daily sessions and conversions for the last 90 days beside Graystone Motors North and tell me whether conversions moved on the switch date or moved with traffic.

Tools it calls list_websites get_ga4_overview

Some groups also tag every store into one shared group property. That roll-up holds only while every provider sends identical events to both. The guide to comparing GA4 properties without a 360 roll-up weighs the options.

Six gates a rooftop clears before entering the group table

  • Same key events. You have listed the key events on each property and agreed one set for the group.
  • Scheduler reports home. A test service booking at that store shows up in its own GA4 property.
  • Third-party tools send. Chat, trade-in and credit tools on the site send their events to that rooftop's property.
  • Path rules written down. You know the platform's URL pattern for SRPs, VDPs and service pages.
  • Sold units handled. You know what a sold vehicle's URL returns.
  • Switch dates logged. Provider changes and rebuilds carry dates, so a step change has an explanation.

Bringing every rooftop in, one website provider at a time

Groups rarely buy every site from one vendor. The ASC's benefits page names OEM mandates as the reason many groups run several website platforms, and in practice the provider, not the store, is where access lives. Treat each provider as one setup job covering all the rooftops it hosts.

Count websites before you start: each rooftop domain is one, and a group inventory site listing every store's cars is one more.

  1. Write one access request per provider, not per store

    Sort your rooftop domains by the provider that hosts them. Each provider often created, and still holds, the GA4 property and Search Console site for every store on its platform, so send it a single request: the list of its rooftops, the Google account you will use with DuckDive, and a request for read access on each store's property and site. One message per vendor beats twenty separate tickets, and it flushes out the store where nobody at the vendor can say who holds the property. Getting Google access for every site includes request wording you can adapt per vendor.

  2. Name each website by rooftop and brand

    A DuckDive website takes a name as well as a URL. Use the name your staff say out loud, plus the franchise the store carries, and give acquired stores the group prefix even if their sign never changed: "Graystone: Lakeshore Imports" rather than the bare domain. The website list accepts a text search, so a steady naming pattern lets your agent pull every store of one make, or every store in the group, before it compares anything. Folding an acquired store's domain into a group site instead? Take a baseline first, as the page on redirecting a brand's site inside a holding company lays out.

  3. Log the provider and its URL patterns the day a store goes in

    Keep a sheet with one row per rooftop: website provider, scheduler domain, and the path patterns for SRPs, VDPs (a VIN, /used/, /vehicle-details/) and service pages. DuckDive does not store any of this, yet every two-funnel prompt on this page depends on it. Paste the rows into your agent before asking for the split, and edit a row the day a store changes vendor, because the patterns move with the platform.

  4. Hand the linking to Google sign-in or to your agent

    You can click Continue with Google and link stores yourself, or let your agent work from the line below. Either way the work runs under a DuckDive admin login, and an agent also needs actions allowed when you connect it. The agent links each rooftop's GA4 and Search Console, asks before pulling a property off another website, and history usually arrives within minutes, longer for stores with years of data. A 20-store rollout is easier in batches, as onboarding many websites with an agent explains.

    Paste this into your agent
    Set up DuckDive for my website. Follow https://analytics.duckdive.ai/agents.md

    A store's paid accounts, Google Ads and Local Services Ads, can join its DuckDive website alongside GA4 and Search Console. At a dealer group the Ads account may sit with the group, an agency or a manufacturer program under a different login, so confirm your Google sign-in can see it before you expect it in the list. What a linked Ads account returns is on the Google Ads connection page.

  5. Keep a new store out of the group table until its sync passes

    A half-imported rooftop drags the group averages, so check it before it counts.

    Ask your agent
    Pinecrest Truck Center's sources went in this morning. Tell me for each source whether its import has finished and how recent the data is, before I add Pinecrest to the group table.

    Tools it calls list_websites get_sync_status

A minority of groups skip separate domains and give each store a folder under one group address. DuckDive pairs GA4 and Search Console with whole websites rather than folders, so to DuckDive that address is a single website, and your agent can separate stores only by reading the folder in each landing page path. Groups set up that way are better served by the multi-location overview.

What stays in your DMS, CRM and OEM tools

A dealer group's numbers are spread across several systems, and DuckDive holds only the website and Google search slice. These jobs stay where they are:

  • Units sold, gross and repair orders. Your DMS. DuckDive cannot say whether a VDP visitor bought the car.
  • Lead handling and response time. Your CRM. DuckDive sees that a form event fired, not who called the customer back.
  • OEM co-op claims and program compliance. Not a source. Those stay with the manufacturer's portals and your co-op administrator.
  • Keyword, ad group and campaign performance. Google Ads itself. A linked Ads account comes through as account totals only.
  • Event-level and department reports. GA4. The tools return conversions added up per page and channel, over fixed ranges from 7 days to 12 months, with at most 100 rows per call.

For attribution from VDP view to delivered unit, pick a tool that joins your DMS and CRM. DuckDive covers what happens upstream of the showroom: which rooftop sites draw shoppers and service customers, and which ones miscount them.

Rooftop data questions from group managers

Our rooftops run on different website providers. Can we still compare them in one table?

Yes. The provider makes no difference to DuckDive once each store's GA4 property and Search Console site sit on a DuckDive website of their own; the agent reads them store by store and assembles the table. Settle one shared list of key events across the rooftops before you trust the ranking.

Can the agent split conversions by the ASC department parameter?

Not directly. DuckDive's GA4 data stops at sessions, conversions and rate per day, per channel and per landing page, and conversions arrive as one total across key events, so the department parameter never reaches the agent. Bucketing pages by URL path into inventory and service stands in for it.

Can we see which VDP shoppers ended up buying?

No. Deals, units and repair orders live in your DMS, and follow-up lives in your CRM. Neither is a DuckDive source. The agent shows which VDPs earn search clicks and website conversions, to set beside your sales reports.

Service appointments get booked on the scheduling vendor's website. Do they count?

Only if they reach the rooftop's GA4 property as key events. DuckDive reads what each property recorded. A scheduler on another domain without cross-domain measurement can lose bookings or send them to a different property. One test booking per store is the fastest check.

A manufacturer program put one store on a certified platform, and that vendor holds its GA4 property. Can we still connect it?

Yes, without transferring anything. When an OEM-mandated platform built the site, the vendor often created the GA4 property and Search Console site and keeps them under its own account. DuckDive needs your Google login to be able to read them, nothing more, so include that store in your request to the vendor. Once the access appears, your agent can link the store.

We are buying a rooftop mid-month. How does that change what we pay?

Billing is per website, so each acquired rooftop you add counts as one more. The first website is on the free plan and needs no card, and paid figures load in the pricing section below. Ask DuckDive how a store added partway through a billing period is charged, and whether a group bringing many stores in at once can agree its own terms.

Sources

  1. NADA Data (National Automobile Dealers Association), read November 16, 2026.
  2. About key events (Google Analytics Help), read November 16, 2026.
  3. Automotive Standards Council for Google Analytics 4 (GA4) (homepage), read November 16, 2026.
  4. Member Benefits (Automotive Standards Council for GA4), read November 16, 2026.
  5. ASC Certified Products for Automotive Dealers (Automotive Standards Council for GA4), read November 16, 2026.
  6. Download the Current ASC GA4 Specification (Automotive Standards Council for GA4), read November 16, 2026.
  7. Set up cross-domain measurement (Google Analytics Help), read November 16, 2026.
  8. Simplifying the search results page (Google Search Central Blog), read November 16, 2026.
  9. Performance report (Search results): Overview and basic setup (Search Console Help), read November 16, 2026.
  10. Optimize your crawl budget (Google Search Central), read November 16, 2026.

Last reviewed . The dealerships, groups and numbers in EXAMPLE DATA blocks are made up, and none describes a real store.

See which service drive is going quiet

Link your first rooftop free, ask the inventory-versus-service question, then bring in the rest of the group.

Free for 2 sites · No credit card · Working in an agent? Let it set DuckDive up