Methods for integrating revenue generating features within a software application and systems thereof

• US 20080072067A1
• Filed: 09/18/2006
• Published: 03/20/2008
• Est. Priority Date: 09/18/2006
• Status: Active Grant

• Current Assignee: Adventive, Inc. (BlueTie, Inc.)
• Original Assignee: BlueTie, Inc.
• Inventors: Koretz, David A.
• Granted Patent: US 9,767,460 B2
• Time in Patent Office: Days
• US Class Current: 713/189
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising

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.

Claims

1. A method for generating revenue within an application, the method comprising:

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;

providing the transactional feature without leaving the application to the user of the application when the determining determines at least one of the stored data, the input data, and the action corresponds with the transactional feature;

receiving at least one selection of one of one or more transaction options from the provided transactional feature; and

providing at least a portion of the revenue for the received selection to the first source.

2. The method as set forth in claim 1 wherein the determining further comprises:

identifying when a personal data driven page in the application is entered;

scanning for enabled data in the personal data driven page; and

determining when the enabled data corresponds with the transactional feature.

3. The method as set forth in claim 1 wherein the determining further comprises:

periodically scanning stored personal data for the user of the application; and

determining when the stored personal data corresponds with the transactional feature.

4. The method as set forth in claim 3 further comprising:

receiving and storing the personal data from one or more users; and

retrieving the personal data for the user of the application from the stored personal data for the one or more users, wherein the periodically scanning further comprises periodically scanning the identified stored personal data for the user of the application.

5. The method as set forth in claim 1 further comprising receiving a selection of the transactional feature to display the one or more transaction options without leaving the application.

6. The method as set forth in claim 1 further comprising:

identifying one or more transaction options which are each associated with a time and date;

entering each of the identified one or more transaction options in a calendar application based on the associated time and date; and

providing an indication if any of the identified one or more transaction options interferes with another appointment in the calendar application.

7. The method as set forth in claim 1 wherein the providing revenue to the first source based on the received selection further comprises providing the revenue to the first source based on each time the user accesses the transactional feature.

8. The method as set forth in claim 1 wherein the providing the revenue further comprises:

retrieving financial data for the user of the application; and

receiving the revenue at the first source from the user for the selection based on the retrieved financial data for the user of the application; and

distributing a portion of the received revenue from the first source to the second source.

9. The method as set forth in claim 8 further comprising:

determining if the financial data for the user of the application is stored;

at least one of receiving existing financial data and new financial data from the user of the application when the determining determines the financial data for the user is not stored; and

storing the at least one of received existing financial data and the new financial data for the retrieving of the financial data for the user of the application.

10. The method as set forth in claim 9 wherein the new financial data is provided to the user of the application by at least one of the second source and a third source and further comprising providing a first compensation to the first source from the at least one of the second source and a third source based on the new financial data for the user of the application.

11. The method as set forth in claim 8 wherein the receiving the revenue further comprises capturing and retaining interest on float from the received revenue at the first source before the distributing the portion of the received revenue from the first source to the second source.

12. The method as set forth in claim 1 wherein the providing the revenue further comprises:

receiving the revenue at the second source from the user for the selection; and

distributing a portion of the received revenue from the second source to the first source.

13. The method as set forth in claim 1 further comprising:

receiving offers from two or more potential sources to be the second source associated with the transactional feature; and

selecting one of the received offers to be the second source based on at least one criteria, wherein the providing the transactional feature is provided from the selected received offer from one of the potential sources.

14. The method as set forth in claim 13 wherein the at least one criteria is one of a lowest requested amount for the portion of the received revenue from the first source to the second source and a highest amount of the received revenue from the second source to the first source.

15. The method as set forth in claim 1 further comprising recording a delivery date for the received at least one selection of one of one or more transaction options in a calendar application.

16. The method as set forth in claim 1 wherein the application is in a Web-based application.

17. The method as set forth in claim 1 wherein the application is a client-server application.

18. A computer readable medium having stored thereon instructions for generating revenue within an application comprising machine executable code which when executed by at least one processor, causes the processor to perform steps comprising:

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;

providing the transactional feature without leaving the application to the user of the application when the determining determines at least one of the stored data, the input data, and the action corresponds with the transactional feature;

receiving at least one selection of one of one or more transaction options from the provided transactional feature; and

providing at least a portion of the revenue for the received selection to the first source.

19. The medium as set forth in claim 18 wherein the determining further comprises:

identifying when a personal data driven page in the application is entered;

scanning for enabled data in the personal data driven page; and

determining when the enabled data corresponds with the transactional feature.

20. The medium as set forth in claim 18 wherein the determining further comprises:

periodically scanning stored personal data for the user of the application; and

determining when the stored personal data corresponds with the transactional feature.

21. The medium as set forth in claim 20 further comprising:

receiving and storing the personal data from one or more users; and

retrieving the personal data for the user of the application from the stored personal data for the one or more users, wherein the periodically scanning further comprises periodically scanning the identified stored personal data for the user of the application.

22. The medium as set forth in claim 18 further comprising receiving a selection of the transactional feature to display the one or more transaction options without leaving the application.

23. The medium as set forth in claim 18 further comprising:

identifying one or more transaction options which are each associated with a time and date;

entering each of the identified one or more transaction options in a calendar application based on the associated time and date; and

providing an indication if any of the identified one or more transaction options interferes with another appointment in the calendar application.

24. The medium as set forth in claim 18 wherein the providing revenue to the first source based on the received selection further comprises providing the revenue to the first source based on each time the user accesses the transactional feature.

