Part of Forge DevKit ecosystem
◇ forge-analytics
Plan measurement before you code
The problem
Tracking added as an afterthought
Feature ships Monday. Someone asks 'how do we measure success?' on Friday. Retroactive tracking misses key events.
Vanity metrics everywhere
Dashboards full of page views and signups. Nobody tracks the events that actually drive business decisions.
Inconsistent event naming
user_clicked_button, buttonClick, click-cta - same event, three names. Analytics becomes unreliable.
How it works
Install
One command adds forge-analytics to your environment.
Configure
3-gate wizard reads product context and establishes measurement principles.
Plan
Generate tracking plans, event schemas, and dashboard specs - all mapped to business decisions.
Implement
Developers get concrete event names, properties, and trigger conditions. No guessing.
Key capabilities
◇3 operational modes
Plan, schema, dashboard. Each produces artifacts developers can implement directly.
◇Decision-mapped events
Every tracked event maps to a business decision. No vanity metrics make it to the spec.
◇Enforced event taxonomy
Consistent event taxonomy generated from product context. One naming scheme for the entire project.
◇Dashboard specs
Layout, dimensions, filters - specified before implementation. Developers build the dashboard once instead of iterating through 5 versions of 'can you add a filter?'
Sample output
A real-world example of what this module produces.
◆ Event Schema - taskflow-app
event: checkout_completed
trigger: User completes payment on /checkout
decision: Measures conversion rate for pricing page changes
properties:
plan_tier: string # starter | pro | team
payment_method: string # card | paypal
trial_converted: boolean # was user on free trial?
cart_value: number # in cents, USD
Dashboard: Revenue Overview | Source: Stripe webhook + clientWho is this for
Product Manager
Define what to measure before features ship - no more retroactive tracking scrambles.
Data-Informed Developer
Get concrete event names, properties, and triggers instead of guessing what to track.
Growth Lead
Ensure every tracked event maps to a business decision - zero vanity metrics.
forge-analytics vs Ad-hoc analytics tracking
| Dimension | Ad-hoc analytics tracking | Forge DevKit |
|---|---|---|
| Timing | After launch, retroactive | Before coding, measurement-first |
| Event quality | Whatever developer thinks to track | Decision-mapped events from product context |
| Consistency | Ad-hoc naming across features | Generated taxonomy with enforced conventions |