# US 9,418,170 B2 · Creating rules for use in third-party tag management systems > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 9,418,170 B2 - Document ID: US9418170B2 - Status: Granted - Kind: B2 - Application number: 13/890,863 - Filed: 2013-05-09 - Published: 2014-09-18 - Granted: 2016-08-16 - Earliest claimed: 2013-03-14 - Assignees: Observepoint, Inc. - Applicants: Robert K. Seolas; John Pestana; Matthew T. Miller; Alan Martin Feuerlein - Inventors: Robert K. Seolas; John Pestana; Matthew T. Miller; Alan Martin Feuerlein - Web page: https://patentgrep.com/patent/US9418170B2 ## CPC - G06F 16/9566: {URL specific, e.g. using aliases, detecting broken or misspelled links} - G06F 16/951: Indexing; Web crawling techniques - G06F 16/986: {Document structures and storage, e.g. HTML extensions} - G06Q 30/00: Commerce - H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP] - 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 - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Methods and system allow for creating rules for a tag management system. One or more implementations create rules for a tag management system can include crawling a page of a website. Additionally, one or more implementations identify the configuration of each of the tags implemented within the page. Further, one or implementations generate one or more rules that enable a tag management system to recreate the configuration of one or more tags implemented within the page. Further still, one or more implementations export the generated one or more rules to a tag management system. ## Claims ### Claim 1 In an online webpage in which webpage content is loaded into memory and processed at a central processing unit, a computer-implemented method for creating rules for a tag management system, the method comprising receiving a universal resource locator (URL) that is associated with a target website; accessing through a network connection the target website, wherein accessing the target website comprises downloading source code that describes one or more webpages within the target website; rendering at least a portion of the source code, wherein rendering at least the portion of the source code includes rendering multimedia content referenced within the source code; identifying, with a computer processor, one or more tags associated with a webpage, wherein the association of the one or more tags with the webpage is identified by: comparing the source code of the webpage and behaviors of the rendered portion of the source code to signatures within a tag signature database; based upon information within the tag signature database and detected behaviors of each of the one or more tags, identifying the configuration of each of the one or more tags implemented within the webpage; generating, with a rule creation module, one or more rules for the webpage that enable a tag management system to recreate the identified configuration of the one or more tags implemented within the webpage; and exporting the generated one or more rules to the tag management system. ### Claim 2 (depends on 1) The method as recited in claim 1, further comprising: identifying one or more tag patterns across a plurality of pages within a website; and generating one or more rules that enable a tag management system to recreate the one or more identified tag patterns. ### Claim 3 (depends on 1) The method as recited in claim 1, further comprising: determining, with the computer processor, that insufficient information is available to fully characterize a particular tag; based upon the identified configuration of the particular tag, creating an incomplete rule that describes the particular tag, wherein the incomplete rule does not fully characterize the particular tag; and generating a user information request, wherein the user information request prompts a user to provide additional information to fully characterize the particular tag. ### Claim 4 (depends on 1) The method as recited in claim 1, further comprising: identifying that the configuration of at least one tag implemented within the page includes at least one variable. ### Claim 5 (depends on 4) The method as recited in claim 4, further comprising: determining potential values for the at least one variable; and generating one or more rules that enable the tag management system to recreate the configuration of the at least one tag implemented within the page. ### Claim 6 (depends on 4) The method as recited in claim 4, further comprising: notifying a user of the identified at least one tag and the identified at least one variable; and receiving, from a user, input relating to at least a portion of the one or more rules that enable the tag management system to recreate the configuration of the at least one tag implemented within the page. ### Claim 7 (depends on 1) The method as recited in claim 1, further comprising: rendering the page of the website; and identifying the configuration of each tag on the page as the page is rendered. ### Claim 8 (depends on 7) The method of claim 7, further comprising: executing a multimedia file that is embedded within the page of the website; and identifying at least one tag that is associated with the multimedia file. ### Claim 9 (depends on 1) The method as recited in claim 1, further comprising: identifying at least one tag that is adapted to execute a specific code portion only on a first page of a particular session; and generating one or more rules that enable a tag management system to recreate the configuration of the at least one tag. ### Claim 10 (depends on 1) The method as recited in claim 1, further comprising: receiving from a user an indication of a specific format in which to export the generated one or more rules to the tag management system. ### Claim 11 In an online webpage in which webpage content is loaded into memory and processed at a central processing unit, a computer-implemented method for creating rules for a tag management system, the method comprising: crawling each one or more pages of a website; identifying one or more tags implemented within each of the one or more pages by comparing source code associated with each of the one or more tags to a database of tag signatures; identifying, with the central processing unit, one or more patterns of the one or more tags implemented within the one or more pages of the website, wherein the one or more patterns comprise common tags and common tag configurations appearing across hierarchically related webpages; generating, with a rule creation module, one or more rules that are configured to enable a tag management system to recreate the one or more identified patterns, wherein the one or more rules describe the common tags and common tag configurations appearing across the hierarchically related webpages; and exporting the generated one or more rules. ### Claim 12 (depends on 11) The method as recited in claim 11, further comprising: accessing the database of tag signatures; and identifying a configuration of each of the tags implemented within the page using information stored within the database of tag signatures. ### Claim 13 (depends on 11) The method as recited in claim 11, further comprising: identifying that the configuration of at least one tag implemented within a page of the website includes at least one variable. ### Claim 14 (depends on 13) The method as recited in claim 13, further comprising: determining potential values for the at least one variable; and generating one or more rules that enable the tag management system to recreate the configuration of the at least one tag implemented within the page. ### Claim 15 (depends on 14) The method as recited in claim 14, further comprising: notifying a user of the identified at least one tag and the identified at least one variable; and receiving, from a user, input relating to at least a portion of the one or more rules that enable the tag management system to recreate the configuration of the at least one tag implemented within the page. ### Claim 16 (depends on 11) The method as recited in claim 11, further comprising: rendering the page of the website; and identifying the configuration of each tag on the page as the page is rendered. ### Claim 17 (depends on 16) The method as recited in claim 16, further comprising: executing a multimedia file that is embedded within the page of the website; and identifying at least one tag that is associated with the multimedia file. ### Claim 18 (depends on 11) The method as recited in claim 11, further comprising: identifying at least one tag that is adapted to execute a specific code portion only on a first page of a particular session; and generating one or more rules that enable a tag management system to recreate the configuration of the at least one tag. ### Claim 19 (depends on 11) The method as recited in claim 11, further comprising: receiving from a user an indication of a specific format in which to export the generated one or more rules to the tag management system. ### Claim 20 A computer program product for use at a computer system, the computer program product for implementing a method for creating rules for a tag management system, the computer program product comprising one or more computer storage media having stored thereon computer-executable instructions that, when executed at a processor, cause the computer system to perform the method, including the following: crawling a webpage of a website; based upon information within a database of tag signatures and detected behaviors of each of one or more tags, identifying the configuration of each of the tags implemented within the page; generating, with a rule creation module, one or more rules for the webpage that enable a tag management system to recreate the identified configuration of the one or more tags implemented within the crawled webpage, wherein the one or more rules are based at least in part upon the information within the database of tag signatures; and exporting the generated one or more rules to the tag management system. ### Claim 21 A computer system for creating rules for a tag management system, comprising one or more processors; and one or more computer-readable media having stored thereon executable instructions that when executed by the one or more processors configure the computer system to perform at least the following: receive a universal resource locator (URL) that is associated with a target website; access through a network connection the target website, wherein accessing the target website comprises downloading source code that describes one or more webpages within the target website; render at least a portion of the source code, wherein rendering at least the portion of the source code includes rendering multimedia content referenced within the source code; identify, with a computer processor, one or more tags associated with a webpage, wherein the association of the one or more tags with the webpage is identified by: comparing the source code of the webpage and behaviors of the rendered portion of the source code to signatures within a tag signature database; based upon information within the tag signature database and detected behaviors of each of the one or more tags, identify the configuration of each of the one or more tags implemented within the webpage; generate, with a rule creation module, one or more rules for the webpage that enable a tag management system to recreate the identified configuration of the one or more tags implemented within the webpage; and export the generated one or more rules to the tag management system. ### Claim 22 (depends on 1) The method as recited in claim 1, wherein the behaviors of the rendered portion of the source code includes resulting network requests. ### Claim 23 (depends on 21) The system as recited in claim 21, wherein the behaviors of the rendered portion of the source code includes resulting network requests.