Website lead forms that feed your CRM, not a shared inbox
Send every website lead form to your CRM: build a form once, then paste it into your site, share it as its own link or post to it from your own server. Every entry arrives as a lead with its campaign tags and consent on record, checked for spam and duplicates, and handed to the right rep.
- Embed, share a link or send signed posts
- Campaign tags and consent saved with the lead
- Spam and duplicate checks before a rep sees it
- ways to publish the same form
- 3
- field types, each checked again on the server
- 12
- Cloudflare Turnstile, until you switch it on for a form
- Off
What arrives with every form entry
- Form answersTyped fields saved into the lead
- ConsentThe notice read and the box ticked
- Campaign tagsUTM tags, gclid and fbclid
- Landing pageWhere the visitor arrived, and from where
- Lead sourceWebsite or embedded, by route
- Submission IDSo a double click never makes two leads
Enquiries that wait in a shared mailbox
Your contact form sends an email to info@, where it sits between invoices and newsletters until someone notices it. Nobody owns it, nobody knows whether it was answered, and the buyer who filled it in on Friday evening has called a competitor by Monday.
No record of which campaign paid for it
A visitor clicks your Google ad, reads three pages and fills in the form. The email that arrives says nothing about the ad, so the enquiry is copied into a sheet as 'website' and nobody can tell which campaign is producing buyers and which is burning budget.
Bots, repeats and consent you cannot prove
Spam fills the inbox, the same person submits twice and gets two replies, and when someone asks why you messaged them there is no record of what they agreed to or when. A plain form email gives you no way to sort any of it out.
A lead capture form built once, with exactly the fields you need
Add up to 40 fields from twelve types: short and long text, email, phone, number, date, website address, dropdowns, single and multiple choice, checkboxes and a consent box. Give each one a label, placeholder, help text and limits, and choose the lead field its answer is saved into. Every rule is checked again on the server, so a submission that skips the browser still cannot break your data.
- Twelve field types, up to 40 fields a form
- Choices typed in, or taken from your lead sources and tags
- Each answer saved into a lead field, or kept as an answer
- Every rule re-checked on the server, field by field
A consent box that holds up when someone asks
A consent field names what the visitor is agreeing to, marketing, sales outreach or both, and the channels it covers: email, SMS and WhatsApp. The notice you write sits above the box, and the box always starts unticked; a form that tries to pre-tick it cannot be saved. When a visitor ticks it, the notice they read, the time, their IP address and their browser are recorded.
- Purposes and channels chosen for each consent box
- The notice shown before the box, never after it
- Never pre-ticked, and a pre-ticked box is refused
- Notice, time, IP address and browser kept as evidence
One script tag puts the form on your own page
Copy the snippet from the form and paste it into any page of your site. The script draws your fields, checks the answers before sending and posts them straight to DigiPix Flow, with no signing secret sitting in the browser. Tell it where on the page to appear with a CSS selector, or let it appear where the snippet sits. Once the details are received, the visitor sees a thank-you message.
- One script tag carrying your form's key
- A data-target attribute to choose where it appears
- Answers checked in the browser and again on the server
- A thank-you message once the details are received
No web developer free? Share the form as its own page
Every form also has a hosted page with a link you can use anywhere a link works: a WhatsApp message, an Instagram bio, an email signature or a QR code on a flyer. There is nothing to install. The page is kept out of search results, so it never competes with your website, and it can sit inside an iframe. Add UTM tags to the link and each lead shows the campaign that sent it.
- A link for every form, with nothing to install
- Marked noindex, so it stays out of search results
- An iframe snippet if you would rather place it on a page
- UTM tags on the link saved with each lead
Signed posts from the forms your site already runs
If your website already handles its own form, your server can send each entry on to DigiPix Flow. Every request carries a timestamp, your own submission ID and an HMAC-SHA256 signature made with the form's secret, so it cannot be forged or replayed. The secret is shown once, when the form is created; rotate it whenever you need and the old one stops working straight away.
- Signed with HMAC-SHA256 and the form's own secret
- Timestamps accepted within five minutes of server time
- A repeated submission ID returns the first result
- Ready-made examples in Node.js, PHP and Python
Every lead arrives knowing where it came from
The embed and the hosted page read the page a visitor landed on, the site that referred them, all five UTM tags and the Google and Facebook click IDs, and save them with the lead. The first campaign a visitor arrived from is kept for their browser session, so it survives the click through to your contact page. Each lead is also tagged with the route it came in by, website or embedded.
- utm_source, medium, campaign, content and term
- The gclid and fbclid click IDs from your ads
- The landing page and referrer on every embedded lead
- A source tag for each route, so you can compare them
Spam checks that never cost you a real enquiry
Every embedded and hosted form carries a hidden honeypot field; a bot that fills it gets an ordinary reply and no lead is created. Each visitor can send up to 30 submissions a minute to a form. For a visible challenge, save your own Cloudflare Turnstile keys and switch it on form by form. If Cloudflare cannot be reached, the lead is still accepted and the missed check is logged.
- A hidden honeypot on every embedded and hosted form
- Up to 30 submissions a minute per visitor, per form
- Cloudflare Turnstile on your own keys, off until you choose
- Leads kept, and logged, if Cloudflare cannot be reached
From contact form to CRM to the right rep, with a text back
A form entry goes through the same steps as every other lead. It is checked against the leads you already have, and a likely duplicate is flagged for someone to review rather than combined. Assignment rules pick an owner within working hours, with a default owner to fall back on. Switch on an SMS auto-reply for a form and anyone who left a phone number gets one text.
- Likely duplicates flagged for a person to review
- An owner picked by your assignment rules
- An optional SMS auto-reply from a published template
- No text to numbers on your do-not-contact list
Kavya IyerFrom a new form to an owned lead, in five steps
- STEP 01
Build the form
Pick fields, rules, a consent box and where each answer is saved.
- STEP 02
Publish it your way
Paste the snippet, share the hosted link or sign posts from your server.
- STEP 03
Capture the entry
Answers, consent, campaign tags and landing page arrive together.
- STEP 04
Check it
Spam checks run, then the lead is compared with the ones you have.
- STEP 05
Hand it over
Assignment rules pick an owner, and an SMS auto-reply goes if you want one.
DigiPix Flow forms vs a contact form that emails a shared inbox
| What it covers | A contact form that emails a shared inbox |  DigiPix Flow |
|---|---|---|
| Where an enquiry lands | An email in info@, among everything else | A lead in your CRM, with an owner |
| Which campaign sent it | Lost the moment the email is sent | UTM tags, click IDs and landing page on the lead |
| Consent | A line of text nobody can find later | The notice, time, IP address and browser recorded |
| Spam | Deleted by hand, one email at a time | Honeypot, rate limits and optional Turnstile |
| The same person twice | Two emails, often two replies | Flagged as a likely duplicate for review |
| Who follows up | Whoever opens the mailbox first | Your assignment rules, with a fallback owner |
| Answer checks | Whatever the site's form happened to allow | The same rules checked on the server every time |
The other ways leads reach the same list
Website forms feed the same lead list as your ad platforms, marketplaces and your own systems, so every enquiry is checked, scored and routed the same way.
Website and embed form questions, answered
Should I embed the form, share the link or send signed posts?
Whichever suits each place you collect enquiries; one form supports all three. Embed it when you can paste a script into your site, share the hosted link when you can't or when you want a link for social posts and QR codes, and use signed posts when your own server already handles the form. Publish the form first, because a draft form's links do not accept entries.
Do I need a developer to add the form to my website?
Not for the embed or the hosted page. The embed is one script tag you paste into a page, and the hosted page needs nothing at all beyond sharing its link. Signed server-to-server posts do need someone who can change your site's backend, and DigiPix Flow gives them examples in Node.js, PHP and Python.
How are signed posts protected, and what if we lose the secret?
Each request is signed with HMAC-SHA256 using the form's secret, over the timestamp, your submission ID and the form fields. Requests more than five minutes away from server time are refused. The secret is shown only once; if it is lost, rotate it and update your server, because the old secret stops working straight away.
What kinds of fields can a form have?
Twelve types: short text, long text, email, phone, number, date, website address, dropdown, single choice, multiple choice, checkbox and consent checkbox, with up to 40 fields in a form. Dropdowns can use your lead sources or tags as choices. If a visitor gets an optional field wrong, that answer is dropped rather than the whole enquiry.
How is consent recorded from a form?
Add a consent checkbox, choose whether it covers marketing, sales outreach or both, pick the channels, and write the notice. The notice is shown above the box, which always starts unticked. When the visitor ticks it, their consent is recorded with the notice they saw, the time, their IP address and their browser.
Is Cloudflare Turnstile switched on for every form?
No. Every embedded and hosted form has a hidden honeypot and a limit of 30 submissions a minute per visitor. Turnstile is optional: save your own Cloudflare site and secret keys once, then switch it on for the forms that need it. It applies to the embed and hosted page, since signed posts are already authenticated.
Which campaign details are saved with a lead?
From the embed and the hosted page: the landing page, the referring site, utm_source, utm_medium, utm_campaign, utm_content, utm_term, and the gclid and fbclid click IDs. The first campaign a visitor arrived from is kept for their browser session. Signed posts can send the same details alongside the form fields.
What happens if someone submits the form twice?
A double click on the same form sends the same submission ID, so only one lead is created. If the person comes back later and fills the form in again, the new lead is compared with your existing leads and flagged as a likely duplicate for someone to review. Nothing is combined without a person deciding.
Can visitors get an automatic reply?
Yes, by SMS. Switch on the auto-reply for a form and choose a published SMS template. After the new lead is created and routed, anyone who left a phone number gets one text, sent from your workspace's SMS route. Numbers on your do-not-contact list, or whose consent has been withdrawn, are skipped.
Something we haven't covered? Talk to an expert
Keep exploring
Visit the blog- PRODUCTLead inbox for every enquiry sourceEvery source in one list, checked for duplicates, scored and routed.See how it works
- FEATURESConsent and opt-out recordsHow consent from forms is respected on every later message.Explore the feature
- FEATURESDuplicate lead managementReview likely duplicates and decide what happens to each pair.Explore the feature
- FEATURESWhatsApp and SMS follow-upReach new leads on the channels they check first.Explore the feature
- INTEGRATIONSLead capture APICreate leads from any system with an API key.See the integration
ARTICLEYour leads are not lost, they are just scatteredWhy enquiries slip through when they arrive in five different places.Read the article
GUIDELead Source Tracking: How to Know Which Campaigns Bring Real CustomersA practical guide to lead source tracking: tag links with UTMs, keep Google and Meta click IDs, pass them through hidden form fields, record offline sources and report leads by source.Read the guide
Turn your website's enquiries into leads someone owns
Talk to an expert — bring the form on your site today, and see its next entry arrive with its campaign, consent and owner.
- A real person, not a bot
- Bring your current contact form
- See an entry become a lead