Skip to content

GA4: Expand product telemetry and add internal traffic filtering #42

@sbaker

Description

@sbaker

Summary

Expand GA4 analytics to capture comprehensive product telemetry (no PII) and add internal traffic filtering so developer usage doesn't skew reports.

Internal Traffic Filtering (done)

  • Added ~/.prompd/.internal marker file check at analytics init
  • Tags events with traffic_type: internal user property when marker exists
  • GA4 Data Filter needed: exclude where traffic_type = internal

Telemetry Expansion (TODO)

Currently tracked (6 events)

  • app_open, app_close, prompt_execute (provider only), workflow_execute (no params), deployment_create, package_install

Functions exist but never called

  • prompt_compile, file_open, feature_use

Missing events to add

  • Model/provider tracking: model name, provider on every execute event
  • Compilation: success/fail, stage that failed, error code, duration
  • Workflow: node types used, node count, execution duration, success/fail
  • Editor: file type opened (.prmd, .pdflow, .pdpkg), tab count
  • Registry: search queries (not content), package views, install source
  • Chat mode: mode used (agent, brainstorm, edit, plan), turns per session
  • MCP: tool invocations, server count
  • Errors: error codes (no stack traces or file paths)
  • Session: duration, features touched per session
  • Deployment: trigger type, schedule frequency, success/fail

Privacy constraints

  • No PII, no file names, no prompt content, no file paths
  • Opt-in only (existing consent flow)
  • Anonymous UUID client ID (existing)
  • No privacy policy change needed for product telemetry

🤖 Generated with Claude Code

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions