Computing usage metrics for a content sharing platform

• US 9,953,068 B1
• Filed: 10/16/2013
• Issued: 04/24/2018
• Est. Priority Date: 10/16/2013
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google LLC (Alphabet Inc.)
• Inventors: Taboriskiy, Alexander, Landers, Martin
• Primary Examiner(s): To, Baoquoc N
• Assistant Examiner(s): Ahmed, Saba
• Application Number:
  US14/055,363
• Time in Patent Office: 1,651 Days
• Field of Search: 707755
• CPC Class Codes: G06F 16/2474 Sequence data queries, e.g. querying versioned data
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34

Abstract

A method for computing usage metrics for a content sharing platform is disclosed. The method includes receiving usage logs of a content sharing platform, the usage logs pertaining to a plurality of events associated with content items of the content sharing platform. The method further includes, for each usage log, identifying an event associated with the usage log, parsing the usage log to identify a set of characteristics for the identified event, obtaining additional information about the identified event based on the set of characteristics, and storing the set of characteristics and the additional information as an event entry for the event. The method also includes storing metadata corresponding to the event separately from the event entry, the metadata to be provided with the event entry to a user upon a user request for information about the event.

Claims

1. A method comprising:

receiving, by a processing device, usage logs of a content sharing platform, the usage logs pertaining to events associated with content items of the content sharing platform, wherein the usage logs comprise data pertaining to the events, the data stored using an unstructured format;

for each usage log, processing the usage log in a single parsing and processing pipeline executed by the processing device, where the single parsing and processing pipeline is to;

identify an event associated with the usage log;

parse the unstructured format of the data of the usage log to identify parsed data comprising a set of characteristics for the identified event, wherein parsing the unstructured format of the data comprises delineating the data to associate with different fields corresponding to the set of characteristics for the identified event;

derive classification data about the identified event from the parsed data, the classification data not comprised in the data of the usage log and comprising at least a source of the event and a type of device associated with the event; and

store the parsed data and the classification data as an event entry for the event, wherein the event entry is stored using a structured format; and

storing metadata corresponding to the event separately from the event entry, the metadata to be combined with the event entry to create a log entry, wherein the log entry is provided as a response to a request for information about the event received from a downstream pipeline.

2. The method of claim 1, wherein the set of characteristics comprise at least one of referrer uniform resource locator (URL), a device family, a view type bitmask, a total watch time, or a playback URL.

3. The method of claim 1, wherein the metadata comprises at least one of a channel associated with the one or more content items, owners of the one or more content items, whether the one or more content items are public or private, a list of claims on the one or more content items, or a time of creation of the one or more content items.

4. The method of claim 1, wherein the request comprises a request to generate a report on at least a portion of the usage logs, and wherein the parsed data and the classification data are made available for use in generating the report.

5. The method of claim 4, further comprising aggregating one or more log entries comprising combined event entry and metadata corresponding to one or more content items for the report.

6. The method of claim 1, wherein the deriving the classification data further comprises:

determining the source of the event;

determining the type of device associated with the event;

determining whether the event is to be counted based on a watch time of the event; and

determining whether the event is a promotion.

7. The method of claim 1, wherein the events comprise user requests to view the content items streamed from the content sharing platform.

8. The method of claim 1, wherein the usage logs comprises HyperText Transport Protocol (HTTP) request strings sent from devices of the users when requesting to view the content items.

9. The method of claim 1, wherein the event entry comprises an event baseview entry.

10. A non-transitory machine-readable storage medium storing instructions which, when executed, cause a processing device to perform operations comprising:

receiving, by the processing device, usage logs of a content sharing platform, the usage logs pertaining to events associated with content items of the content sharing platform, wherein the usage logs comprise data pertaining to the events, the data stored using an unstructured format;

for each usage log, processing the usage log in a single parsing and processing pipeline executed by the processing device, where the single parsing and processing pipeline is to;

identify an event associated with the usage log;

parse the unstructured format of the data of the usage log to identify parsed data comprising a set of characteristics for the identified event, wherein parsing the unstructured format of the data comprises delineating the data to associate with different fields corresponding to the set of characteristics for the identified event;

derive classification data about the identified event from the parsed data, the classification data not comprised in the data of the usage log and comprising at least a source of the event and a type of device associated with the event; and

store the parsed data and the classification data as an event entry for the event, wherein the event entry is stored using a structured format; and

storing metadata corresponding to the event separately from the event entry, the metadata to be combined with the event entry to create a log entry, wherein the log entry is provided as a response to a request for information about the event received from a downstream pipeline.

11. The non-transitory machine-readable storage medium of claim 10, wherein the set of characteristics comprise at least one of referrer uniform resource locator (URL), a device family, a view type bitmask, a total watch time, or a playback URL.

12. The non-transitory machine-readable storage medium of claim 10, wherein the metadata comprises at least one of a channel associated with the one or more content items, owners of the one or more content items, whether the one or more content items are public or private, a list of claims on the one or more content items, or a time of creation of the one or more content items.

13. The non-transitory machine-readable storage medium of claim 10, wherein the request comprises a request to generate a report on at least a portion of the usage logs, and wherein the parsed data and the classification data are made available for use in generating the report.

14. The non-transitory machine-readable storage medium of claim 13, further comprising aggregating one or more log entries comprising combined event entry and metadata corresponding to one or more content items for the report.

15. The non-transitory machine-readable storage medium of claim 10, wherein the deriving the classification data further comprises:

determining the source of the event;

determining type of device associated with the event;

determining whether the event is to be counted based on a watch time of the event; and

determining whether the event is a promotion.

16. A system comprising:

a processing device;

a memory coupled to the processing device, the memory to store a plurality of media items; and

a log processing component executable by the processing device from the memory, the log processing component to;

receive usage logs of a content sharing platform, the usage logs pertaining to events associated with content items of the content sharing platform, wherein the usage logs comprise data pertaining to the events, the data stored using an unstructured format;

for each usage log, process the usage log in a single parsing and processing pipeline executed by the processing device, where the single parsing and processing pipeline is to;

identify an event associated with the usage log;

parse the unstructured format of the data of the usage log to identify parsed data comprising a set of characteristics for the identified event, wherein parsing the unstructured format of the data comprises delineating the data to associate with different fields corresponding to the set of characteristics for the identified event;

derive classification data about the identified event from the parsed data, the classification data not comprised in the data of the usage log and comprising at least a source of the event and a type of device associated with the event; and

store the parsed data and the classification data as an event entry for the event, wherein the event entry is stored using a structured format; and

a metadata processing component executable by the processing device from the memory, the metadata processing component to metadata corresponding to the event separately from the event entry, the metadata to be combined with the event entry to create a log entry, wherein the log entry is provided as a response to a request for information about the event received from a downstream pipeline.

17. The system of claim 16, wherein the set of characteristics comprise at least one of referrer uniform resource locator (URL), a device family, a view type bitmask, a total watch time, or a playback URL.

18. The system of claim 16, wherein the metadata comprises at least one of a channel associated with the one or more content items, owners of the one or more content items, whether the one or more content items are public or private, a list of claims on the one or more content items, or a time of creation of the one or more content items.

19. The system of claim 16, further comprising an analytics component to aggregate one or more log entries comprising combined event entry and metadata corresponding to one or more content items for the report.

20. The system of claim 16, wherein the logs processing component to derive the classification data further comprises the logs processing component to:

determine the source of the event;

determine the type of device associated with the event;

determine whether the event is to be counted based on a watch time of the event; and

determine whether the event is a promotion.