Forge Reference Material

Supporting guides and patterns for building analytics into Forge apps

This section contains focused reference material that supports the broader implementation guides.

While the “Complete Forge analytics guide” walks you through how to build the system end-to-end, the pages here serve as deeper reference for key components, design decisions, and usage patterns you’ll encounter while building and maintaining analytics in Forge.

Each page addresses a specific area of concern — from naming events, to handling anonymous users, to calculating daily snapshot metrics.

What You'll Find Here

• Architecture overview for Forge Apps
  A breakdown of the analytics system structure — from frontend calls through backend dispatchers to provider transport.

• Event definition and naming strategy
  Best practices for centralizing event names and properties to keep your analytics schema consistent, discoverable, and reusable.

• Implementing the Event Queue System
  How to reliably queue and process analytics events in Forge using asynchronous handlers and scheduled jobs.

• Snapshot metrics in Forge
  Why and how to calculate point-in-time metrics like object counts or tier usage, and send them as group() traits.

• Instance-Level Tracking in Forge
  How to reduce MTU costs and simplify GDPR compliance by tracking all events under a shared instance ID.

• Tracking Public Users or Unlicensed Access
  When users don’t authenticate — like in JSM portals — this guide shows how to track their usage without bloating your MTU bill.

Who This Is For

• Developers building and maintaining analytics in Forge apps
• Engineers who want reusable, privacy-safe tracking patterns
• Teams trying to keep event definitions consistent across projects