Configuring Google Analytics for a Sitecore Website

Leave a comment

Hello Sitecore Family,

A few weeks back, I had a nice small task to work on, the title of the above post – Configuring Google Analytics for a Sitecore Website. Lets see how easy it can be to configure. Yes, you are right,  the first question that would come to the mind of any Sitecorian, is why Google Analytics and not Sitecore DMS. That proves you are a Sitecorian — but again sometimes, the requirement is such – such as in my case, where the client was using Google Analytics for a number of other sites of his.

So he also wanted the Analytics of the current site to be there in Google Analytics – So be it!


How does Google do to show us the Analytics data?

Basically, we need to copy a Javascript from Google into all our pages along with the Tracking Code generated by Google for us, so that whenever the page loads on the client side, it send its related data back to Google and finally we can see and analyze it.


Configuring Google Analytics, is as simple for Sitecore as for any other Site – so lets divide it into two steps to understand it better:

  • Basics of Google Analytics:

For a beginner who wants to know how to configure Google Analytics, the steps are as given in this link –

There are two ways in which Google does it and we can choose any one of them.

Google’s Classic Analytics code (ga.js)

<script type="text/javascript">

  var _gaq = _gaq || [];
  _gaq.push(['_setAccount', 'UA-XXXXX-X']);

  (function() {
    var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
    ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '';
    var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);


Google’s Universal Analytics code (analytics.js)

<!-- Google Analytics -->
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),

ga('create', 'UA-XXXX-Y', 'auto');
ga('send', 'pageview');

<!-- End Google Analytics -->

As of now, if you are adding Google Analytics to a website, Google recommends to add the Universal Analytics code.


  •  Basics of Configuring Google Analytics in Sitecore:

