Skip to main content
DispatchTrackField service software

Conversion tracking for DispatchTrack

Google Ads says you sold forty sofas last month, DispatchTrack says thirty-one got delivered and signed for, and nobody told the ad platforms about the nine. DispatchTrack takes the order from STORIS, NetSuite, SAP, Oracle, Microsoft or DDI after the sale, sends the customer a link to pick a window, and records the signature at the door, so it is the one system in a furniture or appliance store that knows which sales actually completed. We make delivered orders the conversion, take cancellations and refusals back off, and match showroom orders to the ads that brought the customer in.

Free30 minutesNo obligation

DispatchTrack · what breaks

What goes wrong with DispatchTrack

  1. 01

    The sale counts before the sofa leaves the warehouse

    Your ad platforms record a purchase when the order is placed. DispatchTrack handles everything after, including the customer who cancels a week before the window, and nothing tells Google Ads or Meta. Smart Bidding keeps learning from orders you never delivered.

  2. 02

    Showroom orders are invisible to the ads that drove them

    A couple sees a mattress ad on Instagram, comes in, and the order is keyed into STORIS. It reaches DispatchTrack for delivery and never reaches Meta, so the budget moves to whatever looks better online.

  3. 03

    You keep advertising a dining set to the person who bought it

    After the order, your customer lives in DispatchTrack: the scheduling link, the tracking portal, the two-way texts. None of it touches your website, so your buyer-exclusion audiences never learn they bought.

  4. 04

    Refusals and damage swaps never come off the number

    A refrigerator refused at the door or a scratched dresser swapped on a second route is recorded in DispatchTrack and settled in your ERP. The ad platforms still carry the full original value.

DispatchTrack · the fix

What changes — DispatchTrack

  • Delivered value replaces checkout value

    Completed deliveries, read from your ERP or DispatchTrack's API, go to Google and Meta as the purchase. Cancellations are retracted or adjusted wherever each platform allows it.

  • Showroom sales find their ad

    The delivery contact's hashed email and phone go to Meta as offline events and, where the customer first came in through a quote or financing form on your site, to Google as an enhanced conversion for leads. No earlier online touch, no match, and the report says so.

  • Buyers come out of prospecting

    Delivery contacts sync to exclusion audiences from the day the order lands in DispatchTrack.

DispatchTrack · architecture

What DispatchTrack actually lets you do

DispatchTrack documents ERP connectors, a REST API and two webhooks, nothing for Google Ads, GA4, Meta or Zapier, and its customer pages run on its own domain. So the tracking is built from delivery records, not tags.

  1. 1

    ERP connectors in both directions

    NetSuite, STORIS, Oracle, SAP, Microsoft and DDI are listed. Orders flow in, and completed deliveries are reflected back to the ERP, which is where we usually read delivered status.

  2. 2

    REST API for dispatches, routes and contacts

    Its public docs cover dispatches, routes, dispatch guides, contacts, substatuses, reviews and data exports, with a free lite tier capped at 1,000 requests a day and one a second. Enough to poll a day's dispatches for delivered status when the ERP doesn't carry it back; we confirm on the call that your account exposes the same endpoints the docs describe.

  3. 3

    Route and dispatch webhooks, set up by support

    The same docs describe a route webhook (route created, started or ended) and a dispatch webhook that fires whenever a dispatch is touched. You ask DispatchTrack support to point them at a URL, which is how a signed delivery can reach the server container within minutes instead of on a schedule.

  4. 4

    Customer links hosted by DispatchTrack

    The self-scheduling portal, day-of tracking portal and survey are DispatchTrack pages sent by text or email, with no documented slot for your own tags. Nothing here depends on them firing.

  5. 5

    Messaging and review partners

    Twilio, Plivo, Podium and a Google Review integration are listed. Good for reputation, not a conversion path.

DispatchTrack · diagnose

Where DispatchTrack tracking breaks, in diagnostic order

Start with the count gap, because the first fault is almost always a purchase reported weeks before anyone knew whether it would deliver.

  1. 01

    Compare checkout purchases with completed deliveries

    One closed month, by order ID. The difference is what the platforms never heard about.

  2. 02

    Check whether the order ID survives the trip

    Website or POS, to the ERP, into DispatchTrack and back. If it changes shape, nothing can be matched.

  3. 03

    Check whether web orders keep the click ID

    No GCLID stored on the ERP order means the delivered conversion has nothing to attach to.

  4. 04

    Check whether showroom orders carry a usable contact

    The delivery contact's email and phone are what match an in-store sale to an earlier ad touch.

  5. 05

    Check whether buyers are still in prospecting

    Pull a week of delivery contacts and look for them in your retargeting audiences.

DispatchTrack · prove

The QA evidence — DispatchTrack

Run on real orders that completed delivery, not test dispatches.

Source of truth

DispatchTrack completed-delivery records — orders delivered and signed by date, with order ID, delivered value and any cancellation or refusal status

  • One web order from an ad-tagged URL, with the click ID confirmed on the ERP record that feeds DispatchTrack.
  • That delivery marked complete in DispatchTrack and appearing once, with the delivered value, in Google Ads and Meta.
  • One order cancelled before its window, confirmed retracted or adjusted where supported.
  • One showroom order matched through hashed email or phone to its earlier ad touch.
  • Delivery contacts present in the buyer-exclusion audience within a day of the order landing.
  • Delivered orders reconciled by order ID across a fully closed month.
  • Repeated 30 days later and after any change to the ERP connector.

DispatchTrack · free audit

What we check in the free audit

  • Compare checkout purchases with completed deliveries
  • Check whether the order ID survives the trip
  • Check whether web orders keep the click ID
  • Check whether showroom orders carry a usable contact
  • Check whether buyers are still in prospecting

Checked against

DispatchTrack completed-delivery records — orders delivered and signed by date, with order ID, delivered value and any cancellation or refusal status

Get my free conversion tracking audit

Free30 minutesNo obligation

DispatchTrack · when not to buy

When you don't need this on DispatchTrack

Some stores already have the loop closed in their ERP, and some don't spend enough on ads for the correction to matter.

  • If nearly every order delivers within days and cancellations are rare, the gap may be too small to move your bidding.
  • If your ERP already sends delivered orders and cancellations to Google Ads and Meta, and a month's reconciliation matches, leave it alone.
  • If you sell cash-and-carry and use DispatchTrack only for the occasional large delivery, track the sale in the POS instead.
  • If the only problem is customers seeing ads while they wait for delivery, a scheduled customer-list upload fixes that, and we'll tell you so.

DispatchTrack · what we deliver

The event map on DispatchTrack

  • Quote, financing or lead on your site

    Before DispatchTrack exists. Click ID and the customer's email or phone captured here so the delivered order can be matched later.

  • Order placed, web or showroom

    From the ERP record that feeds DispatchTrack, with value and order ID. Not yet the conversion.

  • Delivery window self-scheduled

    The customer opened DispatchTrack's scheduling link and picked a slot. A sign the order is real; never sent as a purchase.

  • Delivered and signed

    The money event, sent server-side with the delivered value and the original order ID.

  • Cancelled, refused or damage swap

    From DispatchTrack's delivery status and the ERP, reversed or adjusted wherever supported.

  • Post-delivery survey or review left

    DispatchTrack's text NPS and review prompts fire after the truck leaves. Useful for reputation, never sent to an ad platform as a conversion.

FAQ

DispatchTrack questions, answered

Not that it documents. Its integrations page lists ERP connectors, telematics, messaging partners and a Google Review link, with no ad platform, GA4 or Zapier entry.

Free · 30 min

Get DispatchTrack tracking right

Free30 minutesNo obligation