Restaurant Online Ordering Tracking in Canada: Toast, Lightspeed, Square and Delivery Apps
In short: A Canadian restaurant brand usually sells through four channels: its own online ordering (often a Toast, Lightspeed or Square page), delivery apps (SkipTheDishes, Uber Eats, DoorDash), reservations, and walk-ins. Ads can only be measured precisely in the first channel and in reservations. So the playbook has three parts:
- make first-party ordering trackable and attractive
- report delivery-app sales next to ad spend, not as ad conversions
- judge local campaigns on the whole location’s sales
What you can and can’t track
| Channel | Trackable as an ad conversion? | How |
|---|---|---|
| Own online ordering (Toast / Lightspeed / Square page) | Yes | Provider’s tag or analytics integration, cross-domain GA4, or server-side events |
| Reservations (OpenTable, Resy, etc.) | Usually | Booking-widget integration or confirmation tracking |
| Catering & private events | Yes | Form → CRM → offline conversion with booked value |
| Delivery apps | No (order happens in the app) | Weekly sales by location, reported next to ad spend |
| Walk-ins | Indirectly | Location sales trends, store visits where your account is eligible |
Setup for first-party ordering
- Check what your ordering provider supports: a GA4 or GTM field, a Meta pixel field, or webhooks. Use the official integration before building anything custom.
- Fire a
purchaseevent with order value (excluding tax and tips),currency: CADand alocation_id. - Set up cross-domain measurement between your site and the ordering domain, so orders keep the campaign as their source.
- Send the same order to Meta CAPI server-side with a shared
event_id, so browser and server events deduplicate. - Give catering its own conversion with a higher value. A single catering order can be worth dozens of regular orders.
Delivery apps: report, don’t fake
Delivery apps don’t give you a pixel event for each order. Don’t count clicks to “Order on Uber Eats” as purchases. Instead:
- Count clicks to delivery apps as a secondary event, a measure of intent.
- Pull weekly delivery-app sales by location from each partner portal, and show them next to ad spend in Looker Studio.
- Use promo codes or app-specific promotions when you need a rough read on a campaign.
Franchise and multi-location brands
- Add one
location_idto every event, and use the same IDs as your POS. - Decide who owns budgets (head office or franchisees) and structure Google Ads and Meta accounts to match.
- Compare locations on cost per first-party order and total sales trend, not on clicks.
Next steps
- Industry overview: tracking for Canadian restaurants & QSR franchises
- Related setup: food & beverage tracking with GA4 & Meta CAPI
- All sectors compared: Canadian high-demand industries hub
- Want your ordering and location tracking checked? Book a 30-minute call.
Direct Implementation White-Label for Agencies
Need this implemented, audited, or white-labeled?
Whether you are an eCommerce brand owner fixing signal loss or a digital marketing agency needing a senior analytics engineer under strict NDA, I deliver 24–48h SLA turnaround with 8.5+ EMQ match rates.
✓ 24–48h Emergency SLA ✓ Strict Non-Solicitation & NDA ✓ 8.5+ Event Match Quality

