Dealership websites
Website Traffic vs Conversions: How to Measure Your Dealership Website Conversion Rate
What counts as a conversion on a powersports dealership website, how to track forms, calls, texts and chat as GA4 key events, and why traffic alone misleads.
Quick answer
A dealership website conversion rate is the share of visits that end in a lead action: a form, call, text, chat, credit application, trade appraisal or service booking. Track each as a key event in Google Analytics 4, separate sales from service, and follow every lead into the CRM, because traffic and clicks alone sell nothing.
This article began in September 2018 as a video conversation between Danny James and Larry Bruce about what a dealer website is for. Their point still stands. The rest is now a working guide for dealer principals, general managers and BDC leads: what to count as a conversion, how to track it in Google Analytics 4 (GA4), and how to tell whether your website sells anything.
Traffic is not the goal
In the 2018 conversation, Danny James put it plainly: "You can't just build a great website and sit back and wait for it to turn into cash. It doesn't work that way." Larry Bruce named the two jobs a dealer website has:
"Answer questions for the customer"
"Collect leads"
Traffic reports measure the first job only loosely and the second not at all. A month with more sessions can still be a worse month if fewer of those visits turned into a call, a text or a form from someone ready to buy. A conversion rate puts the two side by side.
What counts as a conversion on a powersports website
A conversion is an action that starts a conversation with the store, or moves a purchase forward. On a powersports site there are more of them than most reports count.
| Conversion | What the shopper does | How to track it in GA4 | Counts as a sales lead? |
|---|---|---|---|
| Lead form submitted | Check availability, get a price, contact us | form_submit from enhanced measurement, or a generate_lead event on the thank-you step |
Yes |
| Phone call | Taps the number or dials it from the page | A custom event on taps of tel: links; tracked call numbers for dialed calls |
Yes, if it is a sales call |
| Text message | Taps "Text us" | A custom event on taps of sms: links or the text widget |
Yes |
| Chat | Starts a chat or leaves contact details in it | An event from the chat tool, for the step where contact details are given | Yes, once contact details are given |
| Credit application or pre-qualification | Completes the finance form | A custom event on the confirmation step | Yes, a strong one |
| Trade-in tool | Finishes a trade valuation and leaves details | A custom event on completion | Yes |
| Test ride or appointment request | Books a time | A custom event on confirmation | Yes |
| Service booking | Schedules service online | A custom event on confirmation | No, report it separately |
| Directions | Taps "Get directions" | click (outbound clicks) to the map link |
No, a visit signal |
| Brochure or spec sheet download | Downloads a file | file_download from enhanced measurement |
No, a research signal |
Two rules keep this honest:
- Separate sales from service and parts. A customer calling from your home page to ask whether their bike is ready is a call, but not a sales lead. Count it in its own column.
- Count leads, not events. One shopper may submit a form, then call, then text. That is one lead with three touches. Your CRM knows this. GA4 sees three events.
For how to design the forms themselves, see gathering customer information through your website.
How to calculate your conversion rate
Pick one formula, write it down and keep it.
Website lead conversion rate = sessions with at least one sales lead action ÷ all sessions, for the same period.
Example: 4,000 sessions in a month, 120 of which included a sales form, call tap, text tap, chat lead, credit application or trade appraisal. The website lead conversion rate is 120 ÷ 4,000 = 3%.
Then add the numbers that matter more, from the CRM:
| Stage | Where it comes from | Question it answers |
|---|---|---|
| Sessions | GA4 | How many visits did we get? |
| Sessions with a sales lead action | GA4 key events | How many visits produced a lead action? |
| Unique sales leads | CRM, after merging duplicates | How many real people asked us something? |
| Two-way conversations | CRM | How many did we actually reach? |
| Appointments set and shown | CRM | How many came to the store? |
| Units sold | CRM and dealer management system | How many bought? |
We do not publish a "good" dealership website conversion rate. The figures that circulate use different definitions: some count only forms, some add calls and chat, some include service calls. A number from your own site, measured the same way each month and compared season to season, is the one that helps you decide.
How to track conversions in GA4 as key events
Google renamed GA4 "conversions" to key events. Its help page defines one as "an event that measures an action that's particularly important to the success of your business." A conversion, in Google's newer sense, "is created from a Google Analytics event and provides a consistent way of measuring important actions," and is what Google Ads works with.
- List your conversions. Use the table above. Write the event name for each and whether it is sales, service or a research signal.
- Turn on form interactions. GA4 enhanced measurement sends
form_startthe first time a user interacts with a form in a session, andform_submitwhen the form is submitted. Test it on every form you have, because form tools are built differently, and check which forms send it: a newsletter sign-up is not a sales lead. - Add custom events for what enhanced measurement does not cover. Google's list of enhanced measurement events does not include taps on phone or text links. Add events for
tel:andsms:taps, chat leads, credit application completion, trade tool completion and appointment confirmations, usually through Google Tag Manager or your website platform. - Use Google's lead event names where they fit. GA4's recommended events include
generate_lead, which Google says "measures when a lead has been generated (for example, through a form)," with optionalvalue,currencyandlead_sourceparameters. - Mark the sales actions as key events. In GA4 Admin, open Events and select the star next to the event. Google allows up to 30 key events on a standard property. Leave research signals, such as downloads and directions, as ordinary events.
- Connect Google Ads if you run it. Google says you can create Google Ads conversions "based on your Google Analytics key events." For calls to a Google forwarding number on your website, Google Ads counts a call as a conversion "when it lasts longer than a minimum length you set."
- Test before you trust. Submit each form, tap each button on a phone and confirm one event arrives for each action. Keep personal details such as names, phone numbers and email addresses out of event parameters. This is general information, not legal advice.
- Write it all down. Record each event, what triggers it, when it started and any change. A conversion rate that jumps the week tracking changed is a tracking change, not a sales change.
Key events also change your bounce rate: a session with a key event counts as engaged. Our guide to bounce rate for dealership websites explains why an untracked call tap makes a working VDP look like a failure.
The conversion most reports never see
Most advice on dealer website conversion rate stops at the form or the call. That is where the website's job ends, but not where the sale happens. Three gaps follow:
A lead nobody answers is not a conversion. A form submitted at 8 p.m. on Saturday and answered on Monday morning shows up in GA4 as a success. The shopper may have bought elsewhere by Sunday. See what slow lead response costs a powersports store.
Pages get credit for leads, not for sales. A trade-in tool that produces many leads of low quality can look better in GA4 than a VDP that produces fewer leads that buy. Unless sold units are tied back to the page, source and action that started the lead, you cannot tell.
Calls are the largest blind spot. Plenty of shoppers call rather than fill in a form. Without tracked numbers, a page that drives calls looks like a page that drives nothing. Our guide to call tracking for powersports dealerships covers attribution and recording consent.
The fix is to carry the lead's story from the website into the CRM and back:
- Send the context with every lead: the unit, the page, the source and the action taken.
- Record lead stages in the CRM: contacted, appointment set, shown, sold, lost with a reason.
- Report sales back by source and page. GA4's recommended events include later lead stages too, such as
working_lead("when a user contacts or is contacted by a representative"),qualify_leadandclose_convert_lead("when a qualified lead is successfully converted into a customer"), if your systems can send them. - Judge pages by appointments and sales, not by form counts alone.
PSX Ascend's powersports dealership websites are built to share that context with the AI-powered CRM: "The vehicle, source, behavior, and requested action can move with the lead instead of becoming another disconnected form submission." One PSX Ascend dealer reports what that connection does for response time:
"The PSXAscend website, combined with their CRM, has allowed us to connect in a two-way conversation via phone, text, or email 99% of the time in less than 1 minute from the time a lead is submitted."
Chuck Scott, GM, Edge Performance Sports (dealer-reported)
When a lead goes quiet after associates have worked it, ALMA, PSX Ascend's Automated Lead Management Assistant, takes on the repetitive re-engagement work, aiming to bring the customer back to a live conversation with a person. ALMA does not make AI voice calls.
You can also see the same certified dealership websites on our sister site, PSXDigital's certified dealership websites page.
The pages that convert, and what to give shoppers on them
The 2018 conversation named five pages that do most of the converting on a dealer site: search, the vehicle detail page (VDP), instant trade value, credit application or pre-qualification, and specials. They still do. What each needs:
- Inventory search: filters that work on a phone, and a call or text option on every result.
- VDP: real photos and price, and clear buttons for availability, price, trade, finance, call and text. Our call to action examples for powersports dealer websites show the wording.
- Trade-in: say whether the value depends on inspection, and who will confirm it.
- Finance: a secure form that asks only what that step needs. Danny James's 2018 point holds: "People perceive giving up their social security number a big red flag." A shorter pre-qualification step can come first.
- Specials: real offers with end dates, linked to the units they apply to.
Conversion audit checklist
Run this every quarter, and after any website, form or tracking change.
- Every sales action on the site (form, call tap, text tap, chat lead, credit application, trade tool, test ride request) has its own event.
- Sales actions are marked as key events; service, parts, downloads and directions are reported separately.
- Each form was submitted by hand this quarter and produced one event and one CRM lead.
- Phone numbers on the site are tappable on phones and tracked.
- No personal details are sent to GA4 in event parameters.
- Each lead arrives in the CRM with the unit, page, source and action taken.
- Leads are merged by person, so one shopper is not counted three times.
- Time to first two-way conversation is reported, including evenings and weekends.
- Appointments, shows and sales are reported by source and landing page.
- Conversion rate is compared with the same month last year, not only last month.
- Any tracking change is dated in a change log.
Sources
- Google Analytics Help: Conversions vs. key events in Google Analytics
- Google Analytics Help: Mark events as key events
- Google Analytics Help: Enhanced measurement events
- Google for Developers: Google Analytics recommended events reference
- Google Ads Help: Tracking calls to a phone number on a website
