You can now import data into Accoil—whether you're backfilling old records or making the leap from June. It’s reliable, monitored, and comes with all the bells and retries.

Find it under Settings > Import Data.

📚 Planning a big move? Check out the Data Import Docs and the June Migration Guide .

🔁 Having trouble with it before? Let us know.

We’ve published a full set of migration resources to help teams moving off June.so transition smoothly into Accoil.

You can now:

• ✅ Send new June event data into Accoil
• ✅ Import up to 90 days of historical June data (CSV export via .zst format)
• ✅ Compare June vs. Accoil API formats
• ✅ Switch your browser tracking from June to Accoil

Start here: 👉 How to Migrate from June.so

This is part of our long-term commitment to support June customers following their transition to Amplitude.

Have questions or need help with data exports? Contact us — we’re happy to help.

We have updated the analytics system in our example github app to use the Forge Events 2.0 architecture with direct function handlers. We also simplified and clarified comments in the code base, and improved the README documentation with additional links and explanations.

We’ve added a collection of supporting guides to help you build and maintain analytics in Atlassian Forge apps — beyond the basics.

These reference pages go deeper on specific patterns, design decisions, and common implementation questions. Think of it as a companion to the Complete Forge Analytics Guide, focused on practical answers to real-world tracking challenges.

What’s covered:

• 🔀 Queue system design for reliable tracking
• 🏗️ Naming strategy for consistent event definitions
• 🧮 Calculating snapshot metrics like tier usage or object counts
• 👥 Tracking anonymous and public users (e.g. in JSM portals)
• 🧩 Instance-level tracking to simplify privacy + reduce MTU usage

If you're building analytics into Forge apps, this is the reference material you'll come back to.

👉 Browse the Forge Analytics Reference

We’ve published a full implementation guide for adding analytics to Atlassian Forge apps — with a backend-first, privacy-aware approach and a queue-based delivery system.

This guide walks through how to:

• Set up a queue + consumer pattern for reliable event delivery
• Ensure privacy compliance (no frontend data egress, no PII)
• How to maintain Runs on Atlassian status
• Integrate analytics through backend resolvers only
• Use environment flags for debug mode and MTU reduction

It’s designed for production use, and includes a working example app with:

• Dispatcher, queue, and event handler structure
• Step-by-step manifest.yml and env variable setup
• Code samples for identify, group, and track calls

👉 Read the full guide
👉 View the working example on GitHub

We’ve released a modified version of Atlassian’s Forge Todo App — now with built-in privacy-first analytics using Accoil.

This example shows how to implement analytics in a Forge app while meeting Atlassian’s privacy guidelines. All events are processed through the backend, so no personal data or frontend identifiers are exposed.

What’s inside:

• 🔐 Privacy-aware design: No PII, no frontend egress
• 📊 Event coverage: Tracks CRUD actions, UI events, and daily usage
• 🧱 Modular setup: Backend event queue, clear separation of concerns
• 🧪 MTU tips: Optional ID consolidation to reduce tracked users

If you're building in Forge and want to see how analytics can be done simply — and safely — this is a good place to start.

👉 Check out the repo

Welcome to the Accoil developer site.

We’ve just released our JavaScript tracking library and API documentation, so you can start capturing product engagement data in just a few lines of code.

Here’s what you can do right now:
• Use .identify to tie actions to specific users. • Use .group to organize users into accounts and track account-level traits. • Use .track to log meaningful user actions in your app.

👉 Start here: developer.accoil.com

Need an API key? You’ll find it under Account > General in your Accoil dashboard.

Let’s get you up and running. Your data’s about to get a lot more helpful.