Growthbook

Overview

This third-party service is used for A/B experimentation and feature flags. This product is able to track customer metrics; for example: following a customer journey in an experiment that can lead to a higher add to bag rate that leads to conversion.

• Growthbook Dashboard
• Growthbook Chrome extension

Key features:

• Feature Flags
• Experiments (A/B/C)

---

Technical Direction

When utilizing Growthbook, we want to render the Growthbook experiment on the server-side then pass the data down into our client-side components. Rendering server-side prevents flickering and other React race conditions that can appear "glitchy" to clients.

We're also able to use this deferred loader information in different components in the codebase (if need be), so we don't have to consistently ping the Growthbook API/SDK.

---

Experiment Patterns

Depending on the scope of the experiment, there are two approaches for implementing Growthbook feature flags. Refer to the relevant doc for your use case:

• Component-level experiments — toggling styles, placements, or individual components within an existing page.
• Page model experiments — swapping entire page layouts via separate Builder.io page models per variant.

---

Troubleshooting

• If you're not seeing the feature appear in the Growthbook extension:
  • Make sure the experiment is running. If it's not production ready, uncheck production but keep qa and staging active.
• If you're not able to see the feature appear in the Growthbook extension, despite the experiment running:
  • Try to clear the extension cache in DevTools.