Day 1 with June
For a great configuration of your account, follow this guide on day 1 in June
Once you have connected a data source, here are a few steps to get the most of June
- Track basic actions in your product
- Follow key actions in Slack
- Define your “active” users
- Define the ideal frequency of usage of your product
- Pick the right zoom-level
- Remove your employees
- Track your progress
1. Track basic actions in your product
To get the most out of June we recommend tracking some basic user behaviours inside your product.
🎯 Actions to track
Sign up event
An event when a user signed_up
Core events for your product
Add an event when users open your app, like "application_opened". Or only count users active if they perform the main workflow in your product. An example for Slack could be tracking "sent_a_message"
Events when a feature is used
When launching new features you can add an event when users use them.
Event for milestones to celebrate
Add an event when people upgrade to a paid plan, or when they reach certain milestones in your product.
An event for each step of a workflow
If you have complex workflows, like an onboarding or a complex form add an event as each step gets completed
Illustrations: We’ve listed some metrics with examples of track events that match them on the Analytics Pack. If you need further help to set up the right track events for your product you can book a call with us here.
2. Follow a key action in Slack
Event notification in Slack is a simple yet powerful way to celebrate events in real-time as they occur in your product.
Based on your priorities, notification can be triggered on the following events:
- 🆕 Sign up happened = if acquisition is the priority
- 💰 Purchased a paid plan = if revenue is the priority
- 📩 Invite a colleague = if referral is the priority
3. Define your “active” users
Defining what “active” means is absolutely critical for any business yet often misunderstood. A great definition of an active user is when a user gets the unique value of your product.
For early-stage, 3-5 actions are usually enough.
Log in events: Log in events are risky because they don't directly map to your actual product value, avoid using them if you can.
4. Define the ideal frequency of usage of your product
The second question is whether you should look at your Daily, Weekly or Monthly active users.
To answer this question you need to figure out what makes the most sense for your business.
A rooky mistake: When we started YC we wanted June to be used daily. This is fairly uncommon for analytics tools. We did not understand the natural behavior that people had with our category of product. It made us lose a few weeks.
5. Pick the right zoom level
Some products have multiple users per account. If this is the case then it traditionally makes more sense to check product activity at an account level (we call them “Companies” in June):
Account-level metrics: to adopt account-level metrics in your product you need to implement the “group identify” call. Learn more here.
6. Remove your employees
If you’re getting started there is a good chance that your employees are creating a bias in your data. Open the relevant report and remove your employees from the analysis:
7. Track your progress
You can keep track of the evolution of your metrics without effort using the Slack integration, like this:
If you’re an iOS user you can also use the iOS widget. You can find it in the “Get the iOS widget” section, then follow the instructions.
Congrats on wrapping up Day 1 with June 🥂
Want to go further? Check out Academy ➡️