Event Tracking Google Style Post: 302217372

Sponsored Content

Special Forums News, Links, Events and Announcements Complex Event Processing RSS News Event Tracking Google Style Post 302217372 by Linux Bot on Tuesday 22nd of July 2008 03:50:04 PM

07-22-2008

Registered User

Event Tracking Google Style

Tim Bass
07-22-2008 12:46 PM
Most readers who operate a web site are familar with Google Analytics*(GA). GA users add a bit of Javascript on their web pages. The Javascript has tracking code that executes when visitors request web pages. The GA tracking code basically sets or updates cookies on*the user’s browser and requests a single-pixel image from the GA servers.

In the last release of the GA code, Google added Event Tracking.***In Google-speak, events are actions that visitors take on a web page that do not generate new pageviews. Examples of these events are, interacting with a Flash player, a AJAX widget or an audio player. In the old GA,*webbies could track event-data as a pageview.* However, because*event tracking*using crude pageviews is not very effective,*GA*added*new functionality they refer to as*Event Tracking.

There are 4 components in the GA events data model; Objects, Actions, Labels and Values. GA Objects are areas of web pages that visitors interact with, for example a video player or an Ajax widget.* The second part of the GA event tracking data model is Actions. *Actions are*related to an Object, representing Actions that visitors perform on the Object.* Labels further describe Actions,*associating*context with*Actions.***Last, but not least,*Values are quantities associated with Labels.

Notice how Google defines this event processing model as Event Tracking.** Similar to the reference architecture we described in What is Complex Event Processing?,* operations on single event objects are generally tracking-oriented,*often referred to as Event*Refinement* in the*art-and-science of*multisensor data fusion (MSDF).*

The GA event tracking model does not (yet) incorporate Situation Refinement, which in MSDF-speak, would be object-to-object processing, representing a higher level of interaction modelling.***

Can you provide examples where object-to-object interaction between various*objects on a single web site*represents a real-world*situational (complex event)*model?*

Taking this one step further, can you*think of some examples where object-to-object interaction between various*objects on different web sites represents a real-world*situational model?

*

Source...

Linux Bot

View Public Profile for Linux Bot

Find all posts by Linux Bot

4 More Discussions You Might Find Interesting

1. Post Here to Contact Site Administrators and Moderators

Style not working right

:( The style "Craig's InfoPop" doesn't wrap lines on Netscape 4.79. It seems to work okay on MSIE. When I get home, I'll check on FBSD/Mozilla 1.0. Back to Silk Road ...

2. Post Here to Contact Site Administrators and Moderators

New Style

Hi, I pop in here every so oftern and was suprised to see the changes in colour. I think the new style/colour is great :D

3. Shell Programming and Scripting

event number tracking

Having a bit of trouble trying to sort this one out so any advice is appreciated. I have several scripts running in cron monitoring different events on different servers. These scripts log information events and critical events to a central log file. I wanted to add an event number to every...

4. Web Development

Helpful Tip: Forcing Google to www.google.com

Helpful Tip! Sometimes when we are in another country, Google redirects our request for www.google.com to: www.google.co.in or to: www.google.co.th If you want to force Google to go to the US site, use: www.google.com/webhp

LEARN ABOUT CENTOS

qchildevent

QChildEvent(3qt)														  QChildEvent(3qt)

NAME

       QChildEvent - Event parameters for child object events

SYNOPSIS

       #include <qevent.h>

       Inherits QEvent.

   Public Members
       QChildEvent ( Type type, QObject * child )
       QObject * child () const
       bool inserted () const
       bool removed () const

DESCRIPTION

       The QChildEvent class contains event parameters for child object events.

       Child events are sent to objects when children are inserted or removed.

       A ChildRemoved event is sent immediately, but a ChildInserted event is posted (with QApplication::postEvent()).

       Note that if a child is removed immediately after it is inserted, the ChildInserted event may be suppressed, but the ChildRemoved event
       will always be sent. In this case there will be a ChildRemoved event without a corresponding ChildInserted event.

       The handler for these events is QObject::childEvent().

       See also Event Classes.

MEMBER FUNCTION DOCUMENTATION

QChildEvent::QChildEvent ( Type type, QObject * child )
       Constructs a child event object. The child is the object that is to be removed or inserted.

       The type parameter must be either QEvent::ChildInserted or QEvent::ChildRemoved.

QObject * QChildEvent::child () const
       Returns the child widget that was inserted or removed.

bool QChildEvent::inserted () const
       Returns TRUE if the widget received a new child; otherwise returns FALSE.

bool QChildEvent::removed () const
       Returns TRUE if the object lost a child; otherwise returns FALSE.

SEE ALSO

       http://doc.trolltech.com/qchildevent.html http://www.trolltech.com/faq/tech.html

COPYRIGHT

       Copyright 1992-2007 Trolltech ASA, http://www.trolltech.com.  See the license file included in the distribution for a complete license
       statement.

AUTHOR

       Generated automatically from the source code.

BUGS

       If you find a bug in Qt, please report it as described in http://doc.trolltech.com/bughowto.html.  Good bug reports help us to help you.
       Thank you.

       The definitive Qt documentation is provided in HTML format; it is located at $QTDIR/doc/html and can be read using Qt Assistant or with a
       web browser. This man page is provided as a convenience for those users who prefer man pages, although this format is not officially
       supported by Trolltech.

       If you find errors in this manual page, please report them to qt-bugs@trolltech.com.  Please include the name of the manual page
       (qchildevent.3qt) and the Qt version (3.3.8).

Trolltech AS							  2 February 2007						  QChildEvent(3qt)