Log Types

Site (sgo):

Used on site structure and permanent elements. Typically this will be navigation and search elements. Site has a data resolution of one day. The database is normally updated at the same rate as the other modules, but the data is accumulated on a daily basis.

Editorial (ego):

For logging content, more specifically content or elements that are modified or moved around to optimize the flow of traffic. Typically these elements are what the site is all about, like articles and products. Data resolution is one minute for the previous three hours, and hourly when stored for future analysis. Content logged by Editorial can be viewed in close to real-time.

Additional functionality supported by editorial exclusively:

Editors Eye: Real time monitoring of content on a particular page. Editors eye is most frequently used by editorial staff at news related sites, and for optimizing product mix on front pages in online stores.

Evaluate: Available for all modules, but will in editorial work with an hourly resolution and be able to compare or benchmark on a daily basis.

Commercial (cgo):

Used for logging commercial content like ads and sponsored links. Well suited for elements that you do not wish to run trough an adserver, as commercial will provide you with necessary documentation for the customers. For an overall understanding of you site also elements that are delivered by adserving systems should be logged by commercial. Data resolution for commercial is on a daily basis. In addition customers or partners can get their own login to the system where they may access relevant data and is this way utilize commercial for invoicing purposes.

View (vgo):

For logging page views. The log type utilise a pixelgif with a unique name that is reloaded with the page. This method opens up for great flexiility in deploying the logtype. For Ajax elements, vgo has to be specifically called from within the element to log, and clicks are generally better suited for understanding user behaviour in such context. Logging Views with LinkPulse is primarily to get data for reporting in context, such as click ratios of pages or elements. View data is avialable from LinkPulse the same way as clicks, although vgo data does not have a topage or category (unless you specify one).

Mobile (mgo):

For logging page views on mobile terminals. Works in principle like View and supports different methods depending on terminal type and required attributes, but is defined as a separate data type for reporting purposes. For logging clicks on terminals, standard data types work well, but for reporting purposes you are well advised to ask us about it.

Search