form
Wraps its body in a lead-capture form posting to the platform’s endpoint — honeypot, consent handling, and success handling included. Everything submitted lands in the owner’s CRM stamped with the page it came from.contact, listing, valuation, sold-price, tour, guide, buyer-search. The listing
kind ties the inquiry to a listing:
name, email, phone, address, area, message,
plus tour_date/tour_time for tours and magnet_id for guides. On
success the visitor returns to the page with ?sent=1 and the element
carrying data-form-success is revealed.
When the site owner has completed their commercial sender details, REALsite
automatically adds the consent checkbox and its signed proof token after the
form body. The request identifies the sender, any applicable brokerage, the
office mailing address, contact details, and how to unsubscribe. If the
visitor checks it, the platform records the exact request and sender details
they saw along with the form, page, and time. Do not add a second marketing
consent checkbox in the theme or post your own casl/casl_token fields.
If sender setup is incomplete, the form still captures the lead but does not
offer mailing-list opt-in. The admin guides the site owner to add the missing
office mailing address before consent collection or campaign sending is
enabled.
For buyer-search, send required areas (up to 300 characters) and budget
(up to 100), plus optional preferences (up to 1,000). Budget is free text,
so visitors can describe a range. Use name and email fields too. The shared
Personalized home search section and landing-page preset include this form.
The agent receives the preferences and a copyable brief in Leads. They set up
the search in Matrix / OneHome or their usual tool and invite the buyer there;
REALsite does not create or sync search alerts. Submitting a search request
does not itself grant newsletter consent.
marketing_consent
Use this inside a hand-built form that posts to/lead, such as a custom
contact modal:
{% form %}.
REALsite also normalizes every rendered /lead form, so older customized
layouts are automatically upgraded and incomplete sender setup removes any
stale opt-in instead of showing a checkbox that cannot work. Never hand-code
casl or casl_token fields. The data-lead-form, return_to, and matching
sf values let the platform return to this page and show the correct success,
retry, or email-confirmation message. REALsite supplies safe defaults when an
older custom form does not have them.
zone
An owner-arrangeable region: renders the site’s stored section arrangement, falling back to your inline default.default:. Changing the default
list or switching themes does not replace existing sections or their
settings. Keep zone names and supported section types stable when restyling.
Zones are opt-in. A template without zones is pure developer-authored
Liquid — a supported way to build, not a degraded one.