# US 11,444,856 B2 · Systems and methods for configuring a resource for network traffic analysis > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,444,856 B2 - Document ID: US11444856B2 - Status: Granted - Kind: B2 - Application number: 17/107,777 - Filed: 2020-11-30 - Published: 2021-03-18 - Granted: 2022-09-13 - Earliest claimed: 2015-08-25 - Assignees: Google Inc. - Applicants: Google LLC - Inventors: Frank Geert Kieviet; Matthew Matyas; Robert Gardner; Martin Trieu; David Wieser; Anthony Medeiros; Andres Albano; Zohar Postelnicu; Ajay Nainani; Jens Trapp - Web page: https://patentgrep.com/patent/US11444856B2 ## CPC - H04L 43/045: for graphical visualisation of monitoring data - G06F 11/323: {Visualisation of programs or trace data} - G06F 11/3438: {monitoring of user actions (tracking the activity of the user H04L67/535)} - G06F 11/3466: {Performance evaluation by tracing or monitoring} - G06F 11/3612: {by runtime analysis (performance monitoring G06F11/3466)} - G06Q 10/06: Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling - G06Q 10/063: Operations research, analysis or management - H04L 41/0246: Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols - H04L 43/00: Arrangements for monitoring or testing data switching networks - H04L 43/062: related to network traffic - H04L 43/10: Active monitoring, e.g. heartbeat, ping or trace-route - H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP] - H04L 67/06: specially adapted for file transfer, e.g. file transfer protocol [FTP] - H04L 67/53: using third party service providers - G06F 2201/875: Monitoring of systems including the internet - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR ## Abstract The present disclosure is directed to systems and methods of configuring a resource for network traffic analysis. An agent executed by a computing device receives an indication to record a browsing session. The agent records network activity data of the browsing session. The agent generates a data file with the recording. The agent transmits the data file and a request to generate a report to an analytics server. The analytics server receives the request and extracts the network activity data from the data file. The analytics server applies an event processing protocol to the network activity data. The analytics server generates a report and transmits the report to the client device for display. ## Claims ### Claim 1 A method of analyzing traffic over a computing network, comprising: providing, by a computer executing computer executable instructions, a tag and a tracking code for recording network traffic on a browser session corresponding to a webpage, the tracking code configured for insertion into code of the webpage; receiving, at the computer responsive to activation of the tracking code associated with the tag, data of the network traffic of the webpage; and validating, by the computer, a status of operation of the tag using the data, wherein validating, by the computer, the status of operation of the tag comprises determining whether the tag is in a normal function state or a tag malfunction state. ### Claim 2 (depends on 1) The method of claim 1, wherein validating the status of operation of the tag further comprises identifying an issue correlated to the tag malfunction state. ### Claim 3 (depends on 2) The method of claim 2, wherein validating the status of operation of the tag further comprises determining, by the computer, a corrective action for the malfunction state. ### Claim 4 (depends on 3) The method of claim 3, wherein the corrective action corrects an error attributable to an improper configuration of the tag. ### Claim 5 (depends on 1) The method of claim 1, further comprising testing a conversion goal corresponding to the tag. ### Claim 6 (depends on 5) The method of claim 5, further comprising determining a conversion status for the conversion goal corresponding to the tag. ### Claim 7 (depends on 1) The method of claim 1, further comprising displaying, via a display device, the status of operation of the tag, wherein the status of operation of the tag is represented on the display device by an icon, the icon comprising a status indicator and a number of tag requests. ### Claim 8 (depends on 1) The method of claim 1, wherein validating the status of operation of the tag comprises identifying a tag related event. ### Claim 9 (depends on 1) The method of claim 1, further comprising applying a corrective action responsive to the status of operation of the tag. ### Claim 10 A non-transitory computer readable medium, including computer executable instructions, which when executed by a computer cause the computer to: provide a tag and a tracking code for recording network traffic on a browser session corresponding to a webpage, the tracking code configured for insertion into code of the webpage; receive, responsive to activation of the tracking code associated with the tag, data of the network traffic of the webpage; and validate a status of operation of the tag using the data; wherein the instructions are configured to cause the computer to validate the status of operation of the tag by determining whether the tag is in a tag normal function state or a tag malfunction state. ### Claim 11 (depends on 10) The non-transitory computer readable medium of claim 10, wherein the instructions are further configured to cause the computer to validate the status of operation of the tag further by determining a corrective action for the tag malfunction state. ### Claim 12 (depends on 10) The non-transitory computer readable medium of claim 10, wherein the instructions are further configured to cause the computer to test a conversion goal, wherein the conversion goal is associated with the at least one tag. ### Claim 13 (depends on 12) The non-transitory computer readable medium of claim 12, wherein the instructions are further configured to cause the computer to generate a test report, wherein the test report comprises an indication of a successful conversion and an indication of a conversion irregularity. ### Claim 14 (depends on 11) The non-transitory computer readable medium of claim 11, wherein the corrective action corrects an error attributable to an improper configuration of the tag. ### Claim 15 (depends on 10) The non-transitory computer readable medium of claim 10, wherein the instructions are further configured to cause the computer to display, via a display device, the status of operation of the tag, wherein the status of operation of the tag is represented on the display device by an icon, the icon comprising a status indicator and a number of tag requests. ### Claim 16 (depends on 10) The non-transitory computer readable medium of claim 10, wherein the instructions are further configured to cause the computer to validate the status of operation of the tag by identifying an issue correlated to the tag malfunction state. ### Claim 17 (depends on 10) The non-transitory computer readable medium of claim 10, wherein the instructions are further configured to cause the computer to validate the status of operation of the tag by identifying at least one tag related event. ### Claim 18 (depends on 10) The non-transitory computer readable medium of claim 10, wherein the instructions are further configured to cause the computer to apply a corrective action responsive to the status of operation of the tag.