ekx Docs
Open appSign in

Amplitude Tracking Plan

Amplitude answers product-behavior questions. Sentry remains the source for errors, stack traces, and production support reports.

Primary Question

Most new users appear to create one project, make at most one meaningful canvas update, run one or two studies, and stop. This tracking plan measures where that first-project journey breaks down and whether users come back after signup.

Privacy Rules

  • Do not send project names, component names, electrical values, uploaded file

contents, AI prompt text, calculation payloads, or report contents.

  • Project and study identifiers are allowed for joining funnel events.
  • Onboarding enum answers are allowed.
  • Session Replay uses conservative masking by default. Use

data-amplitude-block or data-sensitive-project on any UI area that should be visually blocked in replay.

Environment

  • NEXT_PUBLIC_AMPLITUDE_ENABLED: enables browser analytics when not "false".
  • NEXT_PUBLIC_AMPLITUDE_API_KEY: browser Amplitude project API key.
  • NEXT_PUBLIC_AMPLITUDE_SERVER_ZONE: US or EU; default is US.
  • NEXT_PUBLIC_AMPLITUDE_SESSION_REPLAY_SAMPLE_RATE: replay sample rate from

0 to 1; default in code is 1 for early diagnostic use.

  • AMPLITUDE_ENABLED: enables server analytics when not "false".
  • AMPLITUDE_API_KEY: server Amplitude project API key.
  • AMPLITUDE_SERVER_ZONE: US or EU; default is US.

Identity

User properties:

  • email
  • name
  • organization_id
  • organization_type
  • organization_role
  • plan_type
  • subscription_status
  • onboarding_completed
  • has_seen_welcome_project
  • signup_date

Group:

  • organization_id

Events

EventSourcePurpose
App OpenedBrowser sessionCounts authenticated sessions.
Activity Day RecordedBrowser once per local dayRetention by days_since_signup.
Onboarding Dialog ShownBrowserMeasures onboarding exposure.
Onboarding Step CompletedBrowserFinds onboarding question drop-off.
Onboarding CompletedServerDurable onboarding completion.
Onboarding SkippedServerDurable onboarding escape hatch.
Welcome Project CreatedServerFirst project created by onboarding flow.
Project OpenedBrowserUser reached the editor.
Project CreatedServerUser manually created a project.
Canvas State SavedServerUser changed saved canvas state.
Study Run CreatedServerUser initiated a study.
Study Run CompletedServerStudy reached a successful result.
Study Run FailedServerStudy failed or hit a blocker.
Component AddedServer project activityUser added SLD content.
Component EditedServer project activityUser edited SLD content.
Component DeletedServer project activityUser removed SLD content.
Connection AddedServer project activityUser connected SLD content.
Connection EditedServer project activityUser changed a connection.
Connection DeletedServer project activityUser removed a connection.
Project Activity RecordedServer project activityFallback for other activity types.

Core Funnels

New-user activation:

  1. Activity Day Recorded where days_since_signup = 0
  2. Onboarding Completed or Onboarding Skipped
  3. Welcome Project Created
  4. Project Opened
  5. Component Added or Canvas State Saved
  6. Study Run Completed
  7. Activity Day Recorded where days_since_signup >= 1

Manual project adoption:

  1. Welcome Project Created
  2. Project Opened
  3. Project Created
  4. Project Opened with the manually created project_id
  5. Study Run Completed

Study dead-end:

  1. Study Run Created
  2. Study Run Failed
  3. No Study Run Completed
  4. No Activity Day Recorded on later days

Dashboard Cuts

  • Split activation funnels by role, company_type, sld_experience, and

design_focus.

  • Cohort users with days_since_signup = 0 and no later Activity Day Recorded.
  • Cohort users with exactly one Project Created, one Canvas State Saved, and

one or two Study Run Completed events.

  • Segment first-project study results by study_type and has_error_message.

On this page

Primary QuestionPrivacy RulesEnvironmentIdentityEventsCore FunnelsDashboard Cuts