Starting with Sitecore 8.1 Geo IP lookup services come pre-installed and configured. All a site owner than need to do is log into the App Center and purchase the service. This is great from an implementer standpoint this is great as it’s one less configuration step that we have to take.
On the downside, if the site owners never purchase the lookup service the log will quickly clutter with ERROR messages.
ManagedPoolThread #12 16:01:15 ERROR Failed to perform GeoIp lookup for dd4795c0-1dca-ea8d-93c4-06d7f7aa5063
Message: The remote name could not be resolved: ‘discovery-ces.cloud.sitecore.net’
at Sitecore.CES.Client.WebClient.ExecuteRequest(String requestUri)
at Sitecore.CES.Client.ResourceConnector`1.Request(String endpoint, Object parameters)
at Sitecore.CES.Discovery.EndpointSource.GetEndpoint(String serviceName)
at Sitecore.CES.GeoIp.SitecoreProvider.GetInformationByIp(String ip)
at Sitecore.Analytics.Lookups.GeoIpManager.GetDataFromLookupProvider(GeoIpHandle geoIpHandle)
The fix isn’t hard; all it requires is a simple patch config to disable the lookup service.
For the full details on the lookup service checkout the full documentation at https://doc.sitecore.net/sitecore_experience_platform/setting_up__maintaining/ip_geolocation/setting_up_sitecore_ip_geolocation.
Quick Refresher: The customer has asked the Sitecore team to provide additional reporting views using data already being collected by Experience Analytics. (To understand the full request take a look at the first part of the guide.)
This post covers the first two steps
Step 1: Create New Dimension
All of the data that is reported against, starts with a dimension. A dimension consist of a Sitecore Artifact in the Marketing Control Panel and a corresponding, compiled aggregation method and table(s) to support the proper data.
Therefore, creating new dimensions is a task that involves both developers and business intelligence analysts. The BI Analysts work with the customer to help define the questions that they want to ask of the data, and then help the developer understand how the currently collected data can be aggregated to get the needed answers.
This is a process in itself, which we will investigate further in future posts.
Step 2: Create New Filter
Filters are created once, and can be reused throughout different segments. Filters are built using the Sitecore Rules engine to define conditions that must be matched so the element will be added to the resulting data set.
- Launch the Marketing Control Panel from the Sitecore Launchpad
- In the content tree, expand Experience Analytics -> Filters
- Right-click on Filters, choose Insert from the context menu, and then select Filter
- In the dialog box, provide a Name for the filter
- Click OK to close-out the Message Dialog
- There are minimal data fields to be filled out for a filter. Expand the Data section of the item and you will see a Rule field to complete
- Click Edit Rule to open the standard rule editor
- Choose the rule that best fits the data that you are looking to filter. Sitecore has done some backend magic, which spoofs the ‘current contact’ to allow rules to properly pull users into the filter in the form of Sitecore.ExperienceAnalytics.Aggregation.Rules.AggregationAdaptor.AggregationAdaptorTracker object
- Finally, be sure to select the action ‘add visit to segment’ to ensure that the contacts are added to the resulting dataset
- Click OK
As always, feel free to tweet me questions or comments @thecodeattic or on Sitecore Slack Community as @gillissm.
This post originally appeared at https://www.paragon-inc.com/resources/blogs-posts/guide_to_creating_dimensions_and_filters.
One click, two click, three click, where is that field? Once a day, I get so lost expanding and collapsing field sections when working in Sitecore’s Content Editor interface, that my poor mouse almost takes a unplanned trip across the office. As the industrious Sitecore developer I am, I decided enough was enough. My decision lead to the creation of Custom Content Editor Buttons.
There is nothing worse than getting half-way to three quarters of the way through a Sitecore upgrade, just to be hit in the face with a strange error related to Solr. In the recent months, my team and I have seen an increase interest in Sitecore upgrades involving Solr implementations. In my latest post Sitecore Upgrades Mixed with Solr, I review some of the hurdles we’ve faced to help you on your path.
One-hundred and forty and counting configuration files, so much power to customize, extend and tweak Sitecore. This is the daily struggle for a Sitecore developer or admin to guess what or where something should happen, in my latest post I debunk how all these files work together.
Web forms are a powerful mechanism to engaging site visitors. In part 3 and part 4, I take you even deeper into what is needed to make Sitecore Web Forms for Marketers even smarter. I’ll show you what’s needed to go from simple form into a smart progressive form, that auto-completes.
Sitecore owners are always looking for new ways to personalize the visitor experience. In my latest two posts I show you how to use some of that collected data to make it easier for a visitor to take action through Web Forms for Marketer (WFFM) forms on your site. Check it out over on the Paragon Blog…