Peer-to-Peer Activity Settings

The Peer-to-Peer (P2P) Activity Settings page controls how activity tracking works for a P2P campaign. These settings determine:

• What participants (child fundraising campaigns) can log

• How activity totals roll up into progress summaries and leaderboards

• How badges are evaluated

• How pledges can be calculated (per-unit vs flat)

• Optional integrations like Strava (manual sync + mapping)

 

Before you start

To ensure the settings behave as expected:

Your parent campaign must have P2P activity tracking enabled.

Activity types should be configured before you ask participants to start logging.

 

Tab: Activity Types (Configuration)

What it controls

This tab defines what can be logged and how it’s measured.

Typical settings in this tab

• Create/edit activity types (examples: Run/Walk, Cycling, Workout Time)

• Assign a single unit per type (Miles, Minutes, Steps, etc.)

• Set the display label used across the UI and exports

What this affects

• Activity log entry forms (which types appear)

• Progress totals and summaries

• Badge rules that are scoped by activity type

Admin tips

Keep names and units simple to reduce logging mistakes.

Avoid creating overlapping types (e.g., “Run” and “Running” with the same unit) unless you want separate totals.

 

Tab: Badges & Rules (Milestones & Awards)

What it controls

• Badge definitions and rules for awarding badges based on activity progress.

Typical settings in this tab

• Create/manage badge definitions (name, description, icon)

• Configure badge rules (thresholds and criteria)

• Scope badges to a specific activity type when relevant

What this affects

• Participant motivation and engagement

• What badges appear on fundraiser pages (child campaigns)

• Admin reporting on achievement

 

Tab: Pledge Rules (Per-Unit and Flat)

What it controls

• Whether and how supporter pledges can be tied to a participant’s activity.

• Common pledge types

  • Per-unit: e.g., $5 per mile

  • Flat amount: e.g., $50 total

What this affects

• Fundraising calculations that depend on activity totals

• Any pledge “preview” or reporting that uses activity totals

Admin tips

• Confirm the activity type/unit setup before allowing per-unit pledges.

• If supporters complain about pledge totals, check for duplicate logs or incorrect units.

 

Tab: Strava (Mapping & Manual Sync)

What it controls

• This tab manages whether Strava can be connected per participant (child campaign)

• Mapping rules (Strava activity type → campaign activity type)

• Manual import/sync behavior

What this affects

• How Strava activities appear as logs

• Whether activities are discarded due to missing mappings

• Data quality in totals, badges, and pledge calculations

Admin tips

• Set mapping rules before encouraging participants to connect Strava.

• If participants report missing activities, verify whether they were unmapped and ignored.