Integration
Form Monitoring
A broken form looks exactly like a slow week. Quarkad separates the two — tracking form views against successful submits, and catching the change to the form that made the difference.
What Quarkad monitors
Quarkad records form views and successful submits as separate events, which is what makes a submit rate possible. Total leads falling can mean anything; form views holding while submits fall means the form is the problem.
Alongside those metrics, Quarkad detects changes to the form itself and timestamps them, so an incident shows the edit that came immediately before the drop instead of leaving you to guess.
What changes can cause incidents
- A required field added, so more visitors abandon before finishing
- A field removed or renamed, breaking validation or the downstream mapping
- The form replaced with a new embed the tracker no longer recognises
- A submit button moved, relabelled, or hidden behind an interaction
- A thank-you or success state that changes, so real submits stop being confirmed
- Spam protection or validation that starts rejecting legitimate visitors
Example incident
Illustrative scenario.
A phone number field is made required on Tuesday afternoon. Traffic is unchanged and form views hold, but the submit rate falls from 14% to 6%. Quarkad raises an incident within the hour, shows the field change as the ranked cause, and routes it to the account channel — instead of the drop being spotted at month end.
Setup
- Install the Quarkad snippet on the page that holds the form.
- Point Quarkad at the form with a CSS selector — the default covers a standard form element.
- Pick the success signal: a thank-you URL, or a success element on the page.
- Add the page to a funnel and enable monitoring so a submit-rate drop raises an incident.
Limitations
- Quarkad tracks forms on pages where the snippet is installed — it does not reach into your form builder’s own dashboard.
- A form inside a cross-domain iframe may not be visible to the tracker; in that case monitor the confirmation step instead.
- Submit-rate drops need enough volume to be meaningful — very low-traffic pages are noisy by nature.
- Ranked causes are likely explanations, not guarantees — always confirm before acting.
Frequently asked questions
- How does Quarkad track my forms?
- Through the same one-line snippet you install on the page. Quarkad records when the form is seen and when a submit succeeds, so it can measure the submit rate rather than just total leads.
- Which form builders are supported?
- Quarkad watches the form as it appears on the page, so it is not tied to a specific builder. You point it at the form with a CSS selector, which means native forms and most embedded ones both work.
- How does Quarkad know a submit actually succeeded?
- You choose the success signal: the visitor reaching a thank-you URL, or a success element appearing on the page. That way a submit that silently failed is not counted as a lead.
- What is the difference between this and CRM monitoring?
- Form monitoring covers the submit itself — did the visitor get through the form. CRM monitoring covers what happens next — did that lead actually arrive in HubSpot. A lead can pass the first and fail the second, which is why Quarkad watches both.
- Can I get alerted when the submit rate drops?
- Yes. Quarkad evaluates the drop against the funnel's recent baseline and raises an incident, then delivers it to email or a Slack channel.
Keep going
Know within the hour when the form stops converting.
Track form views against submits and let Quarkad tie the drop to the change that caused it.