US20100268731A1 - Touchpoint customization system - Google Patents
Touchpoint customization system Download PDFInfo
- Publication number
- US20100268731A1 US20100268731A1 US12/762,012 US76201210A US2010268731A1 US 20100268731 A1 US20100268731 A1 US 20100268731A1 US 76201210 A US76201210 A US 76201210A US 2010268731 A1 US2010268731 A1 US 2010268731A1
- Authority
- US
- United States
- Prior art keywords
- user
- content action
- content
- touchpoint
- action
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0241—Advertisements
- G06Q30/0242—Determining effectiveness of advertisements
- G06Q30/0243—Comparative campaigns
Definitions
- the Internet has become increasingly popular with the consuming public and web pages on the Internet are considered powerful media for advertising. Advertisements on web pages are directly linked to the web pages as fixed inline images, while more flexible systems allow a separation of advertisement selection and placement, but offer only a random selection mechanism. Many of the methods implemented by advertisers are typically too simple to take advantage of the just-in-time selection and delivery process available with web page advertisements. Although conventional filtering techniques allow for precise targeting of the advertisements, the task of selecting whom to target what advertisement are left to largely to the advertiser. This requires extended efforts on the advertiser side, who has to rely on countless statistics and demographic studies.
- FIG. 1 illustrates a system for touchpoint content action customization, according to an embodiment
- FIG. 2A illustrates an example of determining candidate content actions, according to an embodiment
- FIG. 2B illustrates an example of determining a customized content action, according to an embodiment
- FIG. 2C illustrates an additional example of determining a customized content action, according to an embodiment
- FIG. 3 illustrates a tree structure, according to an embodiment
- FIG. 4 illustrates a method for touchpoint content action customization, according to an embodiment
- FIG. 5 illustrates a block diagram of a computing system, according to an embodiment.
- customized content actions are provided to a user at multiple touchpoints the user visits for a customized end-to-end user experience.
- a customized content action is content that is presented and/or an action that is performed.
- the content or action is customized based on a user and their previous interactions and other information. Examples of a customized content action may include a tactic, a strategy, a seminar, a button, a product presentation or demonstration, a product catalog, product pricing, information about a product, a social media piece, frequently asked questions presented to the user as additional information, etc.
- a “touchpoint” is a specific interaction between an entity and a user within a specific channel.
- An entity may be a company, another user or some other type of entity.
- a channel is a medium for providing one or more touchpoints. Examples of channels include the Internet, TV, radio, etc. In instances where the channel is the Internet, examples of touchpoints may be a webpage or a portion of a webpage with which the user interacts.
- the customized content action provided to the user at each touchpoint is based on dynamic desired-outcome driven optimization.
- the system dynamically presents a customized content action to a user at each touchpoint the user visits that is driven by a desired-outcome, such as a business objective.
- the business objective may include selling a particular product to a user, directing the user to subscribe to a specific service, etc.
- a user is funneled through various touchpoints, each with a customized content action, in a customized end-to-end user experience to achieve the business objective.
- the system provides an enhanced automated content action selection process to provide the user with a customized user display.
- FIG. 1 illustrates a system 100 for content action customization, according to an embodiment.
- the system 100 includes a user touchpoint data capture unit 140 , a user touchpoint database 150 , a content action optimization engine 160 , a content action repository 170 , and content action optimization model 180 .
- the system 100 depicted in FIG. 1 may include additional components and that some of the components described herein may be removed and/or modified without departing from a scope of the system 100 .
- Users 110 a - n access touchpoints 120 a - n of a specific channel 115 .
- the channel 115 is the Internet and the touchpoints 120 a - n are web site touchpoints.
- the users 110 a - n may access the web site touchpoints 120 a - n through end user devices connected to the Internet, such as, computers, laptops, cellular telephones, personal digital assistants (PDAs), etc.
- PDAs personal digital assistants
- the system 100 captures user data 130 .
- the user touchpoint data capture unit 140 captures the user data 130 at each of the one or more touchpoints 120 a - n that the user 110 a accesses or visits.
- the user touchpoint data capture unit 140 may capture the user data 130 from HTML or Javascript embedded in the touchpoint 120 a - n , from an agent running on a user device, from third party sources collecting user information, etc.
- the captured user data 130 may include historical data about the course of interaction at the touchpoints 120 a - n already visited by the user, actions taken by the user and user attributes, such as gender, geographic location, purchase habits, etc.
- the user touchpoint data capture unit 140 stores the captured user data 130 in the user touchpoint database 150 .
- the content action optimization engine 160 is depicted as receiving the user data 130 from the user touchpoint database 150 and candidate content actions 195 from the content action repository 170 .
- the content action optimization engine 160 is depicted as receiving a business objective 190 .
- the content action optimization engine 160 is generally configured to use the user data 130 as well as the content action optimization model 180 and business objective 190 to determine a customized content action 198 for each of the touchpoints 120 a - n visited by the user 110 a.
- the content action optimization model 180 includes historic information regarding resulting user behavior in response to various content actions presented to a type or segment of users having particular user attributes at specific touchpoints 120 a - n .
- the content action optimization model 180 includes user data grouped by attributes, touchpoints visited, content actions presented at the touchpoints and observed user behavior.
- one group may include Asian women between 40 and 50 years.
- An observed user behavior for the group may include that they purchased handbags priced over $150.00 55% of the time when presented with a certain content action at a certain touchpoint.
- the content action optimization model 180 may include many different types of observed behavior for many different groups of users for different touchpoints, and this observed behavior may be used to estimate or predict behavior for various touchpoints and users. According to an embodiment, therefore, the content action optimization model 180 may be generated based on the analysis of observed user behavior and/or based on the analysis of historic data provided by external data sources.
- a company may input the business objective 190 to be achieved into the content action optimization engine 160 .
- the business objective 190 may include selling a particular product to a user, directing a user to subscribe to a specific service, or any other desired business outcome.
- the content action optimization engine 160 is configured to dynamically determine the customized content action 198 to implement at a particular touchpoint 120 a .
- a plurality of content actions which may include various tactics, strategies, seminars, buttons, product presentations or demonstrations, product catalogs, product pricing, information about products, social media pieces, frequently asked questions, etc., are stored in the content action repository 170 .
- the content action repository 170 also includes metadata associated with each content action, which identifies each content action, describes each content action, and describes how each content action is used.
- the metadata also includes constraints for each content action, which describes restrictions on the use of the content action, which may be in the form of descriptors, instructional videos, etc. The constraints may describe at which touchpoint the content action may be implemented and for which business objective the content action may be used. For example, a specific content action may only be used for a specific touchpoint or for a specific segment of the population. According to an embodiment, the content actions are grouped according to corresponding business objectives and touchpoints based on the content action metadata.
- the content action optimization engine 160 determines which customized content action to implement at a particular touchpoint. For example, the user 110 a accesses the particular touchpoint 120 a , which comprises a web page on the Internet. In order to determine the customized content action 198 to implement at the touchpoint 120 a for the user 110 a , the content action optimization engine 160 retrieves candidate content actions 195 from the content action repository 170 . Note that in some instances the content action optimization engine 160 retrieves a single candidate content action 195 . The candidate content actions 195 are retrieved based on the particular touchpoint 120 a that the user 110 a is visiting, as well as, the business objective 190 for which the content action is to be used. Thus, the candidate content actions 195 are retrieved based on the metadata of the content actions in the content action repository 170 .
- the metadata for the content actions are compared to current touchpoint information for a user to select the candidate content actions 195 .
- the content action repository 170 includes the content actions listed in table 210 .
- content actions A, B, and C are retrieved as the candidate content actions 195 because the user is at touchpoint 120 a and the business objective 190 is business objective 1 .
- the content actions A, B, and C may be selected and retrieved as the candidate content actions 195 based upon information contained in the metadata for the content actions A, B and C.
- the metadata for content actions D-J describe the content actions D-J as either not being used for touchpoint 120 a or not being for business objective 1 .
- the content action optimization engine 160 may select one of the candidate content actions 195 as the customized content action 198 to be implemented at the touchpoint 120 a .
- the customized content action 198 is the candidate content action that is most likely to achieve the business objective 1 .
- the content action optimization engine 160 identifies a user group to which the user 110 a belongs by matching the user attributes for the user 110 a stored in the user data 130 to the user group data in the optimization model 180 .
- the content action optimization model 180 includes data grouped by user groups. Each user group has a corresponding set of attributes that can be matched to user attributes.
- Each user group in the optimization model 180 may have associated categories including touchpoint visited, content action presented at the touchpoint and observed user behavior. Then, based on the user group to which the user 110 a belongs, the content action optimization engine 160 identifies each of the candidate content actions 195 in the determined user group. The data associated with the identified content actions within the user group include an observed percentage of success at achieving the business objective. In addition, the content action optimization engine 160 analyzes the data associated with each of the identified content actions in the content action optimization model 180 and may select the candidate content action that has the highest percentage of the observed percentage of success at achieving the business objective as the customized content action 198 to implement for the user 110 a at the touchpoint 120 a . According to another embodiment, the content action optimization engine 160 uses different weighting schemes to select the customized content action 198 .
- FIG. 2B illustrates an example of information contained in the content action optimization model 180 for a single user group 221 , shown as Asian Women in the age range of 40-50 years.
- the user attributes in the captured user data 130 for the user 110 a are compared with the user groups in the content action optimization model 180 . If the user 110 a is a 44-year old Asian woman, then the content action optimization engine 160 uses the subset of data in the content action optimization model 180 for the user group 221 of Asian women between 40 and 50.
- the user group 221 is part of a user group data subset in the content action optimization model 180 and includes content actions for several touchpoints and percentages of achieving the business objective 190 for each content action, as shown in table 220 in FIG. 2B .
- the content action A has an observed behavior percentage of 50%
- the content action B has an observed behavior percentage of 20%
- the content action C has an observed behavior percentage of 30%.
- the identified content action of the candidate content actions 195 with the highest observed behavior percentage is the content action A at 50%
- the content action A is the customized content action 198 , as shown in FIG. 2C .
- the customized content action 198 is then implemented at touchpoint 120 a for user 110 a.
- the user data 130 for user 110 a is then updated with data regarding the customized content action 198 that was implemented at touchpoint 120 a and the user data 130 is again saved in the user touchpoint database 150 .
- the user 110 a then may continue to the next touchpoint 120 b .
- a new customized content action to implement at touchpoint 120 b for user 110 a is determined based on the same steps noted above, based on the additional data saved with the captured user data 130 including which content action was presented beforehand at each touchpoint visited by the user 110 a , and continues until the business objective 190 is achieved.
- the user 110 a is funneled through a plurality of touchpoints 120 a - n in which a customized content action is presented at each touchpoint aimed to achieve the business objective 190 , until the business objective 190 is achieved.
- the candidate content actions 195 are branches of a tree structure. At each touchpoint, a new tree structure of candidate content actions 195 is formed since, at each touchpoint, updated user data is captured including the last touchpoint visited data and user attributes. For example, in FIG. 3 , at touchpoint 120 a , three branches are shown as 310 , 320 and 330 . Each branch 310 , 320 and 330 , corresponds to the same user group which is determined based on user attributes as discussed above. Each branch 310 , 320 and 330 , is further distinguished from each other based on the business objective to which the content action sub-branches pertain.
- a variety of candidate content actions 195 are shown.
- content actions A, B and C are shown as sub-branches 340 , 350 and 360 , respectively.
- An observed user behavior and a percentage of observed user behavior success is shown for each content action sub-branch 340 , 350 and 360 .
- the “Observed User Behavior” is “Buy Purse” and the “Percentage” is “50%”.
- 50% of the time when content action A listed as 340 is implemented at touchpoint 120 a , the user in user group 221 buys the purse.
- the tree structure formed at each touchpoint changes according to user attributes, last touchpoint visited, last content action presented, content action metadata, etc.
- the user is funneled through a plurality of touchpoints in which a new tree structure is formed at each touchpoint aimed to achieve the business objective, until the business objective is achieved.
- FIG. 4 illustrates a flowchart of a method 400 for content action customization at a touchpoint, according to an embodiment. It should be understood that the method 400 depicted in FIG. 4 may include additional steps and that some of the steps described herein may be removed and/or modified without departing from a scope of the method 400 . In addition, the method 400 may be implemented by the system 100 described above with respect to FIG. 1 by way of example, but may also be practiced in other systems.
- the system 100 receives input of a business objective 190 .
- the business objective may be a business objective received from a company.
- the business objective may be to sell a product or service.
- the system 100 captures user data of a user visiting the touchpoint.
- the system 100 may capture the user data from HTML or Javascript embedded in the touchpoint, from an agent running on a user device, from third party sources collecting user information, etc.
- the captured user data may include historical data about the course of interaction at the touchpoints already visited by the user, actions taken by the user and user attributes, such as gender, geographic location, purchase habits, etc.
- the captured user data is stored in the user touchpoint database and is used as input for the system 100 , as is further described below.
- the system 100 selects and retrieves one or more candidate content actions 195 .
- the system 100 dynamically determines the candidate content actions from a plurality of content actions are stored in the content action repository 170 .
- the plurality of content actions may include a tactic, a strategy, a seminar, a button, a product presentation or demonstration, a product catalog, product pricing, information about a product, a social media piece, frequently asked questions, etc.
- the content action repository 170 also includes metadata associated with each content action identifying each content action, describing each content action and describing how each content action is used.
- the content action repository 170 further includes constraints for each content action describing restrictions on the use of the content action, which may be in the form of descriptors, instructional videos, etc.
- the constraints may describe at which touchpoint the content action can be implemented and for which business objective the content action can be used. For example, a specific content action may only be used for a specific touchpoint or for a specific segment of the population.
- the content actions in the content action repository are grouped according to corresponding business objectives and touchpoints based on the content action metadata.
- the candidate content actions are retrieved based on the touchpoint the user is currently visiting and based on the business objective for which the content action may be used. Thus, the candidate content actions are retrieved based on the metadata of the content actions in the content action repository.
- the system 100 selects the customized content action to be implemented at the touchpoint.
- the customized content action is the candidate content action that is most likely to achieve the business objective.
- the content action optimization engine 160 identifies a user group to which the user belongs by matching the user attributes for the user stored in the user data to the user group data in the optimization model 180 . Then, based on the user group to which the user belongs, the system 100 identifies each of the candidate content actions in the determined user group.
- the system 100 analyzes the data associated with each of the identified content actions in the content action optimization model, in which the data associated with the identified content actions within the user group include an observed percentage of success at achieving the business objective.
- the system 100 may select the candidate content action that has the highest percentage of the observed percentage of success for the business objective as the customized content action to implement for the user at the touchpoint.
- step 450 the determined customized content action is implemented at the touchpoint.
- step 460 a decision is made whether the business objective has been achieved. If the customized content action implemented at the touchpoint produces the observed behavior that is equivalent to the business objective, the process moves on to step 470 where the method 400 is ended. However, if the customized content action implemented at the touchpoint does not produce the observed behavior that is equivalent to the business objective, the user moves on to the next touchpoint and the process restarts at step 420 .
- step 470 regardless of whether the business objective has been achieved, the captured user data is updated with data regarding the customized content action that was implemented at step 450 . The user data is again saved.
- FIG. 5 shows a computer system 500 that may be used as a hardware platform for the creative marketplace system 100 .
- the computer system 500 may be used as a platform for executing one or more of the steps, methods, and functions described herein that may be embodied as software stored on one or more computer readable storage devices, which are hardware storage devices.
- the computer system 500 includes a processor 502 or processing circuitry that may implement or execute software instructions performing some or all of the methods, functions and other steps described herein. Commands and data from the processor 502 are communicated over a communication bus 504 .
- the computer system 500 also includes a computer readable storage device 503 , such as random access memory (RAM), where the software and data for processor 502 may reside during runtime.
- the storage device 503 may also include non-volatile data storage.
- the computer system 500 may include a network interface 505 for connecting to a network. It will be apparent to one of ordinary skill in the art that other known electronic components may be added or substituted in the computer system 500 .
Abstract
A system for touchpoint content action customization at a current touchpoint to achieve a business objective includes a user touchpoint data capture unit and a content action optimization engine. The content action optimization engine is configured to select a plurality of candidate content actions for the current touchpoint based on content action metadata, to determine an observed percentage of success for an observed user behavior for each of the plurality of candidate content actions based on the user group to which the user belongs, and to determine a customized content action of the plurality of candidate content actions to implement at the current touchpoint to achieve the business objective that has the highest observed percentage of success.
Description
- This application claims priority to U.S. provisional patent application Ser. No. 61/169,892, filed on Apr. 16, 2009, and entitled “Digital Platform”, which is incorporated by reference in its entirety.
- The Internet has become increasingly popular with the consuming public and web pages on the Internet are considered powerful media for advertising. Advertisements on web pages are directly linked to the web pages as fixed inline images, while more flexible systems allow a separation of advertisement selection and placement, but offer only a random selection mechanism. Many of the methods implemented by advertisers are typically too simple to take advantage of the just-in-time selection and delivery process available with web page advertisements. Although conventional filtering techniques allow for precise targeting of the advertisements, the task of selecting whom to target what advertisement are left to largely to the advertiser. This requires extended efforts on the advertiser side, who has to rely on countless statistics and demographic studies.
- The embodiments of the invention will be described in detail in the following description with reference to the following figures.
-
FIG. 1 illustrates a system for touchpoint content action customization, according to an embodiment; -
FIG. 2A illustrates an example of determining candidate content actions, according to an embodiment; -
FIG. 2B illustrates an example of determining a customized content action, according to an embodiment; -
FIG. 2C illustrates an additional example of determining a customized content action, according to an embodiment; -
FIG. 3 illustrates a tree structure, according to an embodiment; -
FIG. 4 illustrates a method for touchpoint content action customization, according to an embodiment; and -
FIG. 5 illustrates a block diagram of a computing system, according to an embodiment. - For simplicity and illustrative purposes, the principles of the embodiments are described by referring mainly to examples thereof. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the embodiments. It will be apparent however, to one of ordinary skill in the art, that the embodiments may be practiced without limitation to these specific details. In some instances, well known methods and structures have not been described in detail so as not to unnecessarily obscure the embodiments. Also, the embodiments described herein may be used with each other in various combinations.
- According to an embodiment of the invention, customized content actions are provided to a user at multiple touchpoints the user visits for a customized end-to-end user experience. A customized content action is content that is presented and/or an action that is performed. The content or action is customized based on a user and their previous interactions and other information. Examples of a customized content action may include a tactic, a strategy, a seminar, a button, a product presentation or demonstration, a product catalog, product pricing, information about a product, a social media piece, frequently asked questions presented to the user as additional information, etc.
- As used herein, a “touchpoint” is a specific interaction between an entity and a user within a specific channel. An entity may be a company, another user or some other type of entity. A channel is a medium for providing one or more touchpoints. Examples of channels include the Internet, TV, radio, etc. In instances where the channel is the Internet, examples of touchpoints may be a webpage or a portion of a webpage with which the user interacts.
- The customized content action provided to the user at each touchpoint is based on dynamic desired-outcome driven optimization. Thus, the system dynamically presents a customized content action to a user at each touchpoint the user visits that is driven by a desired-outcome, such as a business objective. The business objective may include selling a particular product to a user, directing the user to subscribe to a specific service, etc. Thus, a user is funneled through various touchpoints, each with a customized content action, in a customized end-to-end user experience to achieve the business objective. The system provides an enhanced automated content action selection process to provide the user with a customized user display.
-
FIG. 1 illustrates asystem 100 for content action customization, according to an embodiment. As shown therein, thesystem 100 includes a user touchpointdata capture unit 140, a user touchpoint database 150, a contentaction optimization engine 160, acontent action repository 170, and contentaction optimization model 180. It should be understood that thesystem 100 depicted inFIG. 1 may include additional components and that some of the components described herein may be removed and/or modified without departing from a scope of thesystem 100. - Users 110 a-n access touchpoints 120 a-n of a
specific channel 115. For example, thechannel 115 is the Internet and the touchpoints 120 a-n are web site touchpoints. The users 110 a-n may access the web site touchpoints 120 a-n through end user devices connected to the Internet, such as, computers, laptops, cellular telephones, personal digital assistants (PDAs), etc. According to an embodiment, when the users 110 a-n access the web site touchpoints 120 a-n, thesystem 100 captures user data 130. For example, the user touchpointdata capture unit 140 captures the user data 130 at each of the one or more touchpoints 120 a-n that theuser 110 a accesses or visits. The user touchpointdata capture unit 140 may capture the user data 130 from HTML or Javascript embedded in the touchpoint 120 a-n, from an agent running on a user device, from third party sources collecting user information, etc. The captured user data 130 may include historical data about the course of interaction at the touchpoints 120 a-n already visited by the user, actions taken by the user and user attributes, such as gender, geographic location, purchase habits, etc. - As shown in
FIG. 1 , the user touchpointdata capture unit 140 stores the captured user data 130 in the user touchpoint database 150. In addition, the contentaction optimization engine 160 is depicted as receiving the user data 130 from the user touchpoint database 150 andcandidate content actions 195 from thecontent action repository 170. Moreover the contentaction optimization engine 160 is depicted as receiving abusiness objective 190. As discussed in greater detail herein below, the contentaction optimization engine 160 is generally configured to use the user data 130 as well as the contentaction optimization model 180 andbusiness objective 190 to determine a customizedcontent action 198 for each of the touchpoints 120 a-n visited by theuser 110 a. - The content
action optimization model 180 includes historic information regarding resulting user behavior in response to various content actions presented to a type or segment of users having particular user attributes at specific touchpoints 120 a-n. In one example, the contentaction optimization model 180 includes user data grouped by attributes, touchpoints visited, content actions presented at the touchpoints and observed user behavior. For example, one group may include Asian women between 40 and 50 years. An observed user behavior for the group may include that they purchased handbags priced over $150.00 55% of the time when presented with a certain content action at a certain touchpoint. Thus, the contentaction optimization model 180 may include many different types of observed behavior for many different groups of users for different touchpoints, and this observed behavior may be used to estimate or predict behavior for various touchpoints and users. According to an embodiment, therefore, the contentaction optimization model 180 may be generated based on the analysis of observed user behavior and/or based on the analysis of historic data provided by external data sources. - Generally speaking, a company may input the
business objective 190 to be achieved into the contentaction optimization engine 160. For example, thebusiness objective 190 may include selling a particular product to a user, directing a user to subscribe to a specific service, or any other desired business outcome. - Based on the inputs, for instance, the content
action optimization model 180, the user data 130 and thebusiness objective 190, the contentaction optimization engine 160 is configured to dynamically determine the customizedcontent action 198 to implement at aparticular touchpoint 120 a. By way of example, a plurality of content actions, which may include various tactics, strategies, seminars, buttons, product presentations or demonstrations, product catalogs, product pricing, information about products, social media pieces, frequently asked questions, etc., are stored in thecontent action repository 170. - The
content action repository 170 also includes metadata associated with each content action, which identifies each content action, describes each content action, and describes how each content action is used. The metadata also includes constraints for each content action, which describes restrictions on the use of the content action, which may be in the form of descriptors, instructional videos, etc. The constraints may describe at which touchpoint the content action may be implemented and for which business objective the content action may be used. For example, a specific content action may only be used for a specific touchpoint or for a specific segment of the population. According to an embodiment, the content actions are grouped according to corresponding business objectives and touchpoints based on the content action metadata. - The content
action optimization engine 160 determines which customized content action to implement at a particular touchpoint. For example, theuser 110 a accesses theparticular touchpoint 120 a, which comprises a web page on the Internet. In order to determine the customizedcontent action 198 to implement at thetouchpoint 120 a for theuser 110 a, the contentaction optimization engine 160 retrievescandidate content actions 195 from thecontent action repository 170. Note that in some instances the contentaction optimization engine 160 retrieves a singlecandidate content action 195. Thecandidate content actions 195 are retrieved based on theparticular touchpoint 120 a that theuser 110 a is visiting, as well as, thebusiness objective 190 for which the content action is to be used. Thus, thecandidate content actions 195 are retrieved based on the metadata of the content actions in thecontent action repository 170. - In one example, the metadata for the content actions are compared to current touchpoint information for a user to select the
candidate content actions 195. For example, as shown inFIG. 2A , thecontent action repository 170 includes the content actions listed in table 210. As shown in the table 210, content actions A, B, and C are retrieved as thecandidate content actions 195 because the user is attouchpoint 120 a and thebusiness objective 190 isbusiness objective 1. More particularly, the content actions A, B, and C may be selected and retrieved as thecandidate content actions 195 based upon information contained in the metadata for the content actions A, B and C. In contrast, the metadata for content actions D-J describe the content actions D-J as either not being used fortouchpoint 120 a or not being forbusiness objective 1. - Once the
candidate content actions 195 are retrieved from thecontent action repository 170, the contentaction optimization engine 160 may select one of thecandidate content actions 195 as the customizedcontent action 198 to be implemented at thetouchpoint 120 a. In one embodiment, the customizedcontent action 198 is the candidate content action that is most likely to achieve thebusiness objective 1. In one example, to determine the customizedcontent action 198, the contentaction optimization engine 160 identifies a user group to which theuser 110 a belongs by matching the user attributes for theuser 110 a stored in the user data 130 to the user group data in theoptimization model 180. For example, the contentaction optimization model 180 includes data grouped by user groups. Each user group has a corresponding set of attributes that can be matched to user attributes. Each user group in theoptimization model 180 may have associated categories including touchpoint visited, content action presented at the touchpoint and observed user behavior. Then, based on the user group to which theuser 110 a belongs, the contentaction optimization engine 160 identifies each of thecandidate content actions 195 in the determined user group. The data associated with the identified content actions within the user group include an observed percentage of success at achieving the business objective. In addition, the contentaction optimization engine 160 analyzes the data associated with each of the identified content actions in the contentaction optimization model 180 and may select the candidate content action that has the highest percentage of the observed percentage of success at achieving the business objective as the customizedcontent action 198 to implement for theuser 110 a at thetouchpoint 120 a. According to another embodiment, the contentaction optimization engine 160 uses different weighting schemes to select the customizedcontent action 198. -
FIG. 2B illustrates an example of information contained in the contentaction optimization model 180 for asingle user group 221, shown as Asian Women in the age range of 40-50 years. For example, the user attributes in the captured user data 130 for theuser 110 a are compared with the user groups in the contentaction optimization model 180. If theuser 110 a is a 44-year old Asian woman, then the contentaction optimization engine 160 uses the subset of data in the contentaction optimization model 180 for theuser group 221 of Asian women between 40 and 50. Theuser group 221 is part of a user group data subset in the contentaction optimization model 180 and includes content actions for several touchpoints and percentages of achieving thebusiness objective 190 for each content action, as shown in table 220 inFIG. 2B . Based on the subset of data in the contentaction optimization model 180, the content action A has an observed behavior percentage of 50%, the content action B has an observed behavior percentage of 20% and the content action C has an observed behavior percentage of 30%. Thus, the identified content action of thecandidate content actions 195 with the highest observed behavior percentage is the content action A at 50%, and therefore the content action A is the customizedcontent action 198, as shown inFIG. 2C . The customizedcontent action 198 is then implemented attouchpoint 120 a foruser 110 a. - The user data 130 for
user 110 a is then updated with data regarding the customizedcontent action 198 that was implemented attouchpoint 120 a and the user data 130 is again saved in the user touchpoint database 150. - The
user 110 a then may continue to thenext touchpoint 120 b. Attouchpoint 120 b, a new customized content action to implement attouchpoint 120 b foruser 110 a is determined based on the same steps noted above, based on the additional data saved with the captured user data 130 including which content action was presented beforehand at each touchpoint visited by theuser 110 a, and continues until thebusiness objective 190 is achieved. Thus, theuser 110 a is funneled through a plurality of touchpoints 120 a-n in which a customized content action is presented at each touchpoint aimed to achieve thebusiness objective 190, until thebusiness objective 190 is achieved. - According to an embodiment, the
candidate content actions 195 are branches of a tree structure. At each touchpoint, a new tree structure ofcandidate content actions 195 is formed since, at each touchpoint, updated user data is captured including the last touchpoint visited data and user attributes. For example, inFIG. 3 , attouchpoint 120 a, three branches are shown as 310, 320 and 330. Eachbranch branch branch business objective 1 anduser group 221 listed asbranch 310, content actions A, B and C are shown assub-branches content action sub-branch content action sub-branch 340, the “Observed User Behavior” is “Buy Purse” and the “Percentage” is “50%”. Thus, 50% of the time, when content action A listed as 340 is implemented attouchpoint 120 a, the user inuser group 221 buys the purse. Thus, the tree structure formed at each touchpoint changes according to user attributes, last touchpoint visited, last content action presented, content action metadata, etc. In addition, the user is funneled through a plurality of touchpoints in which a new tree structure is formed at each touchpoint aimed to achieve the business objective, until the business objective is achieved. -
FIG. 4 illustrates a flowchart of amethod 400 for content action customization at a touchpoint, according to an embodiment. It should be understood that themethod 400 depicted inFIG. 4 may include additional steps and that some of the steps described herein may be removed and/or modified without departing from a scope of themethod 400. In addition, themethod 400 may be implemented by thesystem 100 described above with respect toFIG. 1 by way of example, but may also be practiced in other systems. - At step 410, the
system 100 receives input of abusiness objective 190. The business objective may be a business objective received from a company. For example, the business objective may be to sell a product or service. - At step 420, the
system 100 captures user data of a user visiting the touchpoint. Thesystem 100 may capture the user data from HTML or Javascript embedded in the touchpoint, from an agent running on a user device, from third party sources collecting user information, etc. The captured user data may include historical data about the course of interaction at the touchpoints already visited by the user, actions taken by the user and user attributes, such as gender, geographic location, purchase habits, etc. In addition, the captured user data is stored in the user touchpoint database and is used as input for thesystem 100, as is further described below. - At
step 430, thesystem 100 selects and retrieves one or morecandidate content actions 195. Based on the contentaction optimization model 180 as described above with regard to thesystem 100, the captured user data and the input business objective, thesystem 100 dynamically determines the candidate content actions from a plurality of content actions are stored in thecontent action repository 170. The plurality of content actions may include a tactic, a strategy, a seminar, a button, a product presentation or demonstration, a product catalog, product pricing, information about a product, a social media piece, frequently asked questions, etc. Thecontent action repository 170 also includes metadata associated with each content action identifying each content action, describing each content action and describing how each content action is used. Thecontent action repository 170 further includes constraints for each content action describing restrictions on the use of the content action, which may be in the form of descriptors, instructional videos, etc. The constraints may describe at which touchpoint the content action can be implemented and for which business objective the content action can be used. For example, a specific content action may only be used for a specific touchpoint or for a specific segment of the population. The content actions in the content action repository are grouped according to corresponding business objectives and touchpoints based on the content action metadata. The candidate content actions are retrieved based on the touchpoint the user is currently visiting and based on the business objective for which the content action may be used. Thus, the candidate content actions are retrieved based on the metadata of the content actions in the content action repository. - At step 440, once the candidate content actions are retrieved from the content action repository, the
system 100 selects the customized content action to be implemented at the touchpoint. In one embodiment, the customized content action is the candidate content action that is most likely to achieve the business objective. For example, to determine the customized content action, the contentaction optimization engine 160 identifies a user group to which the user belongs by matching the user attributes for the user stored in the user data to the user group data in theoptimization model 180. Then, based on the user group to which the user belongs, thesystem 100 identifies each of the candidate content actions in the determined user group. Thesystem 100 analyzes the data associated with each of the identified content actions in the content action optimization model, in which the data associated with the identified content actions within the user group include an observed percentage of success at achieving the business objective. Thesystem 100 may select the candidate content action that has the highest percentage of the observed percentage of success for the business objective as the customized content action to implement for the user at the touchpoint. - In step 450, the determined customized content action is implemented at the touchpoint.
- In step 460, a decision is made whether the business objective has been achieved. If the customized content action implemented at the touchpoint produces the observed behavior that is equivalent to the business objective, the process moves on to step 470 where the
method 400 is ended. However, if the customized content action implemented at the touchpoint does not produce the observed behavior that is equivalent to the business objective, the user moves on to the next touchpoint and the process restarts at step 420. Atstep 470, regardless of whether the business objective has been achieved, the captured user data is updated with data regarding the customized content action that was implemented at step 450. The user data is again saved. -
FIG. 5 shows acomputer system 500 that may be used as a hardware platform for thecreative marketplace system 100. Thecomputer system 500 may be used as a platform for executing one or more of the steps, methods, and functions described herein that may be embodied as software stored on one or more computer readable storage devices, which are hardware storage devices. - The
computer system 500 includes aprocessor 502 or processing circuitry that may implement or execute software instructions performing some or all of the methods, functions and other steps described herein. Commands and data from theprocessor 502 are communicated over acommunication bus 504. Thecomputer system 500 also includes a computerreadable storage device 503, such as random access memory (RAM), where the software and data forprocessor 502 may reside during runtime. Thestorage device 503 may also include non-volatile data storage. Thecomputer system 500 may include anetwork interface 505 for connecting to a network. It will be apparent to one of ordinary skill in the art that other known electronic components may be added or substituted in thecomputer system 500. - While the embodiments have been described with reference to examples, those skilled in the art will be able to make various modifications to the described embodiments without departing from the scope of the claimed embodiments. Also, the embodiments described herein may be used to determine which content actions are undesirable, which content actions to implement that receive the most online traffic, etc.
Claims (20)
1. A system for touchpoint content action customization at a current touchpoint to achieve a business objective, comprising:
a user touchpoint data capture unit configured to receive user data, said user data including user attributes for a user visiting the current touchpoint, and to determine a user group to which the user belongs based on the user attributes of the user; and
a content action optimization engine configured to select a plurality of candidate content actions from a content action repository for the business objective and for the current touchpoint based on content action metadata, wherein said content action metadata describes the business objective for which the content action is used and the touchpoint for which the content action is used, to determine an observed percentage of success for an observed user behavior for each of the plurality of candidate content actions based on the user group to which the user belongs, and determine a customized content action of the plurality of candidate content actions to implement at the current touchpoint to achieve the business objective that has the highest observed percentage of success.
2. The system of claim 1 , wherein the content action optimization engine is configured to implement the customized content action at the current touchpoint.
3. The system of claim 2 , wherein the content action optimization engine is configured to record a user behavior in response to implementing the customized content action at the current touchpoint.
4. The system of claim 3 , wherein the content action optimization engine is configured to compare the business objective to the recorded user behavior to determine if the business objective has been achieved.
5. The system of claim 4 , wherein the content action optimization engine is configured to determined that the business objective has been achieved when the business objective is equivalent to the recorded user behavior.
6. The system of claim 5 , wherein the content action optimization engine is configured to determine another customized content action for a next touchpoint if the business objective is not equivalent to the recorded user behavior.
7. The system of claim 1 , wherein the content action comprises at least one of a tactic, a strategy, a seminar, a button, a product presentation or demonstration, a product catalog, product pricing, information about a product, a social media piece, and a set of frequently asked questions.
8. The system of claim 1 , wherein the content action metadata for each content action further identifies each content action, describes each content action, and describes how each content action is used.
9. The system of claim 1 , wherein the content action metadata for each content action further identifies constraints for each content action's use.
10. A method for touchpoint content action customization at a current touchpoint to achieve a business objective, said method comprising:
receiving user data including user attributes for a user visiting the current touchpoint;
determining a user group to which the user belongs based on the user attributes of the user;
selecting, using a processor, a plurality of candidate content actions from a content action repository for the business objective and for the current touchpoint based on content action metadata, wherein said content action metadata describes the business objective for which the content action is used and the touchpoint for which the content action is used;
determining an observed percentage of success for an observed user behavior for each of the plurality of candidate content actions based on the user group to which the user belongs; and
determining a customized content action of the plurality of candidate content actions to implement at the current touchpoint to achieve the business objective that has the highest observed percentage of success.
11. The method of claim 10 , further comprising:
implementing the customized content action at the current touchpoint.
12. The method of claim 11 , further comprising:
recording the behavior of the user in response to implementing the customized content action at the current touchpoint.
13. The method of claim 12 , further comprising:
comparing the business objective to the recorded user behavior; and
if the business objective is not equivalent to the recorded user behavior, repeating the selecting, determining an observed percentage of success, and determining a customized content action steps.
14. The method of claim 10 , wherein the content action comprises at least one of a tactic, a strategy, a seminar, a button, a product presentation or demonstration, a product catalog, product pricing, information about a product, a social media piece, and a set of frequently asked questions.
15. The method of claim 10 , wherein the content action metadata for each content action further identifies constraints for each content action's use.
16. A computer readable medium having stored thereon a computer executable program for touchpoint content action customization at a current touchpoint to achieve a business objective, the computer executable program when executed causes a computer system to:
receive user data including user attributes for a user visiting the current touchpoint;
determine a user group to which the user belongs based on the user attributes for the user;
select a plurality of candidate content actions from a content action repository for the business objective and for the current touchpoint based on content action metadata, wherein said content action metadata describes the business objective for which the content action is used and the touchpoint for which the content action is used;
determine an observed percentage of success for an observed user behavior for each of the plurality of candidate content actions based on the user group to which the user belongs; and
determine a customized content action of the plurality of candidate content actions to implement at the current touchpoint to achieve the business objective that has the highest observed percentage of success.
17. The computer readable medium of claim 16 , further comprising:
implementing the customized content action at the current touchpoint.
18. The computer readable medium of claim 17 , further comprising:
recording a user behavior in response to implementing the customized content action at the current touchpoint.
19. The computer readable medium of claim 18 , further comprising:
comparing the business objective to the recorded user behavior; and
if the business objective is not equivalent to the recorded user behavior, repeating the selecting, determining an observed percentage of success and determining a customized content action steps.
20. The computer readable medium of claim 16 , wherein the content action comprises at least one of a tactic, a strategy, a seminar, a button, a product presentation or demonstration, a product catalog, product pricing, information about a product, a social media piece, and a set of frequently asked questions.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/762,012 US20100268731A1 (en) | 2009-04-16 | 2010-04-16 | Touchpoint customization system |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16989209P | 2009-04-16 | 2009-04-16 | |
US12/762,012 US20100268731A1 (en) | 2009-04-16 | 2010-04-16 | Touchpoint customization system |
Publications (1)
Publication Number | Publication Date |
---|---|
US20100268731A1 true US20100268731A1 (en) | 2010-10-21 |
Family
ID=42973475
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/761,799 Active 2031-12-15 US9449326B2 (en) | 2009-04-16 | 2010-04-16 | Web site accelerator |
US12/762,012 Abandoned US20100268731A1 (en) | 2009-04-16 | 2010-04-16 | Touchpoint customization system |
US13/264,480 Abandoned US20120030009A1 (en) | 2009-04-16 | 2010-04-16 | Digital creative interaction system |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/761,799 Active 2031-12-15 US9449326B2 (en) | 2009-04-16 | 2010-04-16 | Web site accelerator |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/264,480 Abandoned US20120030009A1 (en) | 2009-04-16 | 2010-04-16 | Digital creative interaction system |
Country Status (8)
Country | Link |
---|---|
US (3) | US9449326B2 (en) |
EP (2) | EP2242016A1 (en) |
JP (3) | JP2010250827A (en) |
KR (2) | KR101233859B1 (en) |
CN (2) | CN101937545B (en) |
AU (2) | AU2010201495B2 (en) |
CA (3) | CA2700030C (en) |
WO (1) | WO2010121132A1 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8195799B1 (en) | 2011-10-26 | 2012-06-05 | SHTC Holdings LLC | Smart test article optimizer |
WO2018213325A1 (en) * | 2017-05-19 | 2018-11-22 | Liveramp, Inc. | Distributed node cluster for establishing a digital touchpoint across multiple devices on a digital communications network |
US10462156B2 (en) * | 2014-09-24 | 2019-10-29 | Mcafee, Llc | Determining a reputation of data using a data visa |
Families Citing this family (28)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DK3056568T3 (en) | 2006-03-31 | 2021-11-01 | Chugai Pharmaceutical Co Ltd | PROCEDURES FOR CONTROL OF THE BLOOD PHARMACOKINETICS OF ANTIBODIES |
JP5334319B2 (en) | 2007-09-26 | 2013-11-06 | 中外製薬株式会社 | Method for modifying isoelectric point of antibody by amino acid substitution of CDR |
US8495171B1 (en) | 2012-05-29 | 2013-07-23 | Limelight Networks, Inc. | Indiscriminate virtual containers for prioritized content-object distribution |
US9058402B2 (en) | 2012-05-29 | 2015-06-16 | Limelight Networks, Inc. | Chronological-progression access prioritization |
US8321533B2 (en) | 2009-08-03 | 2012-11-27 | Limelight Networks, Inc. | Systems and methods thereto for acceleration of web pages access using next page optimization, caching and pre-fetching techniques |
US8346784B1 (en) | 2012-05-29 | 2013-01-01 | Limelight Networks, Inc. | Java script reductor |
TWI667346B (en) | 2010-03-30 | 2019-08-01 | 中外製藥股份有限公司 | Antibodies with modified affinity to fcrn that promote antigen clearance |
CN102404281B (en) * | 2010-09-09 | 2014-08-13 | 北京神州绿盟信息安全科技股份有限公司 | Website scanning device and method |
SG10201509790YA (en) | 2010-11-30 | 2015-12-30 | Chugai Pharmaceutical Co Ltd | Antigen-Binding Molecule Capable Of Binding To Plurality Of Antigen Molecules Repeatedly |
MX352889B (en) | 2011-02-25 | 2017-12-13 | Chugai Pharmaceutical Co Ltd | Fcîriib-specific fc antibody. |
AU2012233313C1 (en) | 2011-03-30 | 2017-08-03 | Chugai Seiyaku Kabushiki Kaisha | Method for altering plasma retention and immunogenicity of antigen-binding molecule |
CN102769634B (en) * | 2011-05-03 | 2016-08-17 | 腾讯科技(北京)有限公司 | A kind of web online information management method and system |
US9098600B2 (en) | 2011-09-14 | 2015-08-04 | International Business Machines Corporation | Deriving dynamic consumer defined product attributes from input queries |
EP3939996A1 (en) | 2011-09-30 | 2022-01-19 | Chugai Seiyaku Kabushiki Kaisha | Antigen-binding molecule promoting disappearance of antigens having plurality of biological activities |
TW201326209A (en) | 2011-09-30 | 2013-07-01 | Chugai Pharmaceutical Co Ltd | Therapeutic antigen-binding molecule with a FcRn-binding domain that promotes antigen clearance |
SG10201609301QA (en) | 2011-11-30 | 2016-12-29 | Chugai Pharmaceutical Co Ltd | Drug containing carrier into cell for forming immune complex |
US9372836B2 (en) | 2012-03-30 | 2016-06-21 | Qualcomm Incorporated | HTML5 I-frame extension |
JP6501521B2 (en) | 2012-08-24 | 2019-04-17 | 中外製薬株式会社 | FcγRIIb-specific Fc region variant |
US9361393B2 (en) * | 2013-03-15 | 2016-06-07 | Paypal, Inc. | User interface overlay application |
US20140280677A1 (en) * | 2013-03-15 | 2014-09-18 | Limelight Networks, Inc. | Two-file preloading for browser-based web acceleration |
AU2014250434B2 (en) | 2013-04-02 | 2019-08-08 | Chugai Seiyaku Kabushiki Kaisha | Fc region variant |
CN103164268B (en) | 2013-04-02 | 2016-04-20 | 北京奇虎科技有限公司 | System optimization method and device |
US9015348B2 (en) | 2013-07-19 | 2015-04-21 | Limelight Networks, Inc. | Dynamically selecting between acceleration techniques based on content request attributes |
US10990924B2 (en) * | 2013-08-30 | 2021-04-27 | Messagepoint Inc. | System and method for variant content management |
CA2863748C (en) | 2013-09-19 | 2023-06-27 | Prinova, Inc. | System and method for variant content navigation |
CN105094755A (en) * | 2014-04-25 | 2015-11-25 | 国际商业机器公司 | Method and apparatus used for presenting web elements in web page |
WO2016040494A1 (en) * | 2014-09-09 | 2016-03-17 | Liveperson, Inc. | Dynamic code management |
US10922713B2 (en) * | 2017-01-03 | 2021-02-16 | Facebook, Inc. | Dynamic creative optimization rule engine for effective content delivery |
Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020199190A1 (en) * | 2001-02-02 | 2002-12-26 | Opentv | Method and apparatus for reformatting of content for display on interactive television |
US20030149623A1 (en) * | 2002-02-06 | 2003-08-07 | Chen Timothy Tianyi | Method and apparatus for targeted marketing |
US6615247B1 (en) * | 1999-07-01 | 2003-09-02 | Micron Technology, Inc. | System and method for customizing requested web page based on information such as previous location visited by customer and search term used by customer |
US20080005098A1 (en) * | 2006-06-30 | 2008-01-03 | Holt Alexander W | System for using business value of performance metrics to adaptively select web content |
US20080046267A1 (en) * | 2006-07-28 | 2008-02-21 | Nick Romano | System and method for customer touchpoint management |
US20090106100A1 (en) * | 2005-04-26 | 2009-04-23 | Governing Dynamics Llc | Method of digital good placement in a dynamic, real time environment |
US7617122B2 (en) * | 2002-08-28 | 2009-11-10 | International Business Machines Corporation | Targeted online marketing |
US8170912B2 (en) * | 2003-11-25 | 2012-05-01 | Carhamm Ltd., Llc | Database structure and front end |
US8352499B2 (en) * | 2003-06-02 | 2013-01-08 | Google Inc. | Serving advertisements using user request information and user information |
Family Cites Families (95)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6029195A (en) * | 1994-11-29 | 2000-02-22 | Herz; Frederick S. M. | System for customized electronic identification of desirable objects |
US5758257A (en) * | 1994-11-29 | 1998-05-26 | Herz; Frederick | System and method for scheduling broadcast of and access to video programs and other data using customer profiles |
US5704017A (en) * | 1996-02-16 | 1997-12-30 | Microsoft Corporation | Collaborative filtering utilizing a belief network |
US5790426A (en) * | 1996-04-30 | 1998-08-04 | Athenium L.L.C. | Automated collaborative filtering system |
US6014638A (en) * | 1996-05-29 | 2000-01-11 | America Online, Inc. | System for customizing computer displays in accordance with user preferences |
US6236978B1 (en) | 1997-11-14 | 2001-05-22 | New York University | System and method for dynamic profiling of users in one-to-one applications |
US6338067B1 (en) * | 1998-09-01 | 2002-01-08 | Sector Data, Llc. | Product/service hierarchy database for market competition and investment analysis |
US6266649B1 (en) * | 1998-09-18 | 2001-07-24 | Amazon.Com, Inc. | Collaborative recommendations using item-to-item similarity mappings |
US6448980B1 (en) * | 1998-10-09 | 2002-09-10 | International Business Machines Corporation | Personalizing rich media presentations based on user response to the presentation |
JP3389948B2 (en) * | 1998-11-27 | 2003-03-24 | 日本電気株式会社 | Display ad selection system |
WO2000058878A2 (en) * | 1999-03-26 | 2000-10-05 | Koninklijke Philips Electronics N.V. | Evolving advertisements via an evolutionary algorithm |
US6907566B1 (en) | 1999-04-02 | 2005-06-14 | Overture Services, Inc. | Method and system for optimum placement of advertisements on a webpage |
US7925610B2 (en) | 1999-09-22 | 2011-04-12 | Google Inc. | Determining a meaning of a knowledge item using document-based information |
JP2003511798A (en) * | 1999-10-08 | 2003-03-25 | モトローラ・インコーポレイテッド | Remotely configurable multimedia entertainment and information system with real-time auction of advertising space |
US20020054089A1 (en) * | 2000-03-14 | 2002-05-09 | Nicholas Donald L. | Method of selecting content for a user |
JP3597104B2 (en) * | 2000-03-14 | 2004-12-02 | 九州日本電気ソフトウェア株式会社 | Electronic catalog automatic collection system |
JP4443719B2 (en) * | 2000-03-31 | 2010-03-31 | 株式会社プラザクリエイト | Advertisement information provision system |
JP4620830B2 (en) * | 2000-04-26 | 2011-01-26 | 株式会社 ボルテージ | Advertisement delivery decision method and delivery optimization system |
JP2001351014A (en) * | 2000-06-06 | 2001-12-21 | Valueflash Japan Inc | Method for distributing information on communication network, method for linking information from server to user on communication network, and multimedia medium |
JP4522543B2 (en) * | 2000-06-15 | 2010-08-11 | 株式会社 ボルテージ | Ad delivery management server |
WO2002007054A2 (en) | 2000-07-18 | 2002-01-24 | Yahoo Inc. | System and method for selecting alternative advertising inventory in place of sold out advertising inventory |
US7346858B1 (en) * | 2000-07-24 | 2008-03-18 | The Hive Group | Computer hierarchical display of multiple data characteristics |
EP1323053A4 (en) * | 2000-08-07 | 2006-08-16 | Active Data Exchange | Syndication methodology to dynamically place digital assets on non-related web sites |
US6895406B2 (en) * | 2000-08-25 | 2005-05-17 | Seaseer R&D, Llc | Dynamic personalization method of creating personalized user profiles for searching a database of information |
US6477575B1 (en) * | 2000-09-12 | 2002-11-05 | Capital One Financial Corporation | System and method for performing dynamic Web marketing and advertising |
US20020112035A1 (en) * | 2000-10-30 | 2002-08-15 | Carey Brian M. | System and method for performing content experience management |
US7313622B2 (en) * | 2000-11-08 | 2007-12-25 | [X+1] Solutions, Inc. | Online system and method for dynamic segmentation and content presentation |
US6718315B1 (en) * | 2000-12-18 | 2004-04-06 | Microsoft Corporation | System and method for approximating probabilities using a decision tree |
US6944679B2 (en) * | 2000-12-22 | 2005-09-13 | Microsoft Corp. | Context-aware systems and methods, location-aware systems and methods, context-aware vehicles and methods of operating the same, and location-aware vehicles and methods of operating the same |
US20020111852A1 (en) * | 2001-01-16 | 2002-08-15 | Levine Robyn R. | Business offering content delivery |
US7343317B2 (en) | 2001-01-18 | 2008-03-11 | Nokia Corporation | Real-time wireless e-coupon (promotion) definition based on available segment |
US20020138331A1 (en) * | 2001-02-05 | 2002-09-26 | Hosea Devin F. | Method and system for web page personalization |
US20020133392A1 (en) * | 2001-02-22 | 2002-09-19 | Angel Mark A. | Distributed customer relationship management systems and methods |
US7735013B2 (en) * | 2001-03-16 | 2010-06-08 | International Business Machines Corporation | Method and apparatus for tailoring content of information delivered over the internet |
US20020173971A1 (en) * | 2001-03-28 | 2002-11-21 | Stirpe Paul Alan | System, method and application of ontology driven inferencing-based personalization systems |
US20030154180A1 (en) * | 2002-02-13 | 2003-08-14 | Case Simon J. | Profile management system |
US6757678B2 (en) * | 2001-04-12 | 2004-06-29 | International Business Machines Corporation | Generalized method and system of merging and pruning of data trees |
US20030217333A1 (en) | 2001-04-16 | 2003-11-20 | Greg Smith | System and method for rules-based web scenarios and campaigns |
JP2004533047A (en) | 2001-04-16 | 2004-10-28 | ビーイーエイ システムズ, インコーポレイテッド | Web-based personalization and e-commerce management system and method |
DE10154656A1 (en) * | 2001-05-10 | 2002-11-21 | Ibm | Computer based method for suggesting articles to individual users grouped with other similar users for marketing and sales persons with user groups determined using dynamically calculated similarity factors |
JP2002366569A (en) | 2001-06-06 | 2002-12-20 | Sony Corp | System and method for selecting advertisement, and storage medium |
US20050193335A1 (en) * | 2001-06-22 | 2005-09-01 | International Business Machines Corporation | Method and system for personalized content conditioning |
JP2003122787A (en) * | 2001-10-12 | 2003-04-25 | Nippon Television Network Corp | System and method for optimizing advertisement distribution |
JP2003132086A (en) * | 2001-10-26 | 2003-05-09 | Megafusion Corp | Web page dynamic generation system |
US20030090513A1 (en) * | 2001-11-09 | 2003-05-15 | Narendran Ramakrishnan | Information personalization by partial evaluation |
US6954901B1 (en) * | 2001-12-13 | 2005-10-11 | Oracle International Corporation | Method and system for tracking a user flow of web pages of a web site to enable efficient updating of the hyperlinks of the web site |
US20030128236A1 (en) * | 2002-01-10 | 2003-07-10 | Chen Meng Chang | Method and system for a self-adaptive personal view agent |
JP2003216608A (en) * | 2002-01-23 | 2003-07-31 | Sony Corp | Information collecting/analyzing method and system |
JP2003256707A (en) * | 2002-03-06 | 2003-09-12 | Mitsubishi Electric Corp | Marketing center device for mobile marketing system |
US9235849B2 (en) | 2003-12-31 | 2016-01-12 | Google Inc. | Generating user information for use in targeted advertising |
US20030208399A1 (en) * | 2002-05-03 | 2003-11-06 | Jayanta Basak | Personalized product recommendation |
US20030212619A1 (en) | 2002-05-10 | 2003-11-13 | Vivek Jain | Targeting customers |
US7321887B2 (en) * | 2002-09-30 | 2008-01-22 | Sap Aktiengesellschaft | Enriching information streams with contextual content |
WO2003107321A1 (en) * | 2002-06-12 | 2003-12-24 | Jena Jordahl | Data storage, retrieval, manipulation and display tools enabling multiple hierarchical points of view |
JP4408635B2 (en) * | 2002-06-27 | 2010-02-03 | ナヴィゲイション テクノロジーズ コーポレイション | How to provide location-based advertising along with route information |
JP2004062446A (en) * | 2002-07-26 | 2004-02-26 | Ibm Japan Ltd | Information gathering system, application server, information gathering method, and program |
JP2004070504A (en) | 2002-08-02 | 2004-03-04 | Hewlett Packard Co <Hp> | Information retrieval method and system based on personal profile information |
CN1485775A (en) * | 2002-09-27 | 2004-03-31 | 英业达股份有限公司 | Display processing system and method for node data of tree structure |
US7349890B1 (en) * | 2002-11-27 | 2008-03-25 | Vignette Corporation | System and method for dynamically applying content management rules |
US7729946B2 (en) * | 2003-01-24 | 2010-06-01 | Massive Incorporated | Online game advertising system |
US20040167796A1 (en) | 2003-02-21 | 2004-08-26 | Arteis, Inc. | Systems and methods for network-based design review |
US7792828B2 (en) * | 2003-06-25 | 2010-09-07 | Jericho Systems Corporation | Method and system for selecting content items to be presented to a viewer |
JP4825669B2 (en) * | 2003-07-30 | 2011-11-30 | グーグル・インク | Method and system for determining the meaning of a document and matching the document with the content |
CN101253524A (en) * | 2004-05-18 | 2008-08-27 | 艾德沃泰兴.Com公司 | Systems and methods of achieving optimal advertising |
JP2006011676A (en) | 2004-06-24 | 2006-01-12 | Kido Insatsusho:Kk | Electronic advertisement distribution system |
JP4880962B2 (en) * | 2004-09-27 | 2012-02-22 | ヤフー株式会社 | Advertisement content distribution ratio calculation program, advertisement content distribution ratio calculation method, advertisement content distribution ratio calculation system, content distribution control system, advertisement content distribution control system, advertisement content distribution control method, and advertisement content distribution control program |
US20060095377A1 (en) | 2004-10-29 | 2006-05-04 | Young Jill D | Method and apparatus for scraping information from a website |
US7249708B2 (en) * | 2005-02-04 | 2007-07-31 | The Procter & Gamble Company | Household management systems and methods |
KR20060100785A (en) * | 2005-03-18 | 2006-09-21 | 구성진 | System and method for providing web site |
WO2006103392A1 (en) * | 2005-03-29 | 2006-10-05 | British Telecommunications Public Limited Company | Content adaptation |
US20060224447A1 (en) | 2005-03-31 | 2006-10-05 | Ross Koningstein | Automated offer management using audience segment information |
US20060282283A1 (en) | 2005-06-13 | 2006-12-14 | Monahan Brian F | Media network |
US20080109306A1 (en) | 2005-06-15 | 2008-05-08 | Maigret Robert J | Media marketplaces |
US20060294084A1 (en) * | 2005-06-28 | 2006-12-28 | Patel Jayendu S | Methods and apparatus for a statistical system for targeting advertisements |
US20070027760A1 (en) | 2005-07-29 | 2007-02-01 | Collins Robert J | System and method for creating and providing a user interface for displaying advertiser defined groups of advertisement campaign information |
US9558498B2 (en) * | 2005-07-29 | 2017-01-31 | Excalibur Ip, Llc | System and method for advertisement management |
US7809731B2 (en) * | 2005-07-29 | 2010-10-05 | Yahoo! Inc. | System and method for reordering a result set copyright notice |
US20070061195A1 (en) * | 2005-09-13 | 2007-03-15 | Yahoo! Inc. | Framework for selecting and delivering advertisements over a network based on combined short-term and long-term user behavioral interests |
US9432468B2 (en) * | 2005-09-14 | 2016-08-30 | Liveperson, Inc. | System and method for design and dynamic generation of a web page |
EP1969461A1 (en) * | 2005-12-29 | 2008-09-17 | Gemplus | System and method for deploying customised web applications |
US7814116B2 (en) * | 2006-03-16 | 2010-10-12 | Hauser Eduardo A | Method and system for creating customized news digests |
JP4875911B2 (en) * | 2006-03-20 | 2012-02-15 | ニフティ株式会社 | Content identification method and apparatus |
US20070265905A1 (en) * | 2006-05-10 | 2007-11-15 | Microsoft Corporation | Agent for discovering relevant content |
JP4163725B2 (en) * | 2006-06-07 | 2008-10-08 | 裕一 磯邉 | Information search apparatus, information search method, information search program, and recording medium recording the program |
CN101071424B (en) | 2006-06-23 | 2010-08-25 | 腾讯科技(深圳)有限公司 | Personalized information push system and method |
CN100456298C (en) * | 2006-07-12 | 2009-01-28 | 百度在线网络技术(北京)有限公司 | Advertisement information retrieval system and method therefor |
JP2008094045A (en) | 2006-10-16 | 2008-04-24 | Ricoh Co Ltd | Image formation apparatus, server, and program |
US20080103795A1 (en) * | 2006-10-25 | 2008-05-01 | Microsoft Corporation | Lightweight and heavyweight interfaces to federated advertising marketplace |
US9715543B2 (en) * | 2007-02-28 | 2017-07-25 | Aol Inc. | Personalization techniques using image clouds |
JP2008225791A (en) * | 2007-03-12 | 2008-09-25 | Nomura Research Institute Ltd | Content distribution system |
US7941740B2 (en) * | 2007-07-10 | 2011-05-10 | Yahoo! Inc. | Automatically fetching web content with user assistance |
US8332258B1 (en) | 2007-08-03 | 2012-12-11 | At&T Mobility Ii Llc | Business to business dynamic pricing system |
US8392246B2 (en) | 2007-08-30 | 2013-03-05 | Google Inc. | Advertiser ad review |
US20090163183A1 (en) | 2007-10-04 | 2009-06-25 | O'donoghue Hugh | Recommendation generation systems, apparatus and methods |
US8850362B1 (en) * | 2007-11-30 | 2014-09-30 | Amazon Technologies, Inc. | Multi-layered hierarchical browsing |
-
2010
- 2010-04-15 AU AU2010201495A patent/AU2010201495B2/en active Active
- 2010-04-15 CA CA2700030A patent/CA2700030C/en active Active
- 2010-04-15 JP JP2010094513A patent/JP2010250827A/en active Pending
- 2010-04-16 WO PCT/US2010/031395 patent/WO2010121132A1/en active Application Filing
- 2010-04-16 KR KR1020100035557A patent/KR101233859B1/en active IP Right Grant
- 2010-04-16 CA CA2700775A patent/CA2700775C/en active Active
- 2010-04-16 CN CN201010203255.XA patent/CN101937545B/en active Active
- 2010-04-16 AU AU2010201518A patent/AU2010201518B2/en active Active
- 2010-04-16 JP JP2010094741A patent/JP5460437B2/en active Active
- 2010-04-16 EP EP10004090A patent/EP2242016A1/en not_active Ceased
- 2010-04-16 EP EP10004091A patent/EP2242017A1/en not_active Ceased
- 2010-04-16 US US12/761,799 patent/US9449326B2/en active Active
- 2010-04-16 CN CN201010195983.0A patent/CN101937446B/en active Active
- 2010-04-16 US US12/762,012 patent/US20100268731A1/en not_active Abandoned
- 2010-04-16 CA CA2758805A patent/CA2758805A1/en not_active Abandoned
- 2010-04-16 KR KR1020100035561A patent/KR101324909B1/en active IP Right Grant
- 2010-04-16 US US13/264,480 patent/US20120030009A1/en not_active Abandoned
-
2014
- 2014-07-31 JP JP2014157162A patent/JP5961666B2/en active Active
Patent Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6615247B1 (en) * | 1999-07-01 | 2003-09-02 | Micron Technology, Inc. | System and method for customizing requested web page based on information such as previous location visited by customer and search term used by customer |
US20020199190A1 (en) * | 2001-02-02 | 2002-12-26 | Opentv | Method and apparatus for reformatting of content for display on interactive television |
US20030149623A1 (en) * | 2002-02-06 | 2003-08-07 | Chen Timothy Tianyi | Method and apparatus for targeted marketing |
US7617122B2 (en) * | 2002-08-28 | 2009-11-10 | International Business Machines Corporation | Targeted online marketing |
US8352499B2 (en) * | 2003-06-02 | 2013-01-08 | Google Inc. | Serving advertisements using user request information and user information |
US8170912B2 (en) * | 2003-11-25 | 2012-05-01 | Carhamm Ltd., Llc | Database structure and front end |
US20090106100A1 (en) * | 2005-04-26 | 2009-04-23 | Governing Dynamics Llc | Method of digital good placement in a dynamic, real time environment |
US20080005098A1 (en) * | 2006-06-30 | 2008-01-03 | Holt Alexander W | System for using business value of performance metrics to adaptively select web content |
US20080046267A1 (en) * | 2006-07-28 | 2008-02-21 | Nick Romano | System and method for customer touchpoint management |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8195799B1 (en) | 2011-10-26 | 2012-06-05 | SHTC Holdings LLC | Smart test article optimizer |
US10462156B2 (en) * | 2014-09-24 | 2019-10-29 | Mcafee, Llc | Determining a reputation of data using a data visa |
US11627145B2 (en) * | 2014-09-24 | 2023-04-11 | Mcafee, Llc | Determining a reputation of data using a data visa including information indicating a reputation |
WO2018213325A1 (en) * | 2017-05-19 | 2018-11-22 | Liveramp, Inc. | Distributed node cluster for establishing a digital touchpoint across multiple devices on a digital communications network |
Also Published As
Publication number | Publication date |
---|---|
US9449326B2 (en) | 2016-09-20 |
JP5460437B2 (en) | 2014-04-02 |
CA2700030A1 (en) | 2010-10-16 |
AU2010236248A1 (en) | 2011-11-03 |
CA2758805A1 (en) | 2010-10-21 |
EP2242016A1 (en) | 2010-10-20 |
CN101937446A (en) | 2011-01-05 |
CN101937446B (en) | 2015-07-15 |
CN101937545B (en) | 2016-01-20 |
KR101324909B1 (en) | 2013-11-04 |
KR20100114860A (en) | 2010-10-26 |
JP2010250830A (en) | 2010-11-04 |
AU2010201518A1 (en) | 2010-11-04 |
US20120030009A1 (en) | 2012-02-02 |
CN101937545A (en) | 2011-01-05 |
AU2010201518B2 (en) | 2012-08-16 |
JP2014199684A (en) | 2014-10-23 |
WO2010121132A1 (en) | 2010-10-21 |
JP2010250827A (en) | 2010-11-04 |
AU2010201495A1 (en) | 2010-11-04 |
JP5961666B2 (en) | 2016-08-02 |
CA2700775A1 (en) | 2010-10-16 |
KR20100114859A (en) | 2010-10-26 |
KR101233859B1 (en) | 2013-02-15 |
US20100269050A1 (en) | 2010-10-21 |
AU2010201495B2 (en) | 2012-04-12 |
EP2242017A1 (en) | 2010-10-20 |
CA2700030C (en) | 2019-11-05 |
CA2700775C (en) | 2016-10-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA2700030C (en) | Touchpoint customization system | |
US20200090230A1 (en) | Systems and methods for suggesting creative types for online content items to an advertiser | |
US8538811B2 (en) | Method and apparatus for social network marketing with advocate referral | |
US8554623B2 (en) | Method and apparatus for social network marketing with consumer referral | |
US8560390B2 (en) | Method and apparatus for social network marketing with brand referral | |
US8655730B1 (en) | Selecting advertisements based on advertising revenue model | |
US8983859B2 (en) | User centric real-time advertisement bidding | |
CA2855205C (en) | Advertisements with multiple targeting criteria bids | |
US8725559B1 (en) | Attribute based advertisement categorization | |
US20110307323A1 (en) | Content items for mobile applications | |
Yuan et al. | Sequential selection of correlated ads by pomdps | |
US20100100417A1 (en) | Commercial incentive presentation system and method | |
US20090259540A1 (en) | System for partitioning and pruning of advertisements | |
US20220237664A1 (en) | Personalized mobile application re-engagement | |
US9508087B1 (en) | Identifying similar display items for potential placement of content items therein | |
De Reyck et al. | Vungle Inc. improves monetization using big data analytics | |
US20150213467A1 (en) | Metadata rich tag for survey re-targeting | |
CN117455574A (en) | Information promotion method, apparatus, device, storage medium, and computer program product | |
CN110675178A (en) | Crowd orientation method, device, equipment and storage medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: ACCENTURE GLOBAL SERVICES GMBH, SWITZERLAND Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ROYTMAN, ANATOLY;SYMONS, MATTHEW;SIGNING DATES FROM 20100414 TO 20100415;REEL/FRAME:024247/0565 |
|
AS | Assignment |
Owner name: ACCENTURE GLOBAL SERVICES LIMITED, IRELAND Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ACCENTURE GLOBAL SERVICES GMBH;REEL/FRAME:025700/0287 Effective date: 20100901 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |