Skip to main content
FleetioDirectories and marketplaces

Fleetio Shop Network conversion tracking: network trucks shouldn't count as ad wins

Your bays are full of Fleetio trucks, your ad reports look great, and you still can't say which fleet accounts the ads brought in. A driver finds your verified shop in Fleetio Go, taps Call or Directions and pulls in; you write the RO in Auto Integrate and the payout arrives by ACH or check through cbCharge. None of that touches your website, so Google and Meta Ads either never see the job or quietly take credit for it. We split network work from ad-won work.

Free30 minutesNo obligation

Fleetio · what breaks

What goes wrong when a Fleetio shop runs ads

  1. 01

    Nothing ties a new fleet account to a source

    A Fleetio job starts with a driver tapping Call in the app and ends with an RO in Auto Integrate. A fleet manager who clicked your search ad calls the same line and gets the same RO. Neither record says which one the ad budget bought, so you raise or cut spend on a guess.

  2. 02

    Network payouts get counted as ad wins at month end

    When revenue is divided by ad spend, every Fleetio payout sits in the numerator. Return on ad spend looks healthy, the budget goes up, and the extra money buys clicks that never become a truck in a bay.

  3. 03

    The driver's call looks like the ad call

    The Call button in Fleetio Go dials the number on your shop profile. If that number is your call-tracking line, every driver call lands in the paid-search column and your cost per lead reads far better than it is.

  4. 04

    Smart bidding learns from the wrong jobs

    If network ROs are imported as conversions, Google's bidding optimizes toward the national fleets Fleetio sends you, not toward the owner-operators and small fleets your ads are meant to reach.

Fleetio · the fix

What changes — Fleetio

  • Two revenue columns instead of one

    Fleetio work is labeled by its Auto Integrate RO ID and account name; ad-won work by the click that started it. They never share a conversion.

  • Ads judged on the fleets they bring in

    A new fleet account that first called from a Google Ads click is the conversion, valued from its first approved RO in your own shop system.

  • Directory performance on its own terms

    New Fleetio accounts and ROs per month, read from the Vendor Portal Activity tab, sit next to the ad numbers.

Fleetio · architecture

What Fleetio actually gives a shop to work with

Fleetio's shop-side help describes a directory, Auto Integrate for repair orders and a Vendor Portal for payouts. It documents no shop-facing pixel, webhook or ad integration, so the useful hooks are records, not tags.

  1. 1

    Shop Directory listing in Fleetio and Fleetio Go

    Fleets search by location or shop name and filter by Network Status, Rating and Shop Features. Your profile shows hours, address, phone and features; reviews come from Fleetio customers and from Google. Verified means you use Auto Integrate and have signed Fleetio's shop agreement.

  2. 2

    Call and Directions buttons in the driver app

    The only documented ways a driver contacts you from the app. The call rings the number on your profile, so that should be a line you can identify, not your tracked ad number.

  3. 3

    Repair orders in Auto Integrate

    Every RO is created by the shop and approved, sent back for changes or rejected by the fleet manager there; Fleetio documents that fleets can't create ROs for you. The Repair Order number is the one identifier only network work carries.

  4. 4

    Vendor Portal Activity tab

    A log of ROs with Transaction Date, Payment Status, Account Name, Shop Invoice, Repair Order, Payment Method, Total, Fees and Payout, exportable to CSV. This is the ledger we reconcile against.

  5. 5

    Nothing sent to Google, Meta or GA4

    Fleetio's shop documentation lists no conversion tag, API or webhook for vendors. Anything reaching an ad platform has to come from your own records.

Fleetio · diagnose

Where tracking breaks for a Fleetio shop, in the order we check

Start with revenue totals, because the usual fault is network money credited to ads rather than ad leads going missing.

  1. 01

    Check what revenue figure feeds the ads reports

    If it's the bank deposit or the shop system's monthly total, Fleetio payouts are in it.

  2. 02

    Check whether the profile phone number is a tracking number

    If the Fleetio Go Call button rings a number filed under paid search, every driver call is a fake conversion.

  3. 03

    Check whether new fleet accounts carry a source

    Open the last ten new accounts and look for a click ID or a Fleetio RO number. Most carry neither.

  4. 04

    Check how repeat ROs are treated

    A fleet on its fifteenth RO isn't a new customer, whichever channel brought it in.

  5. 05

    Check rejected and deleted ROs

    An RO the fleet manager rejected in Auto Integrate, or one you deleted because the work was no longer needed, shouldn't survive in any revenue total.

Fleetio · prove

The QA evidence — Fleetio

Run on real jobs: one website lead from an ad-tagged URL and one network RO from a Fleetio driver, both followed to payout.

Source of truth

Your shop management system's approved repair orders, matched against the Fleetio Vendor Portal Activity export by RO ID and account name

  • The ad-sourced fleet manager's call or form stored with its click ID at first contact.
  • The first approved RO for that account reported once to Google Ads and Meta with its value.
  • The Fleetio driver's RO present in the Activity export and absent from every ad platform.
  • A repeat RO counted for retention and not resent.
  • A rejected RO missing from both revenue columns.
  • Network and ad-won revenue reconciled per account across a closed month.
  • Repeated 30 days later and after any change to your shop profile phone number.

Fleetio · free audit

What we check in the free audit

  • Check what revenue figure feeds the ads reports
  • Check whether the profile phone number is a tracking number
  • Check whether new fleet accounts carry a source
  • Check how repeat ROs are treated
  • Check rejected and deleted ROs

Checked against

Your shop management system's approved repair orders, matched against the Fleetio Vendor Portal Activity export by RO ID and account name

Get my free conversion tracking audit

Free30 minutesNo obligation

Fleetio · when not to buy

When a Fleetio shop doesn't need this

Some shops in the network are better off with a short conversation than a build.

  • If you run no paid ads and your fleet work arrives through Fleetio and word of mouth, there's nothing to separate. The Vendor Portal export is your report.
  • If ad spend is a few hundred dollars a month and your shop system already records where each new account came from, a monthly line in a spreadsheet does the job.
  • If your Fleetio profile number already differs from the number on your ads and your revenue reports never mix the two, the biggest fault is already fixed.
  • If your listing is still Unverified, meaning you're on Auto Integrate but haven't signed Fleetio's shop agreement, wait until the directory sends real work before measuring it.

Fleetio · what we deliver

The event map for a Fleetio network shop

  • Fleet manager call or form from your website

    The lead event, with the click ID stored against the caller's number or the form record.

  • Estimate or inspection scheduled

    Qualified lead, logged in your shop system with the source carried over.

  • First repair order approved for a new fleet account

    The ad conversion, sent to Google Ads and Meta with the approved RO value, only when the account traces to a click.

  • Fleetio network repair order completed

    Recorded from the Vendor Portal Activity log with RO ID, account name and payout. Excluded from every ad platform.

  • Repeat RO from an existing fleet account

    Retention, whichever channel brought the account. Never resent as a new conversion.

  • RO rejected by the fleet manager or deleted

    Removed from the ledger so it inflates neither column.

FAQ

Fleetio questions, answered

No, and you shouldn't try. A driver who finds you in the Fleetio Go directory never clicked an ad. The job belongs in a network revenue column reconciled from the Vendor Portal export, not in Google Ads.

Free · 30 min

Get Fleetio network work out of your ad numbers

Free30 minutesNo obligation