WO2016145402A1 - Methods and systems for conducting marketing research - Google Patents

Abstract

Embodiments of the invention provide a system E that generates a multitude of data structures that each represents an individual virtual user profile. These virtual user profiles can emulate an individual using or interaction with various media, including email blasts, static web page ads, SMS, customized web page ads, etc.. Based on the interactions of the virtual user profiles with the various media, the system generates actionable data, recommendations and analysis of a business and its competition, allowing companies (hereinafter "companies") to make data driven business decisions.

Description

METHODS AND SYSTEMS FOR CONDUCTING MARKETING RESEARCH

RELATED APPLICATIONS

[0001] This application claims priority to U.S. Provisional Application No. 62/132,341, filed March 12, 2015, the entire content of which is herein incorporated by reference.

FIELD

[0002] Embodiments of the invention relate to methods and systems for conducting market research.

BACKGROUND

[0003] The present invention relates to methods of conducting marketing research. People exhibit a wide range of online behaviors, including, but not limited to, visiting websites, reviewing website content, reading email, and making online purchases. These behaviors are dictated by any number of elements, such as efficiency, ease of use, preferences, interests, pricing, sales, attractiveness of website, website layout, etc. As a result, companies use behavior based marketing which utilizes a variety of methods, including, but not limited to, email blasts, static web page ads, SMS, customized web page ads and media ("media"), through devices including but not limited to, desktop computers, laptops, tablets, cellular phones, smart phones, streaming, etc.

SUMMARY

[0004] Online marketing includes a collection of different methods employed by various companies to market goods and services to consumers in those companies' markets. Online marketing targeted at a specific person may be incompatible with marketing directed to another person, based on each person's individual profile. To date, there is no existing mechanism for companies to collect, aggregate, categorize, and analyze data using analytics tailored to many different kinds of individuals.

[0005] In order to effect these and other goals and benefits, the system creates a multitude or plurality of data structures that represent an individual virtual profile. Using these profiles or "personas", the system emulates individuals using, accessing or interacting with various media, and based on the interactions between the personal data structures and the media, the system generates actionable data, recommendations and analysis of a business and its competition, allowing companies to make data driven business decisions. The system enables its users to closely monitor the effectiveness of their own cross-platform actions through the aggregation of various media, such as email, websites and SMS communications aggregated at the persona level and to compare the results of their actions to those of the competition. The system enables personas to differentiate audience or message based on key attributes, i.e. gender, geographic regions, purchase history, or other customer behavior. In one embodiment, companies have the ability to execute more targeted marketing efforts. The system provides users the granular data needed to truly understand their customers, customize the marketing message and monitor the results. The system also gives users the ability to monitor results of competitor marketing tools and strategies. The system "learns" from this analysis by understanding the outcomes of a user's marketing tools and strategies.

[0006] The system compares these results to those of the company's competition as well as industry standards and benchmarks within company's respective market. Personas can be layered onto each of the specific capabilities; website automation, website testing multiple medium interactions, content archiving, third- party integrations, email intelligence, website intelligence and content archiving, which are all unique to the system.

[0007] Other aspects of the invention will become apparent by consideration of the detailed description and accompanying drawings.

DEFINITIONS

[0008] Brands - Can be a single company or entity, or multiple companies or entities which market to consumers using specific electronic media such as website(s), email(s), social properties such as Facebook, etc., and others.

[0009] Property - physical location or type of content, including but not limited to, any website page, such as a retail homepage, Facebook page, direct communication such as email, phone calls or SMS messages, direct messaging such as Skype, Facebook Messaging, Google+ or similar application.

[0010] Persona - A data structure representing an individual virtual profile that can be used by the system to emulate that individual on a digital medium.

BRIEF DESCRIPTION OF THE DRAWINGS

[0011] FIG. 1 is a schematic diagram of a system embodying the invention.

[0012] FIG. 2 is a schematic diagram of the application intelligence of the system, and its association with the builder user interface, application intelligence database and business intelligence module of the system.

[0013] FIG. 3 is an example of a user interface illustrating the builder user interface.

[0014] FIG. 4 illustrates elements of the application intelligence database.

[0015] FIG. 5 is a conceptual representation of the elements of one possible persona.

[0016] FIG. 6 is a conceptual representation of the elements of the action component.

[0017] FIG. 7 is a drawing showing the elements of the actions history database.

[0018] FIG. 8 is a drawing showing the elements of the actions content database.

[0019] FIG. 9 is a drawing showing the elements of the personal history database.

[0020] FIG. 10 is a conceptual representation of the elements of the application intelligence.

[0021] FIG. 11 is an example of the interaction between the application logic and the browser API.

[0022] FIG. 12 is a logic flowchart illustrating the remote browser process.

[0023] FIG. 13 is a logic flowchart illustrating the interaction with the remote browser. [0024] FIG. 14 is a logic flowchart illustrating the process of populating data within the actions history database.

[0025] FIG. 15 is a logic flowchart illustrating the process of interacting with the remote browser and the resulting data populated within the actions content database.

[0026] FIG. 16 is a logic flowchart illustrating the population of data within the persona history database.

REFERENCE NUMBER LIST

[0027] 1 - (Application Intelligence) The combination of algorithms, rules, software code and databases, including but not limited to logic 34, persona(s) 40 and actions 5.

[0028] 2 - (Application Intelligence Database) Is a non-transferrable computer readable medium with instructions stored thereon that when executed with a processor both receives and stores data collected by the Application Intelligence All, the builder user interface 58, and business intelligence 4 and transmits stored data to application intelligence All, the builder user interface 58 and business intelligence 4 . The data is result is then used to determine the accuracy of a single or group of actions performed and to improve further executions of actions 5, more specifically action template 7 and action intelligence 8.

[0029] 3 - (Action Logic) The combination of actions 5 and logic 34 using various statements and variables. An example might be to register a persona 40 on a Website. The application would select a single, or series of action type(s) 6, as well as various logic 34, iterating through each step recording results to action history database 9, actions content database 15 and persona history database 26.

[0030] 4 - (Business Intelligence) The combination using various statements and variables which are used to determine the results and calculate the accuracy of application intelligence 1. This is done using various methods, but most commonly done by a points scale system which helps to evolve actions 5 and application intelligence 34 over time by interpreting the data to determine which grouping of results has the greatest success ratio in completing the particular task executed. Various variables are used such as, but not limited to logic results, timing of results, action distance from logic (the date/time, or recency of a particular task in relation to a previously executed one) and status codes. For example, attempting to register for a site using a version of an action template 7 and action intelligence 8 results in a 60% accuracy that the actions 5 performed "worked." This is determined by application intelligence 1 - through the logic template 35 executing various checks, against the actions 5 performed then the application intelligence 1 understanding the results of the actions 5 performed and recording the results to the application intelligence database 2.

[0031] 5 - (Actions) Combination of several components that are used to perform actions and record specific content. These components include but are not limited to, Action Type 6, Actions History 9, Actions Content 15, persona History 26.

[0032] 6 - (Action Type) Made up of two main components, Action Template 7 and Action Intelligence 8

[0033] 7 - (Action Template) The type of action(s) that should be executed by a persona 40.

