







All information has been written with reference to Sitecore 8 (rev 141212)

Initialize

Namespace: Sitecore.Analytics.Pipelines.TrafficTypes

ReferringSite

Namespace: Sitecore.Analytics.Pipelines.TrafficTypes

args.Interaction.Referrer must not be null or empty.

must not be null or empty. Tracker.Dictionaries.ReferringSites must not be null.

SearchKeywords

Namespace: Sitecore.Analytics.Pipelines.TrafficTypes

OrganicBranded

Namespace: Sitecore.Analytics.Pipelines.TrafficTypes

This post documents Sitecore'spipeline, and is part of a series providing information on all the pipelines and processors in involved in a Sitecore 8 request . It's not a line by line account, but all the key logic is described.I'd like the post to develop over time, so if you find any inaccuracies, would like to contribute more information, or have useful links, then please leave a comment. Better still, contact me on Twitter Thepipeline is quite simple. It's called from theprocessor in thepipeline. The primary focus of each processor is to set the value of theproperty.Unlike several other pipelines of this type, the processors ofdo not abort when the when the primary goal has been achieved. So it seems thatmay be overwritten several times during the course of the pipeline. You should be mindful of this when adding your own additional processors.Theprocessor sets a default state for the the args object. The value ofis set to the constantThis ensures that if none of the other processors are able to set a value then the initial one will still be present.Theprocessor is responsible for settingdepending on whether the request is a referral (i.e. the user clicked a hyperlink on another site). It has the following requirements:If either of these criteria are not met, then the processor returns without performing any actions.Ifis the key of an item in thedictionary, thenis set to that dictionary items'sproperty. Otherwise,is set to the constantThe SearchKeywords processor is responsible for settingdepending on whether the request originated from a search engine result. It simply checks the value of. If that isn't null or empty, thenis set to the constantTheprocessor is responsible for settingdepending on whether the the current interaction's keywords match any in a predetermined list. It initially checks theproperty. If it's null or empty then the processor returns without performing any actions.Next, the processor gets the object at the path "/sitecore/system/Settings/Analytics/Organic Branded Keywords" within the(it returns without doing anything if the item doesn't exist).The value of the item's "Keywords" field is read and converted in to an array of strings (delimited by a line break). If the array contains the value of, thenis set to the constant