Sitecore reporting database rebuild issue

Help, I'm seeing guids in my reports!

So I had this environment where my reports were missing data I was surely having in my xDB database. I double checked this. So my only conclusion was that at some point the reporting database was missing data and I needed to rebuild it. As my version is 8.2 update 5 I followed the manual from this link to the letter. Everything seemed to work ok, until I switched to the fresh reporting database and I started looking at my reports 😧 All goal names, page names etc. were displayed with their item ID guids and not there (display)names. 
I checked the xhr call to the Sitecore api's and saw messages about segments not found and missing translations. 
I figured ok, let's just rebuild indexes, rebuild links and hopefully things will start to work again. WRONG!!
After some digging around I found out that at some point apparently my marketing definition have been redeployed setting the deploy dates of my segments to a date after many of my data was collected. This turned out the be the issue. So what I actually had to do was reset this deploy date in the Analytics database table 'Segments' to something like a year ago, reset my environment and suddenly everything was ok again, including my previously missing analytics! 

So if you run into the same thing, make sure to double check the deploy date of your segments.

Reacties

Een reactie posten

Populaire posts van deze blog

I Robot - Sitecore JSS visitor identification

While working on a Sitecore JSS solution that interacts with our Sitecore solution that hosts some api endpoints for us and add .net session state to cache some user bound data we noticed some unexpected behavior with respect to the session state on our test environments. Our session was configured to expire after 20 minutes of idleness, but no matter what our behavior was: idle or active our session seem to be reset much faster. After much debugging we couldn't find anything wrong with our own code, so we started considering options where maybe Sitecore could influence this. One of the suspects was Sitecore's robot detection mechanism that had given us trouble around session expiry in the past. We started by disabling robot detection. And this indeed seemed to resolve our session disappearing issue. So it was confirmed, we were identified as a robot. Further information proved that indeed, when classified as a robot visitor, Sitecore analytics settings set the session e
Meer lezen

Sitecore campaigns and UTM tracking unified

Afbeelding
Sitecore and UTM  A lot of blogs have been written about Sitecore vs Google Analytics and how they can be complimentary. In many of the implementations I have seen, marketers use these tools side by side.  As marketers seem so fond of Google Analytics and have a hard time parting with it to only use Sitecore, I figured, why not make them work at the same time. Marketers seem to be more familiar with setting up campaigns using UTM than setting them up with custom parameters for Sitecore campaigns, so why not make Sitecore work with these UTM parameters as well.  So what I did is make it configurable in Sitecore to hookup UTM parameters to Sitecore campaigns. This blog shows how I did that. Setting up your templates I started by defining a template where you can tie these together. Field1: UTM Source key Single-line text to copy your UTM source key into Field2: Linked Campaign A droptree field with a query, something like this: query:/sitecore/system/Marketing C
Meer lezen

Sitecore JSS - Sitecore first

JSS - Sitecore First! Recently I started a project where we are upgrading an existing Sitecore 9 MVC portal with AngularJS to Sitecore JSS with Angular 7. With this portal being already implemented, and content preexisting in the solution we wanted to start this with a Sitecore first approach. In this approach we create the JSS layout service endpoint that return Json containing the same content a component now renders in the MVC controller rendering, reusing existing content, templates etc. First things first To start, obviously as a Sitecore developer you have to install the Sitecore JSS server components into your environment. After that you create a Sitedefinition like entry for your JavaScriptServices where you register your JSS app and set the start item for your app root. You setup your API key as defined in the JSS doc site . To make sure your Sitecore instance is aware of this app and where in the Sitecore tree it 'lives'. You extend your Sitecore SiteDefin
Meer lezen