The concept layer between strategy and code
This is the bridge layer for engineers, technical PMs, and martech teams who need to understand how a mechanic actually works before they choose an API, SDK hook, or implementation pattern. Read here when you need the model, the lifecycle, and the trade-offs.
Key takeaways
Quick read- Concept pages are for understanding how a mechanic behaves, not for memorizing endpoints.
- Each concept page should link both up to strategy and down to the API reference or SDK surface.
- Technical PMs usually start here; engineers usually visit after strategy or before implementation.
Library
Browse by mechanic family
Pick the family first, then the primitive. Progression covers always-on mechanics, engagement covers time-bound journeys and competitions, and rewards covers the spendable side of the system.
Guide cluster
Families
Progression
Points, badges, tiers, streaks, and leaderboards. Best for loyalty, retention, status, and habit loops.
Read the guideEngagement
Challenges and contests. Best for journeys, campaigns, and time-bound participation.
Read the guideRewards
Catalogs, claims, inventory, and atomic points deduction.
Read the guideGuide cluster
Direct entry
Points
Ledger model, expiry, idempotent grants, and balance semantics.
Read the guideLeaderboards
Ranking windows, periods, caching, rank lookup, and fairness concerns.
Read the guideChallenges
Objectives, milestones, completion logic, and cohort progress.
Read the guideContests
Competition lifecycle, scoring rules, fraud handling, and prizes.
Read the guideNext steps
After you understand the model
Exact endpoints, request shapes, and examples.
React hooks and custom UI integration.
End-to-end compositions that show multiple primitives working together.
Strategy and market-facing playbooks for marketers, PMs, and martech teams.
Need exact endpoints?
Jump from concept into implementation
Use concept pages to understand the mechanic, then move into API reference, SDK pages, or a copy-paste pattern.