[0034] 8 - (Action Intelligence) The actual action 5 steps which are to be performed by a persona 40 for the associated instruction described in the action template 7.

[0035] 9 - (Actions History Database) Is used to record each step taken by 3, including but not limited to type of action, parameters sent/received and a reference to the particular record, steps, or elements, such as an image, text link, or command for the associated content stored in 15.

[0036] 10 - Identification number assigned in the formulation of a new data within actions history database 9.

[0037] 11 - The Action 6 performed within the particular content

[0038] 12 - The variable that was sent/received or the particular action executed.

[0039] 13 - Reference to the particular record for the associated content stored in actions history content database 15. [0040] 14 - The date/time the action was performed.

[0041] 15 - (Actions History Content Database) The information provided through the medium interaction, as well as variables from browser API 57. This includes but is not limited to, Session Info (data/time, cookies, logs, current URL, Status Codes) Screenshot of entire content, Screenshot of interacted element, content HTML (where exists), HTML of interacted content, associated persona 40 and date/time.

[0042] 16 - Identification number assigned in the formulation of a new data within actions history content database 15.

[0043] 17 - Identification number that links to a particular persona 40.

[0044] 18 - Combination of several variables that identify the particular environment, status and content within the remote browser 71 running inside of browser API 57. These include but are not limited to, logging, device, image/HTML content and cookies.

[0045] 19 - A small piece of data sent from a website while the browser API 57 is interacting with the website. Every time the user loads the website, the browser sends the cookie back to the server to notify the website of the user's previous activity. This data can then be loaded at a later date/time to "resume" the Session and a mechanism for websites to remember a particular user persona 40.

[0046] 20 - The HTML, which is displayed within browser API 57, more specifically the remote browser 71.

[0047] 21 - The Image Representation of the content within browser API 57, more specifically remote browser 71.

[0048] 22 - The Image Representation of the interacted HTML element from 3, which is displayed within browser API 57, more specifically remote browser 71.

[0049] 23 - The interacted HTML element from action logic 3, which is displayed within browser API 57, more specifically remote browser 71. [0050] 24 - The variable that is used to determine the success or failure of a particular action executed within browser API 57. An example would be Click First Name HTML Element - Status = 0.

[0051] 25 - The date/time the formulation of the data within actions history content database 15.

[0052] 26 - (Persona Action History Database Results) The data, which is used to identify the particular brand/property 32 results from action logic 3 executed by a specific persona 40.

[0053] 27 - Identification number assigned in the formulation of a new data within persona action history database results 26.

[0054] 28 - Identification number assigned in the formulation of a persona 40. [0055] 29 - The reference to the particular actions 3 performed.

[0056] 30 - The reference to the starting ID 16 number assigned in the formulation of data within persona action history database results 26.

[0057] 31 - The reference to ending ID 16 number assigned in the formulation of data within persona action history database results 26.

[0058] 32- The date/time the formulation of the data within persona action history database results 26.

[0059] 33- The brand/property that the actions logic 3 were performed on.

[0060] 34- (Application Intelligence - Logic) Various complex statements and variables that are used to deduce the conclusions (additional statements) that must be true by the laws of logic. An example of this could be "Is the text box l value empty? Yes."

[0061] 35 - (Application Intelligence - Logic Template) The embodiment of multiple pieces of information and statements, which are used to answer complex, questions within, but not limited to Webpages, Emails, 3rd-Party API's and existing data. [0062] 36 - Rules and Logic that interacts with WAN 76 that answers questions using predefined statements that can be used individually or combined with others. The Logic interacts using, but not limited to application intelligence 1 and browser API 57 to determine the results for each question. An example could be to check if the remote browser 71 from browser API 57 is Logged In. A series of statements would run looking for indicators within the HTML (example: "log out" or "sign out" within the page), then return the True/False result.

[0063] 37- Similar to rules and logic 36 except it also includes information regarding but not limited to, email to:/from, sent/received, content as well as actions 5 variables/results to determine the answers to complex questions. An example of this could be: Is Email a Password Reset Email? A series of statements would run looking for indicators (contains the words "reset", "password", "requested", etc.) within the HTML as well as the email Sender information.

[0064] 38 - (Application Intelligence - Logic Checks) Rules & Logic that are used to answer questions about browser API 57, action intelligence 1 and application intelligence - logic template 35 results and variables. One embodiment of this would be "Did the URL Change?" This would be deduced by looking at browser API 57 or remote browser 71 current

URL/Website Address. If the URL changed from a previous step, then the logic would return "True".

[0065] 39 - (Logic Accuracy) The accuracy of the executed Action Intelligence performed, formatted using a point scale of 0-100. If it can be verified that the action intelligence 1 performed was successful without a doubt, it would result in 100 (percent) accuracy.

[0066] 40- (Persona) The embodiment of multiple pieces of information and or settings which make up a specific digital user/profile. Such pieces of information include, but are not limited to demographics 53, behavior 49, location 41 and device 44.

[0067] 41 - (Location Geographic/Server) The physical Cloud Instance/Server location and/or Proxy which is used in conjunction with browser API 57. This allows the interactions with remote browser 71 to be executed as if the user/device was located in that geographic location. [0068] 42 - (Physical Server Location) The physical Cloud Instance/Server location where all communication with 76 will be executed through.

[0069] 43 - (Proxy Service) The service which acts as an intermediary for requests from browser API 57 seeking resources from WAN 76, but not limited to.

[0070] 44 - (Devices) A device, or devices are defined within each persona. The Device is made up of any software, hardware combination of the two which acts as the communication between content and the application. A common example would be a Web Browser (Chrome), or a Mobile Phone such as an iPhone.

[0071] 45 - (Device Hardware) Settings which define an object, machine, or piece of equipment that is being used to perform a specific action(s). An example might be an iPhone 5s, or Apple MacBook Pro.

[0072] 46 - (Software Personalization) Settings which define the device hardware 45 & device Version 3.3 can be slightly modified to exclude/include specific features, for example, blocking JavaScript for a device.

[0073] 47 - (Version) Settings which define the unique version name or unique version number for the unique state of a devices 44 software. An example might be OSX 10.10.1 (14B25).

[0074] 48 - (Operating System) Settings which define the operating system of the particular device hardware 45. An example might be Windows, OSX or Android.

[0075] 49 - Settings which define the type of behavior that should be followed, to more specifically match a specific demographic or individual using behavior + rules 51, example might be to look for a particular genders related content such as Women's. By doing this, the persona 40 can be defined as being that particular gender, for example 95+ Female. Other specifics such as, maximum item price, Size/Length/Color, engagement throttle (how fast they perform actions), etc. This same method can be used in a Negative sense using behavior - rules 52. This allows the much broader option to be defined as to what is OK to include and only NOT including what is defined in the Negative persona, such as Everything but Women's. [0076] 50 - (Behavior) Logic or Rules, which are defined to help avoid or identify particular content. One example might be, Include "women", or Exclude "men".

[0077] 51 - (Behavior + Rules) Similar to behavior 50 but are rules that should be Included.

[0078] 52 - (Behavior - Rules) Similar to behavior 50 but are rules that should be Excluded.

[0079] 53 - (Demographics) Combination of several variables to define a demographic profile that provides enough information about a specific hypothetical user/person. The demographics are made up of a person 54, their location(s) 55 and device(s) 56. One

