Skip to content

Case Study · Local Lead Generation

One Field, a Code, and a Booking

Neckles IO · Engagement 2026 · Belleville, Ontario

Client
A nail and spa studio in Belleville, kept anonymous while the launch is young
Engagement
Landing page, offer capture, and a Meta campaign on our client-delivery chassis
Stack
Astro static site on Cloudflare Pages, Cloudflare D1, Pages Functions, Meta Pixel and Conversions API, Turnstile, transactional email and SMS, Fresha booking

The brief

A newly opened nail and spa studio needed first-visit bookings from local Meta traffic. The classic mistake here is to send ad clicks to a booking calendar and hope. Most people who tap an ad are not ready to pick a date and time on the spot, so the calendar leaks. The studio wanted the offer to do the work: give someone a reason to act now, capture them the instant they do, and only then hand them to booking.

One field, one tap

The landing page leads with a single input. Phone or email, one field, one tap to claim. There is no form to fill out, no account to create, no second screen before the value lands. When the guest submits, the server mints a unique coupon for the offer (twenty percent off a first visit, or a free nail-art upgrade), writes a durable lead record, and delivers the code to that guest immediately by both text and email. Then the page sends them straight to the studio's booking page with the code in hand.

Step 1

One field

Phone or email, one tap to claim the offer. Nothing else to fill out.

Step 2

Instant code

A unique coupon is minted and sent by text and email on the spot.

Step 3

Books itself

The guest is sent straight to the booking page to pick a time.

The funnel end to end. The coupon is unique per claim, minted with a collision-safe retry, so no two guests share a code.

Optimized for a single action

Because everything hinges on one submission, the whole system is tuned to that one action. The Meta campaign is optimized for the single-field submission, not for clicks or reach. When a guest claims, the browser fires the Meta Pixel and the server fires the Conversions API for the same event, sharing one event id so Meta counts it once. That server-side signal is what lets a small budget learn quickly: the ad platform sees real claims, not just page views. A Turnstile check guards the form so bots never enter the pipeline.

What the client owns

Every claim writes to the studio's own Cloudflare D1 database, holding the contact, the coupon, the delivery channel, and the timestamps. That data is the client's, not ours, and it is never merged into an agency CRM. On top of the durable record, each claim sends the owner a plain alert email so a real person sees the lead the moment it lands. Delivery is resilient: if the instant text or email is slow, the code still shows on screen with a fallback redirect, so the guest is never left empty-handed.

Early results

The funnel went live in late June 2026. In its first week, on a small launch run, it delivered real coupon claims through to booking, with the codes going out by text and email and the owner alerted on each one. Those are early numbers on a deliberately small budget, so we are not drawing a cost-per-lead from them yet. Fuller performance data is being gathered as the campaign matures. What the first week proves is that the mechanism works end to end with real local guests: claim, deliver, redirect, book.

What the system does

  • Single-field claim: phone or email, one tap
  • Unique coupon minted per claim, collision-safe
  • Instant delivery by both text and email, then redirect to booking
  • Meta optimized for the single-field submission, Pixel and Conversions API deduped on one event id
  • Leads stored in the client's own database, never shared with an agency CRM
  • Turnstile bot protection and a delivery fallback so no claim is lost

Have an offer that should convert on the first tap?

Tell us what you want people to claim, and where they should end up. We will let you know if we can help.

Tell Us What’s Slowing You Down