We've lifted the limitation that prevented users from changing customers' billing currency.
The billing currency is now automatically determined according to the billing currency of customers' active subscriptions.
Customers can be billed in a different billing currency when they don't have any active subscription to paid plans.
We've added the ability to control the behavior of resettable metered features when customers update their subscription using no-code.
The new configuration supports the following options:
1. Always reset usage upon plan transition (default)
2. Never reset usage upon plan transition
3. Reset only if the subscription's billing anchor changes - this configuration is useful when you'd like to reset feature usage upon transition between free, paid and custom plans, and when switching billing periods (monthly <-> annually), while persisting the usage in all other cases.
The new configuration can be controlled separately for each product under the product's customer journey configuration.
Changes to the configuration would only affect future subscription updates, and does not apply retroactively.
Customers that report raw usage events to Stigg and leverage Stigg for aggregation and calculation of customer's usage of metered features can now leverage Stigg to also export these raw events to Snowflake and BigQuery.
With this change you can leverage the same scalable and reliable event ingestion pipeline as the source of truth for usage metering, enforcement and billing as well for usage business intelligence and analytics. Thus, saving you valuable development time and engineering resources.
Exporting data to Snowflake and BigQuery is available as an add-on to the Stigg Growth plan, and is included as part of the Stigg Scale plan.
To export raw usage events as part of this integration, contact Stigg Support.
We've added an ability to view the changes of all of the Stigg SDKs using an SDK changelog.
The changelog includes the SDK version, its release date and changes that were included in that version.
Each SDK has its own separate changelog allowing you to easily keep track of the changes, and make it easier to determine the implications of updating the SDK version in your application.
To access it, use this link.
We've redesigned the filtering experience in the Customer List screen of the Stigg app, and now allow you to define the filter criteria (Customer ID, Name, Email, Billing ID, etc.) and match type (exact match, starts with, ends with, contains). The applied filter is also kept when navigating back from the Customer Details screen of a specific customer. The default filter criteria is an exact match of the customer ID, which based on our analytics was the most commonly used criteria.
We also updated the behavior of our universal search to perform to filter customers and subscription using an exact match. The search behavior of other entities (products, plans, add-ons, etc.) remains the same as before.
With these new changes, navigating to a specific customer or subscription is now lightning fast ⚡️.
We've added an ability to control the default behavior of subscription downgrades using no-code via the Stigg app.
Stigg app users can select between the two most common SaaS best-practices:
By default, products in Stigg are configured to downgrade immediately.
Changing this behavior is possible using the Customer Journey configuration of the each product.
Publishing changes to the Customer Journey configuration affects all future subscription updates, and does not apply retroactively.
As part of continued effort in offering a state-of-the-art developer experience, we're excited to share that the Stigg app now supports a dark mode 🤩.
To toggle between the dark and light modes, use the icon in the top-right corner.
Dark mode is currently in beta and we look forward for your feedback!
The Stigg Checkout Widget consists of 3 steps - plan configuration, add-on selection and payment method selection.
We've added an ability to skip the plan configuration and add-on selection screens. With this change you can now open the Checkout Widget in the add-on step, which is helpful in upsell experiences using add-ons, or jump directly to the payment method selection screen when no subscription configuration is required by the user.
Skipping the steps is possible by passing the skipCheckoutSteps: ['PLAN', 'ADDONS'] parameter to the checkout provider component.
⚠️ Note that if the plan has multiple billing periods, a preferredBillingPeriod parameter must be provided in order to skip the plan step. In addition, if the plan has billable features, all of them must be provided in the billableFeatures input.
Skipping steps in the Checkout Widget is available in the Stigg React SDK from version 5.23.0 or later.
We've extended the Activity Log to include details of the API request that triggered each event and the response that was returned by Stigg.
Such information can be extremely helpful when troubleshooting the integration with Stigg.
The API request details are available under the "API request" tab when viewing the details of an event in the Activity Log.