Skip to content

Commit

Permalink
set up web exp doc tweaks
Browse files Browse the repository at this point in the history
  • Loading branch information
SpencerFleury committed Oct 16, 2024
1 parent de3968f commit b361b62
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 7 deletions.
11 changes: 6 additions & 5 deletions content/collections/web_experiment/en/set-up-a-web-experiment.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ id: b8db5ecf-b7b0-432d-b1f3-19ae70d13291
blueprint: web_experiment
title: 'Set up a web experiment'
updated_by: 5817a4fa-a771-417a-aa94-a0b1e7f55eae
updated_at: 1728677939
updated_at: 1729099005
this_article_will_help_you:
- 'Understand the difference between a Web Experiment and a feature experiment'
- 'Build a Web Experiment using the Visual Editor'
Expand Down Expand Up @@ -54,13 +54,14 @@ If the script isn’t present on the page you specified, Amplitude Experiment ca

Before running your web experiment, Amplitude recommends that you test and preview each variant. Once you're ready:

1. Click the **Test & Preview** button. This doesn't start your experiment, it puts your experiment in test instrumentation mode. Only users who open the page with the preview link can see your changes.
2. In the modal, select the variant you want to preview (usually the treatment) and select **Test in new window**.
3. A new tab opens with the changes you made to the page applied.
1. Click *Test & Preview*. This puts your experiment in test instrumentation mode, but it **doesn't** start your experiment. Only users who open the page with the preview link can see your changes.
2. In the modal, select the variant you want to preview (usually the treatment) and select *Test in new window*.

A new tab opens with the changes you made to the page applied.

Test each variant at least once, and testing on more than one page if your experiment targets multiple pages.

If you don't see your changes applied, **you may need to wait up to 60 seconds** for caches to refresh to see the updated preview. If the changes don't appear correctly after 60 seconds, there might be something wrong with the configuration.
If you don't see your changes, **you may need to wait up to 60 seconds** for caches to refresh. If the changes don't appear correctly after that time, there might be something wrong with the configuration.

## The Visual Editor

Expand Down
2 changes: 0 additions & 2 deletions content/trees/collections/en/sections.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -10,8 +10,6 @@ tree:
-
entry: 4cb8166f-a1a1-44dc-9b76-f2fb51db6b05
children:
-
entry: 7ba36066-3d54-4874-a407-504b27d83a26
-
entry: 427fa0c0-c489-48df-a147-cfe636b803b8
-
Expand Down

0 comments on commit b361b62

Please sign in to comment.