Skip to main content
Both tabs require a paid plan — the Free plan gets a 402 on either. Blocked/spam submission data (the Submissions screen’s own filtering) is unaffected and free on every plan; only visitor-engagement tracking is gated.
Two distinct tabs, both about visitor behavior rather than submitted data itself:

Analytics

Aggregate numbers over time — views, starts, submissions, completion rate.

Activity

A per-event log — every individual view/start, with country, device, and browser.

​
Analytics

Pick a window — 7, 30, or 90 days, or all-time — and see:
​
number
How many times the form was loaded.
​
number
How many visitors interacted with at least one field.
​
number
How many actually completed it.
​
number
totalSubmissions / totalStarts, as a percentage — the gap between “started filling it out” and “actually submitted.” A low number here usually means the form is too long, a field is confusing, or validation is rejecting people silently.
​
array
One entry per day in the window — { date, views, starts, submissions } — for charting the trend rather than just the totals.
Tracked automatically by the SDK/submit.js (view on load, start on first field interaction, submit on success) — see Track an Event if you’re driving this from a headless integration and need to fire these yourself.
200 — a 30-day window
On the Free plan, both tabs return this instead:
402 Payment Required

​
Activity

The raw event log behind the Analytics numbers above — every individual view/start event, with:
  • When it happened
  • Country — derived from IP, never the raw address
  • Device type & browser — derived server-side from the User-Agent, never trusted from the client
  • A session identifier, so you can see which events belong to the same visit
Search and filter by event type, or by time range. Useful for spotting where drop-off happens (a burst of start events with no matching submit) rather than just knowing the aggregate rate is low.
Analytics is opt-out per integration, not per form — a specific integration can skip tracking with data-analytics="false" (Basic HTML) or analytics: false (SDK config), e.g. for a compliance reason that applies to one embed but not others.