Beacon Test Guide

Known Test IDs

Beacon ID	Type	Notes	Links
37PTQ9HJ88	Standard (fixed)	Permanent test share. Use for beacon.html changes. Never delete.	View ?src=qr Admin detail

Add your own: Create a new Pro beacon, note its ID from the admin Shares tab, and paste it into the URL Generator below to get all test links instantly.

Test URL Generator

Enter a Beacon ID

qr Open

qr2 Open

qr3 Open

direct Open

Tip: The qr and qr2 links are for simulating the chain without a physical poster. Open the qr link in your main browser — it auto-updates the address bar to ?src=qr2&ref=XXXX. Copy that updated URL and open it in incognito to simulate a forwarded link (qr2 visitor).

Test Scenarios

1 Direct visitor — no source tag

Open /find/BEACONID with no parameters.

Use the direct link from the URL Generator above, or just visit the bare beacon URL.
In admin → beacon detail → Visitor Sessions: expect a gray [direct] badge under "Other Visitors".
Events logged: src_direct, page_opened

2 Poster scan — qr visitor

Scan the actual printed poster QR code, or open the ?src=qr link from the URL Generator.

The page loads, logs src_qr, then immediately changes the address bar to ?src=qr2&ref=XXXXXXXX.
In admin: an orange [qr] session appears as a Scanner Chain header.
Events logged: src_qr, page_opened:qr
Keep this tab open — you'll need the updated URL for Scenario 3.

3 Forwarded link — qr2 visitor

After Scenario 2, copy the address bar URL (it now shows ?src=qr2&ref=XXXXXXXX) and open it in a different browser or incognito window.

This simulates someone the poster scanner shared with.
Logs: src_qr2, ref_XXXXXXXX — the ref links back to the original scanner.
In admin: a purple [qr2] session appears nested under the qr scanner in the chain.
The incognito address bar now shows ?src=qr3&ref=YYYYYYYY — ready for Scenario 4.

4 Second-generation share — qr3 visitor

Copy the address bar from the qr2 incognito window (shows ?src=qr3&ref=YYYYYYYY) and open in a third browser/profile.

Logs: src_qr3, ref_YYYYYYYY
In admin: a blue [qr3] badge. Chain depth is capped here — further shares stay qr3.
Events carry :qr3 suffix (e.g. page_opened:qr3).

5 Location permission

On any active session, tap the location enable button or allow the browser location prompt.

Event logged: location_permission_granted:qrX — shown in bold orange as a key milestone in the session journey.
Compass and walking map activate once permission is granted.

6 Arrival — gps_near_destination

This fires when the user's GPS places them within ~550m of the beacon's walking destination.

Easy lab method: Create a beacon at your exact current location. Enable location on the beacon page — you'll be "arrived" immediately.
Existing beacon: Use mock location (Android developer options) set to the beacon's lat/lng from admin detail.
In admin: an arrived flag appears in green on the session card.
Events logged: gps_near_destination:qrX, notified_arrived:qrX

Event Reference

Event (base name)	Trigger	Key milestone?
src_qr / src_qr2 / src_qr3 / src_direct	Page load — source identification	—
ref_XXXXXXXX	Page load — sharer fingerprint received	—
page_opened	Page fully initialised	—
location_permission_granted	User allows GPS	Yes
enlarged_photo	Tapped the beacon photo	—
opened_map_view	Opened the drive map panel	—
launched_maps_app	Tapped "Launch Maps"	Yes
opened_walk_split	Entered the walk-to-destination step	Yes
started_drive_route_view	Drive route rendered	—
opened_compass_view	Switched to compass mode	—
opened_livemap_view	Switched to live map mode	—
copied_address	Tapped copy address	—
opened_details_panel	Opened the details drawer	—
notified_driving	Push notification sent — driving reminder	Yes
notified_walking	Push notification sent — walk prompt	Yes
notified_arrived	Push notification sent — arrival	Yes
gps_near_destination	GPS within ~550m of walking target	Yes

All events from QR-chain visitors carry a :qrX suffix (e.g. page_opened:qr2). This suffix is stripped in the session journey display but is visible in the raw All Events list.

Admin Verification Checklist

Open beacon detail in admin (Shares tab → click beacon row). Scroll to Visitor Sessions.
Scenario 1: Session appears with gray [direct] badge under "Other Visitors". Journey shows page_opened.
Scenario 2: Session appears with orange [qr] badge as a Scanner Chain header. Stats row says "no known shares yet" until a qr2 visitor is linked.
Scenario 3: Purple [qr2] session appears nested under the qr scanner. Stats update to "shared with 1". The ref_XXXX in the session's raw events matches the last 8 characters of the qr scanner's visitor ID (visible in All Events).
Scenario 4: Blue [qr3] session appears. If it has a matching ref, it nests under the qr2 session… or appears in Other Visitors if ref linking isn't set up for qr3 chains yet.
Scenario 5: location_permission_granted badge appears in bold orange in the journey badges of the relevant session.
Scenario 6: Green arrived label appears in the session card header. gps_near_destination and notified_arrived appear as bold orange key events.
All Events list (below Visitor Sessions) shows raw events with timestamps and full action strings including :qrX suffixes.