embodiment of this is John Smith, male, age 25, location Milwaukee, WI, uses a MacBook Pro Laptop.

[0080] 54 - (Demographics - Person) Variables that are used to identify a particular hypothetical user, including but not limited to Name, Address, Phone(s), Email, Password, Mobile Number, Common Password Reminder Questions/ Answers and Shipping Address.

[0081] 55 - (Demographics - Location) Reference to one or more location geographic/server 41.

[0082] 56 - (Demographics - Device) Reference to one or more devices 44.

[0083] 57 - Browser Application Programming Interface (hereinafter "Browser API") - A server or servers that provides access to different browser versions and browser configurations centrally and use these instances running on remote machines.

[0084] 58 - (Builder User Interface) The user interface receives user input for: input from user 59, user interface tools 62, session settings 68, website URL 69 and static graphic of remote browser 71 running on browser API 57, using but not limited to text boxes, mouse or other various inputs. This is also the method to save specific actions 5 to be run at a later time.

[0085] 59 - (Input from User) The Input visual location within static graphic of remote browser 70 to designate interaction location within the Interactive Document. [0086] 60 - (HTML Object) Each interaction fetches the HTML object/content from input location from input from user 59 using remote browser 71. The fetched content is rendered and/or displayed as a native HTML object on the users device 61. Further interaction to input location from input from user 59 sends the browser command data 65, visual representation of action performed 72 to remote browser 71.

