# US 12,112,125 B2 · Generating custom application links > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,112,125 B2 - Document ID: US12112125B2 - Status: Granted - Kind: B2 - Application number: 18/339,451 - Filed: 2023-06-22 - Published: 2023-10-19 - Granted: 2024-10-08 - Earliest claimed: 2017-06-09 - Assignees: Branch Metrics, Inc. - Applicants: Branch Metrics, Inc. - Inventors: Alexander Austin; William Lindemann; Cheng-chao Yang; Eric J. Glover; Dmitri Gaskin; Kan Yu; Sofus Macskassy - Web page: https://patentgrep.com/patent/US12112125B2 ## CPC - G06F 40/186: Templates - G06F 16/9535: Search customisation based on user profiles and personalisation - G06F 40/134: Hyperlinking - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A method includes receiving a request from a user device accessing a webpage, the request including a webpage uniform resource locator (URL) and a user device identifier. The method includes retrieving a list of events associated with the user device based on the device identifier. The method further includes retrieving sets of rules. Each set of rules indicates events and URLs that satisfy the set of rules. Each set of rules is associated with a template that includes link rendering data for rendering a link on the user device. The method includes identifying a set of rules that is satisfied by the received URL and events, transmitting link rendering data associated with the identified set of rules to the user device, and transmitting link routing data to the user device. The link routing data is configured to route the user device to an application state corresponding to the webpage. ## Claims ### Claim 1 A method comprising: receiving, at a computing device, a custom link request from a user device accessing a webpage, the custom link request including a uniform resource locator (URL) of the accessed webpage and a device identifier that uniquely identifies the user device; retrieving, at the computing device, a list of historic web events associated with the user device based on the device identifier, wherein each of the historic web events identifies a user action taken on a web browser installed on the user device; retrieving, at the computing device, sets of template rules, wherein each set of template rules indicates one or more partner-defined web events that satisfy the set of template rules, wherein each set of template rules indicates one or more URLs that satisfy the set of template rules, and wherein each set of template rules is associated with a custom link template that includes custom link rendering data for rendering a custom link on the user device; identifying, at the computing device, a set of template rules that is satisfied by the received URL and the retrieved list of historic web events associated with the user device; transmitting, from the computing device, custom link rendering data associated with the identified set of template rules to the user device; and transmitting, from the computing device, custom link routing data to the user device, wherein the custom link routing data is configured to route the user device to an application page of an application corresponding to the accessed webpage in response to user selection of the custom link rendered from the transmitted custom link rendering data. ### Claim 2 (depends on 1) The method of claim 1, wherein the accessed webpage is included on a website, and wherein one or more of the partner-defined web events are satisfied when the website has been accessed by the user device a specified number of times. ### Claim 3 (depends on 2) The method of claim 2, wherein one or more of the partner-defined web events are satisfied when the website has been accessed by the user device the specified number of times within a specified time window. ### Claim 4 (depends on 1) The method of claim 1, wherein the accessed webpage is included on a website, and wherein one or more of the partner-defined web events are satisfied when a specific webpage other than the accessed webpage has been accessed on the website by the user device. ### Claim 5 (depends on 1) The method of claim 1, wherein the accessed webpage is included on a website, and wherein one or more of the partner-defined web events are satisfied based on the absence of activity by the user device on the website within a specified period of time. ### Claim 6 (depends on 1) The method of claim 1, wherein the accessed webpage is included on a website, wherein the one or more partner-defined web events include a web commerce event, and wherein the web commerce event includes at least one of adding an item to a shopping cart on the website and completing a purchase on the website. ### Claim 7 (depends on 1) The method of claim 1, wherein the one or more partner-defined web events include a referral event that is satisfied when the accessed webpage is accessed from a referrer site. ### Claim 8 (depends on 7) The method of claim 7, wherein the referral event is satisfied when the accessed webpage is accessed from a specific referrer website domain. ### Claim 9 (depends on 8) The method of claim 8, wherein the referral event is satisfied when the accessed webpage is accessed from a specific referrer website URL. ### Claim 10 (depends on 7) The method of claim 7, wherein the referral event is satisfied when the accessed webpage is accessed in response to selection of a search result on a specified search engine page. ### Claim 11 (depends on 1) The method of claim 1, wherein the one or more partner-defined web events include selection of an advertisement link. ### Claim 12 (depends on 11) The method of claim 11, wherein the advertisement link is an email advertisement link. ### Claim 13 A system comprising: one or more storage devices configured to store computer-readable instructions; and one or more processing units configured to execute the computer-readable instructions, wherein the computer-readable instructions cause the one or more processing units to: receive a custom link request from a user device accessing a webpage, the custom link request including a uniform resource locator (URL) of the accessed webpage and a device identifier that uniquely identifies the user device; retrieve a list of historic web events associated with the user device based on the device identifier, wherein each of the historic web events identifies a user action taken on a web browser installed on the user device; retrieve sets of template rules, wherein each set of template rules indicates one or more partner-defined web events that satisfy the set of template rules, wherein each set of template rules indicates one or more URLs that satisfy the set of template rules, and wherein each set of template rules is associated with a custom link template that includes custom link rendering data for rendering a custom link on the user device; identify a set of template rules that is satisfied by the received URL and the retrieved list of historic web events associated with the user device; transmit custom link rendering data associated with the identified set of template rules to the user device; and transmit custom link routing data to the user device, wherein the custom link routing data is configured to route the user device to an application page of an application corresponding to the accessed webpage in response to user selection of the custom link rendered from the transmitted custom link rendering data. ### Claim 14 (depends on 13) The system of claim 13, wherein the accessed webpage is included on a website, and wherein one or more of the partner-defined web events are satisfied when the website has been accessed by the user device a specified number of times. ### Claim 15 (depends on 14) The system of claim 14, wherein one or more of the partner-defined web events are satisfied when the website has been accessed by the user device the specified number of times within a specified time window. ### Claim 16 (depends on 13) The system of claim 13, wherein the accessed webpage is included on a website, and wherein one or more of the partner-defined web events are satisfied when a specific webpage other than the accessed webpage has been accessed on the website by the user device. ### Claim 17 (depends on 13) The system of claim 13, wherein the accessed webpage is included on a website, and wherein one or more of the partner-defined web events are satisfied based on the absence of activity by the user device on the website within a specified period of time. ### Claim 18 (depends on 13) The system of claim 13, wherein the accessed webpage is included on a website, wherein the one or more partner-defined web events include a web commerce event, and wherein the web commerce event includes at least one of adding an item to a shopping cart on the website and completing a purchase on the website. ### Claim 19 (depends on 13) The system of claim 13, wherein the one or more partner-defined web events include a referral event that is satisfied when the accessed webpage is accessed from a referrer site. ### Claim 20 (depends on 19) The system of claim 19, wherein the referral event is satisfied when the accessed webpage is accessed from a specific referrer website domain. ### Claim 21 (depends on 20) The system of claim 20, wherein the referral event is satisfied when the accessed webpage is accessed from a specific referrer website URL. ### Claim 22 (depends on 19) The system of claim 19, wherein the referral event is satisfied when the accessed webpage is accessed in response to selection of a search result on a specified search engine page. ### Claim 23 (depends on 13) The system of claim 13, wherein the one or more partner-defined web events include selection of an advertisement link. ### Claim 24 (depends on 23) The system of claim 23, wherein the advertisement link is an email advertisement link.