In person
Most customers of a shop, a restaurant or a holiday let are physically present and will never visit the website. In person is the set of things they scan while they are standing there, and what happened after they did.
Touchpoints
A touchpoint is one QR code with one job. Make one from In person, or from the QR panel inside any published landing page. Give it a name you will recognise (“tents on the window tables”) and say where it lives - table tent, counter card, window, receipt, menu, NFC tag. The placement is what later answers which one is worth its space.
Codes are never deleted, only retired from the list. Whatever carries a code is still sitting on somebody's counter, and a dead scan is a worse outcome than a stale row.
Why the code points at us
A landing-page code encodes floatmessage.com/r/… rather than the page's own address. That is deliberate. A page's public URL changes - you attach a subdomain, you connect a custom domain months later - and a code printed with the old one would simply be dead. The redirect follows the page instead of the URL.
It also means you can point a printed code somewhere else. Swap to the autumn menu, and fifty table tents start opening it without reprinting one of them.
What gets measured
Three steps, per touchpoint:
- Scanned - somebody pointed a phone at it.
- Opened - the page actually loaded.
- Got in touch - they submitted the page's form.
We record a country and a rough device type, and nothing else. No visitor id, no fingerprint, nothing identifying the customer who scanned a code on a table.
What is not measured, and why
A Google review code shows scans and then stops. Its destination is Google's, and we can see nothing past that hop. The performance screen says so rather than printing a zero, because “0 leads” on a review code is not a bad result - it is a measurement nobody took.
Chat conversations, bookings and survey responses that happen on a landing page are not currently tied back to the touchpoint that produced them. Only the page's own form is. We would rather report one number that is true than four that are nearly true.
Contact channels
Every channel you have set up on Contact channels can have its own code - WhatsApp, Telegram, your phone number, your Instagram. A card by the till that opens a chat beats a number somebody has to type in while standing up.
These behave like any other touchpoint. The code encodes your /r/… link rather than the wa.me address, which means two things: the scans get counted, and changing your number updates every card already printed. A bare wa.me code on a sign can do neither.
The channel's own logo sits in the middle of the code, in its own colour, for the same reason the Google mark does on a review card - people hesitate over an anonymous square, and it genuinely does open WhatsApp. A code is offered only once the channel resolves to a working link, so you cannot print one for a number we could not turn into a wa.me address.
Like review codes, these show scans and stop there. Once somebody lands in WhatsApp or their phone dialler, we can see nothing further.
Printed signs
Any touchpoint can be ordered as a proper weatherproof sign, cut and posted. Printing your own stays free - every format downloads at 300dpi - and the printed sign always carries the tracked link so the scans still count.
Signs ordered from a public profile report are placed without an account, so they do not appear in your orders list. There is no way for us to prove they were yours.