Solution (For XP 8.1 And Later)
Change the ContentTesting.AutomaticContentTesting.Enabled setting value to false in the App_Config\Include\ContentTesting\Sitecore.ContentTesting.config file:
<setting name="ContentTesting.AutomaticContentTesting.Enabled" value="false" />
Just like personalizations, the AB tests are stored on the rendering fields. If you are able to see the AB test on the Experience editor so it means that the test has been set.
Now where does Sitecore store the tests items it associate with my page?
On the Marketing Control Panel /Test Lab bucket. If you open the content editor and search for the existing ...
By, almost literally, stepping outside the box. If I'm reading you right, you want to test the following
Original Banner versus Personalised Banner, the latter of which can be one of 3 different data sources. One way to go about it is to swap containers as opposed to swapping content. Bit difficult to explain, but it goes like this:
Create 2 very simple ...
It's unsupported. By Microsoft, so by extension that would mean Sitecore as well.
Azure PaaS runs in what they call a sandbox. It's a restricted environment that only supports in part, what you would normally be able to do in your application.
In the list of unsupported frameworks for the sandbox, we find
Other scenarios that are not supported:
Content Testing has associated roles to allow different capabilities. Per the Experience Optimization and Content Testing FAQ:
There are several security roles that provide access to different
levels of functionality in Experience Optimization.
Authoring – enables the creation, running, and editing of tests. You
typically assign this role to ...
If you go to your page test definition in the content editor under /sitecore/system/Marketing Control Panel/Test Lab after the draft has been saved, you can see that there is a Conversion field that allows you to select multiple goals. However, the Winner Strategy that is provided out-of-the-box, Sitecore.ContentTesting.Analytics.WinnerStrategies....
Is not needed because I can see Rebuild Suggested Test Index commmand is using sitecore_suggested_test_index index.
Sitecore search indexes required for different types of servers in a scaled environment can be seen in below picture :
The information of which variation a particular visitor got should be stored in the Interactions Collection of your Analytics Mongo DB. You can look at a particular Interaction and look at the Pages element in the interaction. There is a lot of information in there that you should be able to see.
Once you find that information in your Mongo DB, then you ...
If you have set the Sitecore setting ContentTesting.AlwaysShowTestCandidateNotification to true but you still do not see the "Create a test" link, it may be because that link will only display if the current item does not have workflow. If you have workflow on the item, then you will need to use the workflow approach to content testing (which means you may ...
In Sitecore 8.1 and above there is a setting which can be turned on to allow the content authors to start test via experience editor.
Please add the below settings either as patch config file or
You can edit the value in the config file (Sitecore.ContentTesting.config).
Setting name is “ContentTesting.AlwaysShowTestCandidateNotification”
Goals are critical to measuring the performance of tests since Sitecore measures content effectiveness of test variations based on value delivered, not just clicks through.
As for the effect, I believe that % is the effect that the test had on the overall engagement value generated on the website - so if you have goals elsewhere on the site it is ...
There is an easy way to do this by editing the link of your call to action in sitecore.
In the querystring value of the link, enter in: sc_trk=goalname
(so if your goal is named "LinkAction1" , then enter sc_trk=LinkAction1)
Save and publish that, and it will only trigger that goal if a user clicks that call to action button.
If you want to include 100% of page visitors in your personalization test, you need to make sure the exposure is set to 100%.
If you're personalizing, you're delivering that personalization through Sitecore components. Make your first data source of the component the default (non-personalized). Then add the personalized versions of the content. Now, ...
The reason why the traffic doesn't split 50/50 when using the Subgroup Round Robin Sticky test strategy is because your page has some components on the page with personalization rules.
This is how Subgroup Round Robin Sticky test strategy is described on the official Sitecore documentation:
The Subgroup Round Robin Sticky test strategy is similar to the ...
I've contacted with Sitecore support for this and they have confirmed there is no out of the box report that retrieves detailed statistics for a/b test variants and registered a feature request to add it in future versions of Sitecore.
In the meantime, we can retrieve this data directly from the collection database. The information about the a/b variant is ...
The name of this index is also specified in the master database separately from configuration files. In order to properly rename this index, you must also update the Index Name field on the following item:
/sitecore/system/Tasks/Commands/Content Testing/Rebuild Suggested Tests Index
I like to think about Content Testing like the scientific method: you have a guess (hypothesis) and then you have to try it out (experiment) and then you see if it worked (measure and learn).
Content Testing for Variant Experiments
Typically, it is a marketer or author who is interested in Content Testing. They have some piece of content on the page and ...
Turns out this feature is supported. In the Test environment where it wasn't working it was related to the Azure WAF blocking the content for some reason. Then it worked fine in UAT and Production (which was under a different WAF).
We encountered this issues earlier on Sitecore 9.0.2 that it was neither showing the previews nor saving the screen shots. Do you see any errors on the logs file? We had the following exception in logs:
16:13:57 ERROR [Content Testing]: Cannot find PhantomJS executable at 'C:\inetpub\wwwroot\MYWEBSITE\App_Data/tools/phantomjs/phantomjs.exe'. Aborting ...
Yes. What you’re doing can’t be done.
1) Tests run on ID level. Item ID. There’s no information collected that would allow you to distinguish multiple versions of an item
2) Only the latest publishable version of an item ever makes it to “web” when you publish.
You need to create multiple copies of your item to test.
I've not done this specifically, but I suspect you could find what you're looking for by inspecting the Analytics database's tables.
You can find out the server and database name by looking in your connection strings for the reporting connection string.
You're on the right track. What you're looking for is a component test, not an A/B test. The A/B test tests a full page against another page or version of the same page. The component test applies a test against all the component variations on a page. Any time you personalize a component (e.g., active member gets component variant A) you have the ability ...
The approach you mention is suitable for when you want to include Rendering Parameters in your A/B test. For just switching between two components however, it is not necessary,
What you need to do, is enable Personalize the presentation of the component. This allows you to select between your Hero and Video components.
More information here: Walkthrough: ...
As long as a component has been added to a placeholder, it can be tested. I assume by static component, you mean something like a breadcrumb that wouldn't typically be editable by a content author. In that case, you could edit do an MV test from inside the presentation details. I'd see this as an edge case and something that we'd want to keep content ...
For your scenario, unfortunately, the answer is that you should use a component test. This does involve duplicating the datasource item (and any other items you want to change related to it).
Page test - usually used for when you move components about or change them on the page
Component test - usually used when you're testing the content of a component (...