Skip to main content
Sitecore

Return to Answer

deleted 16 characters in body
Source Link
Dmytro Shevchenko
Dmytro Shevchenko
  • 12.6k
  • 2
  • 45
  • 90

I know you have already found the exact solution for your particular case. Still, I'm going to list the steps I normally take when troubleshooting data saving issues in xDB. Hopefully, this can help others in the future.

  1. Ensure the analytics connection string is set up properly in the ConnectionStrings.config.
  2. Make sure that you have a valid xDB license. You can see the list of available licenses in the Control Panel –>> Administration –>> Installed licenses. "Sitecore.xDB.base" should be present in that listthere.
  3. Make sure that xDB and its tracking subsystem are enabled. The settings Xdb.Enabled and Xdb.Tracking.Enabled should be set to true when you open this page: /sitecore/admin/ShowConfig.aspx.
  4. The configuration file Sitecore.Analytics.Tracking.Database.config should be enabled.
  5. Tracking should also be enabledEnable tracking on your site definitions—definition by setting enableTracking should be set to true for your site in the <sites> section.
  6. Try making several page requests instead of just one before letting the session expire.
  7. Ensure that all of your layout pages contain the VisitorIdentification control in the <head> section. In MVC layouts, use @Html.Sitecore().VisitorIdentification(); in ASP.NET WebForms layouts, <sc:VisitorIdentification runat="server" />
  • In MVC layouts, use @Html.Sitecore().VisitorIdentification();
  • in ASP.NET WebForms layouts, use <sc:VisitorIdentification runat="server" />.
  1. Try disabling robot detection by setting both Analytics.Robots.IgnoreRobots and Analytics.AutoDetectBots to false. The original values for these settings are located in the Sitecore.Analytics.Tracking.config. If interactions are saved after this, it means your visitors are stillwere recognized as robots.
  2. If nothing helps, go through the steps listed in the article Troubleshooting xDB data issues.

I know you have already found the exact solution for your particular case. Still, I'm going to list the steps I normally take when troubleshooting data saving issues in xDB. Hopefully, this can help others in the future.

  1. Ensure the analytics connection string is set up properly in the ConnectionStrings.config.
  2. Make sure that you have a valid xDB license. You can see the list of available licenses in the Control Panel –> Administration –> Installed licenses. "Sitecore.xDB.base" should be present in that list.
  3. Make sure that xDB and its tracking subsystem are enabled. The settings Xdb.Enabled and Xdb.Tracking.Enabled should be set to true when you open this page: /sitecore/admin/ShowConfig.aspx.
  4. The configuration file Sitecore.Analytics.Tracking.Database.config should be enabled.
  5. Tracking should also be enabled on site definitions—enableTracking should be set to true for your site in the <sites> section.
  6. Try making several page requests instead of just one before letting the session expire.
  7. Ensure that all of your layout pages contain the VisitorIdentification control in the <head> section. In MVC layouts, use @Html.Sitecore().VisitorIdentification(); in ASP.NET WebForms layouts, <sc:VisitorIdentification runat="server" />
  8. Try disabling robot detection by setting both Analytics.Robots.IgnoreRobots and Analytics.AutoDetectBots to false. The original values for these settings are located in the Sitecore.Analytics.Tracking.config. If interactions are saved after this, it means your visitors are still recognized as robots.
  9. If nothing helps, go through the steps listed in the article Troubleshooting xDB data issues.

I know you have already found the exact solution for your particular case. Still, I'm going to list the steps I normally take when troubleshooting data saving issues in xDB. Hopefully, this can help others in the future.

  1. Ensure the analytics connection string is set up properly in the ConnectionStrings.config.
  2. Make sure that you have a valid xDB license. You can see the list of available licenses in the Control Panel > Administration > Installed licenses. "Sitecore.xDB.base" should be present there.
  3. Make sure that xDB and its tracking subsystem are enabled. The settings Xdb.Enabled and Xdb.Tracking.Enabled should be set to true when you open this page: /sitecore/admin/ShowConfig.aspx.
  4. The configuration file Sitecore.Analytics.Tracking.Database.config should be enabled.
  5. Enable tracking on your site definition by setting enableTracking to true for your site in the <sites> section.
  6. Try making several page requests instead of just one before letting the session expire.
  7. Ensure that all of your layout pages contain the VisitorIdentification control in the <head> section.
  • In MVC layouts, use @Html.Sitecore().VisitorIdentification();
  • in ASP.NET WebForms layouts, use <sc:VisitorIdentification runat="server" />.
  1. Try disabling robot detection by setting both Analytics.Robots.IgnoreRobots and Analytics.AutoDetectBots to false. The original values for these settings are located in the Sitecore.Analytics.Tracking.config. If interactions are saved after this, it means your visitors were recognized as robots.
  2. If nothing helps, go through the steps listed in the article Troubleshooting xDB data issues.
Source Link
Dmytro Shevchenko
Dmytro Shevchenko
  • 12.6k
  • 2
  • 45
  • 90

I know you have already found the exact solution for your particular case. Still, I'm going to list the steps I normally take when troubleshooting data saving issues in xDB. Hopefully, this can help others in the future.

  1. Ensure the analytics connection string is set up properly in the ConnectionStrings.config.
  2. Make sure that you have a valid xDB license. You can see the list of available licenses in the Control Panel –> Administration –> Installed licenses. "Sitecore.xDB.base" should be present in that list.
  3. Make sure that xDB and its tracking subsystem are enabled. The settings Xdb.Enabled and Xdb.Tracking.Enabled should be set to true when you open this page: /sitecore/admin/ShowConfig.aspx.
  4. The configuration file Sitecore.Analytics.Tracking.Database.config should be enabled.
  5. Tracking should also be enabled on site definitions—enableTracking should be set to true for your site in the <sites> section.
  6. Try making several page requests instead of just one before letting the session expire.
  7. Ensure that all of your layout pages contain the VisitorIdentification control in the <head> section. In MVC layouts, use @Html.Sitecore().VisitorIdentification(); in ASP.NET WebForms layouts, <sc:VisitorIdentification runat="server" />
  8. Try disabling robot detection by setting both Analytics.Robots.IgnoreRobots and Analytics.AutoDetectBots to false. The original values for these settings are located in the Sitecore.Analytics.Tracking.config. If interactions are saved after this, it means your visitors are still recognized as robots.
  9. If nothing helps, go through the steps listed in the article Troubleshooting xDB data issues.