Abstract: A method and system for the efficient customization of website tracking data includes a data collector with a user interface for assigning custom events and attributes to events occurring on a website. The data collector receives custom tracking data from the website in response to the occurrence of an event to be tracked. Customization of tracking data is achieved through the use of an embedded tracking code and associated data collection file. The embedded tracking code is configured to report tracking data customized for the website. The data collection server is configured via a graphical user interface to receive and store the customized tracking data. A configuration string from the data collector is inserted into the data collection file on the web site. In this manner, the data collection server and website is customized to collect customized tracking data efficiently without assistance from others.

Abstract: A method and system for the efficient customization of website tracking data includes a data collector with a user interface for assigning custom events and attributes to events occurring on a website. The data collector receives custom tracking data from the website in response to the occurrence of an event to be tracked. Customization of tracking data is achieved through the use of an embedded tracking code and associated data collection file. The embedded tracking code is configured to report tracking data customized for the website. The data collection server is configured via a graphical user interface to receive and store the customized tracking data. A configuration string from the data collector is inserted into the data collection file on the web site. In this manner, the data collection server and website is customized to collect customized tracking data efficiently without assistance from others.

Abstract: A client rendering a web page discovers embedded content directing the client to request embedded content from a data collection server. The data collection server performs a cookie handshake by determining whether the request includes a visitor identifier. If a visitor identifier is present, the request data is collected and categorized with the visitor identifier. If the visitor identifier is not present, the data collection server creates a visitor identifier and do not repeat flag and sends these items with a redirection request to the client, thereby establishing a visitor identifier for the redirected contact. Where the client does not accept visitor identifiers, or the visitor identifier otherwise is lost, the data collection server creates a visitor identifier based on the client's address, or some other available data.