GENERATING AND ASSOCIATING TRACKING EVENTS ACROSS ENTITY LIFECYCLES

1 . A method, comprising:

providing a schema for including, by a set of components in a multi-tier architecture, a tracking identifier for an entity instance in the multi-tier architecture;

identifying, from a set of tracking events received from the multi-tier architecture, a subset of the tracking events comprising the tracking identifier;

grouping, by a computer system, the subset of the tracking events into an entity lifecycle for the entity instance; and

outputting the entity lifecycle for use in assessing a performance of the multi-tier architecture by a consumer of tracking data.

2 . The method of claim 1 , further comprising:

grouping the set of tracking events by one or more event types and one or more tracking scopes.

3 . The method of claim 2 , wherein the one or more event types comprise at least one of:

a serving event;

a rendering event;

a view event;

an action event;

an interaction event; and

a navigation event.

4 . The method of claim 2 , wherein the one or more tracking scopes comprise at least one of:

a session;

a browser;

a request;

a page; and

a module.

5 . The method of claim 1 , wherein including the tracking identifier for the entity instance in the multi-tier architecture comprises:

generating the tracking identifier at a first component associated with creating the entity instance; and

propagating the tracking identifier from the first component to a second component that performs additional processing using the entity instance.

6 . The method of claim 1 , wherein grouping the tracking events into the entity lifecycle for the entity comprises:

ordering the tracking events by timestamps and event types in the tracking events.

7 . The method of claim 1 , wherein identifying the subset of the tracking events comprising the tracking identifier comprises:

receiving the set of tracking events in an event stream; and

filtering the tracking events by the tracking identifier.

8 . The method of claim 1 , further comprising:

obtaining, from the set of tracking events, an additional subset of the tracking events comprising an additional tracking identifier; and

using the additional tracking identifier to group the subset into an additional entity lifecycle for an additional entity instance in the multi-tier architecture.

9 . The method of claim 1 , wherein the set of tracking events further comprises at least one of:

a timestamp;

an event name;

an event type;

an entity type;

a tracking scope;

an additional identifier;

client-side data; and

event metadata.

10 . The method of claim 1 , wherein the set of components comprises at least one of:

a client;

a frontend component;

a backend component; and

a middle tier component.

11 . The method of claim 1 , wherein the entity instance is at least one of:

a resource;

a user-interface element;

a page;

a user;

a statistical model;

data; and

metadata.

12 . An apparatus, comprising:

one or more processors; and

memory storing instructions that, when executed by the one or more processors, cause the apparatus to:

provide a schema for including, by a set of components in a multi-tier architecture, a tracking identifier for an entity instance in the multi-tier architecture;

identifying, from a set of tracking events received from the multi-tier architecture, a subset of the tracking events comprising the tracking identifier;

group the subset of the tracking events into an entity lifecycle for the entity instance; and

output the entity lifecycle for use in assessing a performance of the multi-tier architecture by a consumer of tracking data.

13 . The apparatus of claim 12 , wherein the memory further stores instructions that, when executed by the one or more processors, cause the apparatus to:

group the set of tracking events by one or more event types and one or more tracking scopes.

14 . The apparatus of claim 12 , wherein including the tracking identifier for the entity instance in the multi-tier architecture comprises:

generating the tracking identifier at a first component associated with creating the entity instance; and

propagating the tracking identifier from the first component to a second component that performs additional processing using the entity instance.

15 . The apparatus of claim 12 , wherein grouping the tracking events into the entity lifecycle for the entity comprises:

ordering the tracking events by timestamps and event types in the tracking events.

16 . The apparatus of claim 12 , wherein identifying the subset of the tracking events comprising the tracking identifier comprises:

receiving the set of tracking events in an event stream; and

filtering the tracking events by the tracking identifier.

17 . The apparatus of claim 12 , wherein the entity instance is at least one of:

a resource;

a user-interface element;

a page;

a user;

a statistical model;

data; and

metadata.

18 . The apparatus of claim 12 , wherein the set of tracking events further comprises at least one of:

a timestamp;

an event name;

an event type;

an entity type;

a tracking scope;

an additional identifier;

client-side data; and

event metadata.

19 . A system, comprising:

an analysis module comprising a non-transitory computer-readable medium comprising instructions that, when executed, cause the system to:

provide a schema for including, by a set of components in a multi-tier architecture, a tracking identifier for an entity instance in the multi-tier architecture;

identify, from a set of tracking events received from the multi-tier architecture, a subset of the tracking events comprising the tracking identifier; and

group the subset of the tracking events into an entity lifecycle for the entity instance; and

a management module comprising a non-transitory computer-readable medium comprising instructions that, when executed, cause the system to output the entity lifecycle for use in assessing a performance of the multi-tier architecture by a consumer of tracking data.

20 . The system of claim 19 , wherein including the tracking identifier for the entity instance in the multi-tier architecture comprises:

generating the tracking identifier at a first component associated with creating the entity instance; and

propagating the tracking identifier from the first component to a second component that performs additional processing using the entity instance.