[BD-3161] Feature flag experiments | Release Date TBD

[internetisaiah]

Pull Request/Issue Resolution

Description of Change:

New documentation for feature flag experiments.

• Ticket: BD-3161

TODO

• Create draft
• Add screenshots
• Reference in Campaign Analytics.
• Reference in Report Metrics.

Is this change associated with a Braze feature/product release?

• Yes (Insert Feature Release Date Here)
• No

---

✔️ Pull Request Checklist

• Check that you haven't removed any images (replacing an image with an updated one of the same name is fine), as this breaks the French site
• Check that all links work.
• Ensure you have completed our Contributors License Agreement.
• Tag @josh-mccrowell-braze and @internetisaiah as a reviewer when your work is done and ready to be reviewed for merge. Are you an internal product manager? Reference the internal reviewing chart to tag the appropriate reviewer.
• If the documentation involves a 1) paid SKU, 2) a third party, 3) SMS, 4) AI, or 5) privacy, ensure that Ana Teresa Serafino on the Legal team has signed off.
• Tag others as reviewers as necessary.
• If you have modified any links, be sure to add redirects to assets > js > broken_redirect_list.js

⭐ Helpful Wiki Shortcuts

• Writing Style Guide
• Image Style Guide
• Styling Test Page

❗ ATTN: For PR Reviewers

• Read our Reviewing a PR page for more on our reviewing suggestions.
• Read our Previewing Documentation page to see how to check the deployment.
  • Preview all changes in the linked Vercel environment by clicking the preview link in the vercel-bot comment in your PR.

❗ ATTN: Internal Reviewing Chart

Work at Braze and not sure who to tag for review?
Before tagging @josh-mccrowell-braze or @internetisaiah for a general review, reference the following chart to see if a specific product vertical/reviewer applies to your pull request.

Reviewer	Product Vertical
@josh-mccrowell-braze	Monolith Deployments Quality Infrastructure Platform Infrastructure Datalake SDKs Currents
@internetisaiah	Developer Guide Technology partners Channels
@bre-fitzgerald	Intelligence In-App Messages Channels Frontend Infrastructure & Experience (FIX)
@lydia-xie	Ingestion Core Objects Core Messaging Messaging Experience Message Components Email (Composition and Infrastructure) (tag @rachel-feinberg for Liquid use cases)
@rachel-feinberg	Customer Lifecycle, Identity and Permissions SMS User Targeting Reporting

[internetisaiah]

Note: Waiting on PM for a populated test environment to get screenshots.

[internetisaiah]

From DM with @bkasman95 : we are still waiting on engineering for a (semi) populated test environment for this.

[internetisaiah]

@bkasman95 : what is meant by "dimensions"? is that a term that we widely use throughout the product/docs? or is there another/more specific term? I'm unfamiliar with marketing lingo, so i'm not sure either way.

[internetisaiah]

@bkasman95 qq: what are some of the metrics that a user can find here? just want to list a couple as an example here.

[internetisaiah]

still waiting on engineering for a test environment. relevant ticket here: https://jira.braze.com/browse/GE-3514

[internetisaiah]

FYI, still waiting on engineering for test environment. Reached out to relevant stakeholder again today 🫡