Hey team! We are having a lot of issues doing URL Split tests in GrowthBook. A/B tests are easy enough to do, but URL Split tests are a pain since we need to write custom JS. If we write the JS incorrectly, the customer gets in a loop, even the user, and correcting it is a big pain. Maybe we are using the tool incorrectly, so if anyone has feedback please share it. We would love to see this incorporated in the tool if you agree it is valuable.

we have growthbook implemented via Segment - when using the visual editor, is it possible to use event/attribute values to personalize the experience on the page via parameters/variables?

Hello team! Are there any plans for a Rust SDK? We are building a new product with Axum in Rust and would love to integrate with Growthbook to power a few feature flags here and there. No AB testing yet.

Hey team! Is there a plan to update the Dashboard to allow displaying metrics by tags? Tags are very useful and breaking down the metrics by tags might help drive further clarity into what kind of tests the team is running

Hey team! My company has been adopting the tool more and more and would love to have the option to re-brand the UI with our logo and perhaps the background color for the menu and/or the accent color for the buttons so that it matches our brand a little closer. This should be a "simple" feature that would make the tool more appealing to the users in general. Thanks for the consideration!

Hello all, I think a nice feature would be to have enumerations as a flag type. I know you can already achieve a similar thing with strings are with ints but this would add a touch more protection of the value from the server.

Hello everyone, I have been experimenting with API to manage (fact) metrics and building python class to manage them. I have realised that the API does not allow to manage all configuration as the UI does especially with the display setting (minimum number of event for instance). And since it's API managed it's not possible to change this after in the UI. It woulb be nice to be able to manage these configuration too

Potential issue: I've an experiment that times-out after 3 hours, when refreshing data Potential solution: Is it possible to turn off the health tab on 1 experiment? More details When we have an experiment that has complex SQL metrics (like new users who visited checkout) then the data refresh can take a really long time, and I wondered if it's pulling tons of data for the health tab as it once timed out on that query - GB said the query was a 47gb. If this is the case, it would be useful to be able to disable the Health tab/feature on an experiment. (As always I love using GB and loving the updates 🙂)

Hi, I love the new approval feature for feature flags- Are there any plans to create something similar for starting/stopping Experiments?

Visualisation of “gained confidence” I think to mitigate the early peeking problem, but at the same time allow for early stopping of tests it would be great to have a visualisation of the uplift over time as more data comes in. This would allow to see when test results stabilises, but at the same time also highlight (likely) false-positives due to fluctuations in the data

We have multiple Projects and my team is always forgetting to assign a Project when creating feature flags, which can cause frustration as it's not obvious why your feature isn't showing up where you would expect. This could be mitigated by adding the Project assignment field to the Create Feature modal. 🙏

Make it possible to edit Visual Editor code changes directly in the experiment config interface:

DBT Integration

Hi there. Do you plan to allow for DBT integration so that model documentation, for example, could also be shown on metrics calculations? We are transferring some models to DBT for version control, and it would be nice to have this possibility, to avoid too much effort on metrics maintenance.

Automatic refresh of (key) dimensions Would be nice to select some relevant dimensions for a test that are always automatically refreshed. Currently they always require a manual run, which makes it more cumbersome to get the full picture of an experiment.

Hi All, I opened a Github issue about this, but I wanted to check in here what people think. In my organization we run a lot of experiments where we need to filter for activation with specific tags. Right now it seems the way to set up metrics based on these filters is to set up an activation metric for each individual experiment. Firstly, I'm not sure if I'm just missing something and there is a good way to accomplish this? If there isn't a good way to do this currently, I could imagine that parametrized metrics would be a good way to achieve this. This would allow you to create custom variables that are accessible in queries so you could include something like

WHERE tag = {{ customVariable }}

I think this could be implemented relatively easily and I would be interested in working on it if it would be interesting.

Features can work across projects (unless I'm misunderstanding you). You just need to make sure that you set up an SDK connection for all projects and define the features under that.

Hey, I create a lot of custom reports, and it would be great to have: • Duplicate existing report to modify with all the metrics, change dimensions etc • Create templates that could be reused I prefer using custom reports as I can link them in docs for teams to look at the numbers, not just screenshots.

Not sure if it already works, otherwise consider it a suggestion - it would be great to have the option to be able to create saved groups using emails that contain wildcards. For example - my email address is lee@company.com. when testing features / our app we often create new user accounts and use a syntax like lee+test1@company.com. It would be great to be able to setup a saved group with a wildcard so i don't have to add lots of users to our internal test user saved group (e.g. lee+*@company.com to capture all test accounts i might create automatically).

Hi! We have a core set of metrics that we add to every single test. It would be great if we could define this as a pack (in the desired order) and add them with one click instead of selecting each one every time

Give user control over how activation metrics are used. Basically with a lookback window (could happen before experiment exposure) or only after (current config).

Hi. A suggestion to make power analysis easier to use would be remove the need to enter a mean and std deviation for each metric and estimated user per week by using historical data. The user would simply select a metric and select an ‘activation metric’ to represent the population going into the experiment. The analysis would then calculate required inputs using historical data.

Really need to identify experiments with temporary rollouts in the experiments list. I would say include them in the "Running" list but with some visual identifier.

Hi, I've been playing around with coderefs recently in our GB instance and I have a couple of things I think might make the feature more useful: 1. in our codebase right now we have a couple of long-lived branches (main, develop) I'd like to be able to "pin" these to the top of the list when showing code refs as these would generally be the most important references to any features in our apps and 2. provide a way to remove old code references once the branch they were submitted from has been deleted. I'm not sure if this exists already but I don't see anything about it in the github workflow documentation

"Hi, do you know how I can intercept the feature request in Android in order to map it? Thanks!"

Hi it would be great if we could add I.e click tracking on an element in the visual editor. The output could then be some event push on the datalayer

Hey, I want to ask about the interaction effects feature. I heard in a video that there are plans to develop this, and it might already be in progress. Any update would be great 🐿️

Hello, We do a lot of A/B tests where we add new functionality to a page, the new functionality almost always gets new tracking just so we can see the usage and how new features perform. Of course we can’t compare these numbers to the control as the functionality doesn’t exist there. So we would like to have a 4th type of metric in the reporting called “Informative metrics” which then only shows the metrics from the new feature and where we can also connect other existing metrics too like transaction rate etc. so we can compare these metrics with the baseline like for example do users that use the new functionality perform better compared to the default segment. Basically the goal is to get more holistic view that can help us iterate and optimise new features. Hope it makes sense if not I would be happy to jump on a call and explain more in detail. cc @kind-father-85802

Love the new metric correlations feature! Helps me understand the wisdom (or lack of) in using different funnel metrics. I have found that a single outlier can really destroy the visualization's utility though. Requesting Pan/Zoom controls to help remedy this.

How about a dimensional breakdown for other experiment variations? I'm thinking about how to build one into a data model. Not simple though.

Could there be an alternative to _`PROXY_HOST_PUBLIC` for internal requests?_ _For the SDK (client/server -> proxy),

PROXY_HOST_PUBLIC

is used_ _For GB -> proxy,

PROXY_HOST_PRIVATE

could be used_