Skip to content

Gamification 0.9.94 / Integrations

FluentCommunity Rewards integration

Add native community and profile Rewards routes.

FluentCommunity integration

The official Cointacted FluentCommunity bridge must be entitled before addon surfaces mount. In Display → FluentCommunity, the optional Gamification page is a flexible composition: enable individual sections and assign their layout order. There is no implicit “all” choice. Reward history, Balances, Achievements, Ranks, Achievement catalog, Rank catalog, Quests, and Streaks can also be enabled as independent focused pages, together with the flexible page or instead of it. Each destination owns its route, menu label, menu visibility, and order. Member-profile Rewards tabs remain a separate surface with their own profile layout and sections. Shared point-type visibility, activity policy, and empty/signed-out behavior live under Display → Content & privacy.

The bridge registers every enabled page as a native FluentCommunity Vue route and uses FluentCommunity's own page-title bar. A focused route shows that one native title followed directly by its table or content. The flexible Gamification route gives every selected section its own visible heading so a multi-section layout remains scannable. Each route requests only its fixed member dataset, while the optional overview intentionally combines enabled progression sections. Profile presentation can create separate /u/:username/rewards, /balances, /achievements, /ranks, /quests, and /streaks tabs, or one intentionally combined tab. Every page whose menu switch is enabled is added independently to FluentCommunity's native main menu and offered to compatible menu editors as a managed destination. It uses no iframe and executes no shortcode.

Published Cointacted leaderboards are also projected into FluentCommunity Pro's native Leaderboard screen. Each Cointacted board remains an independent native tab/section with its configured name, metric, period, exact score, ranking ties, visibility, and member opt-out. Only members with a FluentCommunity profile are included on that host screen. There is no second leaderboard configuration to maintain: publish, pause, archive, or change visibility on the Cointacted leaderboard definition and the native projection follows it.

This is deliberately a read-only presentation bridge. FluentCommunity continues to own its engagement points, levels, seven-day, thirty-day, and all-time rankings. Cointacted continues to own its ledger, configurable point types, streaks, achievements, quests, and materialized leaderboard scores. The bridge never copies Cointacted scores into FluentCommunity's total_points, so native recalculation, level upgrades, and automations cannot overwrite or loop through Cointacted data.

The separate Migration Center under Gamification > Integrations can discover FluentCommunity's native engagement point type and member totals. With both products entitled, an administrator may preview and import those totals as traceable opening transactions, keep FluentCommunity authoritative with exact background delta synchronization, run comparison-only audits, or declare Cointacted authoritative after cutover. The FluentCommunity addon owns native schema extraction; Gamification owns mappings, checkpoints, provenance, conflicts, and every ledger movement. Complete historical movements are not invented when FluentCommunity exposes only a current total.

The same run converts configured FluentCommunity levels into a dedicated Community levels Cointacted rank ladder. A member's current native level is assigned after the point snapshot, and later promotions or demotions append rank history without duplicating unchanged assignments. Level definitions and assignments participate in preview, source hashing, provider/Cointacted authority, and conflict reporting. Native leaderboard periods remain active; the conversion does not rewrite FluentCommunity level settings or totals.

FluentCommunity usernames are resolved to their owning WordPress users before Gamification applies its privacy policy. The profile owner sees permitted private data; visitors receive only administrator-approved sanitized fields. Signed-out and empty surfaces follow the Display policies. Enabled sections use explicit tables and remain visible with a clear empty row when they have no records. On narrow screens those rows become labelled cards. Gamification Pro controls Gamification features independently and does not unlock unrelated FluentCommunity addon features.

Enable and test Rewards

  1. Confirm Cointacted – Gamification and Cointacted FluentCommunity both show Pro
  2. in the Cointacted Add-ons Hub. Refresh products once after installing either plugin.

  3. Open Cointacted > Gamification > Display > FluentCommunity. Enable the
  4. focused community pages you need. Keep or edit each route, then enable its community-menu switch only when that page should appear in navigation.

  5. Enable Member Rewards tab, choose who can see it, select at least one
  6. active point type under Display > Content & privacy, choose Separate profile tabs or One combined tab, select the profile sections, and save.

The enable switch is the only way to disable the profile tab. When enabled, its visibility is always Profile owner, Signed-in members, or Everyone. Sites saved with the older contradictory Enable + Nobody combination are automatically repaired to Profile owner. Reward history is private to the owner and administrators unless Visitor activity is explicitly set to sanitized summary.

  1. Visit every enabled /portal/ROUTE as a signed-in member. Confirm each page
  2. renders only its named content, each selected menu entry is present, navigation does not refresh the document, and signed-out/empty-state policies are honored.

  3. Visit /portal/u/USERNAME/rewards and each enabled independent profile tab.
  4. Test as the profile owner, another signed-in member, a signed-out visitor, and an administrator. Confirm profile visibility, privacy opt-out, pagination, and activity-history policy are respected.

  5. Under Gamification > Members, post a small manual award to the test member.
  6. Verify the immutable transaction under Ledger and the updated balance on both FluentCommunity Rewards surfaces. Use Diagnostics to dry-run rules, achievements, quests, and streaks against a canonical event before enabling live automation.

  7. Publish a Cointacted leaderboard under Gamification > Competition, then
  8. open FluentCommunity's native Leaderboard screen. Confirm the native boards remain present and the Cointacted board appears separately. Test its public, members-only, private, and member opt-out behavior. A WordPress user without a FluentCommunity member profile is intentionally omitted from this surface.

This bridge owns FluentCommunity presentation and privacy. It does not currently translate FluentCommunity-native post, comment, reaction, follow, or course actions into canonical Gamification events. Those actions require a dedicated provider adapter or explicit canonical event ingestion; the WordPress adapter only covers registered WordPress post types and lifecycle hooks.

Was this documentation helpful?Your response helps us improve this page.