Basic/Beginner Steps:

  1. Create a Sublayout in our Sitecore Solution.
  2. Copy one of the above given code (preferably Universal analytics) to the Sublayout.
  3. Statically bind the Sublayout to all (one or more) main layouts of the Sitecore Site.(
  4. Replace the UA-XXXX-Y with the Google Analytics code for the client website. The client might have given you a code starting with UA. If in case he hasn’t ask him for it. (how to get the Google Analytics code:
  5. Let’s Open our page/s in browser and check in Realtime Tab on the left side to see the data that appears.

This is in normal case that any developer would do.

Now lets consider a case, that we have a multi-site Sitecore Solution. As per the best practices of Programming, we would definitely want to reuse the code.

Advanced Steps:

  1. Make in a section of Global Sublayouts (which would be shared for all the sites in the solution), let’s create a Sublayout for Google Analytics.
  2. Copy the Universal Analytics code to the Sublayout, with just one change – adding a Property to fetch the Google Analytics code on runtime – as below screenshot:Add-Universal-Analytics-dynamic-code
  3. Statically bind the Sublayout to all (one or more) main layouts of the Sitecore Site.(
  4. In the Template of HomePage of the website or in a Global Settings Section template of a site (whichever we feel we are comfortable with, as per the Site structure – nothing is good or bad, right or wrong, Sitecore is so good in architecture, that we can configure as per our requirement and that thing becomes right!) create a field to store the Google Analytics code of a website.Google-Analytics-Code-Template-Structure
  5. Add the code to the specified field of the corresponding item.Google-Analytics-Code-updatead-in-Item
  6. In the code behind of the Sublayout, write the function to fetch the value of the Google Analytics code, from the item.Google-Analytics-Code-Behind

Oh, you want to check the code? — Here it is!

<!-- Google Analytics -->
 (function (i, s, o, g, r, a, m) {
 i['GoogleAnalyticsObject'] = r; i[r] = i[r] || function () {
 (i[r].q = i[r].q || []).push(arguments)
 }, i[r].l = 1 * new Date(); a = s.createElement(o),
 m = s.getElementsByTagName(o)[0]; a.async = 1; a.src = g; m.parentNode.insertBefore(a, m)
 })(window, document, 'script', '//', 'ga');

 ga('create', '<%= GaTrackingCode %>', 'auto'); // Replace with our property ID.
 ga('send', 'pageview');

<!-- End Google Analytics -->

protected string GaTrackingCode { get; private set; }

protected void Page_Load(object sender, EventArgs e)
Item SettingsItem = Sitecore.Context.Database.GetItem(Sitecore.Context.Site.RootPath + Sitecore.Context.Site.StartItem + "/Settings");

GaTrackingCode = SettingsItem["Google Analytics Code"];

Happy Tracking data of our Sitecore Site in Google Analytics! :)

My First Windows App – SitecoreVideos

Leave a comment

Hi Sitecore Lovers,

I was trying my hands on Windows Apps development, thanks to my friend and colleague Nikki Punjabi who has developed a number of apps.

As it was my first, I made one using the AppStudio by provided to us by Microsoft — a real great way of making an app.

The reason why I am referring to the Sitecore community in this post of a Windows App, is because I think that the community would be interested in using this app. The name of the App is SitecoreVideos. (Aha! I can see a smile on your face!) Yes, exactly, as the name suggests, it finds videos on Sitecore shared by some really helpful Youtube channels.

Its available for Windows Phone 8.1 and Windows 8 Store.

Oh, so you want to know how to try it?

Just go to your Windows Store in your Windows Phone or Windows 8 Store, and search for “Sitecore”. You will find it in the search results.

Do try it and let me know if you like it.

And I suppose, with the Sitecore Symposiums going on, its the right time to use such it.


Happy Watching Sitecore Videos in Style!

Page Editor Experience – Add a Thumbail Image to our Presentation Component

Leave a comment

This tip, was given to me by my senior and colleague Nilesh Thakkar. He blogs about his Sitecore Journey, at

He said, some things are not compulsory to be done, but good if they are done to make it easy for the client. Like say add a thumbnail image to your presentation component. How? Lets have a look.

We already know “A Picture is worth thousand words” so yes, we got to agree upon what Nilesh Thakkar says! So, lets see, how it can be done and how helpful can it be for our clients/users.

Setting up a plot:

Lets for example say, we have a Blog to manage in Sitecore. We have already created a few presentation components for various sections of the page as below.

Header Section:

  1. Blog Header
  2. Blog Search

Left Sidebar Section:

  1. Blog Roll
  2. Recent Comments
  3. Recent Posts
  4. Featured Posts
  5. etc..

Main Content Section:

  1. Blog Article Summary
  2. Blog Article
  3. Article Share Tools
  4. Blog Comments

Why Add an image to Presentation Component?

For any Page Editor user, it might definitely be very easy if there is an image, depicting what that particular presentation component does.

Now, lets say, a user is configuring a Blog Landing page, and is confused between two presentation components — Blog Article Summary and Blog Article. So he/she can add it to a page, configure a datasource to it, and see how it looks. We developers always unit test various scenarios whenever we develop some code, to make sure it works well. So instead of, the page editor user has to configure and check, if we add an image of that component while testing, wont it be a great idea?

How to add it?

Let’s say, the Blog Article Summary component looks like as below:


while the Blog Article Component Looks as below:


To configure its thumbnail lets go to the Presentation Component (sublayout in this case) in the content tree.

Make sure that Standard values checkbox is checked in View Tab of the ribbon.


Go to the Appearance Section and find the Thumbnail field in it.


Upload an appropriate Thumbnail image, suitable to the component as well as that makes it recognizable while adding it through the page editor.


Save the item, and now, lets go to the Page Editor mode and click the Components button.


Lets click on “Add to here” so that Select a Rendering dialog opens.


As we see above, the Blog Article Summary component is self explanatory, it becomes pretty easy for the Page Editor users to identify and select it if they want to use it.

So simple it is to make someone’s life easy, by applying a very small effort,  in a right direction. And according to me, that is what a developer is for — to make the life of normal people easy, in whatever way possible, by making great technology.

Happy Sitecoring! :)

Placeholder Settings – Empower your Page Editor Users – Part – 2

Leave a comment

In the part one of this post, we saw what a Placeholder Setting is and why is it good to use Placeholder Settings in architecturing of our Sitecore Projects. In case you missed it, have a look at it here –  Placeholder Settings – Empower your Page Editor Users How to Setup Placeholder Settings? Suppose we are developing a Site with a blog. So lets configure various elements considering that blog has the following  layout:


Various presentation components that we need for the blog are as follows:


Next, lets create a Placeholder Setting item. At the location /sitecore/layout/Placeholder Settings right-click and say insert Placeholder.


Now, we can have the following components in our left Sidebar:

  1. Blog Roll
  2. Recent Comments
  3. Featured Posts
  4. Recent Posts
  5. Subscribe to Blog
  6. Blog Stats
  7. Blog Authors
  8. Blog Archive

So lets add them in Allowed Controls of the setting.


Please note, that in the above screenshot, we haven’t specified any Placeholder Key. This means, it is a Data-Template Placeholder Setting. So, we need to add this setting to the Presentation Details all the blog related items (ideally to blog related template’s standard values).

[Moving a step back from our configuration step, lets discuss why we used a Data-Template specific setting, and how beneficial can it be in our case. The advantage of making a global Placeholder Setting, is that we have the Placeholder Key already specified in the Setting and we do not need to add it to the Presentation Details of that of the item or template standard values. Sitecore identifies, where to apply it, based on the Key that is specified in the Setting. But, its good to use it only if the site follows a single main layout.

Taking our current case of that of the Blog Section of a Site, we are using Sidebar with the key leftSidebar. Lets say, we make this setting as Global, and we have the same key in different layouts for other Site Sections (say Our Services Section) , then these Blog related Presentation Components, will be available for Page Editor users, to be added  in Our Services Section, which is conceptually wrong. So to avoid such cases, whenever we have multiple layouts section-wise its always good to create Data-Template specific placeholder settings. Also, in a case where we have a website setup, and we found later that Placeholder Settings could be useful for us to use, its preferable to make it Data-Template specific instead of Global Placeholder settings to avoid major level of testing into it. ]

Coming back to our How to configure Placeholder Settings, adding the Sidebar Placeholder Setting item, to the Presentation Details of the Blog Section Template’s Standard values and specifying the Placeholder Key as “leftSidebar”.


Once added, it can be seen in the presentation details of every item of that template and when we can click on it, we can see the controls that can be added to the specific Placeholder Key, by our Page Editor Users.


Once this is done, we can start adding components to the left Sidebar. Say we have added Blog Archive.


And some of the following (Recent Posts and Featured Posts) might be added by client in future, so he/she doesn’t need to depend on us, or come to us to get it added. Their Page Editor users can do the same as follows:


As we want to add a new Component, that of Recent Posts, above this blog roll component, we click on the Add to here button above it. Note that, when we hover over the Add to here button, here’s what we see:


The Placeholder’s name is replaced by the Placeholder Setting’s name. And now, on clicking it, we get all the allowed controls.



I’ll Select the Recent Posts Component, and that’s how it looks on my page, in Left Sidebar.


Hope you enjoyed the couple of posts on Placeholder Settings? Lets make use of various things, simple in use yet very powerful features and make situations for our clients and stakeholders easy!

Good Reads:

Happy Sitecoring! :)

