We've added a 7th email to the Recovery flow! This will allow you another chance to recover failed payments from your customers, especially if you lock customers out of your app after 15 days delinquent. As with all of our Recover emails, these are fully customizable. You can check it out here: 

We've improved how Baremetrics manages new subscriptions with backdated dates in our Recurly integration. Now, any subscription created with a past timestamp will be flagged for recalculation, ensuring that it is correctly processed and included in your analytics with the backdated date. 

This ensures that your analytics accurately reflect all subscription activity, giving you complete confidence in the reliability of your data—no matter when a subscription starts. Keep focusing on growth while Baremetrics keeps your numbers precise!

We've refined the account currency switching process within Baremetrics. The expected completion time has been updated to "several hours" instead of "30 minutes," allowing for a more reliable transition. During this period, certain features may be temporarily restricted to ensure accuracy and a smooth switch. 

We’ve updated how we identify trial periods in our Stripe integration. Now, we’ll double-check that the plan amount is actually zero before marking a subscription as trialing. This helps us keep your subscription analytics spot-on, so you’re not left guessing about trial statuses based on invoice descriptions alone.

With this change, you’ll get even more accurate insights into your customers’ trial periods, making it easier to understand where they’re at. And don’t worry—this update has been thoroughly tested to work smoothly with your existing data. You can count on us to keep things clear and reliable!

This issue primarily impacted new companies or newly added plans, where adjustments in MRR were more likely to produce inflated churn percentages. For established companies or longer-standing plans,  this issue was less impactful.

Previously, when a customer upgraded their plan mid-period and then churns, the churn was calculated based on the most recent (higher) MRR, divided by the MRR base from 30 days prior. This inflated the churn percentage disproportionately.

Now, the Churn percentage will not exceed 100%.

Example

• Scenario: A customer upgraded from a $500 plan to $1,379 and subsequently churned.
• Previous Calculation: The churn percentage was calculated as $1,379 (new MRR) / $500 (initial MRR), yielding a 275.8% churn rate.
• Improved Calculation: It is now calculated based on the initial MRR base, capping the churn at 100% where relevant. In this example, churn should be $500 / $500 = 100%.

We have improved our QuickBooks integration to handle payments without line items. We'll now handle this scenario automatically, whereas previously, it may have required manual intervention. 

We’ve fine-tuned how we calculate Lifetime Value (LTV) for segmented queries to give you even more accurate insights and consistent data.

We've also fixed a rounding issue for cases with lower ARPU values, so your financial metrics now reflect even more precise figures, helping you make smarter decisions with confidence.

We've updated our integration with Recurly by adding support for EU subdomains. If you're using Recurly's European services, our platform will automatically recognize and handle these subdomains correctly.

This change means you can expect more seamless and accurate data management and transactions if your business operates with Recurly's EU infrastructure. As always, we aim to provide robust and reliable integrations that adapt to your business needs, whether you're a customer or managing operations.

We've updated our Apple integration to ensure that your subscription states are accurately recorded, even when upgrades and refunds occur simultaneously. Now, if an upgraded subscription and a refunded one share the same timestamp, we'll prioritize the upgraded subscription to prevent it from being mistakenly canceled.

This change addresses issues where refunds incorrectly cancelled upgraded subscriptions, providing our users a more reliable subscription state history. 

We've improved how customer names are handled in Recover emails and Cancellation Insights to ensure more accurate and reliable communications. When retrieving a customer's first name, we prioritize the name stored directly in the customer profile. If the name isn't available, it will default to a friendly 'there' instead of relying on potentially inaccurate data from Clearbit.

This update helps prevent errors and ensures that your emails always address customers correctly, enhancing the professionalism and effectiveness of your communications.