The Orbit Model is a framework for building high-gravity communities. A high gravity community is one that excels at attracting and retaining members by providing an outstanding member experience.

This guide will cover four concepts that are important to understand the foundational ideas that power the framework and how the Orbit application works: Presence, Love, Reach and Orbit Levels.

• Love is a member's overall level of engagement and impact in the community.
• Reach is a measure of a community member’s sphere of influence.
• Presence is a measure of a community member's activity over a period of time.
• Orbit levels are a practical tool for member segmentation and help you create different programs for different types of community members.

Note: As of May 2021 the Orbit application incorporates newer concepts like Presence and a newer method to calculate the member's Love and Orbit Level. If you're an application user and have any questions about the updates, please reach out to team@orbit.love.

Core Concepts

Love

Love is a member's score based on their relative engagement and impact in the community. All members have a Love metric, and this number is what determines a member's Orbit Level.

• The Love of a member changes gradually over time.
• The number of unique channels and groups a member is active in plays a big part
• The weight of each activity and the frequency of activities also play a role

Orbit Levels

Orbit Levels are a tool for segmenting community members by how engaged they are, to help you give the right experience to the right people.

Each member is assigned an Orbit Level based on their ranking as determined by Love:

Activity Weights

Activity Weights range from 0 through 10. They help place members in respective Orbit levels and influence their Love score.

The exceptions are activities with a weight of 0. These are activities that do not contribute to the continuing participation of a member.
For example, opening a pull request is an indicator of active contribution and is assigned a weight of 7, whereas the merging of a pull request does not reflect on the presence of the opener, and is assigned a weight of 0.

To know the weights of the default activities used by your built-in Orbit integrations, click on the Settings tab, then Activity Types in the sidebar:

To modify the weight of an activity type, hover over the channel name next to its activity type name, an icon appears, click it. This will display a modal window that enables you to modify the weight:

For your custom activities, you are free to choose the weights that best fit the needs of your organization. The following table is a suggested guide for how much to weigh these activities:

Presence

Presence is a measure of how active a member is over a selected period of time.

Presence reads like a music score: each vertical bar is a span of time (1 day, 2 days, a week, or a month, depending on the timeframe), each pitch is a channel, and notes are the unique activities.

Further Exploration

The Orbit Model is open source and available on GitHub. We welcome discussions about the model on GitHub.

Are you curious about how the Orbit team uses the Orbit Model in our own work? Read this blog post on the ways we use our own model to power the Orbit community.