jongryn.com

Site and structured data

A 38-page site with a full schema.org entity graph: one canonical Person and RealEstateAgent node; an organization hierarchy modeling the team under the brokerage; sameAs consolidated across nine profiles.

Event lead capture

Built for a community chili cookoff. A QR code opens a mobile form that writes to Postgres. On the day it captured 67 entries over four hours with zero failures.

Deduplication

One person, one entry. Deduplication runs on normalized email and phone: Gmail dot-and-plus normalization for email, E.164 normalization for phone.

Consent, recorded per person

Each contact's consent is stored with the exact consent text shown, a version string, and a timestamp — so marketing permission is provable per contact rather than assumed for the list.

Bot mitigation without CAPTCHA

• A hidden honeypot field.
• A minimum time-on-form.
• MX record validation on the email domain, failing open so a slow DNS lookup never costs a real entrant.
• Per-IP rate limiting, tuned high on purpose: a shared booth device puts every entry behind one address.

The prize drawing

• Uses the platform CSPRNG with modulo-bias rejection.
• Excludes previous winners by record ID, so nobody can win twice.
• An offline fallback caches the entrant list locally so the drawing still runs if venue wifi drops.

CRM integration

HubSpot integration, with the database write always happening first — so a CRM outage can never lose a lead.