8. A method comprising: configuring a data contract definition of a universal tag via a console server, wherein the data contract definition specifies: data events and corresponding event data to collect from a designated website accessed by a user at a user device, and client-defined transformation rules and taxonomy rules for interpreting the collected event data to generate a user profile corresponding to the user, the user profile including key-value pairs and categorizations; storing the data contract definition as a corresponding updated data contract in a database; identifying, via a listening server, the updated data contract in the database; generating, via the listening server, run time code instructions based on the updated data contract; receiving, at a presentation server, the runtime code from the listening server to instantiate a runtime endpoint at the presentation server; collecting, at the presentation server during runtime, event data from the designated website, the event data specified by the data contract definition; applying the transformations to the collected event data, categorizing the transformed event data based on the applied taxonomy rules, and storing the transformed event data in the corresponding user profile at a profile server; wherein collecting event data includes providing a universal tag script, via the presentation server, for running in the context of the designated website to instantiate a universal tag to: collect event data from the designated website, and report the collected event data to the runtime endpoint for applying the transformation and taxonomy rules; and wherein applying the transformations to the collected event data includes performing an iterative loop via the runtime endpoint on the presentation server, the iterative loop comprising: automatically determining, via a data provider servlet application, a list of runtime transformation applications corresponding to data contracts corresponding to a particular provider ID; performing, via a runtime transform application, the appropriate transformations on event-value pairs; and for each event-value pair, return a key-value pair and appropriate category identification for storage at a runtime user profile application.
8. A method comprising: configuring a data contract definition of a universal tag via a console server, wherein the data contract definition specifies: data events and corresponding event data to collect from a designated website accessed by a user at a user device, and client-defined transformation rules and taxonomy rules for interpreting the collected event data to generate a user profile corresponding to the user, the user profile including key-value pairs and categorizations; storing the data contract definition as a corresponding updated data contract in a database; identifying, via a listening server, the updated data contract in the database; generating, via the listening server, run time code instructions based on the updated data contract; receiving, at a presentation server, the runtime code from the listening server to instantiate a runtime endpoint at the presentation server; collecting, at the presentation server during runtime, event data from the designated website, the event data specified by the data contract definition; applying the transformations to the collected event data, categorizing the transformed event data based on the applied taxonomy rules, and storing the transformed event data in the corresponding user profile at a profile server; wherein collecting event data includes providing a universal tag script, via the presentation server, for running in the context of the designated website to instantiate a universal tag to: collect event data from the designated website, and report the collected event data to the runtime endpoint for applying the transformation and taxonomy rules; and wherein applying the transformations to the collected event data includes performing an iterative loop via the runtime endpoint on the presentation server, the iterative loop comprising: automatically determining, via a data provider servlet application, a list of runtime transformation applications corresponding to data contracts corresponding to a particular provider ID; performing, via a runtime transform application, the appropriate transformations on event-value pairs; and for each event-value pair, return a key-value pair and appropriate category identification for storage at a runtime user profile application. 12. The method of claim 8 , wherein collecting event data further includes: gathering, via the presentation server, the contract definitions corresponding to a given provider identification; transmitting the contract definitions to a client device to instantiate the universal tag, the universal tag including a universal tag reporter, wherein the universal tag reporter resolves event expressions at the client device and collects the evaluated event data; and receiving, at the presentation server, the key-value list of event names and values along with provider identification and user identification corresponding to the collected event data.