19

I actually just discovered the answer to my own question after more poking around. Highlight the item in the Sitecore Content Explorer. From the Analyze ribbon select the Attributes button. In the Attributes dialog box that appears click the Settings tab. There is a "Disable analytics for this page" checkbox on this tab. Check it.


14

If cookies are cleared, there is no way if you hadn't gotten them to self identify first. More info: You want to get users to self identify with an email address of some kind as quickly as possible. Then you want to utilize the Tracker.Current.Session.Identify (string identifier) method in order to convert the anonymous user to a Known Contact. The ...


10

This is a pretty complex issue and question, but you have broken it down excellently to allow me to attempt and pinpoint the issue. I believe the issue you are suffering from is what I have called "The Library Computer Problem" Question 1 With the usage of ExM and Engagement Plans we are heavily relying on contacts and the relation from contacts to ...


9

First of all, just to make it 100% clear: if you've disabled the tracker, then you can't track anything. No consent is required for session tracking According to the "EU cookie law", you cannot store certain types of information in the user's browser without the user's consent. Some cookies are covered by this, but not all of them. For example, session ...


9

Make sure it runs before the Sitecore.Analytics.Pipelines.HttpRequest.EndAnalytics processor in the httpRequestProcessed pipeline. Otherwise, the contact is set to null in the EndAnalytics pipeline by Sitecore.Analytics.Pipelines.EndAnalytics.ReleaseContact processor.


8

Yes need to have Analytics enabled for the personalization rules to be enabled in the system, but you can effectively disable it by turning off the database writes. You need to set Analytics.Enabled to true and Analytics.DisableDatabase to true. Example patch file: <configuration xmlns:patch="http://www.sitecore.net/xmlconfig/"> <sitecore> ...


7

My understanding is disabling the DB vs. the config will get you what you need. From here: https://community.sitecore.net/developers/f/9/t/246 The advantage to disabling the database, means that you can set Analytics.Enabled = true and still use the personalization rules engine for your presentation components. If you don't want/need to use those, then ...


7

The reason the tracker is not initialized is because it can't work with session state disabled. As I understand, you don't want this page to be tracked anyway. To ensure that xDB tracking is disabled, just add the following code into the page: <script runat="server"> protected override void OnPreInit(EventArgs e) { Tracker.Enabled = false; } &...


5

