Changelog

Following our recent rebranding, we’re rolling out UI cleanups and regression fixes for the Developer Dashboard. Most of these changes focus on fixing UI glitches and updating certain elements based on our design team’s improvements.

Font & Legibility fixes

• We introduced font anti-aliasing for non-DPI screens to improve legibility.
• We also identified contrast regressions in some lesser-seen UI areas and have fixed the ones found so far.

Alignment fixes

Some modal elements had alignment issues, which have now been fixed.

Data tables have been improved to ensure proper alignment of text and control elements.

We also noticed horizontal scrolling issues in some side navigation menus (sidenavs) and drawers—these have now been fixed.

There have also been various small and medium fixes and updates throughout the system. Stay tuned—we’re working on something exciting in the coming weeks! (Hint: it’s about mobile 😉).

With the release of WordPress SDK 2.11.0, we’ve revamped our SDK Integration UI to make it clearer and align with the latest WordPress.org guidelines.

Simply navigate to the SDK Integration page to check out the new UI. The first step now asks how you’d like to integrate the Freemius WordPress SDK into your project. You can choose from the following options:

1. Manual – You need to download the SDK from our GitHub repository and manage updates manually.
2. Composer – The SDK is downloaded and managed automatically through the package manager.

Once you make a selection, the UI will display the relevant instructions and code snippets.

Choosing Composer Integration

If you’re already using Composer for your project, it makes sense to use the same package manager to install the Freemius WP SDK. As of SDK version 2.10.1, Composer auto-loading is fully supported. To use Composer integration, ensure that you’re running at least this version.

If you’ve been using the old integration method (where the SDK is placed in the main folder of your plugin) and want to switch to Composer, please follow the instructions below.

Migrating from the old integration method

If you’ve been using Freemius for a while, you might have noticed that we now require placing the SDK inside the vendor/freemius directory. This change aligns with WordPress.org guidelines, which recommend placing all third-party code inside the vendor directory.

Previously, we instructed developers to place the SDK directly inside the main folder of their plugin/theme. This is now reflected in the UI, where a “Legacy” option is available in the dropdown.

Unfortunately, changing the SDK location isn’t straightforward due to a bug in SDK versions prior to 2.11.0. To update the SDK location in your product, follow these steps:

1. Release a version with the SDK location unchanged, but ensure you’re using SDK version 2.11.0 or later.
2. Mark this version as an Incremental Release.
3. Release another version where you update the SDK location.

To make this process easier, the last version you deployed with SDK 2.11.0, where the SDK was located in the root of your product, is automatically marked as Incremental.

For more detailed instructions, please refer to our documentation.

We’re excited to announce the immediate availability of a powerful new feature: Incremental Updates!

In the software industry, it’s common to follow a guided update path. For example, you may want all your customers currently on version 1.0.0 to first update to version 1.2.0 before moving to version 2.0.0. This structured approach allows you to manage data migrations, schema changes, or any other breaking changes without compromising your product’s usability.

With Freemius, managing such updates is now easier than ever—it’s just a matter of clicking a few buttons! Simply navigate to the Deployments page in your Developer Dashboard, where you’ll find a new column labeled “Incremental.” From there, you can designate a version as incremental with

Additionally, when releasing a new version, you’ll notice an improved modal that highlights the same option for added convenience.

For more technical details, check out our documentation.

We’ve rolled out a few small but important bug fixes and improvements to the Developer Dashboard, focusing on various checkout-related actions.

Fixed checkout URL for SaaS products under pricing

We identified a regression where clicking the “Checkout Link” button did not generate the correct URL for SaaS products on the Plans page. This issue has now been fixed.

New license action to copy payment method update link

You will now find a new option under the “Action” menu in Licenses to copy the payment method update link. This is particularly useful for customer support when you need to quickly share a payment update link—for example, when a customer’s credit card is expiring or their PayPal account is invalid.

Please note that this link is provided for your convenience only. Freemius still handles dunning and automatically sends payment-related emails for both card and PayPal issues. Additionally, buyers can update their payment method directly through the Customer Portal at any time.

We’re rolling out a set of improvements to enhance the checkout experience — both for users (UI/UX) and developers (DX).

Cart syncing issue with VAT number – fixed!

Freemius Checkout includes a built-in cart system to support various marketing automation features. We discovered an edge-case bug where, due to network errors, the VAT number could become out of sync with the cart, leading to lost information. Additionally, in some cases, the cart was not updating properly when the VAT number was entered or modified. We’ve fixed both issues to ensure seamless VAT handling.

Smarter sandbox prefill

The Prefill button in sandbox checkout is now more intelligent. It adapts based on the full context of the checkout session. For example, if a license is already associated with the checkout, the system will no longer attempt to prefill the email field — ensuring a more accurate experience.

Improved UI responsiveness

