Gamification

Cointacted Gamification is a native WordPress rewards system. It records every point movement as an immutable transaction, derives balances from that ledger, and can publish privacy-aware member progress on WordPress, SnapWeb, Social Terminal, and—through the official bridge—FluentCommunity.

It does not require myCred or GamiPress. Cointacted can be the reward authority itself; Pro integrations can migrate from or synchronize with those providers when required.

Free and Pro

Free provides one native whole-number point type, exact balances, manual awards and deductions, transfers and reversals, canonical event ingestion, member summaries and history, all Gamification shortcodes, and the base PHP and REST APIs.

Pro provides unlimited point types, zero-to-eighteen decimal precision, automation rules, achievements, ranks, campaigns, quests, streaks, leaderboards, advanced diagnostics and export, plus myCred and GamiPress migration or synchronization.

Read Free versus Pro for the enforced downgrade behavior and complete boundary.

Administration map

Open Cointacted → Gamification. The administration tabs follow the setup and operating workflow:

• Overview — health, setup progress, and recent operational status
• Points — point types, balances, and manual ledger operations
• Achievements — achievement and badge definitions
• Ranks — independent ordered progression tracks
• Reward rules — event-driven automation
• Journeys — campaigns, quests, and streaks
• Members — private member inspection and adjustments
• Competition — leaderboard definitions and rebuilds
• Display — WordPress, SnapWeb, FluentCommunity, content, and privacy destinations
• System — activity sources, event monitoring, reward ledger, diagnostics, and migration

Each workspace has its own focused create and edit screens. Display destinations save independently; changing a SnapWeb route cannot reset a WordPress or FluentCommunity destination.

Publishing member rewards

For ordinary WordPress, use the Cointacted Rewards block or the focused shortcodes. Shortcodes can publish a combined member hub or separate balances, history, achievements, ranks, catalogs, quests, streaks, and leaderboards.

For SnapWeb and FluentCommunity, an administrator composes each native destination from individually enabled sections and controls their order. There is no fixed “all in one” mode: selecting every section produces a complete Gamification page, while selecting one produces a focused page. Separately enabled routes can publish the same content types one by one.

The default composed page is named Gamification. Every selected section has its own visible title on a composed page; a focused native page relies on its single host page title.

See SnapWeb integration and FluentCommunity integration for bridge requirements and exact route behavior.

Core guarantees

• Amounts are exact decimal strings, never floating-point values.
• Every balance-changing operation has a stable idempotency key.
• Corrections are reversals or compensating transactions, not silent balance edits.
• Public and member views use the privacy-aware presenter rather than raw ledger tables.
• Provider identifiers remain available for privileged audit and migration work but are not exposed as member-facing labels.
• A Pro downgrade pauses paid listeners and mutations without deleting definitions, balances, history, progress, or migration checkpoints.

Recommended setup order

1. Install the plugin and create the site's one authoritative initial point type.
2. Read Point types and ledger, then verify balances and history.
3. Configure manual access and privacy before granting reward-management capabilities to other roles.
4. With Pro, add automation before achievements, ranks, journeys, or competition.
5. Configure one publishing surface at a time and verify it as the profile owner, another signed-in member, a signed-out visitor, and an administrator.
6. Treat migration and reconciliation as a separate reviewed project with a database backup and staging run.

For operational help, use Troubleshooting. Developers should use the documented APIs and hooks instead of writing directly to Gamification tables.