Add priority-based notice bar with milestone and extrapolation messaging

[danieliser]

Summary

Implements comprehensive upsell enhancement system with intelligent priority-based trigger selection inspired by the Review Request module pattern.

Priority System

4 Priority Groups (highest to lowest):

1. Milestone Achievements (pri: 100) - Celebration messages for user success
2. Conversion Extrapolation (pri: 80) - Data-driven "you could have X more" messaging
3. Integration Detected (pri: 60) - Contextual plugin-based messages
4. Generic Upgrade (pri: 40) - Fallback messages

New Milestone Triggers

• 🎉 First form conversion: Celebration message with 300-500% increase stat
• 📈 High engagement tiers: 1K, 5K, 10K+ popup views with analytics pitch
• 90-day cooldown: Prevents message fatigue while allowing seasonal re-engagement
• Natural progression: Celebration → extrapolation → integration → generic

New Extrapolation Messages

• 💰 Ecommerce users: "You've tracked X form submissions. With Pro+ Exit Intent, you could capture ~Y more!"
  • Uses 33% extrapolation based on industry averages
  • Requires minimum 3 submissions for credibility
• 🎓 LMS users: "You've tracked X form submissions. With Pro+ LMS targeting, you could capture ~Y more!"
  • Uses 40% extrapolation for education sector
  • Requires minimum 3 submissions
• Accurate terminology: Uses "form submissions" not "conversions/enrollments" (free plugin doesn't track specific conversion types - that's what Pro is for!)

Milestone Cooldown System

• 90-day cooldown period for milestone re-showing (seasonal re-engagement)
• Tracks via user meta: _pum_last_milestone_trigger, _pum_last_milestone_at
• Prevents showing same milestone repeatedly within cooldown
• Allows different milestones to show as user progresses
• Non-milestone messages (integration, generic) unaffected by cooldown

Technical Implementation

• New methods:
  • get_notice_bar_triggers() - Priority-based trigger definition system
  • get_current_notice_bar_trigger() - Intelligent trigger selection with cooldown logic
  • get_form_conversion_count() - Helper with graceful fallback
  • rsort_by_priority() - Consistent priority sorting
• Integration:
  • Connects to FormConversionTracking service (gracefully degrades if not available)
  • Uses existing popup view count for engagement milestones
  • All messages use generate_upgrade_url() for UTM tracking
• Backward compatibility:
  • Deprecated old helper methods with @deprecated tags
  • Maintains existing integration detection logic
  • Fallback to generic messages ensures no user sees empty notice bar

Impact

• ✅ Success-triggered messaging instead of frustration-based upsells
• ✅ Data-driven value propositions with concrete numbers
• ✅ Contextual relevance based on actual user behavior and installed plugins
• ✅ Foundation for A/B testing (priority system makes message variants easy to test)
• ✅ Milestone celebration creates positive emotional association with upgrade
• ✅ Accurate terminology that doesn't over-promise on free plugin tracking
• ✅ Quarterly re-engagement prevents message fatigue (90-day cooldown)

Testing Scenarios

• 0 form submissions: Should skip milestone triggers, show integration or generic
• 1 form submission: Should show celebration message
• 1 form submission (repeat visit within 90 days): Should skip to next trigger (cooldown working)
• 1 form submission (after 90 days): Should re-show celebration (cooldown expired)
• 3+ form submissions + ecommerce: Should show extrapolation message
• Popup view milestones: Test 1K, 5K, 10K+ view thresholds
• Fallback behavior: Verify generic messages work when no triggers match
• Pro vs Free users: Verify Pro users see Pro+ messages, Free users see Pro messages

Files Changed

• classes/Upsell.php - Complete refactor of message generation system (2 commits)

Commits

1. b283d213 - feat: add priority-based notice bar with milestone and extrapolation messaging
2. 68c51ed5 - fix: improve messaging accuracy and add milestone cooldown system

🤖 Ready for CodeRabbit review

[coderabbitai]

Warning

Rate limit exceeded

@danieliser has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 13 minutes and 22 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between cceae66 and 68c51ed.

📒 Files selected for processing (6)

• CHANGELOG.md
• assets/js/src/integration/happyforms.js
• assets/js/src/integration/index.js
• classes/Integration/Form/HappyForms.php
• classes/Integrations.php
• classes/Upsell.php

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}