Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: a/b testing doc V2 #8501

Merged
merged 22 commits into from
Nov 7, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
update signals step wording
Co-authored-by: Melinda Fekete <melinda.fekete@getunleash.io>
  • Loading branch information
nnennandukwe and melindafekete authored Nov 7, 2024
commit 0e24b90c1e2435f955adb801ca3ce6be18ed89a8
Original file line number Diff line number Diff line change
@@ -228,7 +228,7 @@ To use Unleash to conduct a multi-arm bandit test, follow these steps:
1. Collect the necessary data from each variant’s performance by enabling impression data for your feature flag
2. Capture impression events in your application code
3. Funnel the impression events captured from your application code to an external analytics tool
4. Create signal endpoints in Unleash that will point to your external analytics tools
4. Create [signal endpoints](/reference/signals) in Unleash and point them to your external analytics tools
5. Create [actions](/reference/actions) in Unleash that can react to your signals

Learn how to configure [actions](/reference/actions) and [signals](/reference/signals) from our documentation to get started.