Home / Blog / GDPR Lead Capture
GDPR lead capture: consent without killing conversion
GDPR does not forbid a lead capture form. It asks four things: a lawful basis, a specific and informed purpose, a real choice, and proof that the person agreed. The forms that lose signups are usually the ones that confuse consent with a cookie banner, or that ask for agreement in a way nobody can prove afterwards. This guide covers what to put in the form, what to store with each lead, and where the common fixes cost more conversion than they save.
Key takeaway: collect an address with a separate, unticked consent box, say in one sentence what will arrive, and store the mode, the exact text, the timestamp and the page URL with the lead. That record is what turns a checkbox into consent you can defend.
The short answer
- What you need: a reason to process the data (consent, contract, legitimate interest), a purpose stated in plain words, a real choice, and a record of the choice.
- What the form needs: the address field, a separate consent checkbox when consent is the basis, the text describing what will be sent, and a link to the privacy policy.
- What most sites get wrong: treating the cookie banner as consent for email, pre-ticking the box, bundling marketing with the terms, or keeping no record at all. Each of those looks like a small saving and removes the value of the whole list.
This is general information about how the rules are usually implemented, not legal advice. For your jurisdiction and your data, ask a lawyer or your data protection advisor.
Cookie banner and email consent are two different things
This is the most common confusion, and it costs conversions in both directions.
| Question | Cookie banner | Email consent |
|---|---|---|
| What it covers | Storage and reading of information on the device: analytics, ads, some widgets | Use of an address to send messages |
| What the person does | Accepts, refuses or chooses categories | Ticks a box, or submits a form that states the purpose |
| When it applies | On the first page view, before the script runs | At the moment the address is collected |
| What it does not replace | Marketing consent | Cookie consent for your analytics or ads |
A visitor who accepts your cookie banner has not agreed to receive email. A visitor who ticks the marketing box at checkout has not agreed to tracking cookies. Each needs its own statement, and each needs its own record.
Three ways to place consent in a form
- Optional (unticked box). The lead is captured with or without the box, and you only mail the people who ticked it. This is the safest default for a capture widget, because it separates the value you deliver now (a guide, a discount) from the permission to send more later.
- Required (must tick to submit). The box is the condition for the form to work. Use it when the message itself is the purpose: a newsletter signup, an event reminder. It costs signups and it is honest, which is the correct trade when email is the only thing you offer.
- Not applicable. A transactional form, where you reply to a request and send nothing else. Do not add a marketing box to hide the absence of a marketing purpose: it creates a record that says nothing.
In GrowthTools, the consent field lives on the widget and can be switched on per widget, with its own text. Check in your own account what is stored with the lead before you rely on it in a dispute: if the record does not include the text and the timestamp, it is a checkbox, not proof.
What to store with every lead
If you cannot produce, months later, evidence that this person agreed to this message, the consent is worth very little. Keep these five items:
- The consent mode used at capture: optional box ticked, required box ticked, or no marketing consent.
- The exact text the person saw, or a hash of it, so a later rewording cannot be confused with what was agreed.
- The timestamp with the timezone.
- The page URL and the widget or form identifier.
- The source where it matters: quiz, chat, checkout, content lock.
Two of these are easy to lose. The text changes when marketing rewrites the checkbox, and the page URL disappears when a campaign is deleted. Store a copy with the lead rather than a pointer to the live widget.
The fixes that cost more than they save
- A pre-ticked box. Saves a click, invalidates the consent in most European readings. The form looks better and the list becomes unusable.
- "By submitting, you agree to receive marketing emails." The purpose is stated, but the choice is not separate: the person cannot get the thing they asked for without the marketing. Fine for a newsletter, weak for a guide.
- Bundling with the terms. "I accept the terms and the newsletter" merges two different decisions. Split it, even if the box count grows.
- A consent wall before the content. Blocking the page until the visitor accepts marketing is the fastest way to lose the visitor and collect nothing.
- A big banner on top of a small form. Two overlays compete for the same tap on mobile, and the visitor closes both. Our mobile interstitial penalty guide covers the layout side of this.
Double opt-in: when it is worth the friction
A confirmation email raises list quality and produces an extra proof of consent. It also removes everyone who does not click, which is often a large share. The pragmatic rule: use double opt-in when the list is the product (newsletters, high-value B2B) or when you collect addresses from sources you do not fully control. Skip it for a transactional follow-up where the person is waiting for your reply, because there the reply itself is the confirmation.
How this shows up in performance
Adding a separate box usually lowers the number of addresses per hundred sessions and raises the share of addresses you can actually mail. Track both:
- Captures per hundred sessions, before and after the change.
- Share of captures with marketing consent, which is the only part you can mail beyond the transactional reply.
- Complaint and unsubscribe rate in the first thirty days. It falls when the consent text matches what actually arrives.
If captures drop sharply and consented captures do not rise, the box is misplaced (too early, wrong wording) rather than unnecessary. Test the wording before removing the box.
Honest limits
No form setting makes a list compliant by itself. The purpose, the retention period, the unsubscribe path and the processor agreements all sit outside the widget, and a perfectly written checkbox next to a two-year silent list is not compliance. The practical goal is narrower and reachable: when someone asks why this person received this email, you can answer with a record that shows what they saw, when, and what they chose.
Add a consent box that survives an audit.
GrowthTools widgets carry an optional consent field with its own wording, so the address and the permission are collected in the same step.
Create your free accountQuestions
It depends on the lawful basis. If you rely on consent to send marketing, you need a clear affirmative action, which usually means an unticked box with a stated purpose. If the form only serves a transactional reply, consent for marketing is not involved, and adding a box without a purpose creates a misleading record. Decide the basis first, then design the field.
No. Cookie consent covers storage and reading of information on the device, such as analytics and advertising. Email consent covers the use of an address to send messages. A visitor can accept one and refuse the other, so each needs its own statement and its own record.
For as long as you rely on that consent, plus the period during which a claim could be made. In practice that means keeping the record while the contact is active and for the retention period stated in your privacy policy, then deleting it. A record you cannot produce is the same as no record.
No. A pre-ticked box is not an affirmative action in most European interpretations and produces consent you cannot defend. If the box costs too many signups, change what you offer or move the box later in the flow, but keep the choice explicit.
Capture with consent, not around it.
Create a free account, switch the consent field on for one widget, and compare consented captures over two weeks.
Create your free accountPublisher: GrowthTools by Seinsights. Product demonstrations are illustrative; results depend on your site and campaign.
Create your free account