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.

• ID: marketing-conversion.conversion-infrastructure.conversion-analytics-events

• Severity: critical

• What to look for: Search the codebase for analytics event calls on conversion actions. Look for: (1) Analytics library calls in form submit handlers — analytics.track(), gtag('event', ...), posthog.capture(), mixpanel.track(), amplitude.track(); (2) Events specifically on conversion-critical actions: form submission success, CTA button clicks, signup completion, checkout completion, trial activation; (3) Check for analytics libraries in package.json (posthog-js, mixpanel-browser, @amplitude/analytics-browser, @segment/analytics-next, react-ga4). Analytics may also be loaded via a script tag in the root layout — check for Google Tag Manager or similar loader patterns.

• Pass criteria: Count all analytics event tracking calls in the codebase and classify each (page view, conversion, custom). At least 1 conversion event (form submission, signup, trial start, or purchase) is explicitly tracked — not just page views. Report: "X conversion events tracked, Y page view events."

• Fail criteria: No analytics event tracking calls found for conversion actions. Only page view tracking exists (if any). OR analytics library is present in package.json but no event calls are found in form submit handlers.

• Skip (N/A) when: No conversion forms or CTAs found in the codebase. This is a theoretical skip — if there is a public marketing page with any conversion goal, this check applies.

• Detail on fail: Describe what was found. Example: "PostHog library installed but only posthog.init() found — no .capture() calls in any form submit handler or CTA click handler." or "No analytics library found in package.json and no gtag/analytics calls in any component.".

• Remediation: Without conversion event tracking, you cannot measure what is working or run meaningful A/B tests. Add event tracking to your form submit handlers:

  // In your signup form submit handler
  async function handleSubmit(data: SignupData) {
    try {
      await createAccount(data)
      // Track the conversion
      analytics.track('signup_completed', {
        method: 'email',
        plan: selectedPlan,
      })
      router.push('/onboarding')
    } catch (err) {
      analytics.track('signup_error', { error: err.message })
    }
  }
  

  For a deeper analysis of the analytics tracking setup, the Analytics & Tracking audit covers the full telemetry pipeline — events, funnels, and attribution.