Skip to main content
tinyanalytics records the interactions that matter on your site automatically, with no code to write. Outbound link clicks, file downloads, button clicks, text copies, form submissions, and engagement are all captured out of the box and appear in your Events explorer. You can measure how visitors interact with a page before you instrument a single custom event. Autocapture is on by default. Each type is an independent toggle you can turn off in your tracking script.

What does tinyanalytics capture automatically?

Each interaction is its own event type, so you can filter to it in the Events explorer’s event-type view and build goals or funnels from it.

Which autocaptured events can I build goals and funnels on?

Four autocapture types can be a goal or a funnel step directly — no custom event required:
  • Outbound link — matched against the destination URL
  • Button click — matched against the button text
  • Form submission — matched against the form’s name, id, or action
  • Copy — matched against the copied text
Add an optional value pattern to target a specific interaction — for example, a goal on outbound links to *.stripe.com, or a funnel step for the button that reads Start free trial. Patterns use * and ** as wildcards; leave the pattern blank (or enter * for a funnel step) to match any event of that type.
Individual input_change events are captured for the Events explorer but can’t be a goal or funnel target — they’re too high-volume to build a conversion on.

How do I browse what’s been captured?

Open the Autocapture dialog on the Events explorer to see every distinct value an autocapture type has recorded over your current date range. Pick a type — outbound links, button clicks, form submissions, or copies — and the table lists each value with its count, its share of that type, and when it was last seen. It’s the quickest way to find the exact button text or outbound URL to target before you build a goal or funnel on it.

What do form captures never record?

Form capture records the shape of a submission, never its contents:
  • A form submission stores the field count, form name, and action — never what a visitor typed.
  • An individual field change stores only the field’s name and type, never its value.
  • Password, hidden, disabled, and read-only fields are skipped entirely.
Copy events do store the copied text (truncated). If visitors might copy sensitive content on a page, turn copy capture off with data-track-copy="false".

Add properties to a captured event

Attach custom properties to any auto-captured event by adding data-ta-prop-<name> attributes to the element. For example, to tag which plan an upgrade button belongs to:
The button click is then captured with plan: "pro" in its properties, so you can break that event down by plan.

Track an element yourself

To handle a specific element with your own custom event instead of the automatic capture, add data-ta-event to opt it out:
tinyanalytics skips the automatic button-click event for that element, leaving you to send exactly the event you want.

Turn autocapture off

Every capture type is on by default and can be turned off independently by setting its attribute to "false":
See configure the tracking script for the full list of attributes.

Frequently asked questions

No. tinyanalytics autocapture is on by default and records button clicks, outbound link clicks, file downloads, text copies, form submissions, and engagement with no code to write. Write a custom event only for actions autocapture can’t infer.
No. A tinyanalytics form submission stores the field count, form name, and action — never what a visitor typed. An individual field change stores only the field’s name and type, and password, hidden, disabled, and read-only fields are skipped entirely.
Add data-ta-prop-<name> attributes to the element. For example, <button data-ta-prop-plan="pro"> captures the button click with plan: "pro" in its properties, so you can break that event down by plan in the Events explorer.
Add data-ta-event to that element. tinyanalytics then skips the automatic capture for it, so you can send your own custom event instead. To turn a capture type off site-wide, set its toggle attribute to "false" on the tracking script.

Track custom events

Send your own named events with properties.

Configure the tracking script

Every auto-capture toggle and data-* attribute.

Events explorer

See every captured event and its properties.

Goals

Turn a captured interaction into a conversion.