A QR menu that actually tells you when guests open it.

Because a static QR is a hyperlink with no analytics. You can't tell whether the QR on table 4 gets opened twice as often as table 12. You can't tell whether your sidewalk decal is pulling foot traffic or just sitting there. A tracked QR makes the menu measurable: every scan logs the time, device, and approximate location. The lunch-rush spike, the Saturday-evening peak, the dead Tuesday at 3pm — those patterns only show up when scans are recorded over time.

Peak hour. Across all tracked clicks on Track Link, 17.7% land in a single hour at 12:00 UTC, and 42.4% are between 11:00 and 14:00 — the lunch window. For restaurants this matters operationally: if 60% of your menu scans happen between 11:30 and 13:30 local time, you know exactly when to staff up, when to refresh the daily special on the linked landing page, and when an out-of-stock item costs you the most.

One per table for table-side dining, one per location for take-out. Per-table QRs let you measure which tables drive the most engagement (window seats vs back booths often differ by 2–3×) and which tables churn fastest (high scans + short visits = waiter attention needed). The free plan covers 10 QR codes — enough for a 10-table dining room A/B test before you commit to per-table tracking permanently.

Yes, that's the entire point of dynamic QR. The QR encodes a Track Link short URL (e.g. gettrack.link/r/main-menu), and you set the destination on Track Link's dashboard. Change the menu PDF, the menu page on your site, the seasonal special URL — the same printed QR routes to whatever you point it at. No reprinting table tents.

Yes, indirectly. Compare scan volume per hour against your covers per hour. If you served 80 dinners between 19:00 and 21:00 but the QR logged only 22 scans, 58 guests preferred paper menus or shared a phone. That ratio matters for designing the menu — heavy text doesn't work for sharing, while photo-rich pages drive more individual scans. Track Link gives you the scan side; your POS gives you the cover side; you draw the conclusion.

Separate is better if you want signal. A single QR routing to a multi-tab landing page (food + drinks + dessert) shows you 'someone scanned' but not which menu they were after. Two QRs — one on the table tent, one on the bar — give you separate scan counts that you can compare day-to-day. The cost is one extra design + one extra print run; the analytics value over a year is worth it.

The geo data on Track Link resolves at the IP address of the scanning phone. Tourists on roaming or local SIMs both resolve to the country they're physically in, so a tourist scanning your menu in Lisbon shows as Portugal regardless of where they're from. If you want to capture nationality, add a 'Where are you visiting from?' question on the landing page itself — Track Link's analytics handle the technical scan, but tourist origin is a content question, not a logging question.

No. Track Link generates clean QR images on free and paid plans. The image you download is yours — print it on table tents, window decals, check holders, takeout bag stickers. We don't add a logo or footer to the QR.