Placeholder Settings – Empower your Page Editor Users

1 Comment

While binding the Content with its presentation, we have two terminologies, Static Binding and Dynamic Binding. Know more..

In this post, we’ll see how Sitecore adds one more level of abstraction over binding Content with its Presentation Components, empowering both – the Developer as well as the Page Editor user – and moving to a simple and very effective solution. I have added this to my list of reasons for Why I Love Sitecore. For anything that we do, we have 3 questions in our What, Why & How? So lets start getting answers for these questions.

What are Sitecore Placeholder Settings?

A Placeholder setting is linked to a Placeholder key and adds a level of abstraction while binding a presentation component with the corresponding content.  In a Placeholder Settings item, we give it a name so that it can be easily identified — for which specific location would it be made — and specify a number of sublayouts and/or renderings in it, which are appropriate according to the design changes of the current website. They are of two types:

  1. Global Placeholder settings
    • Placeholder Key is specified in the Settings item.
    • Does not need to be attached to Presentation details of various Template’s Standard Values or that of items.
    • Sitecore by default identifies if the placeholder key mentioned here is present on the page, and allows us to add the controls allowed here to be added to the page.
  2. Data Template-specific Placeholder settings
    • Placeholder Key is Template specific.
    • Placeholder Key needs to be specified while adding it to the Presentation Details of Template’s Standard values or that of item.

Why Sitecore Placeholder Settings?

  1. It empowers the Page Editor users, to make the necessary design changes at required locations, without being dependent on the Developer.
  2. It relieves the Developer from the hassle of going back to the client site, just to make simple design level changes.
  3. The components that can be added at any location in a website, are specified in the allowed controls of it. So the Page Editors  can select the ones out of them. This not only helps them in selection for which component they want, but also makes sure that an inappropriate component is not added to a location where it should not be. (Lets say, in case of a blog, we have a left sidebar, with components of Recent Posts & Recent Comments. We can have a Placeholder setting, for left sidebar with other allowable components along with the above, say Blog Roll, Blog Archives and link it with the data template to avoid a component of main blog post to be added to the left sidebar)
  4. Ideally, Placeholder settings should be configured before various presentation components are bound to its corresponding content. But in case that’s not done, they can be easily plugged-in whenever we want to, with a little effort, by understanding the broad-level architecture of the site.