I would use Page Event rather than Goal in this case as it is more appropriate. There is not much technical difference between those two. 1) Creating Page Event You can create Page Event under /sitecore/system/Settings/Analytics/Page Events. and then fire it programmatically: private void RegisterPageEvent(string name, Guid definitionId, Guid itemId, ...


5

You should use similar code as below one to fix your problems to get and set custom facet values: Contact contact = client.Get<Contact>( new IdentifiedContactReference(_contactSource, contactIdentifier), new ContactExpandOptions(DynamicDataFacet.DefaultFacetKey)); var list = new List<Data> { data }; if (contact != null) { var facet = ...


5

You can use the code below to add a page to the interactions collection. The pageGuid is the Item ID of the page you want to simulate. NOTE: we are canceling the current page because I am calling all this from an API. And the API page is being tracked as a page in the interactions. private void TrackSection(ID pageGuid) { if (Tracker.Current.Session....


4

You'll want to set a <httpCookies> configuration in your Web.config that allows for a wildcard domain. This is done by specifying the root of your domain in the cookie. Note: that by changing this cookie, this will require people to log back into Sitecore and may need cookies to be cleared in order to take effect. Test heavily to ensure it works for ...


4

In Sitecore 9.x, the engagement value is a calculated facet. If you want to increase the engagement value, you should add an event where you are setting the engagement value e.g. using (XConnectClient client = SitecoreXConnectClientConfiguration.GetClient()) { try { var reference = new IdentifiedContactReference(source, identifier); var ...


4

In a distributed environment, you must enable the following two configuration files on all the servers: Sitecore.FXM.Bundle.config Sitecore.FXM.config Also, make sure that the following configuration files are enabled on your content management servers: Sitecore.FXM.Speak.config Search configs (lucene files or solr files) In addition, on each content ...


4

I received feedback from Sitecore support: The mentioned behavior is expected because the tracker should be only triggered upon a submit as it is expensive to keep it alive after navigating to the next or previous page So it looks that it's not a bug. Tracker is not initialized in Forms "Next" or "Previous" navigation step. To workaround it, you can ...


3

You should add the following setting in Sitecore.Analytics.Tracking.config just below the <settings> section: <setting name="Analytics.CookieDomain" value=".xxx.com">


3

The best way to tackle this is to add an Action Filter on your Controller actions to prevent the events from showing up in your Analytics Reports. Filter code: [AttributeUsage(AttributeTargets.Class | AttributeTargets.Method, AllowMultiple = true)] public sealed class DisableTrackingAttribute : ActionFilterAttribute { public override void ...


3

The Disable Analytics option on item is used during the Processing/Aggregation activities of Sitecore Analytics, specifically the processItem pipeline. <processItem patch:source="Sitecore.Analytics.config"> <processor type="Sitecore.Analytics.Pipelines.ProcessItem.CollectParameters,Sitecore.Analytics"/> <processor type="Sitecore.Analytics....


3

Even though you disabled the "disable analytics tracking for this page" setting for the sitecore/Content/Sites/MySite/Third Party/ item, I don't think it will stop analytics tracking for the child item under that root item. If your support site items are based on different data template (which is not used in other areas of your sitecore content tree), ...


3

Ensure that you are not running in the ContentManagement role in your Web.config. For testing analytics locally you will need to use the Standalone role: <add key="role:define" value="Standalone" />


3

Sitecore 8.2 is not supporting MongoDB 3.4.7 yet, Latest version of mongoDB supported is 3.2.1 See supported versions table here : https://kb.sitecore.net/articles/633863


3

As a comment suggests, the Sitecore does not react to the DNT signals, that is why you have to track it by yourself and stop the Analytics Tracker if there is a DNT header present. You can check a DNT simply by checking the header value: Request.Headers["DNT"] Please, refer to the below answer on how to stop tracking (personally, I suggest that you cancel ...


3

I found a possible solution to your problem, besides checking what @Pete saids about settings. We need to check if you get all items created to analytics works, it including Profiles and Keys Profile Cards (that you assign to some content) Pattern Cards (that sitecore based on the analytics automaticly will set to your visit) "Profile vs Pattern The ...


3

Things to Check There are a number of reasons why the StartTracking pipeline might not work, which are heavily documented on Sitecore Stack Exchange. That being said, I would start with working backward and ensuring that the processor configurations are showing up as shown below. Check Log Files for Errors about Tracker not Initialized or Running Check ...


3

No matter what, if you identify the user each time they log in, you will be fine. Tracker.Current.Session.IdentifyAs(source, identifier); If the husband is logged in, you will notice the Tracker.Current.Session.Contact.ContactId will be one ID. And when you IdentifyAs() the wife, the ID will change to her contact ID. The husbands session will time out and ...


3

At least the first of your requirements can easily be archived by changing default sorting options for a chart. For the 'By URL' detailed list, you can find the default settings in item /sitecore/client/Applications/ExperienceAnalytics/Dashboard/Behavior/Pages/By URL/PageSettings/ListControl Parameters in the core database KeysSortByMetric - determines ...


2

When using the Identify() method and switching identifiers, because the contact is known, Identify() won't merge the contacts like it would for an anonymous original contact. So the end result is that you will have two contacts in xDB, one for each identifier. The information isn't lost, but it's not tracked as one contact. That's where ContactManager ...


2

Sitecore will capture information about the request in the analytics, but if you are just sending the data to the 3rd party analytics API you can probably just use the Request.Browser object that is just part of the MVC Controller request. You could use the following properties public ActionResult MyRendering() { var os = Request.Browser.Platform; ...


2

You have two tracking cookies, one for Session, the other for Global Session (SC_ANALYTICS_SESSION_COOKIE, and SC_ANALYTICS_GLOBAL_COOKIE). Sitecore doesn't track contacts based on the global cookie but you can get it through code. Each of the Contacts has a Global cookie which has a unique ID in the table. That way you can map the anonymous user. Of course, ...


2

If for some reason you need to do it via code, I would go with this: Open Sitecore.Analytics.Tracking.config and find following node <startAnalytics> <processor type="Sitecore.Analytics.Pipelines.StartAnalytics.CheckPreconditions, Sitecore.Analytics" /> <processor type="Sitecore.Analytics.Pipelines.StartAnalytics.CreateTracker, ...


Only top voted, non community-wiki answers of a minimum length are eligible