We've extended our API and SDKs and now support 2 methods for reporting the usage of metered features:

1. Reporting of the usage change (delta) - for example: +A when A seats are provisioned, and -B when B seats are de-provisioned.

2. Setting the usage value - for example: C where C is the current seat count. This new reporting method is useful when the entitlement usage is calculated or aggregated by another data source.

To set the usage value, pass the updateBehavior.set property when reporting measurements.

Setting the calculated usage value is supported in the Stigg Node.js SDK v1.13.0 and Stigg Python SDK v0.5.0 or later.

More details can be found here.

We've made it easier than ever to access Stigg's thorough documentation, directly within Stigg Console using the in-app Intercom widget.

When you need additional information, simply enter the search criteria in the widget that appears at the bottom right of the screen.

Haven't found what you're looking for? No worries, Stigg's customer support representatives are only one message away!

We're also excited to hear your feedback! Leverage the in-app widget to tell us what you think about the product.

Stigg supports the creation of multiple environments in each account to support your existing product development process, for example: Development, Staging, Production, etc.

We've now made it easier to distinguish between the currently selected environment by allowing you to set a color for each environment.

Every time a new environment is created, a different color is automatically preselected to ensure that the distinction between the different environments is clear.

The environment color would then be reflected in the environment picker, as well as in settings section.

The new functionality makes it easier to determine in what environment changes to pricing and packaging are applied and convey the caution that should be taken while applying them, for example: 

1. Development environments can have a green color indicating that they're "safe" to edit.

2. Staging environments can have an orange color indicating that making changes to them.

3. Production environments can have a red color to indicate that applying changes to the environment should be made with the most caution.

We've added the ability to collect customers' phone numbers during checkout when Stigg is integrated with a billing solution.

The collected information is stored in a secure manner directly in the billing provider, and can then be accessed from there by sales representatives to further upsell customers to custom plans.

To collect phone numbers during checkout, simply include the collectPhoneNumber: true parameter in the checkoutOptions the provisionSubscription method.

The new functionality is supported in the Stigg Node.js SDK v1.9.0, Python SDK v0.2.0, and Ruby SDK v0.3.0 or later. More detail can also be found here.

We've extended the Stigg platform to allow you to offer localized pricing to your customers. 

Localized pricing allows you to expand to new markets by accommodating your product's pricing to the local willingness to pay. 

The new functionality can also be leveraged to test and gradually roll out pricing changes in specific geographies before rolling out the change to your main markets. 

Stigg's price localization functionality allows you to:

1. Offer your products using different price points in different countries, for example: $X USD in the US 🇺🇸, $Y USD in Israel 🇮🇱.
2. Offer your products in the local currency per country, decoupled from the current conversion rate, for example: $X USD in the US 🇺🇸, ₹Y INR in India 🇮🇳.
3. Display the localized prices to customers on your public pricing page and in-app paywalls.
4. When Stigg is integrated with a billing solution - bill customers in their local currency, including invoicing, payment collection and receipt generation.

Customers in countries for which no localized pricing has been defined will automatically fall back to using the product's default pricing.

Rolling out price localization to your product can be achieved directly from the Stigg Console using no-code after the initial integration with Stigg.

More details about Stigg's price localization functionality can be found here.

We've extended the no-code widget designer to allow you to customize the appearance of Stigg's widgets even further using CSS.

The new functionality allows you to integrate the Stigg widgets once into your public website or application and fully customize their appearance using no-code.

To customize your widgets' appearance using custom CSS - in the Stigg Console navigate to the Widgets section, select the relevant widget and scroll down to the "Custom CSS" section.

In the Custom CSS section, use the dot (.) to see the available class names that can be customized, for example .stigg-plan-offering-container. The full list is also available in our docs.

A preview of the custom styling will appear on the right side of the screen. To apply it to your public website and application, save the changes.

Custom CSS using the no-code widget designer is supported in the Stigg React SDK v1.26, Stigg Vue 3 SDK v0.9.0 and Stigg Vue 2 SDK v0.0.6 or later.

We've made it easier than ever for customers who use Google Workspaces to access your account in the Stigg Console - you can now do so by simply clicking on the "Login with Google" button in Stigg's login page.

Note that after you login with Google, all subsequent logins must also take place using Google, even if you've used a username and password to access the Stigg Console in the past.

Stigg's mission is to create a reliable and highly available solution that won't interrupt the mission-critical functionality of your application. To make sure that the critical paths are not affected, we have a few guardrails in place.

In the case where the entitlement local data is missing (for example: when a new feature is added to the codebase, but has still not been added to a plan) or our API is unreachable (for example: during a drop of internet connectivity), fallback values can be configured using the Stigg SDKs. 

We've extended the entitlement-check fallback strategy configuration, and now allow developers to define a global fallback strategy during the SDK initialization. 

The new configuration is supported in the Stigg Node.js SDK v0.76.0, Stigg JavaScript SDK v1.13.2 and Stigg React SDK v1.12.0 and later.

We're excited to share the general availability of support for persistent entitlement caching using Redis in the Stigg Node.js SDK.

By default, the Node.js SDK caches entitlement data in-memory to reduce the latency on subsequent entitlement checks. This approach is usually suffice when only one process or service is responsible for accessing the entitlement data.

By configuring the Node.js SDK to leverage a Redis server for caching, entitlement data becomes persistent, is synchronized even when accessed by multiple services and processes, and survives restarts. 

Persistent caching can also greatly reduce the latency of entitlement checks in application that leverage a serverless infrastructure, where each process is transient and can be de-provisioned after a limited period of time.

Persistent caching using Redis is supported by the Stigg Node.js SDK v0.7.5 or later. To enable it, please contact the Stigg Support Team.

More details about Stigg's persistent caching implementation can be found here.

As part of Stigg's support for scheduling downgrades when they're initiated by customers in a self-served manner, we've extended the Stigg Customer Portal widget to notify customers about the scheduled updates.

Using the updated widget, customers can also cancel the scheduled update and stay on the higher-priced plan.

The new change allows you to introduce a full-blown self-served SaaS subscription experience using only a few lines of codes. 

Communication of scheduled updates using the Stigg Customer Portal widget is available in the Stigg React SDK from version 1.11.1, the Stigg Vue 3 SDK from version 0.5.2, the Stigg Vue 2 SDK from version 0.0.6, and the Stigg JavaScript SDK from version v1.13.1.