A message from kapa.ai

Yes, you can use both the React SDK and the Go SDK simultaneously in your application. GrowthBook ensures consistency across all its SDKs by using the same hashing functions. This means that as long as you are passing in the same user attributes in both places, users will get the same variation on both front and back end. This helps to avoid any discrepancies in experiment targeting [source](https://linen.growthbook.io/t/2926235/hi-there-i-m-setting-up-growthbook-for-a-react-app-dotnet-co). However, there are a few things you should be aware of: 1. If you are using both SDKs on the same page, there could be potential conflicts. For instance, if both SDKs trigger the same visual experiment at the same time, there is a chance the rendering could be affected, or that double tracking calls would trigger. This can be mitigated by using different keys for each SDK connection or by using project filtering in each SDK connection to help avoid conflicts [source](https://linen.growthbook.io/t/22727962/hiya-because-of-the-way-our-website-is-built-in-we-have-both). 2. If you are using the Go SDK, be aware that some users have reported issues with real-time updates of feature flags. The GrowthBook team is aware of these issues and is actively working on resolving them [source](https://linen.growthbook.io/t/16076759/i-use-go-sdk-http-github-com-growthbook-growthbook-golang-20). 3. Always ensure that your SDKs are up-to-date. GrowthBook periodically updates its SDKs, and using an outdated version could potentially lead to issues [source](https://linen.growthbook.io/t/10028712/hi-team-would-there-be-any-issues-if-we-hosted-the-growthboo). For more detailed information on how to use the SDKs, you can refer to the official GrowthBook documentation [source](https://docs.growthbook.io/lib).

Yes, you can use both the React SDK and the Go SDK simultaneously in your application. However, there are a few things you should be aware of: 1. SDK Keys: If you are using the same key for both SDK connections, they should work nicely together. However, if you are using different keys, there might be a chance of conflicts. If both SDKs trigger the same visual experiment at the same time, the rendering could be affected, or double tracking calls could be triggered. This should be mitigated by using different keys. You could also try using project filtering in each SDK connection to help avoid conflicts. 2. Consistency Across SDKs: GrowthBook uses the same hashing functions to ensure consistency across all their SDKs. So, assuming you are passing in the same user attributes in both places, users will get the same variation on both front and back end. 3. Updates and Syncing: GrowthBook periodically updates the SDKs, so be careful of the app and the SDK getting out of sync if you host the GrowthBook package on your own server. Remember to check the official documentation for each SDK (React SDK and Go SDK) for specific implementation details and best practices. Sources: [Forum Conversation > T > 22727962](https://linen.growthbook.io/t/22727962/hiya-because-of-the-way-our-website-is-built-in-we-have-both), [Forum Conversation > T > 2926235](https://linen.growthbook.io/t/2926235/hi-there-i-m-setting-up-growthbook-for-a-react-app-dotnet-co), [Forum Conversation > T > 10028712](https://linen.growthbook.io/t/10028712/hi-team-would-there-be-any-issues-if-we-hosted-the-growthboo).

New message text here