Core concepts
Understand the main concepts behind GameBus.
The GameBus Core model
GameBus Core helps you run behavior change campaigns. A campaign is built from a small set of connected concepts: campaigns, groups, waves, missions, skills, activities, properties, consent, and providers.
Read this as an explanation
Campaigns
A campaign is the main container in GameBus Core. It represents one behavior change program and usually runs on its own domain.
Within a campaign, organizers define:
- which groups exist;
- which waves are active;
- which missions and pages are available;
- which activity types can be recorded;
- which providers may send activity data;
- which consent items, license terms, and privacy policies apply.
Campaigns let several programs run on the same platform while keeping their users, content, and rules separate.
Groups
Groups describe where users belong. They can represent a campaign, a study arm, a team, a class, a care group, or any other useful segment.
Groups can be part of a holding. This makes it possible to build a tree of connected groups. For example, a campaign group can have a holding that contains several study arms.
Campaign group
Study arm
Regular group
Membership and roles
A user can be a member of a group with one or more roles.
- Participant takes part in the campaign.
- Trainer supports participants.
- Manager manages the group or campaign work.
Why roles matter
Waves
Waves are time periods with a start and end date. They help organizers control when content is available.
A wave can represent:
- onboarding;
- baseline measurement;
- an intervention period;
- a follow-up period;
- a repeated campaign round.
Campaign content can be made available to a group during a specific wave. This is useful when different groups should see the same content at different times.
Missions, milestones, tasks, and skills
Missions guide users through the campaign. A mission contains milestones. A milestone contains tasks.
Tasks can award progress toward one or more skills. Skills are measured as a percentage from 0 to 100. They can be achieved by a user or by a group.
GameBus can use skill progress to decide:
- whether a milestone is available;
- whether a milestone is complete;
- how far a user or group has progressed.
For example, a milestone may become available when a user reaches 40% on a skill. Another milestone may depend on the average progress of the user's group.
Progress is calculated from activities
Mission enrollment
Campaign organizers can enroll groups in a mission for a given wave. This connects three things: the mission, the group, and the time period.
This makes mission planning flexible. A campaign can run the same mission for different groups in different waves, or assign different missions to different study arms.
Activities, properties, and providers
Activities record what users do. An activity can be a walk, a workout, a feedback form, a reflection, or any other action that matters to the campaign.
Each activity has an activity type. Activity types define which kind of activity is being recorded.
Activities can also have properties. A walking activity might have steps, distance, duration, or heart rate. A feedback activity might have a score or text response.
Providers describe where the activity came from. A provider may be GameBus itself, a connected tracker, or another external system.
Property templates define the default visibility of each property as PUBLIC, PRIVATE, or HIDDEN. This lets campaigns import and evaluate sensitive activity details without automatically showing every detail to other participants.
Activity
Property
Provider
How availability is decided
GameBus combines membership, wave, mission enrollment, and progress.
The result is a campaign that can adapt to each user without needing a separate custom app for every path.
Consent, licenses, and privacy
GameBus Core includes consent and license records so participant obligations are part of the same model as campaigns and activities.
Use this part of the model to make campaign requirements explicit: required consent items block participation where needed, optional items capture separate permission choices, and license agreements record acceptance of terms and privacy policies.