Methods and apparatus to identify main page views

1. A computing system to credit webpage access by a client device, the computing system comprising:

a processor; and

at least one memory storing machine readable instructions that, when executed by the processor, cause the computing system to perform operations comprising:

accessing, from a proxy server, a log of requests made from the client device, the log of requests specifying a respective timestamp for each of the requests;

based on a length of a response time corresponding to a particular one of the requests relative to other response times corresponding to the other requests, identifying the particular one of the requests as a main page request that causes one or more servers to return a main webpage to present;

determining that the timestamps of the other requests occurred within a particular time interval relative to the timestamp of the main page request;

based on the determination that the timestamps of the other requests occurred within the particular time interval relative to the timestamp of the main page request, identifying the other requests as embedded page requests that cause the one or more servers to return embedded webpages to present within the main webpage; and

based on identifying the main page request and the embedded requests:

crediting the client device with viewing the main webpage corresponding to the main page request; and

discarding the embedded page requests from the crediting.

2. The computing system of claim 1 , wherein the particular time interval is 5 seconds.

3. The computing system of claim 1 , wherein identifying the particular one of the requests as the main page request based on the length of the response time corresponding to the particular one of the requests relative to the other response times corresponding to the other requests comprises identifying the particular one of the requests as the main page request based on the length of the response time corresponding to the particular one of the requests being greater than the other response times corresponding to the other requests.

4. The computing system of claim 1 , wherein identifying the particular one of the requests as the main page request is further based on a data size of the response time corresponding to the particular one of the requests being greater than other data sizes of the other requests.

5. The computing system of claim 1 , wherein the main page request includes a status code, the status code indicating the main webpage.

6. The computing system of claim 1 , wherein the main page request includes a uniform resource locator (URL), the URL indicating the main webpage.

7. The computing system of claim 1 , wherein crediting the client device with viewing the main webpage corresponding to the main page request comprises crediting the client device with viewing the main webpage for a particular duration.

8. The computing system of claim 1 , wherein determining that the timestamps of the other requests occurred within the particular time interval relative to the timestamp of the main page request comprises determining that the timestamps of the other requests occurred are the same as the timestamp of the main page request.

9. The computing system of claim 1 , wherein discarding the embedded page requests from crediting is further based on a determination that the embedded page requests are associated with known embedded uniform resource identifiers (URIs).

10. The computing system of claim 1 , wherein accessing the log of requests comprises accessing the log of requests via a Virtual Private Network (VPN), and wherein the main webpage is accessed via the VPN.

11. The computing system of claim 1 , the operations further comprising:

determining, for each of the requests, a corresponding lock status of the client device, wherein crediting the client device with viewing the main webpage corresponding to the main page request is further based on the lock status corresponding to the main page request, and

wherein discarding the embedded page requests from the crediting based on the lock statuses corresponding to the embedded page requests comprises discarding the embedded page requests from the crediting based on the lock statuses corresponding to the embedded page requests being locked statuses.

12. The computing system of claim 11 , wherein crediting the client device with viewing the main webpage corresponding to the main page request based on the lock status corresponding to the main page request comprises crediting the client device with viewing the main webpage corresponding to the main page request based on the lock status corresponding to the main page request being an unlocked status, and

wherein discarding the embedded page requests from the crediting based on the lock statuses corresponding to the embedded page requests comprises discarding the embedded page requests from the crediting based on each of the lock statuses corresponding to the embedded page requests each being a locked status.

13. A non-transitory computer readable medium comprising instructions that, when executed, cause a processor to perform operations comprising:

accessing, from a proxy server, a log of requests made from a client device, the log of requests specifying a respective timestamp for each of the requests;

based on a length of a response time corresponding to a particular one of the requests relative to other response times corresponding to the other requests, identifying the particular one of the requests as a main page request that causes one or more servers to return a main webpage to present:

determining that the timestamps of the other requests occurred within a particular time interval relative to the timestamp of the main page request;

based on the determination that the timestamps of the other requests occurred within the particular time interval relative to the timestamp of the main page request, identifying the other requests as embedded page requests that cause the one or more servers to return embedded webpages to present within the main webpage; and

based on identifying the main page request and the embedded requests:

crediting the client device with viewing the main webpage corresponding to the main page request; and

discarding the embedded page requests from the crediting.

14. The non-transitory computer readable medium of claim 13 , wherein crediting the client device with viewing the main webpage corresponding to the main page request comprises crediting the client device with viewing the main webpage for a particular duration.

15. The non-transitory computer readable medium of claim 13 , the operations further comprising:

determining, for each of the requests, a corresponding lock status of the client device, wherein crediting the client device with viewing the main webpage corresponding to the main page request is further based on the lock status corresponding to the main page request, and

wherein discarding the embedded page requests from the crediting based on the lock statuses corresponding to the embedded page requests comprises discarding the embedded page requests from the crediting based on the lock statuses corresponding to the embedded page requests being locked statuses.

16. The non-transitory computer readable medium of claim 13 , wherein identifying the particular one of the requests as the main page request based on the length of the response time corresponding to the particular one of the requests relative to the other response times corresponding to the other requests comprises identifying the particular one of the requests as the main page request based on the length of the response time corresponding to the particular one of the requests being greater than the other response times corresponding to the other requests.

17. The non-transitory computer readable medium of claim 13 , wherein determining that the timestamps of the other requests occurred within the particular time interval relative to the timestamp of the main page request comprises determining that the timestamps of the other requests occurred are the same as the timestamp of the main page request.

18. A method performed by a computing system, the method comprising:

accessing, from a proxy server, a log of requests made from a client device, the log of requests specifying a respective timestamp for each of the requests;

based on a length of a response time corresponding to a particular one of the requests relative to other response times corresponding to the other requests, identifying the particular one of the requests as a main page request that causes one or more servers to return a main webpage to present;

determining that the timestamps of the other requests occurred within a particular time interval relative to the timestamp of the main page request;

based on the determination that the timestamps of the other requests occurred within the particular time interval relative to the timestamp of the main page request, identifying the other requests as embedded page requests that cause the one or more servers to return embedded webpages to present within the main webpage; and

based on identifying the main page request and the embedded requests:

crediting the client device with viewing the main webpage corresponding to the main page request; and

discarding the embedded page requests from the crediting.

19. The method of claim 18 , wherein identifying the particular one of the requests as the main page request based on the length of the response time corresponding to the particular one of the requests relative to the other response times corresponding to the other requests comprises identifying the particular one of the requests as the main page request based on the length of the response time corresponding to the particular one of the requests being greater than the other response times corresponding to the other requests.

20. The method of claim 18 , wherein determining that the timestamps of the other requests occurred within the particular time interval relative to the timestamp of the main page request comprises determining that the timestamps of the other requests occurred are the same as the timestamp of the main page request.