We’ve made subtle tweaks to improve the responsiveness of checkout line items, ensuring they adapt better to different container widths for a cleaner, more consistent layout across all the languages our Checkout app supports.

At Freemius, we offer a robust Affiliate Platform for all our makers. Our system automatically generates and tracks affiliate links and calculates affiliate payouts every month. We already send an email notification when payouts are due, so you know when it’s time to reward your affiliates.

To further enhance the system — especially for makers with many affiliates — we’re introducing a new webhook: affiliate.payout.pending. Each month, as our system calculates pending affiliate payouts, it will trigger this webhook event. You can subscribe to this webhook to automate various tasks, such as:

• Create automated payment flows within your own system
• Notify your accounting department

…and more!

To get started, visit the Custom Webhooks page and look for the affiliate.payout.pending event. Check out our documentation for more details on how our webhook mechanism works.

This week, we’re deploying some minor improvements to our Developer Dashboard. Please find the details below.

Fixed regression in the secret key UI component

We identified a regression where the copy button for the secret key component on the profile page wasn’t functioning. This has now been fixed.

Please note that since we do not load the Developer’s secret key (not even in memory), you will need to click the “Reveal” button before the copy button is displayed.

Other fixes

• We addressed console errors caused by incorrect interpolation of SVG icons.
• We also fixed an issue where the feature ordering wasn’t working correctly for certain products.

We’re excited to share the latest UI/UX improvements we’ve made to our Checkout application! At Freemius, we deeply value conversion optimization—because your success is our success. Here’s a look at what’s new.

Mobile UI/UX improvements

We’ve resolved form label alignment issues on mobile and small-screen devices for certain languages. Long labels are now truncated instead of overflowing or wrapping to the next line, with a tooltip added to display the full text. This update ensures the billing form maintains a clean and consistent visual hierarchy.

We also identified a glitch in the language selector UI on mobile devices where the flag failed to render, displaying a placeholder text like ‘flag-us’ instead. To simplify the user experience, we’ve opted to remove the flag on mobile and display only the language label. On desktop devices the UI still renders with flags as before.

Lastly, we addressed a visual glitch in the upsell component. The switch was not rendering correctly, either appearing shrunken or overflowing onto two lines. This issue has now been resolved.

Improved asset loading

We noticed that the Checkout was incorrectly making network calls for certain assets, resulting in 404 errors and increased loading times. We’ve identified the root cause and resolved the issue.

We’ve also updated the Freemius logo to align with our recent rebranding.

Improved Credit card 3DS flow

We’ve improved error detection for credit card payments when the issuer requires 2FA authentication. Our Checkout now handles edge-case errors more effectively, ensuring a smoother experience for buyers in these scenarios.

Fixed discount for lifetime trials

We identified an edge case where coupon discounts were not properly applied to lifetime trials. The root cause has been resolved, and a fix has been deployed.

Fixed issue with the coupon UI

We also discovered an edge case where the coupon UI wasn’t updating correctly after entering a license, particularly during renewals of migrated licenses. This issue occurred when the pro-rated discount and the product’s renewal discount exceeded the coupon value. Given the various configurations a coupon can have during a license renewal or update, we’ve carefully addressed the root cause and deployed a fix.

The Freemius WordPress SDK includes an opt-in mechanism that allows users to decide whether to connect their site with Freemius. To prevent misuse, this mechanism incorporates an email verification process.

We recently discovered that certain misconfigurations in a WordPress site could lead to the verification email being sent multiple times, causing confusion for buyers.

To address this, we have improved the system on our end to identify and prevent duplicate messages. No changes to the SDK are required for this update to take effect.

Just as we were about to wrap up our data liberation project, we received an exciting request from our makers that we couldn’t ignore. In addition to exporting affiliate payments, they asked for the ability to export the list of affiliates as well.

We’re thrilled to announce the immediate availability of this feature! Simply navigate to the “Affiliates” tab under the “Affiliate Program” page, where you’ll find a Download button. This allows you to export all your affiliates along with details such as their name, email, CTR, earnings, and more.

If you haven’t already, be sure to explore our Affiliate Platform feature to grow your business.

As 2024 draws to a close, we’re ending the year with an electrifying finale! Introducing a dazzling new design, game-changing UX enhancements, and lightning-fast performance upgrades specifically for the Developer Dashboard!

Fresh New UI

Our brand and design team has delivered a new UI, focusing on readability and legibility for consuming large amounts of data.

Freemius provides you with a wealth of data and actionable insights in our Dashboard. The primary goal of the UI/UX team has been to make it as easy and seamless as possible to consume this information. With this mission in mind, we present the new UI for the Developer Dashboard.

We have introduced numerous changes to enhance your experience. Here are just a few highlights:

Improved Data View

