Changelog

Freemius has a very handy feature called “Log in as User”. While working with customer support, it is often helpful to view the Freemius Customer Portal exactly as your customer would see it. This allows you to pinpoint the exact button a customer should click or the specific information they need to look for. To use this feature, simply click the Log in as User button from the Users page of your product in the Developer Dashboard.

Recently, we noticed that when makers were using this feature to debug license upgrade scenarios, it sometimes created a cart entity on Freemius on behalf of the user. As a result, our cart recovery mechanism was triggered, and recovery emails were sent to the buyer. This could understandably be a little annoying to your customers.

To address this, we’ve now ensured that carts are not created in these scenarios. This means you can safely use the Log in as User feature to debug customer issues without triggering any unnecessary cart recovery workflows or side-effects.

At Freemius, we love to celebrate—and what better occasion than our makers’ success? For a long time, we’ve been sending various milestone emails to our makers, not only to recognize their achievements but also to help chart the next steps toward even greater success.

For example, after your first sale, we invite you to join our exclusive Slack group.

Similarly, after your first renewal, we discuss dunning mechanisms and how to optimize your renewals further with special discounts.

Once you reach 100 sales, we celebrate in style and talk about strategies to increase your Customer Lifetime Value (CLTV).

Today, we’re excited to announce that all of these milestone emails have been rebranded with our new design, and they look fantastic. This, in itself, is yet another milestone in our ongoing rebranding project (see the pun?).

Curious to see these milestone emails in action? Start selling with Freemius and experience each one as you grow.

We discovered an edge case bug where closing the subscription cancellation dialog in the Customer Portal could incorrectly trigger the cancellation API call.

We have identified the root cause and have issued a fix. Now, simply closing the dialog will not result in any unwanted cancellation actions.

We have deployed two new API endpoints this week to ease our SaaS integration experience. In our guide, we ask to store the license ID after purchase to identify the user and their active plan on Freemius. However, we didn’t have a clear way to access the subscriptions of the user from the license itself. The recommended way was to search for the subscription using the user_id from the license. But since a license can have multiple subscriptions associated with it (due to plan upgrades, payment method updates, etc.), we didn’t have a clear instruction or method to find the latest and current subscription associated with the license.

To ease this integration and to provide better Developer Experience, we have introduced two new API endpoints:

Access Subscription of a License

GET https://api.freemius.com/v1/products/{product_id}/licenses/{license_id}/subscription.json

This will give you the latest subscription under a license. You can use it to show current billing information to your users. More information can be found here.

Cancel the Subscription

DELETE https://api.freemius.com/v1/products/{product_id}/licenses/{license_id}/subscription.json

This will immediately cancel the subscription and it will not go for any upcoming renewals. The license itself will still stay active until the next renewal time and after that will expire. Find the API reference here.

We have rolled out a minor UI fix for our Checkout. Specifically, we improved the vertical alignment of the legal text in overlay mode to ensure better visual consistency between the two lines of copy.

While this was purely a visual tweak, we care deeply about the quality of our UI and the overall user experience. As a Merchant of Record (MoR), the legal block in the Checkout plays a key role in setting clear expectations with buyers by transparently presenting the terms of sale, service, and privacy policy – all of which are required for compliance and building trust at the point of conversion.

We noticed a minor UI glitch in the “Add New Team Member” UI, where the auto-complete overlay could block the visibility of the input field.

This has now been fixed. You can seamlessly add team members to your product for moderation, support, account management, and more without any visual interruptions.

We discovered a bug in the newly introduced billing cycle selector UI of our Checkout. In cases where a plan’s pricing options had inconsistent billing cycles, the selector could still render an invalid option.

While this was an edge case, we prioritized the fix. The UI will now behave correctly regardless of how your plans are configured.

Reminder: The billing cycle selector is not shown by default. To enable it, you must opt in by adding the billing_cycle_selector option in your Checkout config.

We recommend using the billing cycle selector UI only if you don’t have a pricing page where buyers can pre-select their billing cycles. By default, Freemius’ upsell UI is optimized for conversion and offers the best purchase flow.

Freemius offers a powerful webhook and events system to support your custom integrations. For example, when a new version is deployed, a plugin.version.deployed event is triggered, which your webhook can use to perform automations, such as notifying customers via email.

