Frequently Asked Questions

A curated summary of the top questions asked on our Slack community, often relating to implementation, functionality, and building better products generally.
Statsig FAQs

Can two different web projects share the same Statsig API keys and what is the impact on billing?

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.

Join the #1 Community for Product Experimentation

Connect with like-minded product leaders, data scientists, and engineers to share the latest in product experimentation.

Try Statsig Today

Get started for free. Add your whole team!

What builders love about us

OpenAI OpenAI
Brex Brex
Notion Notion
SoundCloud SoundCloud
Ancestry Ancestry
At OpenAI, we want to iterate as fast as possible. Statsig enables us to grow, scale, and learn efficiently. Integrating experimentation with product analytics and feature flagging has been crucial for quickly understanding and addressing our users' top priorities.
Dave Cummings
Engineering Manager, ChatGPT
Brex's mission is to help businesses move fast. Statsig is now helping our engineers move fast. It has been a game changer to automate the manual lift typical to running experiments and has helped product teams ship the right features to their users quickly.
Karandeep Anand
At Notion, we're continuously learning what our users value and want every team to run experiments to learn more. It’s also critical to maintain speed as a habit. Statsig's experimentation platform enables both this speed and learning for us.
Mengying Li
Data Science Manager
We evaluated Optimizely, LaunchDarkly, Split, and Eppo, but ultimately selected Statsig due to its comprehensive end-to-end integration. We wanted a complete solution rather than a partial one, including everything from the stats engine to data ingestion.
Don Browning
SVP, Data & Platform Engineering
We only had so many analysts. Statsig provided the necessary tools to remove the bottleneck. I know that we are able to impact our key business metrics in a positive way with Statsig. We are definitely heading in the right direction with Statsig.
Partha Sarathi
Director of Engineering
We use cookies to ensure you get the best experience on our website.
Privacy Policy