{"id":824,"date":"2025-12-18T05:49:21","date_gmt":"2025-12-18T05:49:21","guid":{"rendered":"https:\/\/blog.taskon.xyz\/?p=824"},"modified":"2025-12-19T03:40:02","modified_gmt":"2025-12-19T03:40:02","slug":"growth-accounting-decomposing-dau-mau-new-churn-and-resurrection","status":"publish","type":"post","link":"https:\/\/blog.taskon.xyz\/?p=824","title":{"rendered":"Growth Accounting: Decomposing DAU\/MAU \u2014 New, Churn, and Resurrection"},"content":{"rendered":"\n

In the Web3 world, 80% of DAU\/MAU<\/strong> volatility can be explained by the “Growth Accounting Trio” \u2014 New \/ Churn \/ Resurrection<\/strong>.<\/p>\n\n\n\n

How do we build an executable decomposition method and form a positive growth flywheel?<\/p>\n\n\n\n

The growth platform TaskOn constructs a comprehensive growth flywheel through features like Quest, Level\/EXP, Eligibility, API-Verified, Anti-Bot, Leaderboard, and Benefits distribution. This creates a closed loop of “Operational Action \u2014 Metric Change \u2014 Incentive Bonding.”<\/p>\n\n\n\n

\n\n\n\n

I. The Growth Accounting Model (Web3 Context)<\/h3>\n\n\n\n

The Core Identity (Applicable to Daily\/Weekly\/Monthly):<\/p>\n\n\n\n

$$MAU_t = MAU_{t-1} + New_t + Resurrection_t – Churn_t$$<\/p>\n\n\n\n

The split for DAU<\/strong> follows the same logic, simply shrinking the window from 30 days to 1 day.<\/em><\/p>\n\n\n\n

    \n
  • New:<\/strong> “Active addresses\/accounts” participating in your ecosystem for the first time<\/strong> (e.g., completing a Quest for the first time).<\/li>\n\n\n\n
  • Churn:<\/strong> Existing active users who haven’t appeared within the current window period.<\/li>\n\n\n\n
  • Resurrection:<\/strong> Users who were formerly active, went silent, and returned during this period.<\/li>\n<\/ul>\n\n\n\n

    TaskOn\u2019s project console and help center explicitly provide entrances for data download and analysis, task data export, and user eligibility\/completion dimensions, supporting this exact breakdown and recalculation. It also covers Dashboard modules, data export capabilities, and task templates\/eligibility settings.<\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n
    \n\n\n\n

    II. Mapping “New\/Churn\/Resurrection” to TaskOn Product Capabilities<\/h3>\n\n\n\n
    Attribution<\/strong><\/td>Where does the data come from?<\/strong><\/td>TaskOn Capability<\/strong><\/td>Context & Trustworthiness<\/strong><\/td><\/tr><\/thead>
    New<\/strong><\/td>First-time qualified participation of a new address\/account<\/td>Quest<\/strong> (Acquisition campaigns), Eligibility<\/strong> (Gating), Anti-Bot<\/strong><\/td>Supports KYC-less acquisition, but uses Level\/Holdings\/NFT\/Geo<\/strong> as gates, layered with Google reCAPTCHA + TaskOn\u2019s proprietary algo<\/strong> to ensure authenticity.<\/td><\/tr>
    Churn<\/strong><\/td>Existing users inactive for the last N days<\/td>DayChain<\/strong> (Streaks), API-Verified Task<\/strong>, Auto-Reward<\/strong><\/td>Front-load short-term incentives via continuous streaks\/interactions and automated settlement to reduce churn; API verifies real product usage. Docs list “API-Verified Task” integration and auto-reward specs.<\/td><\/tr>
    Resurrection<\/strong><\/td>Active $\\to$ Silent $\\to$ Returns this period<\/td>Win-back Quest<\/strong>, Leaderboard<\/strong>, Benefits<\/strong> (Redemption\/Spots)<\/td>Stimulate returns via leaderboard competition and benefits store\/point perks; “leaderboard\/benefits” routing and community case pages are visible on-site.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Level\/EXP & Incentive Bonding:<\/strong> EXP<\/strong> constitutes TaskOn’s points system, linked to Level<\/strong>. It serves as a reward for tasks and a threshold for campaign entry; reaching higher Levels unlocks more events and subsequent benefits.<\/p>\n\n\n\n

    \n\n\n\n

    III. Four Common Causes of DAU\/MAU Fluctuations<\/h3>\n\n\n\n

    1. Change in Acquisition Density<\/strong><\/p>\n\n\n\n

      \n
    • Signal:<\/strong> New<\/strong> spikes $\\to$ DAU\/MAU<\/strong> synchronizes upward.<\/li>\n\n\n\n
    • On TaskOn:<\/strong> Check the qualified submission count for new addresses in that cycle, the source task type (Twitter\/Discord\/On-chain\/API), and the Anti-Bot pass rate. Documentation provides task template lists and eligibility\/anti-cheat settings.<\/li>\n<\/ul>\n\n\n\n

      2. Incentive Release Curve & Reward Rhythm<\/strong><\/p>\n\n\n\n

        \n
      • Signal:<\/strong> Activity boosts during the reward window and announcement period; if it’s a one-time airdrop without a roadmap, activity drops off.<\/li>\n\n\n\n
      • On TaskOn:<\/strong> Use Auto-Reward<\/strong> + Phased Targets<\/strong> (Milestones); sustain engagement via Benefits\/welfare spots<\/strong>. Official docs support auto-distribution and phased management.<\/li>\n<\/ul>\n\n\n\n

        3. Verification Intensity Adjustment (Anti-Sybil\/Scripting)<\/strong><\/p>\n\n\n\n

          \n
        • Signal:<\/strong> After ramping up verification, “vanity metrics” (surface activity) drop, but real conversion rates\/retention improve.<\/li>\n\n\n\n
        • On TaskOn:<\/strong> Enable Google reCAPTCHA + Proprietary Risk Control<\/strong>, and use On-chain\/API-Verified<\/strong> to validate real interactions, cutting out “fake activity.”<\/li>\n<\/ul>\n\n\n\n

          4. Benefit Structure\/Threshold Changes (Level Gate)<\/strong><\/p>\n\n\n\n

            \n
          • Signal:<\/strong> Binding premium rewards to Level\/EXP<\/strong>. New user growth might slow, but Resurrection\/Retention rises, making the activity “thicker” (higher quality).<\/li>\n\n\n\n
          • On TaskOn:<\/strong> Enable conditions like TaskOn Level<\/strong>, NFT\/Token Balance<\/strong> in Eligibility<\/strong>. The docs list four types of eligibility templates.<\/li>\n<\/ul>\n\n\n\n
            \n\n\n\n

            IV. Operational Actions $\\rightleftarrows$ Data Changes $\\rightleftarrows$ Incentive Bonding<\/h3>\n\n\n\n
            Goal<\/strong><\/td>Primary Impact<\/strong><\/td>Recommended TaskOn Action<\/strong><\/td>Incentive & Benefit Bonding<\/strong><\/td>Data Change<\/strong><\/td><\/tr><\/thead>
            Short-term Acquisition<\/strong><\/td>New<\/strong><\/td>Launch new Quest<\/strong> (Social + Light On-chain), Open Eligibility<\/strong> (Low barrier)<\/td>EXP Base Points + Small Pool, enable Auto-Reward<\/strong><\/td>New $\\uparrow$, DAU $\\uparrow$<\/strong>; If Anti-Bot is on, quality pass rate $\\uparrow$.<\/td><\/tr>
            Curbing Churn<\/strong><\/td>Churn<\/strong><\/td>Configure DayChain<\/strong> (Streaks); Bind API-Verified<\/strong> to real features (e.g., Swap\/Stake)<\/td>Streak Rewards $\\to$ EXP\/Level Up $\\to$ Unlock more events<\/td>Continuous Activity Rate $\\uparrow$<\/strong>, Next Day\/7-Day Retention $\\uparrow$.<\/td><\/tr>
            Boosting Resurrection<\/strong><\/td>Resurrection<\/strong><\/td>Targeted Win-back Quest<\/strong> (Visible only to silent users), overlay Leaderboard<\/strong> Season<\/td>Leaderboard Spots\/OG Roles\/Whitelists placed in Benefits<\/strong><\/td>Resurrection $\\uparrow$<\/strong>, ratio of vintage users increases.<\/td><\/tr>
            Purifying Activity<\/strong><\/td>Real Activity Rate<\/strong><\/td>Increase Anti-Bot<\/strong> settings\/Eligibility; More On-chain\/API<\/strong> verification<\/td>High-value Benefits (WL, NFT, Token) bound to higher Level<\/strong><\/td>Surface activity might $\\downarrow$, but Effective Conversion\/Retention\/ARPU $\\uparrow$<\/strong>.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
            \n\n\n\n

            V. The MVP “Growth Accounting” Dashboard<\/h3>\n\n\n\n

            The Instrument Layer (Weekly\/Monthly view):<\/strong><\/p>\n\n\n\n

              \n
            1. MAU\/DAU Overview + MoM (Month-over-Month)<\/strong><\/li>\n\n\n\n
            2. New \/ Churn \/ Resurrection<\/strong> (Three-line chart)<\/li>\n\n\n\n
            3. New Contribution by Task Type<\/strong> (Twitter \/ Discord \/ On-chain \/ API)<\/li>\n\n\n\n
            4. Eligibility\/Anti-Bot Pass Rate<\/strong> (Crucial when adjusting verification intensity)<\/li>\n\n\n\n
            5. Level\/EXP Structure<\/strong> (Ratio of L1\u2013L5 users, to judge if benefit thresholds are reasonable)<\/li>\n<\/ol>\n\n\n\n

              Basis:<\/strong> TaskOn ToB documentation outlines Dashboard\/Data Export<\/strong>, Task Templates<\/strong> (including Twitter\/Discord\/On-chain\/API), Eligibility<\/strong> (Level\/NFT\/Token\/Geo), Anti-Bot<\/strong>, and Auto-Reward<\/strong> capabilities, which are sufficient to recalculate and plot the charts above.<\/p>\n\n\n\n

              \n\n\n\n

              VI. About “Incentive Bonding”: Creating the “Use More $\\to$ Get More $\\to$ Want More” Loop<\/h3>\n\n\n\n
                \n
              • EXP\/Level:<\/strong> Officially defined as the loyalty point and tier system. Higher Level<\/strong> brings access to more campaigns and potential perks. Projects can also set Level as an Eligibility<\/strong> gate, back-loading scarce benefits to “Real Value Users.”<\/li>\n\n\n\n
              • Benefits:<\/strong> Used to handle the “Points $\\to$ Rights” conversion (many communities on-site already have \/benefits<\/strong> and leaderboard<\/strong> pages). This extends one-time rewards into visible, climbable long-term returns.<\/li>\n\n\n\n
              • Anti-Bot + API-Verified:<\/strong> Upgrading “Incentives” from a “Complete Button” to a “Completed Fact” (Compliant social actions + On-chain\/Product API usage), avoiding “Fake Activity.”<\/li>\n<\/ul>\n\n\n\n
                \n\n\n\n

                VII. Implementation Paradigm: Two Tables + One Cycle<\/h3>\n\n\n\n

                Table A | User Segmentation (Based on last 30 days)<\/strong><\/p>\n\n\n\n

                  \n
                • New30:<\/strong> First qualified task completion within 30 days.<\/li>\n\n\n\n
                • Active30:<\/strong> Active within the last 30 days.<\/li>\n\n\n\n
                • Silent30:<\/strong> Inactive for 31\u201390 days.<\/li>\n\n\n\n
                • Dormant90+:<\/strong> Inactive for over 90 days.<\/li>\n<\/ul>\n\n\n\n

                  Table B | Task Type & Verification Matrix<\/strong><\/p>\n\n\n\n

                    \n
                  • Dim 1:<\/strong> Social (Follow\/RT\/Join)<\/li>\n\n\n\n
                  • Dim 2:<\/strong> Light On-chain (Sign\/Interact)<\/li>\n\n\n\n
                  • Dim 3:<\/strong> API-Verified (Swap\/Stake\/Bridge\/\u2026)<\/li>\n\n\n\n
                  • Dim 4:<\/strong> DayChain (Streaks) \/ TaskChain (Sequential)<\/li>\n\n\n\n
                  • Dim 5:<\/strong> Eligibility (Level\/NFT\/Token\/Geo)<\/li>\n<\/ul>\n\n\n\n

                    Action:<\/strong> Use Table A<\/strong> to define the specific logic for Resurrection\/Churn; Use Table B<\/strong> to design the Quest mix. Create via templates in the TaskOn Console<\/strong>, enable Anti-Bot<\/strong>, and configure Auto-Reward<\/strong> and data export. Relevant capabilities are disclosed in the official docs and help center.<\/p>\n\n\n\n

                    \n\n\n\n

                    Conclusion<\/h3>\n\n\n\n

                    Don’t just treat “Activity” as a counter. Use Growth Accounting<\/strong> to decompose DAU\/MAU into New\/Churn\/Resurrection<\/strong>, then use TaskOn\u2019s task verification, eligibility gates, point levels, auto-rewards, and benefit spots to translate “Data Changes” into “Executable Product & Operational Actions.”<\/p>\n\n\n\n

                    When “Use More $\\to$ Get More $\\to$ Want More”<\/strong> becomes the consensus in your community, growth stops being a short-lived spike and becomes a sustainable slope.<\/p>\n","protected":false},"excerpt":{"rendered":"

                    In the Web3 world, 80% of DAU\/MAU volatility can be explained by the “Growth Accounting Trio” \u2014 New \/ Churn \/ Resurrection. How do we build an executable decomposition method and form a positive growth flywheel? The growth platform TaskOn constructs a comprehensive growth flywheel through features like Quest, Level\/EXP, Eligibility, API-Verified, Anti-Bot, Leaderboard, and […]<\/p>\n","protected":false},"author":1,"featured_media":925,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[30],"tags":[],"class_list":["post-824","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-academy"],"_links":{"self":[{"href":"https:\/\/blog.taskon.xyz\/index.php?rest_route=\/wp\/v2\/posts\/824","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.taskon.xyz\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.taskon.xyz\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.taskon.xyz\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.taskon.xyz\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=824"}],"version-history":[{"count":1,"href":"https:\/\/blog.taskon.xyz\/index.php?rest_route=\/wp\/v2\/posts\/824\/revisions"}],"predecessor-version":[{"id":826,"href":"https:\/\/blog.taskon.xyz\/index.php?rest_route=\/wp\/v2\/posts\/824\/revisions\/826"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.taskon.xyz\/index.php?rest_route=\/wp\/v2\/media\/925"}],"wp:attachment":[{"href":"https:\/\/blog.taskon.xyz\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=824"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.taskon.xyz\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=824"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.taskon.xyz\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=824"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}