Activity Trackers
Use activity trackers as providers for GameBus activities.
Overview
Activity trackers can send real-world activity data to GameBus. This helps campaigns use data such as walks, rides, distance, duration, and steps without asking users to enter everything by hand.
In GameBus Core, tracker data becomes activities. Activity properties store details such as distance or time. The tracker itself acts as the provider.
Tracker data is still campaign data
Imported activities can count toward tasks, skills, and milestones when the campaign rules say they should.
What to define first
Before connecting a tracker, define the campaign model.
- Which activity types will the tracker create?
- Which properties do those activities need?
- Which users may connect a tracker account?
- Which tasks or skills use tracker activity?
- How will you handle missing or duplicate data?
Activity type
The kind of activity imported, such as walking, running, or cycling.
Properties
The values stored with the activity, such as distance, duration, or steps.
Provider
The external system that supplied the activity data.
Integration pattern
Most tracker integrations follow the same pattern:
- The user connects their tracker account.
- The tracker authorizes GameBus to read activity data.
- GameBus imports supported activities.
- Imported activities receive structured properties.
- Campaign rules use those activities for progress.