One script
One script. First lead visible in minutes.
The first lead shows in the inbox within minutes of the script going live.
Capture
What reaches the inbox
A submitted form becomes a lead. A partial is stored only when consent to save was recorded.
76
Emma Collins
Home insurance · Manchester
Keep every submission, and every consented partial, in one stream with its field trail.
| Event | Stored when | Left out |
|---|---|---|
| Submitted form | The visitor submits | Nothing from that submission |
| Partial | Consent to save was recorded | A partial with no consent |
| Field trail | The form records the field event | Fields the form never sent |
What capture stores
Capture stores each submitted form, with the field trail and the source, on the forms already on the site. One script or a tag-manager template is enough. The form is not rebuilt.
A submitted form becomes a lead. A partial is stored only when consent to save was recorded.
The stored record is the submitted form as the visitor sent it. The field trail is the sequence of field events that form already recorded. The source is kept on the lead, so a later visit does not replace where the submission started.
The script listens to the form already on the page. A tag-manager template does the same job when the page loads tags that way. Neither one replaces the fields, the layout, or the button the visitor uses to submit. The form stays the form the site already has.
One submitted form produces one lead in the workspace. That lead holds the values that arrived, the field trail, and the source. Capture does not merge two submissions into one lead, and it does not split one submission into two because the visitor opened a second campaign page after sending.
A partial is the record of a form left before submit. It is stored only when consent to save was recorded on that visit. Consent to save is a record the page already made. Capture does not treat a long pause, or a field that was focused, as consent.
What capture stores is the record that exists before the first reply. The first reply is one message, signed as the customer, sent from the customer's domain, and limited to approved knowledge. Capture does not draft that message, and it does not send it. The inbox receives the lead. Sending is a later step.
The field trail is stored when the form records the field event. A field the visitor never reached stays absent. A value the form never sent is not written onto the lead to make the record look complete. The source stays on that same lead.
Several campaign pages can load the same script and land in the same workspace. Each page keeps the form already on that page. The script does not rebuild a page so its fields match another campaign. What the inbox shows is the submission that page actually sent, with the field trail and the source beside it.
What is left out
A partial with no consent is not stored. Fields the form never sent are not invented.
The first submission is visible in the inbox within minutes of the script going live. That is a sample of install time, not a response-time claim.
Left out means the unfinished visit with no consent to save. Capture does not keep a hidden copy of that visit, and it does not create a lead from fields that were typed and then abandoned when consent was never recorded. Nothing from that visit reaches the inbox.
A field the form never sent is left out in the same way. If the page did not ask for a start date, the lead does not gain one. If a field was on the page and the visitor left it blank, the blank stays blank. Capture does not borrow a value from another lead to fill the gap.
The minutes after the script goes live measure install. They measure how soon the first submission can be seen in the inbox once the script is on the site. They do not measure how soon a person hears back. Capture does not send the reply, so that interval is not a reply time.
A sample of install time is one observation after the script is added. It is not a promise that every later submission appears in the same number of minutes, and it is not a promise about the first reply. The reply waits for a separate step, on the customer's domain, limited to approved knowledge.
What is also left out is any message. Storing the submitted form does not send a confirmation. Storing a consented partial does not send a recovery message. The lead can sit in the inbox with its field trail and its source while no message has gone out.
A partial that is stored still waits. Consent to save records that the partial may be kept. It does not by itself send anything. The continuation of that partial is a later record. Until then, the stored partial is the fields that were entered, and only those fields.
The boundary is the same on the table above. A submitted form is stored when the visitor submits. A partial is stored when consent to save was recorded. A field trail is stored when the form records the field event. A partial with no consent, and fields the form never sent, stay out.
Where an example of the reply lives
The form already exists. An example of the wording, which you can read without sending anything, is on LeadForms.
Sending that wording from your domain is the lead follow-up. Capture does not send it.
The example is wording you can read. Opening it does not submit the form on your site, and it does not send a message from your domain. The form the visitor uses is still the form already on the page. Capture stores that form. The example shows a shape of words. It is not the send.
The first reply, when it is sent, is one message from the customer's domain, limited to approved knowledge, and signed as the customer. That message confirms what the stored form already holds. It does not add a fact the form never sent. Capture's record is the input. The reply is not part of the stored form.
Approved knowledge is the set of facts the customer has accepted for replies. Capture does not read a sentence from that set and attach it to the lead as if the visitor had typed it. The lead stays the submitted form, the field trail, and the source. Knowledge limits the later message. It does not fill empty fields.
A new form starts in approval before a reply can leave. That approval is a state of the reply. It is not a state of the lead capture stored. The lead can be in the inbox, with its source, while the reply is still unsent. Capture does not move the reply from approval to sent.
You can read the example before any script is installed. The example does not require a submission from your site. When a real submission arrives, the stored record is that submission, not a copy of the example. The example remains a page you can open. The lead remains the form the visitor sent.
Because capture does not send, a person can hold the reply. The wording on the example is not dispatched when the form is stored. The domain is not asked to send at the moment the lead appears. The inbox shows the record. The message waits.
The form already on the site is also why the example stays separate. Capture does not replace that form with the example, and it does not ask the visitor to complete a second form so the wording can be sent. One script, or a tag-manager template, records the form that is already there.
Which record uses it
The sample on this page is an insurance quote: cover in Manchester, source kept on the lead, score 76.
A consented partial continues under one recovery message. Several campaign pages can load the same script and land in the same workspace.
The sample lead is Emma Collins, a home-insurance submission, cover in Manchester, source Google Ads, score 76. The score is the sample on that record. It is not a promise that every insurance submission scores 76, and it is not a reason to send a reply. Capture stores the submission. The score sits on the lead. The reply is still unsent by this step.
Cover in Manchester is the fact the form recorded. The source stays on the lead as Google Ads for this sample, rather than only as a click that disappears after the visit. The field trail is the field events that form recorded. Fields the sample form never sent are not added to make the quote look longer.
An insurance quote, on this page, is the record capture stores: the submitted form, the cover requested, the field trail, and the source. The reply that later confirms that cover is a different step. Capture does not confirm a premium, and it does not invent cover the form did not name. The sample stops at the stored quote.
A consented partial on the same form is stored only with consent to save. That partial continues as one recovery message, not as a series of reminders from capture. Capture does not send the recovery message. It keeps the partial so that one message has a record to use, and only when consent to save was recorded.
A partial with no consent does not become a second sample. It is not stored, so it cannot continue into a recovery message. The sample on this page is a submission: Emma Collins, cover in Manchester, source kept on the lead, score 76. An unfinished visit without consent is absent from the inbox.
Several campaign pages can load the same script. A home quote on one page and another campaign page that uses the same script both land in the same workspace. Each page keeps its own form. The workspace receives the submission each form actually sent, with that page's field trail and source. The script is not a second form.
Score 76 belongs to this sample and stays on the lead with the source. It does not send the first reply. The first reply, from the customer's domain and limited to approved knowledge, reads the stored form later. Until that message is sent, the record this page describes is the submitted quote and any consented partial beside it.
Related
How it runs
Questions
Before you install.
No. The script listens to the form already on the site.