Hello team, We run multiple brands within the same product ecosystem (same codebase, different brands). In growthbook, what is the recommended approach: using a single project with a brand attribute for targeting, or creating separate projects per brand?

both are fine - usually we see separate projects if you're running a lot of features/experiments

@fresh-football-47124 thanks a lot

you prob want the attribute regardless of how you organize via projects

Is there any documentation or guide for structuring growthbook in a multi-brand setup (projects vs attributes)? Would love to read more about recommended patterns.

I dont think we've written anything on that

I got you

projects allow you to have separate SDK end points, to reduce the payload size of unrelated features

Thanks, that helps. In our case features are mostly identical across brands, so I assume a single project with a brand attribute would likely be the better fit. Does that sound right?