What is event tracking?

Which events should you track?

The discipline is restraint. Every event added is one more thing to maintain, and an unused event is pure cost.

Start from questions rather than from capability. "Do people who read a case study convert better" implies a case-study-read event. "We could track hovers" implies nothing.

A workable baseline for B2B SaaS:

• Form start and form submit, separately, since the gap between them is form abandonment
• Primary CTA clicks, distinguished by location on the page
• Pricing page view
• Outbound clicks to docs, app stores, or booking tools
• File downloads
• Scroll to a decisive element, using element visibility rather than a page percentage

What to skip: every click on every element, hovers, and anything you cannot name a decision for.

How should events be named?

Inconsistent naming is the most common way an analytics implementation becomes unusable, and it is unfixable retroactively without reprocessing.

Rules that hold up:

Pick a convention and write it down.object_action in lower snake case is a good default: form_submit, cta_click, pricing_view.

Use parameters for variation, not new event names. One cta_click event with a location parameter beats cta_click_hero, cta_click_footer, and cta_click_pricing. Separate names fragment reporting and consume the property's cap on distinct event names.

Keep names stable. Renaming an event splits its history in two.

Never put personal data in event names or parameters. An email address in an event parameter is a data protection problem, Google's terms prohibit sending it, and there is no retroactive cleanup once it is collected. Form tracking is where it reaches production by accident.

How do you set up event tracking on Webflow?

Three routes.

GA4 enhanced measurement. On by default for a web data stream. With no code it collects outbound clicks, file downloads, site search, video engagement on embedded YouTube players, and a single scroll event at 90% depth. Form interactions (form_start, form_submit) are a separate toggle in the same panel. Two limits shape what is left to build: the scroll event fires only at 90%, so any other threshold needs a custom event, and form_submit fires on the submission attempt rather than on a confirmed success, which is precisely the distinction a Webflow form requires.

Google Tag Manager. Add the GTM snippet in Site Settings, Custom Code, then configure triggers against CSS selectors or Webflow element IDs. The standard approach when events go past the automatic ones.

Custom code. A script in Site Settings, Custom Code, Footer Code, attaching listeners and calling the analytics API directly. Most control, most maintenance.

Webflow specifics:

• Give elements stable IDs in the Designer. Triggers bound to auto-generated class names break when styling changes.
• Form success fires no page load. Bind the success event to the success element becoming visible, or redirect to a confirmation page and count the pageview.
• Custom code does not run in the Designer canvas or preview. Publish before testing.
• Collection lists render repeated markup, so a selector matching one card matches all of them. Use event delegation and read the item identity from a data attribute.

Related terms

Micro conversion · Goal completion · Scroll depth · Conversion funnel · Form analytics

Service: Conversion Rate Optimization.

FAQ

What is the difference between an event and a conversion in GA4?

An event is any recorded action. A conversion is an event you have flagged as representing business value, renamed a key event in GA4 in 2024 while Google Ads kept the word conversion. All conversions are events, most events are not conversions.

How many events should a site track?

Enough to answer the questions you actually ask, which for a B2B SaaS site tends to land between ten and twenty. If you cannot name the decision an event would inform, it is maintenance cost with no return.

Do you need Google Tag Manager for event tracking on Webflow?

No, though it helps. GA4 enhanced measurement covers common events automatically, and custom code can handle the rest. GTM earns its place when non-developers need to add or change tracking without a site publish.