[0087] 61 - (Native HTML object displayed on the user's device) Similar to HTML object 60, but in this case renders it as it would on the user's device. For example, it would display the HTML required to display a drop-down menu with options, allowing the user to interact with the HTML object 60 as they normally would.

[0088] 62 - (UI Tools) The tools used to interact with remote browser 71 and browser API

57 from within builder user interface 58.

[0089] 63 - (Input location - from user input) Using the builder user interface 58 and the static graphic of remote browser running on browser API 70 the input from user 59 are determined using the Cartesian coordinate system which specifies each point uniquely in a plane by a pair of numerical coordinates, which are the signed distances from the point to two fixed perpendicular directed lines, measured in the same unit of length. This is done using the static graphic of remote browser 70 size (width/height) and calculations of input from user 59 positioning within static graphic of remote browser 70 starting at the top left. An example of this might be 200px down, 450px right.

[0090] 64 - (History of actions performed/recorded) Records of interactions performed by input from input from user 59, command type 66 then reflected within the builder user interface

58 using a graphical icon.

[0091] 65 - (Browser Command Data) The Browser Command Data stores the data which is sent/received from/to remote browser 70 and browser API 57, as well as the specific actions database 83.

[0092] 66 - (Browser Data Type) The input from user 59 from static graphic of remote browser 70 or remote browser 71 is inspected to determine the type of interaction needed with browser API 57. The various options include but not limited to click, type/characters, website URL 69.

[0093] 67 - (Cookie Data) A small piece of data retrieved from remote browser 71 that is used to uniquely identify the particular, or set of interactions with browser API 57 and web pages.

[0094] 68 - (Session Settings) Various options that include but not limited to the device 44, geographic location 41 and persona 40.

[0095] 69 - (Website URL) The input provided by users or application intelligence 1 to retrieve a particular piece of media.

[0096] 70 - (Static Graphic of Remote browser running on Browser API) The graphical representation of what is being displayed with the users unique remote browser 71 running inside of browser API 57. This is performed using browser API 57, which takes a screenshot of the remote browser 71, then transmits the screenshot to the user interface 58. This is also used to calculate input location from user input 63 coordinates.

[0097] 71 - (Remote Browser) The web browser instance created and controlled within browser API 57 which sends commands to a web browser running on a separate system, and can retrieve results. The browser is configured using the persona 40 device 44, for example Chrome web browser running on a Windows 8 desktop.

[0098] 72 - (Visual representation of Action Performed) With each interaction performed on a remote browser 71 a graphical representation of a screenshot is taken of the elementVHTML object with which the interaction occurred. The static graphic of remote browser running on Browser API 70, is a visual representation of the entire web page, whereas the visual

representation of a specific action performed 72 by a user on a web page is a visual

representation or screenshot of that specific action. The screenshot recording of this action helps the user verify what the system has interpreted the users interaction to be, so that future execution of this action by system is in fact what the user intended. [0099] 73 - (Screenshot Storage) The Screenshot Storage is a non-transferrable computer readable medium with instructions stored thereon that when executed with a processor stores screenshots of a specific resource such as but not limited to, full webpage, full email, a single web page element (textbox, button etc.).

[00100] 74 - (Scheduler Database) The Scheduler Database is a non-transferrable computer readable medium with instructions stored thereon that when executed with a processor stores information as to when certain actions including but not limited to specific actions 83, application intelligence 1 and business intelligence 4 , should be performed, including the frequency for which the actions should be performed - example: such a 58x per

day/week/day/month/year.

[00101] 75 - (User Database) This non-transferrable computer readable medium with instructions stored thereon that when executed with a processor stores information about a specific user account, including but not limited to email, password, address, billing and preferences.

[00102] 76 - (WAN) The external sources that are used to retrieve content such as, but not limited to webpages, Emails and 3rd Party API's.

[00103] 77 - (World Wide Web) Any single or group of webpages.

[00104] 78 - (Email) Emails which are received using a specified username or password, or a saved email from an application such as Outlook or from online sources such as GMAIL.

[00105] 79 - 3rd Party Application Program Interface (hereinafter "3rd Party Application Program Interface" or "3rd Party API") A single or group of API's which are methods for allowing the Application Intelligence to communicate with other outside applications.

[00106] 80 - Rules and Logic that interacts with 3rd party API's 79 that answers questions using predefined statements that can be used individually or combined with others. The Logic interacts using, but not limited to application intelligence 1 & browser API 57 to determine the results for each question. An example could be using Facebook's 3rd party API to verify if a user persona 40 is able to login successfully using the persona 40 defined credentials. [00107] 81 - A high-level example of how both the actions 5 and the logic 34 which are executed.

[00108] 82 - A detailed explanation of how both the actions 5 and the logic 34 which are executed 81.

[00109] 83 - The combination of custom actions logic 3 created using builder user interface 58 and saved, then executed using the scheduler database 74 at specified time/interval.

[00110] 84 - The Master List Database contains an evolving list of predefined actions logic 3 and unique identifiers for each of the different brand properties that are aggregating content. The purpose of this database is to group all content by their respective brand to better identify differences in persona content. For every piece of content that is aggregated, it is assigned as part of a brand and or property, for example Pottery Barn. All Pottery Barn content can then be compared, by one or all of the following: persona 40, Behavior

[00111] 85 - Is a schematic illustration of an interaction with the start remote browser process.

[00112] 86 - Is a schematic illustration of an interaction with remote browser process.

[00113] 87 - Is a schematic illustration of an interaction with remote browser process and the resulting data populated within the actions history database 9.

[00114] 88 - Is a schematic illustration of an interaction with remote browser process and the resulting data populated within the actions content database 15.

[00115] 89 - Is a schematic illustration of an interaction with remote browser 86 process and the resulting data populated within the persona history database 26.

[00116] 201 - Is a schematic illustration of a prompt for a send URL to application intelligence process

[00117] 210 - Is a schematic illustration of an identification number assigned process. [00118] 212 - Is a schematic illustration of a user parameter(s) identified process. [00119] 213 - Is a schematic illustration of a actions content database identification number assigned process.

[00120] 214 - Is a schematic illustration of a determine current date/time process.

[00121] 215 - Is a schematic illustration of an add to action content history database process.

[00122] 216- Is a schematic illustration of an identification number assigned to new content ID process.

[00123] 218 - Is a schematic illustration of a identify session items, cookies, status of command executed, selected persona ID and current date/time process.

[00124] 220- Is a schematic illustration of an identify external content (HTML, screenshot) from WAN process.

[00125] 222 - Is a schematic illustration of an interacted object element screenshot process.

[00126] 223 - Is a schematic illustration of an interacted object element HTML process.

[00127] 226 - Is a schematic illustration of a add data to persona action history database process.

[00128] 227 - Is a schematic illustration of an identification number assigned of new content ID process.

[00129] 228 - Is a schematic illustration of an identify selected persona ID, reference to the particular actions that was performed, the particular brand/property, current date/time process.

[00130] 230 - Is a schematic illustration of an identify the starting identification number assigned in the formulation of the actions content database data ID process.

[00131] 231 - Is a schematic illustration of an identify the ending identification number assigned in the formulation of the actions content database data ID process.

[00132] 257 - Is a schematic illustration of a communicate to browser API process. [00133] 258 - Is a schematic illustration of a load builder user interface process.

[00134] 259 - Is a schematic illustration of a user input, location, type captured process.

[00135] 260- Is a schematic illustration of an interaction with HTML object on remote browser process.

[00136] 263 - Is a schematic illustration of a determine interaction X, Y coordinates process.

[00137] 264 - Is a schematic illustration of an add to history of actions performed/recorded process.

[00138] 269 - Is a schematic illustration of a prompt for a starting URL process.

[00139] 270 - Is a schematic illustration of a graphical representation of what is displayed on remote browser process.

[00140] 271 - Is a schematic illustration of a send commands to remote browser process.

[00141] 272 - Is a schematic illustration of a graphical representation of interacted HTML object process.

[00142] 276 - Is a schematic illustration of a retrieve external content from WAN process. [00143] 283- Is a schematic illustration of a user actions identified process. DETAILED DESCRIPTION

[00144] Before any embodiments of the system are explained in detail, it is to be understood that the system is not limited in its application to the details of the software in the arrangement of components set forth in the following description or illustrated in the following drawings. The system is capable of other embodiments and of being practiced or being carried out in various ways. Also, it is to be understood that phraseology and terminology used herein is for the purpose of description and should not be regarded as limited. The use of "including," "such as" and/or variations thereof herein is meant to encompass the items listed thereafter and equivalents thereof as well as additional items. The terms "connect," "store," "aggregate," "collect," "create," "manage" are used broadly and encompass both direct and indirect connection, storage, aggregation, collection, creation, and management. Also, electronic communications and notifications may be performed using any known means of direct connections, wireless connections, etc. through multiple media and devices such as for example, mobile phone, tablet, laptop, desktop, smart watch, Google Glasses or similar wearable device.

[00145] It should be noted that a plurality of hardware and software based elements and devices, as well as a plurality of different structural components may be utilized to implement the present invention. Furthermore, and as described in subsequent paragraphs, the specific configurations illustrated in the drawings are intended to exemplify embodiments of the present invention and that other alternative configurations are possible.

[00146] FIGURE 1 shows the Browser Application Programming Interface (Browser API OR "the hub") 57, the wide area network (WAN) 76, and the system E, which work together to collect, aggregate, store, and analyze data in a way that is unique to the present invention. With Browser API 57, one server acts as the hub. The application intelligence 1 contacts the hub 57 to obtain access to browser instances 71. The hub 57 has a list of servers that provide access to browser instances (or "nodes") 71 and use of these instances 71. Browser API 57 allows running multiple browsers in parallel on multiple machines to manage different browser versions and browser configurations centrally. This is the primary tool which is used to communicate with both internal and external digital content. One embodiment of this may be starting a new remote browser session with application intelligence 1, which results in a browser instance 71 being created within browser API 57 that would then interact with any component of the wide area network 76. The wide area network 76 includes external sources that are used to retrieve content. These external sources can include the World Wide Web 77, email 78, and third party application program interfaces 79. The system E (used to collect, aggregate, store, and analyze data) creates a multitude of pre-configured personas 40 that are continuously obtaining data from the WAN 76 sources using an evolving database list of predefined actions logic 3 and unique identifiers for each of the different brand properties that are aggregating content. The purpose of this database list is to group all content by its respective brand to better identify differences in persona content. For every piece of content that is aggregated, it is assigned as part of a brand and or property, for example, Pottery Barn. [00147] The personas 40 are individual virtual profiles of imaginary users which are shown in figure 5 and described in greater detail below. Different embodiments of the system E include use of the personas 40 in the following manners:

[00148] Websites: personas 40 go to one or a plurality of retailer websites and obtain a screen- shot specifically capturing the time, date, content, layout, and more.

[00149] Third-party providers: these sites will allow personas 40 to make and receive both phone calls and SMS communications. In some instances, the application intelligence 1 of the system E will speak directly to third-party providers.

[00150] Externally housed public servers for email (e.g., Gmail, Hotmail, etc.): The application intelligence 1 of the system E establishes and maintains persona email accounts, which can be checked via the interface either continuously or at-intervals.

[00151] Figure 2 depicts the core of the system E used to collect, aggregate, store, and analyze data, the application intelligence 1, as well as three (3) of the components within the system E, but can be external to the application intelligence 1. These components include: 1) the business intelligence 4; 2) the application intelligence database 2; and 3) the builder user interface 58. The application intelligence 1 houses the essential components for data collection and analysis and transmits data to and from source and storage locations. The persona 40, action 5, and logic 34 are the three elements that make up the application intelligence 1. The application

intelligence database 2 both receives and stores data collected by the application intelligence 1, the builder user interface 58, and business intelligence 4 and transmits stored data to the application intelligence 1, the builder user interface 58, and business intelligence 4. The application intelligence database 2 is used to determine the accuracy of a single or group of actions 5 performed. The application intelligence database 2 also serves as a method to improve further executions of actions 5 based on action types 6, or more specifically, action template 7 and action intelligence 8. Business intelligence 4 is the combination, using various statements and variables, which are used to calculate the accuracy of the application intelligence 1. This is done using a point scale which helps to evolve actions 5 and logic 34 over time by understanding which grouping results in the most accurate execution. Assorted variables are used, such as, but not limited to, logic results, timing of results, action distance from logic (the date/time, or recency of a particular task in relation to a previously executed one), and status codes. For example, attempting to register for a site using a version of an action template 7 and action intelligence 8 results in a sixty percent (60%) accuracy determination that the action "worked successfully." The accuracy is determined by logic template 35, which executes various checks, understands the results, and then records the results to the application intelligence database 2. The application intelligence 1 tries to learn from each medium and property interaction. The application intelligence 1 examines what task the persona 40 is intending to complete and whether the intended task was completed or if actions such as options, steps, etc. are correct or if options, steps, etc. are missing, or if new actions such as, options, steps, etc. are added.

