The present subject matter relates generally to systems and methods for adding interactive functionality to a website, other digital media objects, and computer processor applications. Systems and methods for adding functionality to content served by a first server, may include receiving, at a second server, a request from a client-computer for code to add purchase functionality to the content. The code may be sent to the client-computer based on the request. A further request may be received from the client-computer containing information about objects identified in the content as relating to the purchase functionality and a request for information about the objects. Information about the objects may be sent to the client-computer based on the further request. An instruction to complete the purchase may be received from the client-computer, and a confirmation of the completion of the purchase may be sent to the client-computer. The content may be an HTML document and the objects may be objects according to the HTML Document Object Model.
Legal claims defining the scope of protection, as filed with the USPTO.
1. A method for adding functionality to application content served to a client-computer by a first server, the method comprising: providing API to the application content served by the first server; at a second server including a microprocessor, receiving a first request from the client-computer to add purchase functionality to the application content being served by the first server, the first request generated by the API; generating first client-side code based on the first request, the first client-side code including instructions for adding the purchase functionality to the application content; sending the first client-side code to the client-computer using the microprocessor, wherein said first client-side code includes instructions configured to present an interface that allows purchase of an item; receiving a second request from the client-computer, the second request including a product reference for the item; generating second client-side code based on the second request, the second client-side code including information about the item; sending the second client-side code to the client-computer using the microprocessor; and receiving a third request from the client computer, the third request including an instruction to purchase the item and payment information; and sending third client-side code to the client-computer, the third client-side code including a confirmation of the completion of the purchase and instructions to cause the client-computer to display the confirmation using the microprocessor.
2. The method of claim 1 , wherein the second server automatically determines an instruction related to the purchase based on at least one of a first server identity, a first server API key, a first server URL, a first server domain, and a particular cookie in a web browser that is displaying the application content.
3. The method of claim 1 , wherein at least one of product pricing and product availability are determined by the second server based on at least one of a first server identity, a first server API key, a first server URL, and a first server domain.
4. The method of claim 1 , wherein at least one of product pricing and product availability are determined by the second server based on a particular cookie in a web browser that is displaying the application content.
5. The method of claim 1 , wherein the API is provided by an operator of the second server.
6. The method of claim 1 , wherein the purchase functionality includes a purchase window that is embedded by the application content presented on the client-computer within other content served by the first server.
7. The method of claim 6 , wherein the appearance of the purchase window is based at least in part on information associated with the first server.
8. The method of claim 1 , further comprising adding an entry to a log of user activity across different domains based on at least one of receipt of the API-generated requests or a session cookie that tracks the user's history.
9. The method of claim 1 , wherein the information about the item includes a price for the item.
10. The method of claim 1 , wherein the purchase functionality includes an icon configured to initiate the second request.
11. The method of claim 1 , wherein the API is configured to include indicia unique to the first server in the first request, such that responses called by the API may be different depending on the identity of the first server.
12. The method of claim 1 , wherein the API is further configured to allow a user of the client-computer to identify themselves to the second server, without sharing that information with the first server.
13. The method of claim 1 , wherein at least one of the second client-side code or the third client-side code includes a request for a delivery address for the purchase.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
August 14, 2020
June 28, 2022
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.