It is technically possible for two different web projects to share the same Statsig API keys. However, it is generally recommended to create separate Statsig projects for distinct websites with their own userIDs and metrics. This approach aids in managing each product independently. If you aim to track success across multiple websites, you may want to manage them in the same project. The decision ultimately depends on your specific use case and goals.
As for the impact on billing, it would depend on your usage. Statsig's pricing is based on Monthly Active Users (MAUs), which are unique users that interact with Statsig in a calendar month, regardless of how many API keys are used. If the same users are interacting with both projects, it would not increase your MAUs. However, if different sets of users are interacting with each project, it could potentially increase your MAUs.
When considering whether to create/use a new Statsig project, it's important to understand when it's appropriate to do so. You can refer to the guidance provided in the Statsig documentation. If you decide to create a new project, remember that the API keys are unique per project.
In conclusion, while it's technically possible to share API keys between projects, it's generally better to have separate keys for each project for easier debugging and management. The impact on billing is based on the number of unique users interacting with Statsig, not the number of API keys used.
Permanent gates do count towards billable events. An event is recorded when your application calls the Statsig SDK to check whether a user should be exposed to a feature gate or experiment, and this includes permanent gates. However, if a permanent gate is set to 'Launched' or 'Disabled', it will always return the default value and stop generating billable exposure events.
During the rollout or test period of a permanent gate, exposures will be collected and results will be measured. This is when the gate is billable. Once you Launch or Disable the gate, it is no longer billable. The differentiation with permanent gates is that it tells our system not to nudge you to clean it up, and that it will end up living in your codebase long term. More details can be found in the permanent and stale gates documentation.
If you want to launch a feature flag, but only set a subset group to true, you can achieve this with a Permanent, non-billable gate that targets a specific set of users. You can toggle off “Measure Metric Lifts”, but keep the gate enabled. You don’t need to click “Launch” using that other workflow.
Marking a gate as permanent effectively turns off billable events. This is a useful feature if you want to target a specific set of users without running up billable events.
Please note that we are continuously working on streamlining this process and improving the user experience. Your feedback is always appreciated.
Dynamic Config usage does not count towards the 1M free metered events.
When it comes to the propagation of changes in Dynamic Config, it is officially stated as "near real-time". While there is no precise time frame, changes are typically reflected in the services within 30 seconds of updating, based on anecdotal evidence. However, this is not a guaranteed service level agreement (SLA).
For server SDKs such as nodeJS, the update should happen automatically. Calls to getConfig will start returning the new value quickly. For client SDKs, updates do not occur in the middle of a session to maintain a consistent user experience. If you believe forcing a refresh is necessary, you might have to call Statsig.initialize again.
Please note that the above information is based on expert observations and official documentation, which can be found here.
If you need to change the owner of your account and upgrade your tier, but the previous owner has left the company, you can reach out to our support team for assistance. Please email them at support@statsig.com from an account that has administrative privileges.
Our support team can help you change the owner of your account and upgrade your tier. To do this, you will need to provide the email of the person you would like to change the owner to.
Please note that this process requires backend changes, which our support team can handle for you. Ensure that you have the necessary permissions and information before reaching out to the support team.