Embodiments of the application intelligence 1 included, but are not limited to: 1) were the exact same number of clicks required previously for the exact same interaction with the same type of medium and 2) did the type of medium interaction take the same amount of time required previously for the exact same interaction with the same type of medium. The builder user interface 58 receives user input for: input from user 59, user interface tools 62, session settings 68, website URL 69 and browser running on browser API 70, using, but not limited to, text boxes, mouse, or other various inputs. This is also the method to save specific actions logic 83, and can be used to create actions 5 to be run at a later time. An embodiment of this could be entering the checkout process of a particular website, for example, Pottery Barn. The user would first identify the URL 69, then proceed to navigate the website just as they would normally within any web browser, but instead within the remote browser 71 running on browser API 57 as a Static Graphic 70. Then identifying the Input location 63 from user input 59 to click on a shopping category inside of the builder user interface 58, resulting in the recording of the command data 67 (where and what on the page any interaction occurred), command type 66 (the type of interaction; click, typing characters, etc.), as well as the current cookie data 67, session settings 68, and current website URL 69. Once the user has completed all of the steps necessary for entering the checkout process, the user then determines the schedule 74, and then saves the steps and data to the specific actions logic database 83.

[00152] The system E works using personas 40 to collect, aggregate, categorize, and analyze data from various electronic media including, but not limited to, email, websites, social media, and SMS. A persona 40 is defined by various values and a combination of attributes, including but not limited to, demographics, behavior, geographic location, and device, and may involve defining a plurality of personas for a single persona identity. The system E creates systems and methods stored with instructions on non-transferrable computer readable media described herein that are directed to create and manage personas 40, perform specific tasks with personas 40, aggregate data using multiple personas 40, and use the business intelligence 4 to intelligently identify content and results from each of the tasks. A simple way of defining a persona 40 would be to use constant values including, but not limited to, age, gender, or geographic location 53, devices 44 to be used with the persona 40, plus behaviors of personas 40, including, but not limited to, purchase habits, occurrence of website interactions, and length of website interactions 49. The system E can create unlimited variations of personas 40 with the result that tens, hundreds, thousands, or hundreds of thousands of these personas 40 are continually aggregating data by individual values or a combination of values with each persona 40 having its own unique identity application intelligence 1, application intelligence database 2, browser API 57, builder user interface 58, browser command data 65, screenshot storage 73, scheduler database 74, user database 75, and WAN 76.

[00153] There are two types of methods for aggregating data using personas 40. One method collects, aggregates, categorizes, and analyzes data using the master list 84 , the predefined actions logic 3 contained within, and uses the following system components: the application intelligence 1, application intelligence database 2, action logic 3, business intelligence 4, actions 5, browser API 57, screenshot storage 73, scheduler database 74, user database 75, and the WAN 76. The other type which does not use the master list 84, instead uses the following: user database 75, specific actions logic 83 (browser command data 65, browser data type click/text 66, cookie data 67, session settings 68, website URL 69), as well as all of the other components from the first type of method above. Some examples of a persona 40 interacting with digital media, include, for example, a website where the persona 40 is identified through cookie data 67 by the website within remote browser 71 as "first time visitor", "purchased items previously" or "new email subscriber". The system E can then use these results and data to distinguish if and what content, such as different versions of an email 78, website 77, social media messaging 77, SMS 79, etc., to display from one persona 40 to another different persona 40 is varied and why. The system E used to collect, aggregate, store, and analyze data and can then generate actionable data, recommendations, and analysis of a business and its competition allowing companies to make data driven business decisions. The system E combined with browser API 57 and WAN 76 enables its users to closely monitor the effectiveness of their own cross-platform actions. Specifically, the system E aggregates the responses from various digital media and changes the data structure of the persona 40 to either include data identifying how those various digital media interact with the specific persona 40 or include a link to the data identifying how those various digital media interact with the specific persona 40. The creation of this data enables the system E to differentiate audience or messaging based on key attributes such as gender 54, geographic regions 55, device 44, purchase history 49, or other customer behavior 49. One example of the application of the system E is that users may have the ability to execute more targeted marketing efforts based on how others brands digital marketing is being done. The system E gives users the granular data needed to understand their own digital marketing to customers or customized digital marketing media to a particular variation of persona 40 and monitor the results. The system E also gives users the ability to monitor results of competitor digital marketing content and strategies. The system "learns" from this analysis by understanding the outcomes of a user's marketing content and strategies 4. It can then compares those outcomes to those of the user's competition as well as industry standards and benchmarks within user's respective vertical or market.

[00154] Content communicated through the application intelligence 1 is stored in multiple databases within the system E used to collect, aggregate, store, and analyze data, including the scheduler database 74, the user database 75, screenshot storage 73, and specific actions logic database 83. The scheduler database 74 stores information as to when certain actions including, but not limited to, specific actions logic 5, application intelligence 1, and business intelligence 4 , should be performed and the frequency for which the actions should be performed (e.g., once per day, once per week, once per month, and/or once per year). The user database 75 stores specific user account data, including ,but not limited, to user email, user password, user address, user billing information, and user preferences. The user database 75 is also the database that users log in and out of for purposes, including, but not limited to, accessing their account, making payments for their account subscription and services as well as defining specific configurations to be used with application intelligence 1 and business intelligence 4. Screenshot storage 73 stores screenshots of a specific resource such as but not limited to, full webpage, full email, and a single HTML object 60 (e.g. textbox, button, etc.). The specific actions logic 83 is a combination of custom actions logic 3 created using builder user interface 58 and saved, then executed using the scheduler database 74 at specified time/interval.

[00155] Figure 3 is a drawing showing the builder user interface 58, which is used to create a combination of custom actions logic 3 and saved to the users specific actions logic 83 to then be executed using the scheduler database 74 at the specified time/interval. A schematic illustration of a start remote browser process 85 and interacting remote browser process 86.

[00156] Figure 4 is a drawing of the elements contained in the application intelligence database 2. The application intelligence database 2 stores the results of and transmits stored data to application intelligence 1, which is used to determine the accuracy of a single or group of actions logic 3 performed in conjunction with business intelligence 4, and serves as a method to improve further executions of the above. The following are the data identifiers for the application intelligence database: SOURCE ID = Brand 33; 26-ID = identification number assigned in the formulation of a persona 40; 6-Type = identification assigned in the formulation of a action type, Accuracy = success ratio as a result of the actions logic 3 and business intelligence 4, Calculation Date = Date/Time the process was executed.

[00157] As shown in Figure 5, the persona 40 is one of the three components of the artificial intelligence and is the essential element of the system in that it overlays each of the specific capabilities of the system E: website automation, website testing multiple medium interactions, content archiving, third- party integrations, email intelligence, website intelligence and content archiving. The system E works by using personas 40 to collect, aggregate, and categorize data from various marketing media including, but not limited to media such as, email, website, social and SMS. The system E creates and manages personas, performs specific tasks with personas, aggregates data using multiple personas and geographic locations, and intelligently identifies content and results from each of the tasks.

