Disclaimer - Community Collaboration Statement
A note outlining the intended use of our Forge analytics documentation as reference material, with an open invitation for community feedback.
Reference-Only Documentation
The content in this Atlassian Forge Analytics section is provided for informational and educational purposes only. It is designed to serve as reference material, showcasing patterns, strategies, and implementation concepts that have worked well in our own experience building analytics into Forge apps.
While we strive to make the guidance here practical and widely applicable, we do not guarantee that these approaches will be universally suitable for every app or vendor in the Atlassian Forge ecosystem. Variations in architecture, feature sets, compliance requirements, and performance needs may affect how well these recommendations apply to your specific use case.
Why We’re Sharing This
Our goal is to provide a strong foundation for teams who want to:
- Understand best practices for event definition and naming.
- Implement reusable analytics patterns that respect privacy and scale with product usage.
- Reduce data overhead while tracking meaningful user and instance behavior in Forge.
Community Input Welcome
We recognise that each Forge app team faces unique challenges. That’s why we actively welcome feedback and conversation with other vendors and developers. If you’ve found gaps in the documentation, uncovered alternative approaches, or want to better align our guides with community needs — we’d love to hear from you.
Together, we can make analytics implementation in Forge stronger, safer, and more useful for everyone in the Atlassian ecosystem.
👉 Interested in sharing feedback or proposing improvements? Reach out to us — we’d be happy to collaborate.
Updated 1 day ago