Persist and process analytics data dimensions for server-side sessionization
First Claim
1. A machine-implemented method for propagating information from an initial analytics tracking data communication to subsequent analytics tracking data communications at an analytics server, the method comprising:
- receiving, by a processor of an analytics server, campaign information comprising uniform resource identifiers for a set of webpages of a content publisher defined by the content publisher as associated with a campaign from among a total set of webpages for a website of the content publisher, at least one of the uniform resource identifiers or a referral path included in communications received by the processor responsive to visits to a webpage of the set of webpages indicating a campaign type with which the incoming traffic is associated from among a plurality of campaign types;
receiving, by the processor of the analytics server, a communication generated responsive to a client visiting a first webpage of a set of webpages of a content publisher, the communication comprising at least one of a first uniform resource identifier of the first webpage or a first referrer path leading to the first webpage, the communication including analytics tracking data for tracking activity of the client visiting the first webpage;
storing the analytics tracking data in non-persistent storage to allow for later-received analytics tracking data to be combined with the tracking data stored in the non-persistent storage;
determining that the analytics tracking data included in the received communication indicates that the received communication is associated with the same client and the same campaign as the initial analytics tracking data communication using the at least one of the first uniform resource identifier or the first referrer path indicating the campaign type with which the visit to the first webpage is associated and by determining a second webpage associated with the initial analytics tracking data communication belongs to the set of webpages defined by the content publisher as being associated with the campaign;
identifying attributes in the analytics tracking data included in the received communication;
identifying one or more previously stored attributes, associated with at least one of the client or the campaign, that are not present in the analytics tracking data included in the received communication responsive to determining the received communication is associated with the same client and the same campaign as the initial analytics tracking data communication;
propagating the identified one or more previously stored attributes from previously received analytics tracking data to the analytics tracking data stored in the non-persistent storage and merging the analytics tracking data with the propagated attributes; and
storing the analytics tracking data including the propagated attributes in a persistent memory operably coupled to the analytics server to be included in subsequent analytics tracking data communications.
2 Assignments
0 Petitions
Accused Products
Abstract
The subject technology provides configurations for propagating information from an initial analytics tracking data communication to subsequent analytics tracking data communications at an analytics server. In one example, the subject technology receives an analytics tracking data communication. The subject technology determines if the received analytics tracking data communication includes state changing information based on analytics tracking data included in the analytics tracking data communication. The subject technology then determines one or more attributes for propagating to subsequent analytics tracking data if the analytics tracking data communication includes state changing information. The state changing information are stored as one or more of the determined one or more attributes. The subject technology stores the analytics tracking data including the determined one or more attributes.
55 Citations
18 Claims
-
1. A machine-implemented method for propagating information from an initial analytics tracking data communication to subsequent analytics tracking data communications at an analytics server, the method comprising:
-
receiving, by a processor of an analytics server, campaign information comprising uniform resource identifiers for a set of webpages of a content publisher defined by the content publisher as associated with a campaign from among a total set of webpages for a website of the content publisher, at least one of the uniform resource identifiers or a referral path included in communications received by the processor responsive to visits to a webpage of the set of webpages indicating a campaign type with which the incoming traffic is associated from among a plurality of campaign types; receiving, by the processor of the analytics server, a communication generated responsive to a client visiting a first webpage of a set of webpages of a content publisher, the communication comprising at least one of a first uniform resource identifier of the first webpage or a first referrer path leading to the first webpage, the communication including analytics tracking data for tracking activity of the client visiting the first webpage; storing the analytics tracking data in non-persistent storage to allow for later-received analytics tracking data to be combined with the tracking data stored in the non-persistent storage; determining that the analytics tracking data included in the received communication indicates that the received communication is associated with the same client and the same campaign as the initial analytics tracking data communication using the at least one of the first uniform resource identifier or the first referrer path indicating the campaign type with which the visit to the first webpage is associated and by determining a second webpage associated with the initial analytics tracking data communication belongs to the set of webpages defined by the content publisher as being associated with the campaign; identifying attributes in the analytics tracking data included in the received communication; identifying one or more previously stored attributes, associated with at least one of the client or the campaign, that are not present in the analytics tracking data included in the received communication responsive to determining the received communication is associated with the same client and the same campaign as the initial analytics tracking data communication; propagating the identified one or more previously stored attributes from previously received analytics tracking data to the analytics tracking data stored in the non-persistent storage and merging the analytics tracking data with the propagated attributes; and storing the analytics tracking data including the propagated attributes in a persistent memory operably coupled to the analytics server to be included in subsequent analytics tracking data communications. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 17, 18)
-
-
10. A system, comprising:
-
memory; a processor configured to execute instructions stored in memory, the processor configured to receive campaign information comprising uniform resource identifiers for a set of webpages of a content publisher defined by the content publisher as associated with a campaign from among a total set of webpages for a website of the content publisher, at least one of the uniform resource identifiers or a referral path included in communications received by the processor responsive to visits to a webpage of the set of webpages indicating a campaign type with which the incoming traffic is associated from among a plurality of campaign types; receive a communication generated responsive to a client visiting a first webpage of a set of webpages of a content publisher, the communication comprising at least one of a first uniform resource identifier of the first webpage or a first referrer path leading to the first webpage, the communication including analytics tracking data for tracking activity of the client visiting the first webpage; store the analytics tracking data in non-persistent storage to allow for later-received analytics tracking data to be combined with the tracking data stored in the non-persistent storage; determine that the analytics tracking data included in the received communication indicates that the received communication is associated with the same client and the same campaign as the initial analytics tracking data communication using the at least one of the first uniform resource identifier or the first referrer path indicating the campaign type with which the visit to the first webpage is associated and by determining a second webpage associated with the initial analytics tracking data communication belongs to the set of webpages defined by the content publisher as being associated with the campaign; identify attributes in the analytics tracking data included in the received communication; identify one or more previously stored attributes, associated with at least one of the client or the campaign, that are not present in the analytics tracking data included in the received communication responsive to determining the received communication is associated with the same client and the same campaign as the initial analytics tracking data communication; propagate the identified one or more previously stored attributes from previously received analytics tracking data to the analytics tracking data stored in the non-persistent storage and merge the analytics tracking data with the propagated attributes; and store the analytics tracking data including the propagated attributes in a persistent memory operably coupled to the analytics server to be included in subsequent analytics tracking data communications. - View Dependent Claims (11, 12, 13, 14, 15)
-
-
16. A non-transitory machine-readable medium comprising instructions stored therein, which when executed by a machine, cause the machine to perform operations comprising:
-
receiving campaign information comprising uniform resource identifiers for a set of webpages of a content publisher defined by the content publisher as associated with a campaign from among a total set of webpages for a website of the content publisher, at least one of the uniform resource identifiers or a referral path included in communications received by the processor responsive to visits to a webpage of the set of webpages indicating a campaign type with which the incoming traffic is associated from among a plurality of campaign types; receiving a communication generated responsive to a client visiting a first webpage of a set of webpages of a content publisher, the communication comprising at least one of a first uniform resource identifier of the first webpage or a first referrer path leading to the first webpage, the communication including analytics tracking data for tracking activity of the client visiting the first webpage; storing the analytics tracking data in non-persistent storage to allow for later-received analytics tracking data to be combined with the tracking data stored in the non-persistent storage; determining that the analytics tracking data included in the received communication indicates that the received communication is associated with the same client and the same campaign as the initial analytics tracking data communication using the at least one of the first uniform resource identifier or the first referrer path indicating the campaign type with which the visit to the first webpage is associated and by determining a second webpage associated with the initial analytics tracking data communication belongs to the set of webpages defined by the content publisher as being associated with the campaign; identifying attributes in the analytics tracking data included in the received communication; identifying one or more previously stored attributes, associated with at least one of the client or the campaign, that are not present in the analytics tracking data included in the received communication responsive to determining the received communication is associated with the same client and the same campaign as the initial analytics tracking data communication; determining a first set of the identified previously stored attributes designated to be propagated from previously received analytics tracking data to the analytics tracking data included in the received communication; determining a second set of the identified previously stored attributes designated to not be propagated from previously received analytics tracking data to the analytics tracking data included in the received communication; propagating the first set of attributes to the analytics tracking data stored in the non-persistent storage and merging the analytics tracking data with the propagated attributes; restricting the second set of attributes from propagating to the analytics tracking data; and storing the analytics tracking data including the propagated attributes in a persistent memory operably coupled to the analytics server to be included in subsequent analytics tracking data communications.
-
Specification