Welcome to Accoil!
To get value from your product engagement data, there are three core phases to getting fully set up:
Phase | Action | Why It Matters |
1. Send Data
| Connect your product analytics or use our API | Enables Accoil to calculate engagement |
2. Configure
| Define account traits and optionally assign features | Ensures data is meaningful and accurate |
3. Build a Profile | Create and tune engagement scores | Powers segmentation, health scores, and insights |
💡 Pro Tips for a Smooth Start
Don’t wait for perfection — start with rough weights and iterate
Profiles are flexible: you can update them anytime
Features are helpful but not mandatory at day one
Your scoring model should evolve as you learn what signals matter most
How to migrate from June.so
A guide for teams migrating from June.so to Accoil — with familiar integrations, deeper insights, and a product built for long-term growth.
✅ Phase 1: Account Setup
To start using Accoil, we first need your product activity data. You can send it using one of the following options:
🔌 Step 1: Send your product data to Accoil
Segment – Add Accoil as a destination (⏱ ~3 min setup)
RudderStack – Set up destination (⏱ ~3 min setup)
PostHog - Set up an Data Pipeline
Direct API – Send events directly to Accoil's API (developer required)
Accoil Tracker Library – For teams without analytics (developer required)
👉 You’ll need your Accoil API Key, provided at sign-up or under Settings > Account > General.
⏳ Step 2: Wait for Incoming Data
Once integration is complete, give it time (typically 8–24 hours) for data to start flowing in. Accoil only begins processing engagement metrics once we’ve received at least one full day’s worth of event data.
📝 Tip: Return the next day to proceed with configuration.
⚙️ Phase 2: Configuration
Tell Accoil How to Interpret Your Data
Once data is flowing, it’s time to configure how Accoil understands your accounts, traits, and product features. This is critical for accurate scoring, insights, and filtering.
🧩 Step 1: (Recommended) Map Key Account Traits
Go to Settings → Configuration
Set the following fields:
Account Display Name: The account trait that is the human-readable name (e.g.
name)Account Created At: The timestamp field to track account age (e.g.
createdat)
📌 These mappings ensure Accoil can identify accounts and track growth or maturity.
🧱 Step 2: (Optional) Set Up Features
Go to Settings → Features
Features help group product events into logical chunks like "Form Submissions" or "Dashboard Views".
Why Features Matter:
They simplify engagement scoring
Make Activation Steps easier to understand
Power segmentation and feature usage reporting
To create features:
Click ➕ Add Feature
Provide a name and description
Assign relevant events (each event can only belong to one feature)
📌 You can always come back and assign more events once usage grows.
🏷 Step 3: (Optional) Set Trait Data Types
Go to Settings → Trait Data Types
Why it matters:
Accurate trait types (e.g., string, number, date) improve filtering, segmentation, and scoring logic.
Steps:
Review traits under both User traits and Account traits
For each trait, select the correct data type from the dropdown
👉 Focus especially on traits like timestamps and numerical values, so that you get the right options (e.g. days since, or great than) when building segments.
📊 Phase 3: Create a Profile
Once you done enough configuration, build your first engagement profile. This defines how Accoil calculates account or user engagement.
Go to: Profiles → Add Profile
Step 1. Name your profile
Give it a descriptive name like Trial Engagement, Customer Health Score, or Free Plan Usage.
Step 2. Select time window
Choose how far back you want Accoil to look:
1 day
7 days
30 days
💡 Tip: 30 days is a common starting point for most SaaS products.
Step 3. Add Features or Unassigned Events
Use the Add Features button to:
Include existing feature groups, or
Directly add individual events from your data feed
If you have not configured features, or the event you need is not assigned to a feature, you can Add Events individually.
Step 4. Weight Features
Each event or feature can be given a weight between 1 and 10:
7–10: Power/Admin user or high-intent signals (the quality end of the scale.
4–6: Core feature usage
1–3: Everyday usage (the quantity end of the scale)
Step 5. (Optional) Filter the Profile
Filter which users this profile applies to (e.g. trial users only, paid accounts, admins, etc.)
📝 Tip: If this is your first profile, start without filters to learn from all users before segmenting.
📊 Congratulations!
Return to the dashboard to see how your users and accounts are performing.
