Formcraft

Lead capture for paid traffic

Forms that capture the lead and tell the ad platform it worked.

Most form builders stop at the submission. Formcraft is built for what happens after it: the number gets verified, the consent gets recorded, the attribution survives the handoff, and the conversion goes back to Google and Meta so the bidding has something true to learn from.

3 of 5

Property

What condition is the property in overall?

Move in ready
Needs minor work
Needs significant work
ContinueAutosaved

Captured automatically

utm_sourcegoogle
utm_campaignsell-fast-ca
gclidCj0KCQiA_8
fbclidIwAR2n4Qp

One lead, start to finish.

01

They arrive

Campaign tags and the click ID come in with them, from Google, Meta, Microsoft, TikTok or wherever the click was bought.

02

They answer

One question at a time, with the branches they do not need skipped, so a long qualifier feels like a short one.

03

You get the lead

To your CRM, your automation, your inbox or your phone, with everything that came in alongside the answers.

04

The platform learns

The conversion goes back to the ad account server side, so the bidding optimizes against leads that were real.

Real numbers only

A code by text, before the lead counts.

Optional per form. The answers are stored before the code is ever asked for, so somebody who abandons the step still reaches you, marked unverified. Nothing is held hostage to it.

Enter the code we texted you

4192

The lead is already saved. This only decides whether it says verified.

stored with response · 2026-10-15 09:14:22

Proof, not a promise

The exact words they agreed to, kept.

Calling a number somebody gave you is the one thing they can later say they never agreed to. Formcraft stores the disclosure that was on the screen, word for word, with the time. Edit the copy later and the old record still says what it said.

Nothing lost in the handoff

Delivered, and reported back.

The lead goes where you need it. The conversion goes back to the ad account server side, with the email and phone hashed before they leave. When something does not land, you are told what the other end said, and it retries on its own.

Delivery

Zapier webhook202 Accepted
Meta Conversions APILead, matched
Google AdsQualified lead
Client CRM500, retrying in 5m

The rest of what it does.

Build it by describing it

Paste the questions, or the spreadsheet of values a client's system expects, and the builder drafts the form. Then rename, reorder and branch it by hand.

One tag, any page

Six kilobytes. It renders in an iframe, resizes itself, and cannot be broken by the theme around it. Or send traffic to a hosted page and skip the site.

Junk never reaches the client

Flagged submissions are held for a human instead of landing in a CRM. Dead numbers and undeliverable mailboxes are caught at the field.

See where it leaks

Drop off per question, so the one that costs you half the form stops being a guess.

Book the appointment

Cal.com, Calendly or Google Calendar inside the form, so a qualified lead picks a time before they leave.

Told when it breaks

A delivery that fails gets emailed to you with the reason the other end gave, rather than found out from the client a week later.

Put it on a page and watch what it keeps.

Formcraft runs the lead forms behind our own campaigns. If you want it on yours, get in touch and we will set you up.

Request Access