Sitecore Goals are activities that visitors can perform on your website. You create goals to track and measure how visitors engage with the website and campaigns. Normally, a user may trigger a goal when performing a successful registration or buy it now. You may receive some requirements from clients which say that goal should be triggered only once per user.
Following my article on Sitecore with Personalization At Scale, I am writing this one today to give more insight about how to use Microsoft Cognitive Services – Recommendation API with Sitecore Profile Cards. I’ll be explaining how to use the result from the Recommendation API and to tag content. What I want to achieve with Sitecore and Recommendation API is to show anonymous users contents which will drive more registration and once registered on the site, to show users contents to perform buy it now or post review actions.
The title of this article is self described. There are some cases where you want to index some items but not all of them. Within the Sitecore Index Configuration file, you normally create a crawler with the database property and the root. The root is the path where you want to the item and its descendants to be indexed.
It’s been a while since my last post. I was taken up with a new major project. So, today, I will share with you a summary of the Sitecore Personalization At Scale. This was a presentation performed by my co-worker Jo Bobo. The presentation was based on how to use Sitecore Personalization to drive content with respect to a situation.
During the past few months now, I have been working mainly on the Sitecore Analytics. On one of our environment, our logs were being flood with an error. The error was “Failed to synchronize segments”. Even though the same issue was raised on the Sitecore Stack Exchange here, I will write up a summary or checklist if you want on how we got this issue fixed.
Sitecore Analytics Aggregators are pipelines required to emit data from MongoDB to the Reporting DB. The aggregators get executed every minute. This pipeline is responsible to aggregate the different values collected in the MongoDB, example, number of visits, goals triggered and so on, and push them the to SQL database.
Following my blog post about Sitecore Cache, I wanted to extend the current Sitecore Cache page to another level. Currently, the default cache page (http://yourdomain/sitecore/admin/cache.aspx) only allows you to clear all the cache. This may be a small post today but I’ll try to explain what is the Sitecore Cache Extension page.