Any publish event stops any A/B tests that are currently in progress and sets all A/B tests with an Active status to Inactive. This happens whether the site is published by a user clicking the publish button for a site, or by an auto-publish event that occurs after certain related events.
The related events which cause an auto-publish event to occur are:
Evaluation of a site is stopped or restarted.
The single-page application status is changed.
A change is made to an operating hours set that is used in a rule currently associated with a site.
A change is made to the WebCare account settings screen for the account which is used to access Engagement Engine.
A change is made in WebCare Link Builder to a call or chat invite that is used in a rule that is currently associated with a site.
All active tests are affected by a publish event and their status changes in accordance with the following table:
Test status before publish event | Test status after publish event |
|---|---|
Idle | Void |
In Progress | Incomplete and inactive |
Incomplete | Incomplete and inactive |
Complete | Complete and inactive |
If you try to publish a site, stop or start evaluation of a site or change the single-page application setting, a message is displayed warning you of the potential impact on your A/B tests. However, WebCare does not display any warning about the impact of making changes on your A/B tests, so it is important that anyone who might make changes via WebCare is aware of the potential impact on A/B tests.