25. The medium as set forth in claim 18 wherein the providing the revenue further comprises:

retrieving financial data for the user of the application; and

receiving the revenue at the first source from the user for the selection based on the retrieved financial data for the user of the application; and

distributing a portion of the received revenue from the first source to the second source.

26. The medium as set forth in claim 25 further comprising:

determining if the financial data for the user of the application is stored;

at least one of receiving existing financial data and new financial data from the user of the application when the determining determines the financial data for the user is not stored; and

storing the at least one of received existing financial data and the new financial data for the retrieving of the financial data for the user of the application.

27. The medium as set forth in claim 26 wherein the new financial data is provided to the user of the application by at least one of the second source and a third source and further comprising providing a first compensation to the first source from the at least one of the second source and a third source based on the new financial data for the user of the application.

28. The medium as set forth in claim 25 wherein the receiving the revenue further comprises capturing and retaining interest on float from the received revenue at the first source before the distributing the portion of the received revenue from the first source to the second source.

29. The medium as set forth in claim 18 wherein the providing the revenue further comprises:

receiving the revenue at the second source from the user for the selection; and

distributing a portion of the received revenue from the second source to the first source.

30. The medium as set forth in claim 18 further comprising:

receiving offers from two or more potential sources to be the second source associated with the transactional feature; and

selecting one of the received offers to be the second source based on at least one criteria, wherein the providing the transactional feature is provided from the selected received offer from one of the potential sources.

31. The medium as set forth in claim 30 wherein the at least one criteria is a lowest requested amount for the portion of the received revenue from the first source to the second source and a highest amount of the received revenue from the second source to the first source.

32. The medium as set forth in claim 18 further comprising recording a delivery date for the received selection of one of one or more transaction options in a calendar application.

33. The medium as set forth in claim 18 wherein the application is in a Web-based application.

34. The medium as set forth in claim 18 wherein the application is a client-server application.

35. A system that generates revenue within an application, the system comprising:

a determination system that determines 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 display system that provides the transactional feature without leaving the application to the user of the application when the determination system determines at least one of the stored data, the input data, and the action corresponds with the transactional feature;

a selection processing system that receives at least one selection of one of one or more transaction options from the provided transactional feature; and

a revenue processing system that provides revenue to the first source based on the received selection.

36. The system as set forth in claim 35 wherein the determination system further comprises:

an identification system that identifies when a personal data driven page in the application is entered;

a scanning system that scans for enabled data in the personal data driven page; and

a correspondence system that determines when the enabled data corresponds with the transactional feature.

37. The system as set forth in claim 35 wherein the determination system further comprises:

a scanning system that periodically scans stored personal data for the user of the application; and

a correspondence system determines when the stored personal data corresponds with the transactional feature.

38. The system as set forth in claim 37 further comprising:

a personal data storage system that receives and stores the personal data from one or more users; and

a retrieval system that retrieves the personal data for the user of the application from the stored personal data for the one or more users, wherein the scanning system periodically scans the identified stored personal data for the user of the application.

39. The system as set forth in claim 35 further comprising a selection receipt system that receives a selection of the transactional feature to display the one or more transaction options without leaving the application.

40. The system as set forth in claim 35 further comprising:

a timing identification system that identifies one or more transaction options which are each associated with a time and date;

a calendar processing system that enters each of the identified one or more transaction options in a calendar application based on the associated time and date; and

a notification system that provides an indication if any of the identified one or more transaction options interferes with another appointment in the calendar application.

41. The system as set forth in claim 35 wherein the revenue processing system provides the revenue to the first source based on each time the user accesses the transactional feature.

42. The system as set forth in claim 35 wherein the revenue processing system retrieves financial data for the user of the application, receives the revenue at the first source from the user for the selection based on the retrieved financial data for the user of the application, and distributes a portion of the received revenue from the first source to the second source.

43. The system as set forth in claim 42 wherein the revenue processing system determines if the financial data for the user of the application is stored, at least one of receives existing financial data and new financial data from the user of the application when the determining determines the financial data for the user is not stored, and stores the at least one of received existing financial data and the new financial data for the retrieving of the financial data for the user of the application.

44. The system as set forth in claim 43 wherein the new financial data is provided to the user of the application by at least one of the second source and a third source and wherein the revenue processing system provides a first compensation to the first source from the at least one of the second source and a third source based on the new financial data for the user of the application.

45. The system as set forth in claim 42 wherein the revenue processing system captures and retains interest on float from the received revenue at the first source before distributing the portion of the received revenue from the first source to the second source.

46. The system as set forth in claim 35 wherein the revenue processing system receives the revenue at the second source from the user for the selection and distributes a portion of the received revenue from the second source to the first source.

47. The system as set forth in claim 35 further comprising an offer processing system that receives offers from two or more potential sources to provide the one or more transaction options and selects one of the received offers to be the second source based on at least one criteria, wherein the display system provides the transactional feature from the selected received offer from one of the potential sources.

48. The system as set forth in claim 47 wherein the at least one criteria is a lowest requested amount for the portion of the received revenue from the first source to the second source and a highest amount of the received revenue from the second source to the first source.

49. The system as set forth in claim 35 further comprising a recordation system that records a delivery date for the received at least one selection of one of one or more transaction options in a calendar application.

50. The system as set forth in claim 35 wherein the application is in a Web-based application.

51. The system as set forth in claim 35 wherein the application is a client-server application.