Framework components
Overview of the GameBus framework components.
Overview
The GameBus framework is made of several parts. Each part has a clear role. Together, they help teams create, run, and extend behavior change campaigns.
GameBus Core
The source of truth for clients, users, groups, waves, missions, tasks, skills, activities, consent, providers, and trusted embeds.
GameBus Docs
The documentation site for teams that configure, extend, and operate GameBus.
GameBus Assistants
Assistant tooling that can help users or staff with campaign tasks, guidance, or support flows.
GameBus Stories
Turns video into interactive experiences with dynamic overlays like quizzes, personalizing what plays next based on each viewer’s choices.
GameBus Integrations
Connectors that bring data from outside systems into GameBus, such as activity trackers or partner services.
How the parts fit together
GameBus Core is the source of truth for the campaign model. Other components build on it instead of duplicating participant enrollment, progress, consent, and activity records.
- Docs explain how the framework works.
- Assistants can help people use or manage a campaign.
- Stories can provide interactive video stories with announcements, quizzes, branching rules, and embeddable playback.
- Integrations send activity data to Core through providers and activity templates.
Why Core stays central
GameBus is an open, configurable system-of-systems for empirical behavior change research. In the current implementation, Core plays that central coordinating role.
- Campaign configuration: clients, domains, branding, groups, group holdings, waves, menu items, missions, milestones, tasks, and skills define the intervention.
- Measurement: activities, activity templates, property templates, task rules, task contributions, and skill achievements make progress measurable.
- Privacy and consent: consent items, license agreements, group membership, property visibility, provider authorizations, and trusted embed origins constrain data flow.
- Extension points: providers, custom tasks, custom menu items, custom pages, stories, and assistants add specialized behavior without changing the core campaign model.
Keep Core central
When you design a campaign, start with the Core model. Define the campaign, groups, waves, missions, and activities first. Add stories, assistants, and integrations when they serve that model.
What GameBus Core does
GameBus Core is the central application in the framework. It manages the rules that decide what a user can see, what they can do, and how progress is measured.
It supports:
- campaigns that run on their own domain;
- groups, study arms, and roles for end users and staff;
- waves that define time windows;
- missions, milestones, tasks, and skills;
- activities with structured properties;
- providers that bring activity data into the system;
- consent items, license agreements, and property visibility defaults;
- custom menu items, embedded pages, and embedded tasks for trusted external experiences.