A Lead Capture block is an inline form on your Experience. No redirect, no pop-up, no account for the visitor to create. They type, they tap, and a thank-you screen replaces the form.
What the visitor fills in
You choose the fields with three switches: Ask for a name, Ask for an email, Ask for a phone number. The last is off by default. Above them sits your prompt, which is the one required field: Stay in touch is the default, and it is worth replacing with something that says what they get.
Consent text is optional and changes the form's behaviour: add it and the visitor has to tick the box before they can submit. On success they see a tick and your thank-you message, defaulting to Thanks, we'll be in touch.
- 1
Add the Lead Capture block
It sits in Questions & answers in the block picker, marked with a lightning bolt. Starter plan and above.
- 2
Write the prompt
This is the only required field. Say what they get, not what you want: Get the members' preview list beats Stay in touch.
- 3
Choose the fields
Name, email, phone. Ask for the fewest you will actually use; every extra field costs completions.
- 4
Add consent text if you need it
Adding it makes the tick box mandatory before the form will submit. It is written for you if you deliver by text.
- 5
Write the thank-you message
It replaces the form on success, so make it specific about what happens next.
- 6
Switch on Send to the NearField app
This is the switch that tells you a lead arrived: a push to the NearField app, a row in your inbox, and a copy emailed to your account address. Install the app on the phone that should hear about it.
Delivering a file in return
The classic trade. Upload a PDF under Deliver a file after submit, give it a label, and choose Send it by: Email, Text, or Both. The thank-you screen then also carries a download button, so nobody has to wait for a message to arrive to get the thing they asked for.
- Send it by → Email
- NearField emails the file. The success screen says Sent to your address. It can take a minute, but the link below works right now.
- Send it by → Text
- NearField texts the link on your behalf, naming you, with Reply STOP to opt out in the message. NearField records what each visitor agreed to and honours STOP for you: that is what keeps the number in good standing with carriers.
- Send it as
- The name the visitor sees on the email or text. Leave it blank to use your account name; set it when this Action stands for a second brand or a property.
One submission per person
Switch on One submission per person and a visitor who has already submitted cannot claim again. Think free trials and one-time offers. Match repeat visitors by decides how a repeat is recognised: Email, Phone, or Both. With Both, matching either one counts as a repeat.
Matching happens on our server, not in the visitor's browser, so a repeat visitor on a brand-new phone is still caught. They see the message you wrote under Message for repeat visitors and no download button. The submission still lands in your Audience and you are still notified: the file simply is not sent twice.
What happens the moment they submit
One endpoint does the whole job, in one round trip: it records the submission, checks it against your repeat rule, delivers the file by whichever channels you chose, and tells you, by push and by email. That is deliberate: the alternative was four things that could each half-succeed.
Your push carries the Experience name and the submission: New lead: Sarah (sarah@example.com). A gated repeat reads differently, saying that they already have the file and it was not re-sent. The email copy has a subject like New lead: Sarah (Harbour Point Aquarium), lists every field they filled in, and links to them in Audience. Reply to it and your reply goes to the address they gave.
What Lead Capture remembers, and what it does not
A submission writes the name, email and phone into NearField Memory, so the lead lands in Audience with the same Marker attribution as every other answer, and so a later block on the same Experience can greet them by name.
What it deliberately will not do
Lead Capture cannot be put behind phone verification. Every other gateable block can, and this one is excluded on purpose: asking someone to verify a phone number in order to reach a form asking for their email is a wall in front of a door.
Example
Ridgewood Museum of Natural History: the membership prompt
A Marker at the end of the dinosaur gallery, where visitors are already impressed and standing still. The prompt reads Get the members' preview list: new exhibits a week before they open. Name and email on, phone off.
Deliver a file after submit carries a two-page PDF of the next season's programme, sent by email, labelled Autumn programme. One submission per person is on, matched by email, with the repeat message You're already on the list. The next programme opens in September.
A Name Capture block sits on the museum's welcome Experience instead, so the greeting at the café Marker still works for people who never touched the membership prompt.
Do I need consent text?
Only for texting, where NearField writes one if you do not. For email it is optional and depends on your jurisdiction and your own policy. Adding it makes the tick box mandatory before the form will submit.
Can I use Lead Capture without giving anything away?
Yes. Leave the file fields blank and it is a plain contact form with a thank-you message.
Where do the leads end up?
In Audience, on the People tab. Filter by Has email or Has phone, and export a contacts CSV when you need them elsewhere.
Can a visitor opt out after giving me their number?
Yes. Replying STOP to a NearField text opts them out, and NearField honours it without you having to do anything. A visitor can also clear their whole profile from the accessibility menu on your Experience.