Where the results go

There are three places a completed Action shows up, and one channel most people assume exists and does not. Read the last section before you rely on this for anything time-critical.

The three real channels

Push to the NearField app

This is the only channel that reaches you the moment something lands. It needs the NearField app installed on your phone and signed in — a push has nowhere to go otherwise.

1. 1

   Open the block in the builder

   Any block that captures an answer has a When someone answers panel below its own settings.

2. 2

   Switch on Notify me

   The hint reads Sends a push to the NearField app on your phone. On Lead Capture and Request this appears inside the editor instead, as Send to the NearField app.

3. 3

   For a Rating, choose when

   Notify me about offers Every rating or Only low scores. A rating you hear about is one you can still do something about; being told about every five-star is how people learn to ignore notifications.

4. 4

   Manage the rest in Account

   Account → Notifications has the master switch and a per-Experience mute list, so you can turn one off without turning them all off.

Fourteen block types can notify, including Lead Capture, Waiver, Request, Review & Feedback, Rating, Quick Choice, Custom Input, Check-In, Geo Check-In, Passport, Quiz and the three contact-capture blocks.

Audience

Every answer and every lead lands in Audience as a row against a visitor profile, with the Experience and the Marker that captured it. The Timeline tab reads it as a day-by-day feed. The People tab reads it as contacts, filterable by whether you have an email, a phone number or a name.

The Overview tab narrates it in plain English: someone left their details at Ridgewood membership desk, someone signed your waiver, someone tried to claim your offer again. Contact details are masked by default — the Show contact details in full switch reveals them, and it is off until you turn it on.

Stats

The Action performance card counts four things per Action, and the gaps between them are the interesting part.

• Taps — the visitor engaged with the block.
• Completions — the outcome finished.
• Fallbacks — something did not work as intended, most often a clipboard permission denied inside an in-app browser.
• Gated — a repeat visitor was turned away by a one-per-person rule.

For Donate and Pay, taps and completions come from different places on purpose: your page can only ever record that checkout was opened, and the completion is confirmed by Stripe. The gap between the two is your Stripe Checkout drop-off, which is a genuinely useful number.

What NearField does not send

Two settings read as though they contradict that, and both are worth understanding precisely.

Lead Capture → Send it by (Email / Text / Both)

This delivers your file to the visitor. It is the email me the brochure trade. Nothing about it goes to you.

Request → Send requests by (Text / Email)

This builds a message and opens the visitor's own mail or messaging app with the request already written. It reaches you only if they press send, and you have no way of knowing when they do not. Switch on Send to the NearField app alongside it so you have a channel that does not depend on a stranger finishing an SMS.

What does arrive by email is the weekly audience digest, which says what happened in your space without anyone opening a dashboard, and the shareable live stats report — a link a board member, an owner or a sponsor can open with no account.