Conversion events are tracked in analytics

Without conversion event tracking, you cannot distinguish a high-performing landing page variant from a broken one, measure funnel drop-off, or justify any product decision with data. If an analytics library is installed but .capture() or .track() calls are absent from form submit handlers, you have the instrumentation overhead with none of the insight. ISO 25010:2011 reliability requires that quality-relevant behaviors be observable — a conversion funnel that is invisible to your analytics stack cannot be measured, improved, or debugged. Teams flying blind here routinely ship changes that hurt conversion and have no way to detect it.

Add an explicit .track() call in the success branch of every conversion-critical form submit handler. Track the event name and enough properties to segment later:

async function handleSubmit(data: SignupData) {
  try {
    await createAccount(data)
    analytics.track('signup_completed', {
      method: 'email',
      plan: selectedPlan,
    })
    router.push('/onboarding')
  } catch (err) {
    analytics.track('signup_error', { error: err.message })
  }
}

Track failures too — signup_error events reveal validation problems and backend failures that would otherwise surface only as a silent dip in your conversion rate. For full funnel coverage (page views, feature events, attribution), see the Analytics & Tracking audit.