Timeline for In Sitecore XP, how can I personalize 2 different components with the same rules and track the effect on drop rate of the site?
Current License: CC BY-SA 4.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 21 at 8:08 | comment | added | Anna Bastron | @AronBender great, glad you sorted it! | |
| Aug 20 at 16:59 | comment | added | Aron Bender | I was able to locate the problem. It turns out my server setup was correct, but a while back, I implemented a workflow and accidentally assigned it as a default to the Standard template's Standard values. So any of the items that are part of workflow processing are inheriting that and not getting published as part of the test. I appreciate all of your help in this. | |
| Aug 20 at 14:42 | comment | added | Anna Bastron |
@AronBender I had this problem a few times - the issue with config happened on 9.2 but applicable to any version (basically the setting Xdb.Tracking.Enabled was set to "false" on the Processing server by mistake and A/B test data aggregation was not working). Another one was just after upgrading to 10.2, the Reporting DB was not fully upgraded and its schema was not compatible with Processing server requests. There can be various reasons causing this, so I'd recommend going through all steps to find where exactly the data is lost and then checking logs and configs on that server.
|
|
| Aug 20 at 13:38 | comment | added | Aron Bender | what version of Sitecore are you on? | |
| Aug 20 at 7:12 | comment | added | Anna Bastron | @AronBender please try troubleshooting steps from this article linkedin.com/pulse/…, I had a similar problem in the past where Experience Analytics was working but tests were not showing any results and it turned out the problem was in the Processing role config files. Though you may have a different issue so it's worth going through all troubleshooting steps. | |
| Aug 19 at 15:37 | comment | added | Aron Bender | I realize I marked your answer as complete, but I'm noticing that no data is being colelcted for the test. The test is started and both versions exist in the Web DB. Furthermore, I was able to confirm seeing both versions of the page in quickly testing in Incognito mode. We are certainly collecting data (experience anlytics shows a lot). | |
| Aug 19 at 14:31 | vote | accept | Aron Bender | ||
| Aug 15 at 14:50 | comment | added | Anna Bastron | @AronBender no worries, if it all works as expected for you, feel free to mark this answer as accepted by adding the green tick next to it :) | |
| Aug 15 at 14:36 | comment | added | Aron Bender | Thanks again. This was excellent information. | |
| Aug 15 at 14:18 | comment | added | Anna Bastron | @AronBender no problem, I've included relevant documentation links and updated the answer with details about the drop off rate - hopefully the Bounce rate metric is what you need! | |
| Aug 15 at 14:16 | history | edited | Anna Bastron | CC BY-SA 4.0 |
updated with additional details about test objectives
|
| Aug 15 at 13:08 | comment | added | Aron Bender | Your answer and @ckhanna's answer are very similar (yours was posted first). Would you mind editing your answer to include a link to the documentation as his does? | |
| Aug 15 at 13:05 | comment | added | Aron Bender | Thank you for this! This makes total sense, but was hoping you could answer one more part of my question. How do you determine drop rate in a page test? We are basically trying to determine whether or not, based on the content variability, if they stay on our site or drop off at a greater rate. | |
| Aug 15 at 8:39 | history | answered | Anna Bastron | CC BY-SA 4.0 |