Gamebus Docs

Strava

Import supported Strava activities into GameBus.

Overview

The Strava integration lets GameBus use activities recorded in Strava. For campaigns that focus on movement, this can reduce manual entry and make progress feel more immediate.

In GameBus, Strava acts as a provider. Imported Strava records become GameBus activities with properties such as distance, duration, and activity type.

Use Strava for movement-based tasks

Strava is a good fit when a campaign rewards walking, running, cycling, or other tracked movement.

Typical flow

  1. A participant connects their Strava account.
  2. Strava asks the participant to grant access.
  3. GameBus receives activity data from Strava.
  4. GameBus maps the data to campaign activity types.
  5. Tasks and skills are updated when the imported activity matches campaign rules.

What to configure

Before enabling Strava for a campaign, decide:

  • which Strava activity types are allowed;
  • which GameBus activity type each Strava type maps to;
  • which properties are stored, such as distance or duration;
  • whether imported activities should count toward tasks;
  • how users can disconnect their account.

Map activities

Decide how Strava runs, rides, walks, or other activities become GameBus activities.

Store properties

Keep only the values that the campaign needs for progress or reporting.

Update progress

Make sure task and skill rules use the imported activity types.

Practical checks

Good fit

Use Strava when the campaign goal depends on tracked physical activity. Use manual entry or another provider when the campaign needs activities that Strava does not capture.

On this page