In part 2 of this post, lets see how to configure Placeholder Settings.


Happy Sitecoring! :)

Sitecore Beginner – Static and Dynamic Binding


As a Sitecore beginner, we are very eager to know more and more about Sitecore.

The Content:

We first create the templates, which defines the structure of our content. — What all is needed Next, we create all the required items from these templates and fill them up with the required content. Know more..

The Presentation:

Next, we create layouts (ASPX Files) and sublayouts (ASCX User controls) defining the structure of the pages of our website. Sitecore, offers us the opportunity of code reuse, and hence, its always a good way to create our presentation components in such a way, that we can make most reuse of our presentation items. Know more..

Binding Presentation and Content:

Now, we know that our content is ready in the content items, and how our data will look is ready in our presentation — layouts and sublayouts.  So what remains is mapping our content on our presentation items, so that it is displayed on a page in a website. We have two ways of doing it.

Static Binding:

Static binding, as the name suggests, is something like hardcoding a value on a page. Its like knowing at compile time, what component will be rendered at which location. Lets take an example. In our website, we might have some portions on a page, which are common for all the pages, or atleast for some pages. Say a control which renders the company logo, or the search bar, or say the navigation component, or a footer with copyrights or social media icons etc. This is to make architecture of a site quite simple, in case of all those components and renderings, which are required on all the pages. Instead of taking the pains of adding them to each page individually, they can be added directly to the main layout — the main aspx page, responsible for the rendering — and thus save our as well as content editor’s time, in linking them to various content items, individually. An example of Static binding is as follows:

<sc:rendering id="Navigation" runat="server" renderingname="SiteNavigation"></sc:rendering>
<sc:sublayout id="Search" runat="server" path="/layouts/global/SiteSearch.ascx"></sc:sublayout>

Dynamic Binding:

Dynamic binding, goes by its name. Various page components, — renderings and sublayouts are bound to their respective content, dynamically, on runtime. The binding takes place using placeholders — various placeholders as per requirement are added to the layout and the sublayouts, and different required presentation components, are assigned the placeholder key as per their rendering location. This is way, the rendering location of the various presentation components, can be managed as per requirement, and changed on runtime.

<sc:Placeholder runat="server" ID="phleftSidebar" Key="leftSidebar" />

This way, Sitecore Supports better modularizing of your application as well as code reuse.  Again, to avoid adding various presentation components to each and every item of your site, its good to configure and add the bindings to the Standard Values of the respective item templates.

As far as using both the above is concerned, there isn’t a best case or worst case. Using them at appropriate locations of our site is the key and we can design an architecture which is best suited for our case.

Good Reads:

Your Sitecore Blog gets a new name – Sitecore Endeavor

Leave a comment

My dear Sitecore Lovers,

Your very loved Sitecore Blog, gets a new name today – Sitecore Endeavor.

What? You have three questions in your mind – What, Why and How? Well, lets know more about it then.

What was the name previously? What is Endeavor? What is Sitecore Endeavor?

Previously, there was no particular name of the blog, it was simply called .Net Sitecore Blog. Endeavor means, an attempt to achieve a goal. Sitecore endeavor means, an attempt to achieve a goal, in the Sitecore Community.

How Sitecore Endeavor?

I thought a lot for a suitable name the blog.  After a lot of effort and discussion with my friends Muktesh Mehta and Sandeepkumar Gupta, the word Endeavor came to be worth it.

I thank Muktesh and Sandeep from the bottom of my heart to get us with a rightful name for the blog.

Why Sitecore Endeavor?

The reason I started blogging on Sitecore and Dotnet related stuff, was with an intention of sharing as much information as possible with various developers, about any issues I face and their solutions that I find on various forums or I try to get it myself. The reason was about sharing my experiences of working with various things, and to avoid DRY (Don’t Repeat Yourself) rule, for any other developer, because a Developer’s time is very precious!

Sitecore Endeavor is, my attempt to achieve a goal, specifically, my personal goal of sharing as much information about Sitecore that I have with the Sitecore Family!

Let’s all of us say,

Happy Sitecore Endeavoring! :)

Older Entries


Get every new post delivered to your Inbox.

Join 394 other followers

%d bloggers like this: