Methods for integrating revenue generating features within a software application and systems thereof
First Claim
1. A method for optimizing the identification of relevant and targeted transactional features to embed within applications in order to improve click-through rate and capture an increased number of transactions, the method comprising:
- scanning by an application provider device without user intervention or input for stored data associated with a user of a web-based application;
comparing by the application provider device the scanned stored data to a plurality of transactional features to determine when the stored data corresponds with a product or service offered through one of the transactional features, the one transactional feature comprising digital content identifying the product or service;
enabling by the application provider device the one transactional feature without leaving the application only upon determining the stored data corresponds with the product or service offered through the one transactional feature, the enabling comprising displaying the one transactional feature on a display device and within the application;
receiving by the application provider device at least one selection of one of one or more transaction options from the enabled transactional feature and determining when a transaction associated with the enabled transactional feature and corresponding to the one transaction option is completed without leaving the application; and
receiving by the application provider device revenue in the form of an electronic payment for the completed transaction, providing at least a portion of the revenue via one or more communication networks to a source provider device associated with a provider of the product or service offered through the enabled transactional feature, and retaining at least a portion of the revenue, when the determining indicates that the transaction is completed.
2 Assignments
0 Petitions
Accused Products
Abstract
A method and system for generating revenue within an application includes determining when at least one of stored data associated with a user of an application, input data entered by the user of the application, and an action by the user of the application corresponds with at least one transactional feature embedded in the at least one application, a first source is associated with the application and a second source is associated with the transactional feature. A first source is associated with the application and a second source is associated with the transactional feature. The transactional feature is provided without leaving the application to the user when the determining determines at least one of the stored data, the input data, and the action corresponds with the transactional feature. At least one selection of one of one or more transaction options from the transactional feature is received and revenue is provided to the first source based on the received selection.
-
Citations
36 Claims
-
1. A method for optimizing the identification of relevant and targeted transactional features to embed within applications in order to improve click-through rate and capture an increased number of transactions, the method comprising:
-
scanning by an application provider device without user intervention or input for stored data associated with a user of a web-based application; comparing by the application provider device the scanned stored data to a plurality of transactional features to determine when the stored data corresponds with a product or service offered through one of the transactional features, the one transactional feature comprising digital content identifying the product or service; enabling by the application provider device the one transactional feature without leaving the application only upon determining the stored data corresponds with the product or service offered through the one transactional feature, the enabling comprising displaying the one transactional feature on a display device and within the application; receiving by the application provider device at least one selection of one of one or more transaction options from the enabled transactional feature and determining when a transaction associated with the enabled transactional feature and corresponding to the one transaction option is completed without leaving the application; and receiving by the application provider device revenue in the form of an electronic payment for the completed transaction, providing at least a portion of the revenue via one or more communication networks to a source provider device associated with a provider of the product or service offered through the enabled transactional feature, and retaining at least a portion of the revenue, when the determining indicates that the transaction is completed. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 34)
-
-
12. A non-transitory computer readable medium having stored thereon instructions for optimizing the identification of relevant and targeted transactional features to embed within applications in order to improve click-through rate and capture an increased number of transactions comprising machine executable code which when executed by at least one processor, causes the processor to perform steps comprising:
-
scanning without user intervention or input for stored data associated with a user of a web-based application; comparing the scanned stored data to a plurality of transactional features to determine when the stored data corresponds with a product or service offered through one of the transactional features, the one transactional feature comprising digital content identifying the product or service; enabling the one transactional feature without leaving the application only upon determining the stored data corresponds with the product or service offered through the one transactional feature, the enabling comprising displaying the one transactional feature on a display device and within the application; receiving at least one selection of one of one or more transaction options from the enabled transactional feature and determining when a transaction associated with the enabled transactional feature and corresponding to the one transaction option is completed without leaving the application; and receiving revenue in the form of an electronic payment for the completed transaction, providing at least a portion of the revenue via one or more communication networks to a source provider device associated with a provider of the product or service offered through the enabled transactional feature, and retaining at least a portion of the revenue, when the determining indicates that the transaction is completed. - View Dependent Claims (13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 35)
-
-
23. An application provider device comprising:
a processor coupled to a memory comprising programmed instructions stored in the memory, wherein the processor is configured to execute the programmed instructions stored in the memory to; scan without user intervention or input for stored data associated with a user of a web-based application; compare the scanned stored data to a plurality of transactional features to determine when the stored data corresponds with a product or service offered through one of the transactional features, the one transactional feature comprising digital content identifying the product or service; enable the one transactional feature without leaving the application only upon determining the stored data corresponds with the product or service offered through the one transactional feature, and display the one transactional feature on a display device and within the application; receive at least one selection of one of one or more transaction options from the enabled transactional feature and determine when a transaction associated with the enabled transactional feature and corresponding to the one transaction option is completed without leaving the application; and receive revenue in the form of an electronic payment for the completed transaction, provide at least a portion of the revenue via one or more communication networks to a source provider device associated with a provider of the product or service offered through the enabled transactional feature, and retain at least a portion of the revenue, when the determining indicates that the transaction is completed. - View Dependent Claims (24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 36)
Specification