[00158] The system E generates the multitude of personas using the persona generator (a set of logic and defined variables within the application intelligence 1). A user of the system E may also define their own specific persona or persona template using criteria established or entered into defined fields. The personas 40 are created as follows: a database of random first names is cross-combined with a database of random last names to create random combinations of first and last names. These combinations are then each assigned by the persona generator a valid email (selected from a list of email accounts previously created by the system using Gmail or other similar email systems), and phone number (for SMS messaging, selected from a list of available unused phone numbers). No two personas can have the same email and/or phone number. The system E can successfully retrieve emails from the account, and pair the emails with the previously created phone number from the 3rd party API 79.

[00159] A simple way of defining a persona 40 would be to use constant values including, but not limited to, age, gender, geographic location, and behaviors of personas, including, but not limited to, purchase habits, occurrence of website interactions, and length of website interactions. Thousands of these personas 40 are continually aggregating data by individual values or a combination of values with each persona 40 having its own unique definition. The personas 40 are capable of performing specific actions, such as accessing a website and adding items to a virtual shopping cart. Using different profiles of personas 40, for example, the response of the media to various demographics, for example, male, using devices Desktop (MacBook Pro) and Mobile (iPhone 6) can be assessed. Moreover, the response of the media to certain aspects of the persona 40, such as "first time visitor" or "purchased items previously" or "new email subscriber", can be assessed. The system E is able to distinguish if and what content, such as different versions of an email, website, social media messaging, is varied and why. The persona 40 is a combination of attributes such as, but not limited to, demographics 53, behavior 49, geographic location 41 and device 44, and may involve defining a plurality of personas for a single persona identity to be used. It is the encompassment of multiple pieces of information and/or settings to make up a specific digital user/profile. One embodiment of a persona 40 may have a grouping as follows: Female, Age 35, lives in Milwaukee, Wisconsin, Height 5.9", Weight 134 lbs., and Upper-Middle Income grouping. A second embodiment of this may have a grouping as follows: Female, lives in Denver, Colorado, uses a laptop, laptop is a Mac running OS X Yosemite, is high spender, and is eco-conscious. Each of these attributes results in a specific behavior that must be followed using the system's logic 34, actions 5, action logic 3, and application intelligence 1. [00160] Figure 6 illustrates the action component 5, one of the three (3) components of the application intelligence 1. The action component 5 contains action type 6, which includes the action template 7 and the action intelligence 8, as well as the actions history 9 (see Fig. 7), actions content database 15 (see Fig. 8), and persona history 26 (see Fig. 9). The action template 7 is the type of action(s) that should be executed by a persona 40. Action templates 7 are both pre-determined or determined by the user. Action intelligence 8 are the actual action steps which are to be performed by a persona 40 for the associated instruction described in the action template 7. A few embodiments of action templates 7 are: "John Smith go register on Pottery Barn website" or "John Smith go add something to your cart" or "John Smith go do A, B, C, predetermined tasks." The associated action intelligence 8 embodiments would be actions history 9 records each step taken by actions intelligence 1, including, but not limited to, type of action, parameters sent/received and a reference to the particular record, steps, or elements, such as an image, text link, or command for the associated content stored in actions history content database 15. Actions Content 15 is a database containing the information provided through the medium interaction, as well as variables from Browser API 57. This includes, but is not limited to, session information (data/time, cookies, logs, current URL, status codes) screenshot of entire content, screenshot of interacted element, content HTML (where exists), HTML of interacted content, associated persona 40, and date/time. Persona history 26 is the data used to identify the particular results from action logic 3 executed by a specific persona 40.

[00161] Figure 7 is a chart of the elements contained in the actions history database 9. The actions history database 9 stores each step executed by action logic 3, including, but not limited to, type of action 11, parameter 12 sent/received, and an identification number assigned in the formulation of ID 16 from actions content database 15 for example elements, such as an image, text link, or command for the associated content stored in actions content database 15.

[00162] Figure 8 is a chart of the elements contained in the actions content database 15. The actions content database 15 stores the content of each step executed by action logic 3, including, but not limited to, an identification number assigned in the formulation of new content ID 16, the identification number assigned in the formulation of the selected persona 40 data 17 as well as receiving the following from the remote browser 71; the session variables 18, cookie(s) 19, HTML 20, screenshot 21, interacted object screenshot 22, interacted object HTML 23, success or failure status 24 of task performed.

[00163] Figure 9 is a chart of the elements contained in the persona history database 26. The persona history database 26 stores the data to identify the particular brand/property 32 results from action logic 3, executed by a specific persona 40. This data includes, but is not limited to, an identification number assigned in the formulation of the data ID 27, the identification number assigned in the formulation of the selected persona 40 data 28, reference to the particular actions 3 performed, the starting identification 30 number assigned in the formulation of the actions content database data ID 16, the ending identification 31 number assigned in the formulation of the actions content database data ID 16, and date/time the task was executed 33.

[00164] Figure 10 is a schematic illustraion of the elements contained in the application intelligence - Logic 34, which are comprised of Logic Templates 35 most commonly website 36, email 37 and 3rd Party API 80, as well as logic checks 38 that are used to deduce the conclusions (additional statements) that must be true by the laws of logic.

[00165] Figure 11 illustrates an example of the interaction between application logic 3 and the browser API 57 stepping through specific actions 5 and the logic 34 to complete a single or group of tasks. The basic example 81 illustrates how each of the steps are iterated through by sequential order predefined, for example, step 1) Load Webpage. The example explained 82 is a more granular breakup of each step and how it relates to the system components.

[00166] Figure 12 illustrates the start remote browser 85 process, which can include the load builder user interface 258, prompt for starting URL 283, a send URL to application intelligence 201, a communicate to browser API 257, a send commands to remote browser 271, a retrieve external content from WAN 276 task, and a graphical representation of what is displayed on Remote Browser 270 task.

[00167] Figure 13 illustrates the process of interacting with remote browser 86, which can include the load builder user interface 258, Graphical representation of what is displayed on Remote Browser 270 task, determine interaction X,Y coordinates 263 task, user input, location, type captured 259 task, user actions identified 283 task, communicate 263, 259, 283 to Browser API 257 task, Send commands to remote browser 271 task, Interaction with HTML object on remote browser 260 task, retrieve external content from WAN 276 task, graphical representation of interacted HTML object 272 task, and a add to history of actions performed/recorded 264 task.

[00168] Figure 14 illustrates the population of data within the actions history database 9, which includes the ID 210 - identification number assigned, the user input 259 (action 11, location 63, type 6), user parameter 12 identified 212, actions content database 15 identification number assigned 213, determine 214 current date/time 14.

[00169] Figure 15 illustrates the interaction with remote browser 86 process and the resulting data populated within the actions content database 15, which includes sending commands to remote browser 271, retrieving external content from WAN 276, identifying 218 session items 18, cookies 19, success or failure status 24 of command executed 271 and selected persona 40 ID 17 and current date/time 25, identifying external content (HTML 20, screenshot 21) 220, ID 16 identification number assigned of new content 216, interaction 260 with HTML object 60 on remote browser 71, identifying 222 interacted Object element screenshot 22, identify 223 interacted Object element HTML 23, and adding to 215 action content history database 15.