Based on requests from our maker community, we’ve enhanced the payloads of the following events:

• plugin.version.deployed & plugin.version.updated — now include file, version, and release_mode fields.
• plugin.version.deleted — now includes the version field.

These enriched payloads should give you more actionable data to build powerful automations.

As a reminder, all plugin.version.* events include a tag field that holds the deployment ID. You can use that ID to retrieve full deployment details via a single API call if additional data is needed.

This week, we’re rolling out another update to make our platform more optimized for SaaS and App based products. When you create a product in Freemius, you’re be taken straight to the Setup Checklist page. This checklist outlines the key steps needed to complete your product’s integration with Freemius.

We’ve revised the flow by updating existing steps and introducing new ones to provide better guidance. For example, SaaS products now link directly to our integration guide and include hints for setting up webhooks, making it easier to build tighter integrations.

No matter what stage you’re at in your integration journey, you can always access the Setup Checklist from the sidebar. And if anything’s unclear, our support team is just a message away.

We noticed two bugs in our deployment-related endpoints. When generating the download links for the latest deployment (or “tag” as we call them internally), we found that in some cases, the links were not properly signed and were getting blocked by our authentication layer.

1. Get latest deployment for a product
2. Retrieve latest update for an install

We’ve identified the root cause and rolled out a fix. If you’re using these endpoints for a custom integration, you should no longer encounter any issues.

Note: Our WP SDK was not affected by this bug and its auto-update functionality remained fully operational.

The Customer Portal includes a powerful support form that allows your buyers to easily reach out to you. It also supports upsells, HelpScout, and documentation integration out-of-the-box. If preferred, you can even link to your own external support form.

With this week’s deployment, we’ve improved the success message shown after a customer submits a support request.

To reduce confusion and improve transparency, the message now clearly displays the product name and the email address where the request was sent, helping your customers trust that their message reached the right destination.

This week, we’re rolling out an exciting new feature to improve financial transparency and make accounting smoother for our makers.

At the beginning of every month, as your payable earnings are calculated, you’ll now receive an email with all the details related to your upcoming payout.

The email will include a link to a pro-forma invoice, which you can use as documentation for incoming payments with your financial institutions — such as PayPal or your bank.

Once the payout is completed you’ll receive a follow-up email with the updated information and a link to the finalized paid invoice.

This new feature is another step toward our ongoing mission to remove operational friction from your workflow — letting you focus on building amazing products.

This week, we’re rolling out several enhancements to the Plans page in the Developer Dashboard to improve your product onboarding experience.

Updated Plan Form

• The Title field now appears first and automatically generates the Unique Name, making plan creation quicker and more intuitive.
• For non-WordPress product types, the Description field has been removed, since it’s only relevant when using the built-in pricing page in the WP SDK.

Updated Pricing Form

• The page heading on the pricing form now clearly displays the currency for each pricing item.
• We’ve renamed “Lifetime price” to “One-off price”, which better reflects SaaS-oriented terminology.
• The price recommendation hint has been removed for SaaS products, as pricing varies widely across different business models.

If you’d like help with pricing strategies, feel free to contact our support team.

We recently introduced Custom Selling Unit labels for SaaS and App products. While these updates were already integrated into core components like the Checkout and transactional emails, the Customer Portal hadn’t yet caught up.

This week, we’re closing that gap.

The Customer Portal has been updated to show the configured unit labels in all relevant areas of the UI.

You’ll primarily notice this improvement in the Upgrade/Downgrade flows under the Licenses and Renewals & Billing sections.

Buyers will now clearly see the specific license unit they’ve purchased, with a consistent and accurate label guiding them through the upgrade experience.

We discovered a bug in some of our API endpoints responsible for fetching the latest deployment of a WordPress product — for example, products/{product_id}/tags/latest.json.

Instead of returning information about the most recent deployed version, these endpoints were incorrectly returning the latest incremental release. We’ve identified the root cause, and a fix has been deployed.

This bug did not affect the update flow of our WordPress SDK. The SDK has always expected and correctly received updates based on the incremental versioning and other release mechanisms that Freemius offers.