How to track from where visitor downloaded a PDF file

For the Website owner it is important to know how the data is accessed in order to understand the flow. This information will be used in Website personalization process to optimize.  For the content page we can use Path Analyzer.  For media assets it is a different story.  In our case a visitor cans download from landing page, case study detail page and search results page. He has to find a way how to track in xDB all PDF downloads regardless from where the visitor access it.

Continue reading

How to exclude a list of specific items from Solr search results

I’m pretty sure that happens to you to look for items that match specific criteria except  few specific ones. We all have friends that don’t  know what they want, but they know what they don’t want. (I love you baby).

In my case, the client wanted a list of case studies specific to an  industry except those that the visitor already saw.  The first thought is to get results from Solr and then filter those already seen. But what about metadata that helps us implement paging, or just get  first 10 items ? Do we need another query ? Tee answer is to sent exclusion param with our query .

Continue reading

Switch Solr indexes

The content rendered on the Website should not be affected by index rebuild. A solution to that is to setup Solr in a way that it will rebuild an index in a separate core so that the rebuilding does not affect the search index that is currently used. Once the rebuilding and the optimization of the index completes, Sitecore switches the two cores, and the rebuilt and optimized index is used.

I will describe the implementation steps with Sitecore 8.2 and Solr 5.3.1. I don’t expect this to be different with newer version.

Continue reading

Sitecore 8.2 Rendering Issues

We experienced issues with shared layout on few of our pages. Presentation assembling seemed not following Presentation Detail Information Flow.

Based on Sitecore documentation this is a flow

rendering

 

  • SharedLayout option uses __Rendering field
  • FinalLayout option uses __Final Rendering field
  • Going from right to left, if a field has a layout delta, it goes to the field to its left to gather more presentation information.

After the investigation we noticed that on Save Button click in Experience Editor, the full share layout is saved and not the delta in __rendering fields. ( in case when a page is inheriting renderings from standards values).

Sitecore provided us with a patch. You can request one – the reference number is 144214

Is your xDB Cloud Consumption plan right for you ?

When I join my current project first thing I did as architect is an audit.  Make sure that architecture is optimized for current traffic and all best practices has been followed.  The client website use Sitecore xDB Cloud with xDB Plus subscription. It allows you up to 250 000 contacts at anytime and up to 2 500 000 interactions per month.

Contacts

How it’s measured: Total identified contact stored at any time.

Interactions

How it’s measured: Net new interaction created in a given period of time.

I check our current consumption to find out that we can switch to xDB base subscription and pay 30% of what are paying right now.

In some cases you better pay overage price before switch to the next subscription plan.

2017-10-24 11_42_15-xDB - Sales Enablement - March 2015 V2.pptx [Protected View] - PowerPoint

In case you want to generate your own reports or load data directly from mongo, you can access to your xDB database using and mongo viewer application.
Open your connectionstrings.config file and find the “analytics” connection string:
mongodb://{user-name}:{password}@{host1}:{port1},{host2}:{port2}/{guid}-Analytics?ssl=true;replicaSet={hostX}
You have replicaset on XdbCloud so use the host1 and port1 to connect.
Set up values in the following way:

con 2

con 2

But the best approche is to use  sitecore xDB Cloud API

https://gateway-xdb-scs.cloud.sitecore.net/api/xdb/Consumption/licenseId/deploymentId/year/month

where

  • licenseId – your Sitecore license ID
  • deploymentId – the unique identification of the deployment
  • year – the consumption year
  • month – the consumption month

Important

To ensure that your customers only access their own xDB sets, you must use a valid authentication token whenever you make a call to the xDB Cloud API. You can generate these tokens by using a valid Sitecore license file to call the SSO Encode Sitecore License endpoint. You must include the generated token as a HTTP header in all other requests called X-ScS-Nexus-Auth.

Visit this page -> xDB Cloud Consumption