Platform / Collect / Website form
Your own form, tied to the ad.
A small script remembers which ad brought the visitor; your server tells us about the application after it's saved — signed, so nobody else can post in your name.
| Lead | Ad | Check | Received |
|---|---|---|---|
| Jane Miller | Traffic › Spring LP | verified | 18m ago |
| Omar Haddad | Traffic › Pricing LP | verified | 2h ago |
| Nina Castillo | Traffic › Spring LP | verified | 5h ago |
How it works
Step by step.
What you actually get
Website form, in detail.
Consent first
The script runs after your visitor agrees, if you use a consent manager. No consent, nothing read.
Signed notifications
Every request carries a signature made with your secret. Unsigned or altered requests are refused.
Nothing read while typing
We never capture form fields as people type — only what your server sends after saving.
Which ad, first and last
The visit's ad parameters travel with the lead: first and last touch are chosen when reading, not stored.
One secret per source
Create a source, copy its secret once. Lost it? Close it and open a new one.
Works with any stack
WordPress, Webflow, your own app — anything that can make one server call.
Works with
Connect what you already use.
Meta, your website and a CSV from any CRM today. Direct CRM and payment connections are next.
Do I need a developer?
For one short server call after the form is saved. We set it up with you on the call.
Does the script slow my site?
It's a small script loaded with defer, so it doesn't hold up your page.
What do you store about visitors?
An anonymous visit key, the ad parameters, and — only with consent — the click ID and browser details Meta needs. No fingerprinting.
Your own form, tied to the ad
on your own data.
Book a 30-minute call — we set it up with you live.
Book demo