Form views

Is the QR code on the counter getting used? Did adding the form to the website make a difference? Form views answers that.

You'll find it in the editor's Getting in step: the web form card shows the totals, and Set up the form → has the breakdown. For the Last 30 days, it shows views and requests sent from:

• The link you shared by email or text,
• QR codes,
• Website embeds, and
• the Chat bubble on your website (once someone has used it; see Chat bubble for your website).

Views by your own team aren't counted, so testing the form doesn't skew the numbers.

Reading it: lots of views but few requests usually means the form is too long. Try hiding or pre-filling fields: see Form fields.

Where each request came from

Every web form request also remembers where it came from, so you can tell which ad, email or page brings in work:

• The page. For a form on your website, the page it's embedded on (the embed code includes a one-line script that tells the form). For a link, the website that linked to it.
• UTM tags. If the page or your form link has tags like ?utm_source=newsletter&utm_campaign=spring, they're kept too.

Your team sees it on the ticket under Created by as Came from. Requesters don't see it. To add it up, use ↓ Export and tick Came from page and the UTM columns. Tagging your own links is easy: add ?utm_source=flyer to the form link you print on a flyer, and ?utm_source=facebook to the one you post.

If you embedded the form before November 2026, copy the embed code again to get the page as well as the tags.