Many of you have probably seen "IP_NOT_FOUND" entries in Engagement Analytics application.
Usually, it's a visits from internal IP address (like 192.*.*.* or 10.*.*.*) - your company network, monitoring systems, etc.
Such addresses cannot be resolved by MaxMind, so they're just displayed as "Not Found". Also, sometimes you might want to update GeoIP information manually (for example, if you know more about the particular IP than MaxMind does)
The simplest way to do it is to update the DMS database directly. This can be done in 2 easy steps.
Sitecore Snippets
Useful and ready to use solutions
Monday, April 2, 2012
Sunday, January 1, 2012
Sitecore Snippets - Blog Statistics Overview
Saturday, December 10, 2011
Sitecore GeoIP Country Resolving - Jump to Lightspeed
In this article, I'll show how to customize Sitecore, to use GeoLite database for instant country resolving.
Labels:
country resolving,
dms,
geoip,
lightspeed
Saturday, November 5, 2011
Client Event Tracker - Examples & Demo Page
My previous blog post about Client Event Tracker module for Sitecore was rather technical and did not contain real examples. Since it's much better to show something once than say about it many times, I've created Demo Page, where you can see how the module can be used, side by side with simple results view.There are 3 examples, let's review them briefly.
Wednesday, November 2, 2011
Sitecore Update Helper
In this blog post I just want to present my project called Sitecore Update Helper. It's a simple website that helps to prepare to Sitecore CMS update by displaying update steps and links to appropriate pages on SDN.
You just need to specify source / target versions, and click "Process".
This is what you get if you want to upgrade from 6.1.0 Initial Rel. to 6.5.0 Update-1:
You just need to specify source / target versions, and click "Process".
This is what you get if you want to upgrade from 6.1.0 Initial Rel. to 6.5.0 Update-1:
If you have any questions or ideas - do not hesitate to leave your comments.
Monday, October 24, 2011
Language Fallback and Sitecore Dictionary
Sitecore CMS Dictionary is the best place to keep all texts that can be used across the site: "read more", "click here", etc. . It's internal architecture is a little unusual - it stores key/value pairs in the temp file /{yourSiteRoot}/temp/dictionary.dat, which is updated during item:saved event(via the handler in web.config).
Monday, September 26, 2011
Client-Side Event Tracking with Sitecore Analytics
After the previous blog post about combining JavaScript and CSS, I decided to create more modules standardizing features that can be used out of the box at many websites.
Today I'll describe new module that allows tracking client-side events with Sitecore Analytics. Such feature is really important for today's highly interactive sites, and you'll see how easy it is to implement it for Sitecore.
After installing the module, you'll be able to track external file downloads, Ajax events and any kind of visitor interaction that does not cause the page to refresh (expanding / collapsing page areas, popup windows, etc.).
Today I'll describe new module that allows tracking client-side events with Sitecore Analytics. Such feature is really important for today's highly interactive sites, and you'll see how easy it is to implement it for Sitecore.
After installing the module, you'll be able to track external file downloads, Ajax events and any kind of visitor interaction that does not cause the page to refresh (expanding / collapsing page areas, popup windows, etc.).
Labels:
analytic,
api,
events,
interactive sites,
JavaScript,
oms,
Shared Source,
sitecore
Subscribe to:
Posts (Atom)




