Tried to do some searching on this so forgive me if this has already been answered. For non self hosted usage, should the api keys be kept out of source control? First thought was yes but you would not be able to avoid that if using frontend clients. Might be a trivial answer that I missed in the docs as well. If this is unavoidable is self hosting a solution if we want to prevent anyone from accessing our feature flag data?

Hello everybody! I am trying to integrate growthbook experiments. So far I am fetching proper data from growthbook, but it seems that something might be wrong with my approach. I created simple experiment with default variations

Control

and

Variation 1

in my case I am just switching between GREEN and RED box. In experiment configuration I gave 100% traffic and

0/100 split

in favor of

Variation 1

. Unfortunately I am still receiving output for variation

Control

instead of only

Variation 1

. If there is anybody who would like to have a look at my dummy repo feel free to check it out https://github.com/krzysztofpodmokly/growthbook (Add your

apiKey

in

index.js

line 36). Repo created with

nextJS

basic template,

npm run dev

to run it. Once

devTools

are opened you can manipulate

userId

in

Application

tab. Thank you in advance!

Hi there! 👋 We're working with the growthbook python sdk and we found an unexpected behaviour. Let me address it and share the details in the thread below: 👇

Hi! I'm having yet another issue when adding a data source. I'm trying to add Google Analytics but I get an error when trying to authenticate. Also, I am logged in to my company's gmail account, which also has acces to GA so I'm not sure why it's not working. We are not using Google Analytics 4, and there are no other data sources added(also, I deleted

config.yml

).

Posthog has a feature comparison page for 5 feature flag solutions incl. GrowthBook, do you think it’s a fair and up to date comparison? https://posthog.com/product/feature-flags

Hi, a few quick questions: • Will doing the "Inline experiment" automatically create the experiment in GrowthBook just based on the events we send or do we still need to create the experiment? • For people using it with Segment: ◦ Does or can GrowthBook send any automatic events via Segment (like experiment viewed) or do we need to explicitly add those in callbacks? Cause based on the docs here: https://docs.growthbook.io/app/features#experiments it sounds like it does tracking (sending events) automatically? ◦ Do we need to explicitly set an attribute for ID (user id or anonymous ID) on init or does it pick it up automatically from Segment data somehow?

Hi guys! I had a doubt the other day about computing the average of CTR, when the observed unit is a user. 1. Should I compute the avg. CTR per user, instead of (all Clicks) / (all Impressions)? To maintain the units independency; 2. Should I compute the harmonic mean instead of the aritmethic mean, since i'm averaging rates?

I read the docs on setting capped values, but I’d love to know how people approach setting a cap. Are you reviewing the distribution of values per user and setting based on the 95/99% value, for example? Many of our metrics are skewed, with most values low and a long power law tail to the right.

Hi everyone! I'm trying to use Growth Book android kotlin SDK. I just wanna know is there any way to use it on android SDK version 21 and above?

Encountering some bizarre behavior with

@growthbook/growthbook-react

. We’re using

nx

as our mono-repo tool, which could likely be a factor. We have a specific

feature-flags

package that houses our

FeatureFlagContextProvider

component which renders the

GrowthbookProvider

. This gets imported and rendered at the root of our

web-app

(separate “package”). If I write some code to

useFeature

in either of these packages we have no problems. We then have a separate

queries

package that houses all of our

react-query

queries for loading application data. I was attempting to use a feature in one of the queries, however, in debugging it was clear that this line in

useFeature

const { growthbook } = useContext(GrowthbookContext)

was the culprit in that

growthbook

was

undefined

. It’s interesting because if I call the function that wraps this logic side by side with

useFeature

in

web-app

, the

useFeature

in

web-app

correctly gets the feature value whereas the one in

queries

is unable to because

growthbook

is

undefined

. Anyone encounter a similar issue ever?