Documentation
On this page

Track forms and visible sections

Use form goals to count validated browser submissions, or visibility goals to learn whether a section was seen. These are different from a completed server action.

Install the helper

Keep your existing core tracker. Add this second tag immediately after it, using the same script host as your installation:

<script defer src="YOUR_SCRIPT_HOST/jelto.goals.js"></script>

YOUR_SCRIPT_HOST is a placeholder for the origin serving your Jelto scripts. Both tags must execute in order; keep defer and do not add async.

Track a form submission

  1. Register contact_submitted and its optional form property in Events settings.
  2. Add attributes to the form itself:
<form action="/contact" method="post"
      data-jelto-event="contact_submitted"
      data-jelto-event-form="contact">
  <!-- Your existing fields and submit button -->
</form>
  1. Publish, complete the required fields and submit. An invalid form should not produce this event.

The event means browser validation passed and a submit event occurred. It does not mean your server accepted the message. The helper reads declared attributes, not field contents or FormData. If your app handles submission with JavaScript, put a manual event in the confirmed-success handler instead.

Track a visible section

Register pricing_seen, then add:

<section data-jelto-visible="pricing_seen"
         data-jelto-visible-threshold="0.5"
         data-jelto-visible-delay="1000">
  <!-- Your pricing content -->
</section>

Here, at least half the element must stay visible for one second. The default threshold is 0.5; the default delay is 0 milliseconds, with a maximum of 60000. It fires once per element per accepted pageview while the document is visible.

A visibility event is passive: it does not turn a bounce into an engaged visit. Avoid placing it on an element taller than the viewport when the chosen visible fraction cannot be reached.

Verify

Visit the page, scroll the section into view and keep it there for the delay. Find the event in Goals. If nothing arrives, verify the core tracker first, then helper order, event registration, element height and page exclusions.