[00170] Figure 16 illustrates the population of data within the persona history database 26, which includes capturing the results of add to 215 action content history database 15. The following are included in this process: adding to 215 action content history database 15, identifying 230 the starting identification 30 number assigned in the formulation of the actions content database data ID 16, identifying the ending identification 30 number assigned in the formulation of the actions content database data ID 16, current date/time 33, identification 227 number assigned of new content, ID 16, and adding data 226 to persona action history database 26.

[00171] The system E is used to collect, aggregate, store, and analyze data using a defined persona 40, or a persona 40 which is created according to user defined criteria. All personas 40 can be reused and/or copied by other users within the system E as well as combined with other attributes and/or personas 40. The system E has three capabilities which are unique to the system and do not exist elsewhere in the same implementation: Website Automation, Website testing, and Multiple Medium Interactions. The system E also allows for third-party integrations, email intelligence, website intelligence and content archiving as a result of the data aggregated. An example of how website automation and/or website testing is executed within the system E, see below, as well as Figure 12 and Figure 13. An example of how multiple medium interactions is executed within the system is it collects, aggregates, stores, and analyzes data from different types of media, such as website(s) 77 and email 78, while using the same individual virtual profile persona 40. This data is then linked to the particular persona 40 and its respective attributes such as demographics 53, geographic location 41, device 45, and defined behavior 49. The system E can then use these results and data to distinguish if and what content, such as different versions of an email 78, website 77, social media messaging 77, SMS 79, etc. display due to interacting with one or many varying medium(s) either before or after visiting a different medium using the same one persona 40. The results can then be compared to a different persona 40 which did not perform the same multiple medium interactions as the first. An example of how third-party integrations is executed within the system is it collects, aggregates, stores, and analyzes data from communication with other outside applications using their provided application program interface (API), for example Twilio which is an API for Text Messaging, VoIP & Voice in the Cloud. Using this, the system E can sign-up for SMS messaging through a website 77 and the application intelligence 1 using the persona 40 details, more specifically a phone number. The phone number is then also identifiable within the third-party API 79 and the system E can communicate to the API and collect, aggregate, store, and analyze data, such as marketing SMS messaging from a brand. An example of how multiple medium interactions is executed within the system E is it collects, aggregates, stores, and analyzes data from email intelligence is it analyzes the email 78 data to assist in identifying patterns and behaviors, for instance, how many emails are sent to a particular persona 40 in a set amount of time. A similar example of this could be understanding when is the most popular times email(s) 78 are being sent, the subjects, the number of emails which are classified as "promotional", etc., to a particular persona 40. The results can then be compared to a different persona 40 which did not perform the same tasks or does not contain similar attributes such as demographics 53, geographic location 41, device 45, and defined behavior 49. [00172] An example of how multiple medium interactions is executed within the system E is it collects, aggregates, stores, and analyzes data from website intelligence, is very similar to email intelligence, except it uses the world wide web 77 instead of email 78. The data is used to assist in identifying patterns and behaviors, for instance how often a brand homepage drastically changes, when a brand began promoting a particular holiday (example: "Thanksgiving") to a particular persona 40. Another example of this could be wherein the system E understands the types of digital content being displayed to a particular persona 40. The results can then be compared to a different persona 40 which did not perform the same tasks or does not contain similar attributes such as demographics 53, geographic location 41, device 45, and defined behavior 49. An example of how content archiving is executed within the system E is it collects, aggregates, stores, and analyzes data for all communication done using the application intelligence 1 and/or browser API 57, WAN 76, application intelligence database 2, and business intelligence 4. By archiving this content, the user is able to look back to view specific dates/times, variations of digital media based on the persona 40 attributes, search content for specific text (i.e., "sale", "free shipping", etc.), print, or other tasks performed by the user using the content and data collected/archived.

[00173] The system E used to collect, aggregate, store, and analyze data gives companies the data and analytics necessary to determine how their own and competitor online marketing efforts, including, but not limited to, email 79, ad placements 77, website content 77, text messaging (SMS) 78, etc. are being executed. In one embodiment of the present invention users setup one or more "company" structure and one or more "competitor" structure (models, templates) to track activity. The system E then identifies any existing data that match these components (Restoration Hardware, Crate and Barrel and Pier 1), then filters that data through the application intelligence 1. In addition to the automated data to be captured using the master list database 84, users can define a specific set of actions or series of steps or web pages they want the system E to capture 58, as well as a specifying persona(s) 40. One embodiment of this might be a user's interest in archiving their purchase and checkout process from start to finish using the builder user interface 58, to include the following steps:

1) Go To 66 restorationhardware.com 69 2) Click 66 on category (Bath) link 60

3) Select 66 a product (Faucet) 60

4) Click 66 Add product to cart

5) Click 66 Checkout

6) Key-in 66 checkout information using persona 40 data.

[00174] Another embodiment is as follows: A user may define a set of specific actions 83 using the builder user interface 83 that result in those specific actions being performed within the browser API 57 on a single or group of web pages 77, then recorded by the application intelligence 1, learned by the system's business intelligence 4, and over time can be automated for other websites or sets of actions and stored in the application intelligence database 2. During the set up process within the builder user interface 83 the user is asked what sort of action type they are trying to complete 6. A few embodiments of these actions are: email sign up, search submission, registration, purchase an item, sign up for text alerts, etc., The system E, knowing what the user is trying to accomplish, categorizes the set of actions to more clearly define the template, statements, variables, logic and expected results within specific actions logic 83 to improve the accuracy of further executions with the application intelligence database 2. The specific actions logic 83 can then be added to the evolving list of action template(s) 7, which can be used for other users or future similar actions logic 5 . The resulting data is then analyzed using application intelligence 1, compared with the users own action 5, and can then deliver recommendations to the user. One embodiment of a recommendation resulting from an analysis like this may, in a very simplistic sense, look something like this: "Pottery Barn: your competitor, Restoration Hardware, is sending an Abandoned Cart email 5 minutes after adding an item to the cart and leaving; therefore you may want to consider trying something similar."). Another embodiment is aggregating the data by industry segment and brand (e.g. home goods - Pottery Barn, home goods - Crate and Barrel). Another embodiment is aggregating data by vertical of industry (e.g. apparel/accessories, hardware/home improvement, office supplies, mass merchant, etc. By using all of this information, it can be aggregated together to deliver specific recommendations to users, or exported from the system in the form of reporting or graphs/charts. An embodiment of this would be: Based on 20 user accounts who receive emails using persona X,Y or Z, the content was different/varied one (1) out of two (2) times. The reason for the difference is calculated by using rules, templates, and/or algorithms for the particular content.

[00175] The following is one example of how system E is used to collect, aggregate, store, and analyze data.

Hypothetical Example:

[00176] A hypothetical example of system E used by the retailer A to collect, aggregate, store, and analyze data is the following: Retailer A would like to gain more insight into how their own marketing communications and digital media differ from that of their competition. To do this, they would tell the system E to first identify the brands which they would like to "follow." For example, the system E would identify competitors B, C and D of retailer A. If data is already stored within the system E for the specified brands, then the user is presented with various views and reporting of the data (see Report 1).

[00177] Report 1 - Summary of Delta's between User Site/Brand and Competitors