• All data tables are now consolidated within a clean white background for maximum legibility.
• The primary action button to create new entities is now placed inside the toolbar on the left-hand side.
• Row action buttons are aligned to the right without drawing too much attention, allowing you to focus on the data.
• Most inline action elements now appear only when hovering over a row.

Consolidated Details View

We have reviewed and streamlined all detail view items (side navigations), making them cleaner.

• Only the most relevant information is displayed initially, with expandable sections to show more details as needed.
• Negative action buttons are now properly highlighted at the end of the details panel.

Plans Page Improvements

• The action button has been moved to the top, including the “Release plans to users”.
• Checkout code and links are now consolidated into a single dropdown button.

Deployment Page Improvements

• Notices for SDKs and other actionable items are now clearer and more attention-grabbing.
• Configuration options, such as “Add Freemius as a plugin contributor,” have been moved to the top for better visibility.

Resizable and Collapsible Sidenav

The UX of the sidenav has been improved to accommodate large data views and different screen sizes.

• A drag handler allows you to adjust the width of the sidenav to suit your preference.
• A collapse button enables you to hide the sidebar, letting you focus more on the data.

Unified Dialogs

All modal dialogs now feature a clear and consistent design. The primary button is always blue, providing a clear hint about the next step, and headers are sticky to maintain context within the dialog.

Dark mode along with sync to system

If you’re wondering where the dark mode is, don’t worry—it hasn’t gone anywhere! It has simply been relocated to the main dropdown menu on the far right.

Plus, there’s now a new option to sync the theme with your system or browser settings for a more seamless experience.

Performance Improvement

We saved the best for last! This release comes with a significant performance boost, making the Developer Dashboard noticeably snappier and rendering faster.

We identified the biggest bottleneck when navigating through different pages: the numerous HTTP requests made to load template files. Previously, the system had to wait until all the templates for all components were loaded, even though the data was already prepared.

So, we eliminated this bottleneck without compromising initial load time. The app now smartly makes a single HTTP request to preemptively cache all the template files.

This change results in significantly fewer HTTP requests when navigating between pages. It is clearly visible in the video below:

Contrast this with the previous experience, which was noticeably less snappy; the skeletons and components were loaded one after another before the data was finally being displayed (the traditional waterfall experience).

Additionally, we’ve removed outdated scripts that were no longer in use, further contributing to faster loading times.

We hope you enjoy these improvements! Explore the Developer Dashboard further to uncover even more changes!

This week, we’re excited to roll out updates that enhance the system emails sent by Freemius.

Weekly sales report email

Freemius sends weekly reporting emails to all our makers, highlighting new upgrades, renewals, and downgrades. These emails also compare the data with the previous week, providing quick insights into your product’s performance.

This week’s update brings two key improvements.

First, we have made the email more responsive, ensuring it displays better on smaller screens.

Second, we addressed an issue where the report included data for migrated payments and subscriptions. Freemius supports migrations from platforms like WooCommerce, EDD, and Lemon Squeezy, but since these payments weren’t processed through Freemius, their inclusion caused confusion for some makers. With this update, such data is now excluded, allowing the report to focus solely on transactions processed by Freemius.

Fixing duplicate emails

We also addressed an issue where duplicate emails were being sent in specific scenarios, such as Affiliate payouts. This bug has been resolved, and the system is now more resilient to prevent similar issues from occurring in the future.

As you sell with Freemius, you have various options for your payouts, including wire transfers, where the money is sent directly to your bank account.

You can transfer earnings from different currencies to the same or different bank accounts, with the option to convert the earnings to any target currency of your preference.

However, there are certain restrictions on wire transfers that are beyond our control. For example, transferring PKR (Pakistani Rupee) to a PK business account through wire transfer is not supported by regulation.

This week, we are rolling out updates to surface these restrictions directly in the UI as you configure your payout settings. This improvement will help you choose the right currency and avoid delays in receiving your payments. As always, we strive to make the payout process as efficient and transparent as possible—after all, it’s your money.

As part of our ongoing Data Liberation Project, we’re excited to announce a new capability: you can now download affiliate payout data directly from your Developer Dashboard!

Freemius’s built-in affiliate platform helps boost your marketing efforts by tracking all sales made through affiliate links and managing calculations for affiliate payouts. This data, available under the Payouts tab on the Affiliation page, can now be exported with ease.

This feature marks the completion of our Data Liberation Project. At Freemius, we value transparency and are committed to ensuring you have full control of your data. Now, you can access and take your data wherever you need.

If you missed earlier updates on this project, check out our detailed blog post to learn more!

We identified an issue where the requested currency was not being honored during Checkout if the plan_id parameter was missing.

Historically, we recommend including the plan_id parameter when using our Checkout. When it is not provided, the system defaults to loading the cheapest visible plan.

However, in such cases, the currency parameter was not being applied correctly, even when specified.

This issue has now been resolved, and the requested currency will be respected as intended.