Lead pages and tracked links
A lead page is where the thing you promised in the message actually gets delivered — and where a LinkedIn comment turns into an email address you own.
Creating a page
A page has a title, a short body, one thing to deliver and a gate. It is published at p/ and a slug you choose, on our domain, and it is live as soon as you publish it.
Pages are fast and plain by design. The audience arrives from a LinkedIn message on a phone, and the only job of the page is to trade one email address for one file.
The gate
The gate is what the page asks for before it delivers.
| Gate | Asks for | Creates a lead? |
|---|---|---|
email |
Email address only. The shortest form converts best. | Yes |
email_name |
Email address and one name field. The name is split into a first name for your templates. | Yes |
none |
Nothing. This is a plain content page — it creates no lead, no submission and no CRM contact. | No |
Consent
An email address given to reach a file is not permission to market to that person. The page therefore carries a separate marketing consent checkbox, it is never pre-ticked, and the answer is stored with the submission along with the time and a hashed IP address.
We hash the IP with a secret rather than storing it, so the stored value is not reversible into an address. It is enough to demonstrate that a specific consent was given at a specific moment, which is what a supervisory authority asks for, and not enough to be a record of who visited.
Whether someone consented is on the lead, and it travels with them into your CRM. A lead who declined is still a lead — you have their address because they asked for a file — but they have not agreed to a newsletter, and nothing in LeadAdapter pretends otherwise.
Delivery
After the form, the visitor gets what you attached: a file we host, a link to somewhere else, or a straight redirect.
Hosted files are served through a signed link valid for 60 minutes. It is long enough to survive a slow phone and a distracted person, and short enough that the link pasted into a group chat two days later has expired.
Tracked links
A tracked link is a short redirect on our domain, at l/ and a slug, pointing anywhere you like. Use one in a message template and you can see which automation, which post and which person produced the click.
When the person clicking is someone we already know — because they commented on your post and got the link in a message — the click is attached to their lead record rather than to an anonymous counter. That is the whole point of using one instead of a bare URL.
What the analytics count
Views, submissions, the conversion rate between them, and where the traffic came from, including UTM parameters carried through from the link that sent them.
There is no third-party analytics script on a lead page, and no cookie beyond the one that carries the session. The page loads as one document. That is also why a lead page cannot tell you anything about a visitor who did not submit the form beyond that a view happened.
Retention and erasure
Leads are kept for 24 months by default and the audit log for 24 months. Both are configurable per workspace.
You can export everything a workspace holds, and you can delete an account. Deletion cascades to leads and submissions and anonymises the audit log — the fact that an action happened survives, the person it concerned does not.
Every cap, limit, timeout and tool name on this page is read from the running product when the page loads. If the software changes, this page changes with it.