If you are using the synchronous provider and Server Side Rendering (SSR), the assignment reasons chart should be 100% with the reason “Bootstrap”. There should not be any “network”/“Cache”/etc. If you are seeing a lot of uninitialized values, it could point to a potential implementation issue.
One possible cause could be changes in the user object that you pass into the synchronous provider. If there are fields on the user object that you are loading asynchronously or in an effect elsewhere, it could trigger the SDK to update the values for the user.
To debug this issue, you should verify each of the render passes on the StatsigSynchronousProvider
and ensure that there is only a single render with a static user object. If the user object changes and it rerenders, it could lead to the issue you are experiencing.
If you are calling useExperiment()
in your code, make sure that the user
object passed into the provider is static and never changes. If the user
object changes after you bootstrap the StatsigSynchronousProvider
, it will cause the provider to re-fetch initialize values using a network request, effectively discarding the results passed to it through SSR.
It's also important to note that if you are using SSR correctly, you should never have a “network” reason. If you are seeing a “network” reason, it could indicate that your users are only going through the Client Side Rendering (CSR) flow.