slug (e.g., o1ulpplq), a permanent scan URL (nearnode.io/v/o1ulpplq), and a configurable function type that determines what happens when someone scans it.
Lifecycle
Every node moves through a lifecycle. Status transitions are tracked and logged.| Status | Description |
|---|---|
draft | Created but not yet written to hardware |
in_production | Written to a tag/chip but not yet deployed in the field |
active | Live and serving scans |
paused | Temporarily disabled — scans return a 404 |
lost | Tag is reported lost or stolen (kill switch activated) |
retired | Permanently decommissioned |
Function Types
Thefunction_type field determines how a scan is handled:
- Redirect
- vCard
- WiFi
- Action
- Microsite
The simplest type. Scans redirect (HTTP 307) to a destination URL.
Routing Rules
Each node can have multiple routing rules evaluated in priority order. Rules enable:A/B Testing
Split traffic between page variants and measure conversion.
Time-Based
Different destinations for office hours vs. after-hours.
Geo-Targeting
Route DACH region to German content, rest of world to English.
Device Routing
Mobile users get the app store, desktop users get the website.