{# DE + SK hreflang odebráno 2026-05-24 — viz core/settings.py LANGUAGES. cross_lang_alternates is set False by views whose CS/EN versions live on DIFFERENT paths (KB articles/categories, blog posts) — there the naive same-path alternate would point at a non-existent URL, so we emit only the self-canonical instead of a wrong reciprocal. #} Skip to content

Server-side tracking for restaurants and delivery: your own channel vs. aggregators

Restaurants and delivery measure between two worlds: your own site with reservations and orders, and aggregators that own the customer. How to reliably measure your own channel server-side.

D
DataNostro Team 7. 6. 2026 · 10 min · Intermediate

Restaurants and delivery live between two measurement worlds. One is your own site — reservations, takeaway orders, a loyalty program. The other is aggregators (delivery platforms) that keep the customer and their data to themselves. Here's how to reliably measure at least what's truly yours.

Why restaurants are different

  • Own channel vs. aggregators. An order through a delivery platform gives you no customer data — the customer belongs to the platform. So good measurement is mainly about your own site.
  • Strong local and repeat intent. Guests return, order repeatedly, decide fast and often on mobile.
  • Conversion takes several forms. A table reservation, a takeaway order, a gift voucher — each is a different conversion with a different value.

Challenge 1: drive customers to your own channel and measure it accurately

Every order on your own site instead of via an aggregator is more valuable — you pay no commission and you get the customer's data. So it matters all the more that conversions on your own site are measured reliably. Server-side tracking captures them even through ad-blockers and iOS, so the ads bringing people to your site have accurate data to optimize on. More in the complete guide.

Challenge 2: reservations and orders as separate conversions

A table reservation and a takeaway order aren't the same. Measure them as separate events with their own values, so ads optimize for what you actually want. The basis is a clean data layer with unambiguous events.

Challenge 3: fast, mobile, repeat decisions

Restaurant intent is fast and largely mobile — exactly the environment where client-side measurement loses most on iOS and Safari. Server-side, with longer-lived identification, helps recognize a returning guest and separate acquisition from loyalty. This relates to ITP, iOS and ad-blockers.

Practical advice

  • Focus accurate measurement on your own channel — that's where you have the data and the margin.
  • Measure reservations and orders separately, with their own values.
  • Deploy server-side for mobile and iOS traffic.
  • Respect consent — see Consent Mode v2 in practice.

Summary

In restaurants you can't measure what happens inside someone else's delivery platform — but you can precisely measure your own channel, which is more valuable. Server-side tracking ensures the ads bringing guests to your site work with accurate data, not half the truth. Try DataNostro for free.

Share

A new article once a month

In-depth server-side tracking guides + case studies from the CZ market. No spam, just 1 email a month. Unsubscribe anytime.

Back to Tracking