There is no “share” button on the visitor's side of an Experience, by design: the page belongs to you, not to us, and it does not advertise itself. Sharing is something you do from your side, and there are four routes.
The four routes
| Route | Looks like | Best for |
|---|---|---|
| Full link | getnearfield.com/view/abc123defg | Email, chat, a link on your website. |
| Short link | getnearfield.com/e/abc123defg | Anything printed or read aloud. |
| QR code | A code you generate in the builder | Posters, table tents, screens, packaging. |
| A Marker | A physical square with both a chip and a code | Walls, plinths, nightstands, rails. |
All four land on the same page. They differ only in how the arrival is recorded, which is what lets you tell a poster apart from a newsletter later.
Copying a link
- 1
Open your dashboard
Hover the Experience's row on a desktop, or open its overflow menu on a phone.
- 2
Choose Copy link
You get the short form, which is the one to use when a human might have to type or read it out.
- 3
Paste it wherever it is going
The link works with no account, no app and nothing to install at the other end.
The publish hub and the manage panel both carry the full link with a copy button as well, next to a QR code of the same address.
QR codes
The QR code offered in the builder encodes the Experience's own address, and it is a fine thing to print. Understand the trade-off before you commit it to a laminated sign: a printed QR points at that Experience forever, while a Marker points at whatever you have most recently chosen.
What a tap does
A phone touches the Marker
Or the camera reads its QR code. No app, no account, nothing to install.
The Marker's own address opens
/m/{marker}?src=nfc
This never changes. It is printed into the chip and the code at the factory.
NearField looks up what it points at
This is the part you control, and the part you can change at any time.
Your Experience renders
/view/{experience}
Counted as a visit, with the tap or scan recorded against that Marker.
Where each arrival is filed
Every visit is recorded as a tap, a scan or a direct arrival. Copy link produces a direct link, builder QR codes produce scans, and the two halves of a Marker produce taps and scans respectively, which is exactly how you find out whether anybody uses the printed code on a Marker.
A builder QR code has no Marker behind it. Its scans show as Builder QR in How people found you on Stats, apart from QR scan, which counts your Markers' own codes, and they stay out of the From a Marker tile, which only counts visits that came through one of your Markers.
Sharing a draft
Drafts have no public link. Use the QR in the Preview panel, which mints a link that works for an hour. See previewing before anyone sees it. Never send the address from your browser's bar: that is the builder, and it will ask your reviewer to sign in.
Example
The Bellhaven Hotel
The Bellhaven puts a Marker on every nightstand, prints the short link on the back of the key card holder for guests who prefer to type, and pastes the full link into the pre-arrival email. Three routes, one Experience, and the stats separate them cleanly, which is how they learned that the pre-arrival email drives more first opens than the Marker does, and moved the check-in details higher up the page.
Can I use my own domain?
Not currently. Every Experience lives on a getnearfield.com address, and the short form keeps it brief enough to print.
Will the link ever change?
No. It belongs to the Experience for as long as the Experience exists, through publishing, unpublishing and any amount of editing.
Can I see who opened a shared link?
Not by name. You see counts, sources and answers people chose to give. See Stats and Audience.
What happens if somebody shares the link on social media?
It works, and the visits are filed as direct arrivals. Nothing about the page depends on how the visitor got there.