Your ads count the Spoke Dispatch order, not the delivery
Google Ads and Meta record a purchase the moment a meal-prep or water customer pays on your site. Whether the driver delivered that order sits in Spoke Dispatch (formerly Circuit for Teams), where no ad platform looks, so failed stops and repeat subscription routes get reported as wins. We take the delivered stop from Spoke's webhook, join it to the order and its click ID on your own server, and send that as the conversion instead.
Free30 minutesNo obligation
Spoke Dispatch · what breaks
What goes wrong with Spoke Dispatch
- 01
The ad gets credit at checkout, not at the doorstep
A meal-prep or water-delivery order fires a purchase when the customer pays online. If the driver marks that stop failed_not_home the next morning, the ad platform keeps the revenue and bids for more customers like that one.
- 02
Spoke knows the delivery; your ads know nothing about Spoke
Spoke documents Zapier, a Shopify app, a public API and a webhook. There is no Google Ads, GA4, GTM or Meta setting to switch on, so delivered and failed stops stay in the dispatcher dashboard unless something carries them out.
- 03
Spreadsheet imports lose the thread to the ad
A .csv row with Address Line 1, Recipient Email and an Id column says nothing about which campaign produced the order. If the Id column is blank, the delivery can never be joined to the click that paid for it.
- 04
Recurring customers look like new wins
A weekly meal-prep subscriber or a standing 5-gallon water account creates a stop on every route. Reported as fresh purchases, they make cost-per-acquisition look far better than it is.
Spoke Dispatch · the fix
What changes — Spoke Dispatch
Revenue reported when the stop is delivered
The paid conversion goes out after Spoke's webhook reports the stop with succeeded set to true, valued from your store's order total.
Failed stops never reach the bidding
A stop in any failed_ state is held back, and a browser purchase that already fired is corrected where the platform allows.
First order and repeat route separated
The delivery that lands a new customer counts as acquisition; the next thirty routes to the same address count as retention.
Spoke Dispatch · architecture
What Spoke Dispatch actually lets you do
Everything below is from Spoke's help center, developer docs and pricing page. Where the docs stop short, it is listed as a check.
- 1
Webhook API on every plan
Spoke's pricing page lists the Webhook API on all three plans, and the developer docs name a stop.attempted_delivery event that fires whether the attempt succeeded or not, with the full Stop in the payload. Developer API support is reserved for accounts spending over $50,000 a year, so a local delivery business builds against the docs alone.
- 2
The Stop payload carries the outcome
deliveryInfo.succeeded, a state such as delivered_to_recipient or failed_not_home, attemptedAt, photo URLs and a signature URL. Enough to send a conversion only for stops that completed.
- 3
External ID on each stop
The spreadsheet import has an Id column, the Shopify app maps Order Name to External ID, and the API stop model has recipient.externalId and orderInfo.sellerOrderId. One of those must hold the order number your ad produced; we confirm which one your import fills.
- 4
Shopify fulfillment write-back
The Shopify app, still labeled beta, can mark an order fulfilled when the stop is delivered (the default), when the route starts or at import. That timestamp is a second source for the delivered conversion if the webhook is not an option for you.
- 5
Zapier, inbound only as documented
Spoke's Zapier guide imports stops from Google Sheets with a code step and the API key from Settings > Integrations > API. It documents no trigger for a delivered stop.
- 6
No ad-platform connection
No Google Ads, GA4, GTM, Meta Pixel or Conversions API setting exists in Spoke Dispatch. The recipient tracking page is served by Spoke and the docs describe no place to add your own tags.
Spoke Dispatch · diagnose
Where Spoke Dispatch tracking breaks, in diagnostic order
Start with the join key: on Spoke the usual fault is a delivery that can't be tied to its order, not a tag that misfires.
- 01
Check the External ID on live stops
If the Id column was blank on import, or the Shopify Order Name mapping isn't in use, no delivery can be matched.
- 02
Check whether the click ID survives to the order record
Order once from an ad-tagged URL and confirm the GCLID or Meta click ID is stored on that order, not only in an expired cookie.
- 03
Compare successful stops with reported purchases
Per order, over a closed week, using the stop state from Spoke's detailed export. The gap is failed stops and repeat routes.
- 04
Check how failed stops are reported
A failed_ stop already counted at checkout inflates every return-on-ad-spend figure until corrected.
- 05
Separate first deliveries from subscription routes
On a meal-prep or water route most stops are repeat customers; reported as purchases, they make acquisition cost look artificially low.
Spoke Dispatch · prove
The QA evidence — Spoke Dispatch
Run on a real order delivered by a real driver on a live route, not a test.send_event fired from the dashboard.
Source of truth
Spoke Dispatch stop records, by External ID and attemptedAt, with deliveryInfo.succeeded and the delivery state
- One order from an ad-tagged URL, with the click ID stored on the order and the order number confirmed on the stop's External ID in Spoke.
- The stop.attempted_delivery event received on the first-party server with that External ID and succeeded true.
- Exactly one purchase for that delivered order in Google Ads and Meta Events Manager, deduplicated on a shared event ID.
- A failed_ stop confirmed absent from both platforms, and its browser purchase corrected where allowed.
- A repeat delivery to an existing customer confirmed absent from the acquisition conversion.
- Successful stops from Spoke's detailed export reconciled order by order against each platform across a closed week, then again 30 days later and after any change to the import method, Shopify fulfillment trigger or webhook endpoint.
Spoke Dispatch · free audit
What we check in the free audit
- Check the External ID on live stops
- Check whether the click ID survives to the order record
- Compare successful stops with reported purchases
- Check how failed stops are reported
- Separate first deliveries from subscription routes
Checked against
Spoke Dispatch stop records, by External ID and attemptedAt, with deliveryInfo.succeeded and the delivery state
Free30 minutesNo obligation
Spoke Dispatch · when not to buy
When you don't need this on Spoke Dispatch
Some delivery businesses are better off leaving the checkout purchase as the conversion.
- If nearly every stop is delivered first time and Spoke's success rate already matches your order count, the checkout purchase is close enough.
- If most routes are subscription renewals and you advertise only occasionally, Spoke's analytics will tell you more than per-stop attribution.
- If stops reach Spoke only by spreadsheet and the Id column is never filled, fix the import first; there is nothing to join until it is.
- If your Shopify store already marks orders fulfilled on delivery and you run one ad platform, sending the fulfillment event from the store may be enough.
Spoke Dispatch · what we deliver
The event map on Spoke Dispatch
Order placed on your site or Shopify store
Browser-side signal, with the click ID stored against the order number before it reaches Spoke.
Stop imported into Spoke
Order number written to the stop's External ID via the Shopify Order Name mapping, the Id spreadsheet column or the API's recipient.externalId and orderInfo.sellerOrderId fields.
Route started, stop out for delivery
stop.out_for_delivery logged for timing only. Nothing goes to an ad platform until the driver marks the stop.
Stop delivered
The conversion. Taken from the stop.attempted_delivery event with succeeded true, joined to the order and click ID, sent server-side to Google and Meta.
Stop failed
Excluded. A correction is sent if the browser purchase already fired.
Repeat delivery to an existing customer
Logged for lifetime-value reporting, kept out of acquisition.
Written guarantee
95%+ tracking accuracy
Measured against Spoke Dispatch stop records, by External ID and attemptedAt, with deliveryInfo.succeeded and the delivery state. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Spoke Dispatch questions, answered
Yes. The vendor announced on 23 October 2025 that Circuit for Teams is now Spoke Dispatch and the Circuit Client Portal is now Spoke Connect, calling it a name change only.
No. Spoke documents Zapier, a Shopify app, a public API and a webhook, nothing for Google Ads, GA4, GTM or Meta. Delivered stops reach an ad platform only through a server you control.
Not from what Spoke documents. The Zapier guide imports stops from Google Sheets; it describes no trigger for a delivered stop. The stop.attempted_delivery webhook is the documented way out.
The purchase fires at checkout, before any driver leaves. Failed stops and cancelled orders stay counted, and repeat subscription deliveries widen the gap every week.
Only if the Id column carries your order number on every row and your store keeps the click ID against that order. Filling that column consistently is the part most teams skip.
No. The link in Spoke's SMS and email notifications opens a Spoke-served page where the recipient watches the driver and sees proof of delivery; the docs give you no place to put tags on it. The conversion comes from the stop record.
More on Spoke Dispatch
- Enhanced ConversionsEnhanced Conversions enrich the conversions that already fire. First we make sur…
- Meta CAPIA one-click CAPI integration sends thin events. That's why your Event Match Qual…
- Cross-Domain TrackingYour checkout provider is the best performing traffic source in your GA4 account…
RELATED GUIDES
Booking tools beside Spoke Dispatch, and what their bookings feed
- YemboYembo conversion tracking: see which ads book signed moves
- BuildOpsYour BuildOps pipeline knows which ads won contracts. Google and Meta don't.
- LMNLMN conversion tracking: stop guessing which ads turn into Won estimates
- GranotGranot conversion tracking for movers who can't tell which ads book moves
- FieldPulseFieldPulse is full of booked jobs. Your ads can't see any of them.
- Agero SwoopAgero Swoop conversion tracking: see which tows your ads actually pay for
- CurbWasteConversion tracking for CurbWaste
- MarkateMarkate is full of booked jobs. Your ads can't see which clicks booked them.
Free · 30 min
Get Spoke Dispatch tracking right
Free30 minutesNo obligation