[00178] If there is no data for these items, then the brands must be setup within application intelligence 1. To set up a brand, the user first identifies the "medium" such as Web 77, Email 78 or 3rd party API 79. Once this has been set up, application intelligence 1 can begin to aggregate the defined brands' (e.g. Crate & Barrel, Restoration Hardware, Pier 1, etc.) content using predetermined actions 5, persona(s) 40 and logic 34, application intelligence database 2 and business intelligence 4. To explain this fully, the application intelligence 1 would start with the first brand, Competitor B and identify the URL for this brand (i.e.,

http://www.competitorB.com). The physical location 42 of the persona 40 is used to determine which geographic server or proxy service 43 is used for all further communication by the specific persona 40. The device(s) 44 contained within the persona' s 40 definition are then used to launch the particular remote browser 71 instance within the browser API 57. Once the browser instance 71 has loaded the URL 83 successfully, the action logic 3 can begin to execute communications to the browser instance 71, through 57 using the various logic template(s) 35, such as Register on Site, or Signup for Newsletter etc. The action logic 3 then iterates through each of the actions 5, such as Load Webpage, Logic 34 -> Find Signup/Register Form, Actions 5 -> Fill out Form, etc., using persona demographics person data 53. During each action 5, the results are then communicated with various databases including, but not limited to, actions content 15, actions history 9, persona history 26, application intelligence 2, as well as storing all screenshots to screenshot storage 73. After the completion of application intelligence 1, the accuracy of the previous steps is determined and stored inside of application intelligence database 2 for future action logic 3 executions. This process is then repeated using a slightly different persona 40 (for example returning visitor persona H, I, J, etc.), then the content is also archived and can be analyzed. This process is repeated multiple times using different persona(s) 40, action logic 5, and action templates 7 then properly organized.

[00179] If a user would like to define a specific set of actions 83 which are not already defined within the application intelligence 1, then the user can do so using the builder user interface 58 (Figure 12. 258). The user will start this process by entering a URL 69 (Figure 12. 283) into the UI tools 62 similarly to the process above, which will then load a browser instance 71 within the browser API 57 (Figure 12. 257) using the application intelligence 1 (Figure 12. 201). During this process the user can elect to use a previously used persona 40, define a new persona 40 using specified demographics 53, behavior 49, location 41 and device(s) 45, or do nothing, and the application intelligence 1 will select a persona 40 on its own. After entering the URL 69 into the UI tools 62 (for example, http://www.competitorD.com), the data is transmitted from the browser instance 71 (Figure 12. 271), through browser API 57 and the results/content from WAN 76 (Figure 12. 276) are communicated back to the users device which they are using system E with, more specifically displayed as a static graphic of remote browser running 70 (Figure 12. 270). Any further actions within 70 by the users input 59 is then transmitted back to the browser API 57, then to the browser instance using the input location 63 X & Y coordinates calculated within 70, the type of interaction and HTML Object 60, then returned from 57 to the users device inside of 58 as a native HTML Object 61. During each of these interactions, the system E does several calculations to determine where the user is intending to interact with on the remote browser instance 71, as well, recording each of the command type(s) 66, command data 65, cookie data 67, session settings 68 and current URL 69, which are then displayed where applicable within the history of actions performed 64, with a visual representation of the action performed 72. The user may then also define the frequency (for example, lx per day, week, month, etc.) at which these specific actions 65 will be performed within the scheduler database 74.

[00180] Thus, the invention provides, among other things, a methods and systems for conducting marketing research. Various features and advantages of the invention are set forth in the following claims.

Claims

CLAIMS What is claimed is:

1. A method of conducting marketing research, the method comprising: providing an application for installation on a computing device including an electronic processor; generating, via the application executed by the electronic processor of the computing device, a virtual user profile of a virtual user; performing, via the application executed by the electronic processor of the computing device, a virtual user interaction with media based on the virtual user profile; determining, via the application executed by the electronic processor of the computing device, actionable data based on the virtual user interaction with the media; and outputting an analysis of the actionable data to a display of the computing device.

2. The method of claim 1, wherein performing the virtual user interaction with the media includes capturing a screenshot of the media.

3. The method of claim 1, wherein performing the virtual user interaction with the media includes transmitting an electronic communication via the media.

4. The method of claim 1, wherein performing the virtual user interaction with the media includes establishing an electronic communication account via the media.

5. The method of claim 1, wherein performing the virtual user interaction with the media includes interacting with at least one selected from the group consisting of a website, social media, a telephone call, a text message, and an email account via the media.

6. The method of claim 1, further compri collecting the actionable data from the media; aggregating the actionable data from the media; and storing the actionable data from the media in a database.

7. The method of claim 1, wherein the virtual user profile includes at least one selected from the group consisting of a virtual user demographic, a virtual user behavior, a virtual user geographic location, and a virtual user device.

8. The method of claim 1, further comprising: analyzing the actionable data; generating a recommendation based on the analysis of the actionable data; and outputting the recommendation via the display of the computing device.

9. The method of claim 1, wherein generating the virtual user profile includes randomly selecting a first name, randomly selecting a last name, combining the first name and the last name, assigning a valid email address to the combination of the first name and the last name; assigning a valid phone number to the combination of the first name and the last name, and storing, in a database of the computing device, the combination of the first name and the last name, the valid email address assigned to the combination of the first name and the last name, and the valid phone number assigned to the combination of the first name and the last name as the virtual user profile.

10. A system of conducting marketing research, the system comprising: a database; and a computing device having an interface for communicating with the database, a computer-readable medium for storing instructions, and an electronic processor for executing the instructions stored in the computer-readable medium, wherein the electronic processor executes the instructions stored in the computer-readable medium to generate a virtual user profile of a virtual user, store the generated virtual user profile in the database, perform a virtual user interaction with media based on the virtual user profile, determine actionable data from the media based on the virtual user interaction with the media, and output an analysis of the actionable data to a display of the computing device.

11. The system of claim 10, wherein the virtual user interaction includes capturing a screenshot of the media.

12. The system of claim 10, wherein the virtual user interaction includes transmitting an electronic communication via the media.

13. The system of claim 10, wherein the virtual user interaction includes establishing an electronic communication account via the media.

14. The system of claim 10, wherein the virtual user interaction includes interacting with at least one selected from the group consisting of a website, social media, a telephone call, a text message, and an email account via the media.

15. The system of claim 10, wherein the instructions stored in the computer-readable medium further include instructions to collect the actionable data from the media, aggregate the actionable data from the media, and store the actionable data from the media in the database.

16. The system of claim 10, wherein the virtual user profile includes at least one selected from the group consisting of a virtual user demographic, a virtual user behavior, a virtual user geographic location, and a virtual user device.

17. The system of claim 10, wherein the instructions stored in the computer-readable medium further include instructions to analyze the actionable data, generate a recommendation based on the analysis of the actionable data, and output the recommendation via the interface of the computing device.

18. The system of claim 10, wherein the instruction to generate the virtual user interface further includes instructions to randomly select a first name, randomly select a last name, combine the first name and the last name, assign a valid email address to the combination of the first name and the last name, assign a valid phone number to the combination of the first name and the last name, and store, in the database of the computing device, the combination of the first name and the last name, the valid email address assigned to the combination of the first name and the last name, and the valid phone number assigned to the combination of the first name and the last name as the virtual user profile.