US20180300423A1
2018-10-18
16/015,273
2018-06-22
Certain exemplary embodiments can provide a method comprising automatically rendering a message to a webpage user, the message created by a webpage operator via an automatic merger of a customized message content that corresponds to a message-generator-selected message identifier with a message template that corresponds to a message-generator-selected message template identifier, the message-generator-selected message identifier and the message-generator-selected message template identifier provided by the message generator to the webpage operator responsive to receipt of data gathered from the webpage user by the webpage operator.
Get notified when new applications in this technology area are published.
G06Q30/0253 » CPC further
Commerce, e.g. shopping or e-commerce; Marketing, e.g. market research and analysis, surveying, promotions, advertising, buyer profiling, customer management or rewards; Price estimation or determination; Advertisement; Targeted advertisement During e-commerce, i.e. online transactions
G06Q30/0251 » CPC further
Commerce, e.g. shopping or e-commerce; Marketing, e.g. market research and analysis, surveying, promotions, advertising, buyer profiling, customer management or rewards; Price estimation or determination; Advertisement Targeted advertisement
G06Q30/02 IPC
Commerce, e.g. shopping or e-commerce Marketing, e.g. market research and analysis, surveying, promotions, advertising, buyer profiling, customer management or rewards; Price estimation or determination
A wide variety of potential practical and useful embodiments will be more readily understood through the following detailed description of certain exemplary embodiments, with reference to the accompanying exemplary drawings in which:
FIG. 1 is an illustration of an exemplary embodiment of an advertisement;
FIG. 2 is a sequence diagram of an exemplary initial setup method;
FIG. 3 is a sequence diagram of an exemplary runtime method;
FIG. 4 is a block diagram of an exemplary embodiment of system 4000;
FIG. 5 is a block diagram of an exemplary embodiment of an information device 5000; and
FIG. 6 is a flowchart of an exemplary embodiment of a method 6000.
When the following terms are used substantively herein, the accompanying definitions apply. These terms and definitions are presented without prejudice, and, consistent with the application, the right to redefine these terms during the prosecution of this application or any application claiming priority hereto is reserved. For the purpose of interpreting a claim of any patent that claims priority hereto, each definition (or redefined term if an original definition was amended during the prosecution of that patent), functions as a clear and unambiguous disavowal of the subject matter outside of that definition.
Certain exemplary embodiments can provide a method comprising automatically rendering a message to a webpage user, the message created by a webpage operator via an automatic merger of a customized message content that corresponds to a message-generator-selected message identifier with a message template that corresponds to a message-generator-selected message template identifier, the message-generator-selected message identifier and the message-generator-selected message template identifier provided by the message generator to the webpage operator responsive to receipt of data gathered from the webpage user by the webpage operator.
Certain exemplary embodiments can provide a method, herein called “weaving”, that can allow two parties (partner and sponsor) to agree on parameters for Internet-based advertisements without agreeing on specifics about each advertisement that appears on the partner's web site (which could number in the thousands). Weaving can allow each party to control specific parameters about the advertisement that matter most to them.
Via certain exemplary embodiments, the partner can pre-approve all advertising content by placing the content in a special location on the partner's web server. When a partner's web page is viewed on the Internet, the sponsor can supply the customer-matched advertisement based on a proprietary algorithm, but instead of sending the partner the advertisement containing content, the sponsor can send a reference to the customer-matched template and the customer-matched message to use for each product advertised on the partner's web site. As the page is rendered dynamically in the partner's web server, the actual content for the advertisement can be chosen from the pre-approved content on the partner's web site.
Via certain exemplary embodiments, the partner can pre-approve the specific advertisement message text elements that might appear to their customers and the advertisement's location on the web page. This can be important because partners can be extremely reluctant to delegate control to an outside party (sponsor) over the content (and possibly design) of advertisements on the partner's web site. Partners can spend lots of resources ensuring their customers get a consistent message and the customer's experience on the partner's web site is pleasant. Allowing an outside party to control critical pieces like the advertising message content (and possibly design) (including the ability to make changes without the partner's approval) can be viewed as risky because it can give up too much control of the customer's experience to an outside party.
Written from the perspective of the partner, weaving can help answer the question: “how do we delegate the appropriate permissions to an outside party (sponsor) to generate the “customer matched” advertisement based on their expertise while ensuring we retain full control over the advertisement messages and placement presented to our customers?”
Via certain exemplary embodiments, the sponsor can control a proprietary algorithm that can create a “customer matched” advertisement based on input parameters from the partner's customer, and/or which message template and/or message tag the partner uses when rendering a specific advertisement. The sponsor can spend lots of resources researching, testing, and/or refining the set of product and message text combinations that have a substantial and/or the greatest chance for generating a sale for the sponsor. As experts in this area, they often want to ensure that each opportunity with a customer is maximized, thus they often want to determine the optimal selection of products and message presented to the customer in order to maximize sales.
Written from the perspective of the sponsor, weaving can help answer: “how do we dynamically create a customer matched advertisement for our partners and their customers that yields strong and/or the most sales (based on our expertise with what products and messages work well and/or the best) while allowing our partners to pre-approve the content elements (and possibly design) of the advertisement on their web page?”
The weaving process can strike a balance between these competing needs such that both parties can be ensured that a customer-matched advertisement appears to the partner's customers in language approved by the partner.
Via certain exemplary embodiments, the partner can create an advertisement from pre-approved component parts. This can guarantee that the partner has pre-approved all textual content (from messages) and potentially all design (e.g., layout, fonts, look and feel, etc. (from message templates)). Through a business process, the sponsor and partner can agree in advance which messages and templates are acceptable. The sponsor and partner can collaboratively introduce new messages and/or new message templates at any time, without requiring any change in the software technology in use by either the partner or sponsor. This can avoid either sponsor or partner having to wait for development resources when new and/or revised message text and/or messages templates are desired. Certain exemplary embodiments can utilize an information exchange tool that is stable, open source, and/or standard, such as XSLT.
What follows describes the logic of exemplary XSLT code of an exemplary message template, which specifies how to process the information in an exemplary Quote Pack, and that emits (outputs) HTML text designed to become part of an exemplary web page.
The XSLT code can contain rules that, when run against an XML document, result in a piece of HTML text designed to become part of the web page. The original XML is typically unchanged, and the HTML is typically generated (“printed”) as output from the XSLT transformation, although results of the transformation can be provided in any graphics language, print language, video language, and/or any other media language that can be rendered via webpage, graphic, print, video, and/or any other media.
The XSLT rules can use pattern matching. That is, they can look for specific sections of the source XML document, those sections marked by start and end tags, and print the output HTML based on the contents of those marked sections.
The following describes how this transformation can work on an exemplary Quote Pack.
| Initial Rule: Find an element in the quote pack marked “HeavyQuotePackData” |
| (this section will have a start tag of <HeavyQuotePackData> and an end tag | |
| of </HeavyQuotePackData>) |
| Print starting div tag (<div>; div is short for division and is used to |
| organize sections of HTML) |
| Run all other rules against any element marked |
| “TemplateMessageList” |
| (this section will have a start tag of <TemplateMessageList> and an |
| end tag of </Template MessageList>) |
| Run all other rules against any element marked “HeavyQuotes” | |
| (this section will have a start tag of <HeavyQuotes> and an end tag of |
| </HeavyQuotes>) |
| Run all other rules against any element marked |
| “TemplateMessageList/HeavierMessageData” |
| (this indicates a section marked HeavierMessageData that is inside of |
| a section marked TemplateMessageList) |
| Print ending div tag (</div>) |
| Rule: Find an element in the quote pack marked “TemplateMessageList” |
| (this section will have a start tag of <TemplateMessageList> and an end tag | |
| of </TemplateMessageList>) |
| For each contained element marked “HeavierMessageData” | |
| (this section will have a start tag of <HeavierMessageData> and an |
| end tag of </HeavierMessageData>) |
| If this element's “tag” has a value of “HEADER” |
| Print starting header tag (<h2>) |
| Print the value of the “Text” element | |
| Print ending header tag (</h2>) | |
| Print line break tag (<br/>) |
| Print starting paragraph tag (<p>) |
| For each element marked “HeavierMessageData” |
| If this element's “tag” has a value of “INTRO” | |
| If this element has a non-empty “Url” element |
| Print an anchor tag with a link to that URL with the element's Text |
| value as the hypertext (“clickable”) | |
| Otherwise |
| Print starting label tag (<label>) | |
| Print this element's “Text” element | |
| Print ending label tag (</label>) | |
| Print ending paragraph tag (</p>) |
| Rule: Find an element in the quote pack marked “HeavyQuotes” |
| Run all rules against elements marked “HeavyQuoteData” |
| Rule: Find an element in the quote pack marked “HeavyQuoteData” |
| Print starting paragraph tag (<p>) | |
| Print radio button tag with the name attribute set to “RadioGroup” and |
| the id attribute set to the text of the contained element marked “ProductID”. | |
| (<input type=“radio” name=“RadioGroup” id=“text of element marked | |
| ProductID” />) |
| For each element marked “Messages/HeavierMessageData” | |
| (these sections |
| If this element's “Tag” value is “OPTION” |
| If this element has a non-empty “Url” element |
| Print an anchor tag with a link to that URL |
| with the element's Text value as the hypertext (“clickable”) |
| Otherwise |
| Print starting label tag (<label>) | |
| Print this element's “Text” element | |
| Print ending label tag (</label>) | |
| Print ending paragraph tag (</p>) |
| If this element's “Tag” has a value of “PRICE” |
| Print starting strong tag (<strong>; indicates text should be |
| bold) |
| Print the value of the current element's “Text” field | |
| Print ending strong tag (</strong>) | |
| Print ending paragraph tag (</p>) |
| Rule: Find an element in the quote pack marked |
| “TemplateMessageList/HeavierMessageData” |
| If this element's “Tag” has a value of “FOOTER” |
| Print starting paragraph tag (<p>) | |
| Print starting label tag (<label>) | |
| If this element has a non-empty “Url” element |
| Print an anchor tag with a link to that URL with the element's Text |
| value as the hypertext (“clickable”) | |
| Otherwise |
| Print this element's “Text” element | |
| Print ending label tag (</label>) | |
| Print ending paragraph tag (</p>) | |
FIG. 1 illustrates an exemplary embodiment of an advertisement 1000 generated based on a weaving of an exemplary template and exemplary messages that were identified in an exemplary Quote Pack. That is, when the partner runs the XSLT transform against a Quote Pack, the emitted HTML can result in a customer-matched advertisement, such as illustrated in FIG. 1.
Note that the message template can specify attributes such as radio button design, background color, link button to purchase, link to view details, and where to place “HEADER” and “FOOTER” messages, etc. The message template can specify the “look” of the advertisement and how it will appear to the end customer. There can be multiple message templates, each one with a different “look”. Each message template can have a unique identifier.
An exemplary embodiment of the weaving process can start when a partner sends the following exemplary customer-provided information to the sponsor. The exemplary information can come from the partner's customer who has input this data on the partner's web site. The customer's data can be sent to the sponsor in XML format:
| Passenger Name Record Fields | Example Customer Data | |
| Partner | Airlines | |
| Booking Date | Sep. 11, 2007 | |
| Travel Start Date | Dec. 21, 2007 | |
| Travel End Date | Dec. 28, 2007 | |
| Zip Code | 23220 | |
| Home Country | USA | |
| Trip Origination | DCA | |
| Trip Destination | LAX | |
| Number of Passengers | 2 | |
| Purchase Segments | Air | |
| Class of Service | Coach | |
| Cost of Trip by Segment | $1,230 | |
| Customer ID | 983937221833 | |
This data can be received by the sponsor who can run an algorithm to determine products the sponsor desires to offer this customer based on the customer data provided. The sponsor's offer can be returned to the partner in the form of a Quote Pack (table) containing, in this exemplary case, two products (rows):
| Template Indicator | TI-001 | |
| Message Id | Message Tag |
| Offer Pack Messages |
| 400000 | HEADER | |
| 400001 | INTRO | |
| 400002d | INTRO | |
| 400007 | FOOTER |
| Offer Messages for the “Yes” Offer |
| 400003 | OPTION | |
| 400004 | PRICE | |
| 400005d | OPTION |
| Offer Messages for the “No” Offer |
| 400006 | OPTION | |
As described above, during initial setup, the sponsor can provide a suggested configuration of messages for the partner to utilize. The partner can accept the suggested messages (and/or message text) to use and/or can customize desired messages for their customers. The sponsor can provide a message template to use for transforming one or more messages into an advertisement. Depending on how their relationship is negotiated, in some cases, the partner may edit desired message templates, and in other cases, only the sponsor may edit any message template. In any event, the partner can approve these messages and/or templates by uploading them to the partner's web server(s).
During runtime, the partner can send a request via the Internet to the sponsor with data gathered from the customer. The sponsor in near real-time (<2.5 seconds) can determine the customer-matched product for the partner based on a proprietary algorithm. The sponsor can return a response to the partner in the form of a Quote Pack. On the partner's web server, the Quote Pack can be woven together with the identified partner-approved message and message template to create an HTML-coded Internet advertisement for rendering via the partner's web site.
Certain exemplary embodiments can allow the partner to pre-approve the advertisement's message content displayed to their customers while delegating the decision about which product to advertise to the sponsor (who can use their customer match algorithm to determine the product, message, and template for the advertisement). Conversely, the sponsor can control which product is displayed on the partner's web site and can influence (but not completely control) the message content (and/or design of that content) used to market the product to the customer. This can be done by referencing, in the Quote Pack, a specific message ID (and/or message template ID) to use when creating the advertisement. Using this process can allow each party to retain control of information that is important to them while delegating control of the information most important to the other party. It can enable each party to unilaterally make changes to the parts they control without the consent of the other party.
The weaving processes can be considered in two parts: initial setup and runtime. FIG. 2 is a sequence diagram of an exemplary initial setup method 2000, which can be preconditioned on obtaining a signed contract identifying appropriate terms and conditions. FIG. 3 is a sequence diagram of an exemplary runtime method 3000, which can be preconditioned on completing the set-up process and/or integration testing.
FIG. 2 and FIG. 3 show how the parties (sponsor and partner) can collaborate to provide a customer-matched advertisement (one that the sponsor believes will increase the likelihood of a product sale) that appears to the partner's customers in language approved and controlled by the partner.
Certain exemplary embodiments can be used with a product (such as the Travel Insurance 2.0 product from Elvia (a sponsor) of Richmond, Va.), to supply advertisements to the sponsor's customers (e.g., partners) for the sponsor's products. Certain exemplary embodiments can allow the partners to display advertisements to their customers for products provided by the sponsor.
In certain exemplary embodiments, the sponsor can implement the initial setup process by providing the initial message templates and/or messages (which can be customized by the partner) to the partner and ensuring that the sponsor can generate a Quote Pack in response to a request from the partner's web server.
The partner can implement the initial setup process by reviewing and uploading the approved message content and/or templates to their web site and configuring their web servers to send requests to the sponsor's service at the appropriate time during the customer's checkout.
The partner can implement the runtime process by having the industry-standard Extensible Stylesheet Language Transformation (XSLT) technology installed and configured to weave together sponsor-approved message templates and messages provided in Quote Packs with partner-approved content and/or layouts for the advertisements. XSLT can transform the Extensible Markup Language (XML) Quote Packs and message templates into Hypertext Markup Language (HTML) code used to create, provide, transmit, and/or render web pages viewable on the Internet.
In certain exemplary embodiments, a sponsor can create an advertisement (in HTML code) containing text and/or images to advertise their products on the Internet. The sponsor can find a partner who is willing to put this advertisement on the partner's web site during for display during the partner's customer's checkout process in order to cross-sell products from the sponsor to the partner's customer. The sponsor and the partner can enter into a contract whereby the sponsor agrees to deliver a “customer-matched” advertisement to the partner's web server (for viewing on the partner's web site) in exchange for the partner getting a percentage of all revenue originating from customers of the partner who followed the instructions in the advertisement and purchased the sponsor's products.
The sponsor can manually decompose the Internet advertisement into four logical parts:
As shown in FIG. 2 and FIG. 3, the sponsor can design a process for allowing both parties to collaborate on the four parts but ultimately giving the partner control over at least the message content for the advertisement while giving the sponsor control over what products are advertised and potentially the resulting advertisement's design (such as in the form of sponsor-supplied XSLT message templates). To make the process operational, the sponsor can develop components such as:
With this information, the partner can modify the checkout process on their web site to invoke the sponsor's service (URL), passing the desired customer input data (e.g., in XML format, adhering to the XML Schema specification) to the sponsor. Upon receipt of the Quote Pack response back from the sponsor (e.g., in XML format), an industry-standard XSLT engine installed on the partner's web server(s) can utilize the information contained and/or referenced in the Quote Pack to weave the identified local partner-approved message template with the local partner-approved message content to produce an Internet advertisement (e.g., HTML code) for display on the partner's web site.
Once the partner has modified their web site to integrate the sponsor-supplied messages and message templates, the partner can test their updated checkout process to ensure that customer information is sent to the sponsor at the appropriate point and the resulting internet advertisement for the “customer matched” products are displayed.
Once the initial setup process is tested, the partner can roll-out the sponsor-supplied advertisements to their customers and the runtime process (previously described) can be used for the lifetime of the sponsor-partner partnership as defined by terms in the contract between the sponsor and partner.
FIG. 4 is a block diagram of an exemplary embodiment of system 4000, which can comprise a customer information device 4100, 4200, 4300, which can run a web browser 4120 to render a web page 4140 displaying an advertisement 4160, and which can be connected to a network 4400, such as the Internet.
Also connected to network 4400 can be one or more partner information devices 4500, 4600, either of which can run a message processor 4520, 4620 and/or a web page server adapted to generate, transmit, and cause to be rendered advertisement 4140, based on message content 4540, 4640 and/or message templates 4560, 4660 stored and/or referenced in memory device 4580, 4680.
Also connected to network 4400 can be one or more sponsor information devices 4700, 4800, either of which can run customer-matched advertisement selection software 4720, 4820, which can be adapted to evaluate, select, and transmit a message content 4740, 4840 (and/or an identifier thereof) and/or a message template 4760, 4860 (and/or an identifier thereof) stored in memory device 4780, 4780 to one or more partner information device 4500, 4600.
FIG. 5 is a block diagram of an exemplary embodiment of an information device 5000, which in certain operative embodiments can comprise, for example, customer information device 4100, 4200, 4300, partner information device 4500, 4600, and/or sponsor information device 4700, 4800 of FIG. 4. Information device 5000 can comprise any of numerous circuits and/or components, such as for example, one or more network interfaces 5100, one or more processors 5200, one or more memories 5300 containing instructions 5400, one or more input/output (I/O) devices 5500, and/or one or more user interfaces 5600 coupled to I/O device 5500, etc.
In certain exemplary embodiments, via one or more user interfaces 5600, such as a graphical user interface, a user can view a rendering of information related to researching, designing, modeling, creating, developing, building, manufacturing, operating, maintaining, storing, marketing, selling, delivering, selecting, specifying, requesting, ordering, receiving, returning, rating, and/or recommending any of the products, services, methods, and/or information described herein.
FIG. 6 is a flowchart of an exemplary embodiment of a method 6000. At activity 6100, a partner (which can be considered a “webpage operator”) can request, receive, and/or store one or more sponsor-generated: suggested message contents, corresponding message identifiers, message tags, message templates, and/or corresponding message template identifiers, etc. At activity 6200, the partner can modify and store a selected portion of the suggested message contents and/or a selected portion of the message templates. At activity 6300, from a customer visiting the partner's web site, the partner can gather data regarding that customer (which can be considered a “webpage user”) and/or another customer, person, and/or entity. At activity 6400, the partner can provide gathered customer data to the sponsor (which can be considered a “message generator”). At activity 6500, the partner can automatically receive from the sponsor one or more customer-matched message tags, message identifiers, and/or template identifiers, those tags and/or identifiers determined by the sponsor based on the customer data and/or information regarding the partner. At activity 6600, the partner can automatically: look-up the message contents and message template(s) corresponding to the received identifiers, merge the identified message contents into the identified message template(s), potentially according to any received message tags, and/or generate a customer-matched advertisement that is formatted according to the sponsor-determined, partner-approved, and/or partner-modified message template and/or contains the sponsor-determined, partner-approved, and/or partner-modified message contents. At activity 6700, the partner can automatically: post the customer-matched advertisement to the partner's web site, transmit the customer-matched advertisement to the customer's information device, and/or cause the customer's information device and/or browser to render the customer-matched advertisement.
Still other substantially and specifically practical and useful embodiments will become readily apparent to those skilled in this art from reading the above-recited and/or herein-included detailed description and/or drawings of certain exemplary embodiments. It should be understood that numerous variations, modifications, and additional embodiments are possible, and accordingly, all such variations, modifications, and embodiments are to be regarded as being within the scope of this application.
Thus, regardless of the content of any portion (e.g., title, field, background, summary, description, abstract, drawing figure, etc.) of this application, unless clearly specified to the contrary, such as via explicit definition, assertion, or argument, with respect to any claim, whether of this application and/or any claim of any application claiming priority hereto, and whether originally presented or otherwise:
Moreover, when any number or range is described herein, unless clearly stated otherwise, that number or range is approximate. When any range is described herein, unless clearly stated otherwise, that range includes all values therein and all subranges therein. For example, if a range of 1 to 10 is described, that range includes all values therebetween, such as for example, 1.1, 2.5, 3.335, 5, 6.179, 8.9999, etc., and includes all subranges therebetween, such as for example, 1 to 3.65, 2.8 to 8.14, 1.93 to 9, etc.
When any claim element, of this application or any application to claim priority hereto, is followed by a drawing element number, that drawing element number is exemplary and non-limiting on claim scope.
Any information in any material (e.g., a United States patent, United States patent application, book, article, etc.) that has been incorporated by reference herein, is only incorporated by reference to the extent that no conflict exists between such information and the other statements and drawings set forth herein. In the event of such conflict, including a conflict that would render invalid any claim herein or seeking priority hereto, then any such conflicting information in such incorporated by reference material is specifically not incorporated by reference herein.
Accordingly, every portion (e.g., title, field, background, summary, description, abstract, drawing figure, etc.) of this application, other than the claims themselves, is to be regarded as illustrative in nature, and not as restrictive.
1. A method configured to cause an internet-based checkout process of a webpage operator to render, to a webpage user, message content selected by a message generator and customized by the webpage operator, the checkout process configured to sell any of a plurality of products of the webpage operator, the method comprising:
responsive to the webpage user initiating the checkout process; for at least one product from the plurality of products of the webpage operator, automatically providing data obtained from one or more information devices of the webpage user to one or more information devices of the message generator; and
automatically causing an automatically-created message to be rendered to the webpage user during the checkout process via the one or more information devices of the webpage user;
wherein:
the automatically-created message is created by one or more information devices of the webpage operator via an automatic merger of a customized message content that corresponds to a message-generator-selected message identifier with a message template that corresponds to a message-generator-selected message template identifier;
a message tag corresponding to the message-generator-selected message identifier defines where the customized message content appears in the automatically-created message;
the message tag is provided by the message generator; and
the message-generator-selected message identifier and the message-generator-selected message template identifier are automatically provided by one or more information devices of the message generator to the one or more information devices of the webpage operator responsive to receipt of the data obtained from the one or more information devices of the webpage user by the one or more information devices of the webpage operator.
2. The method of claim 1, wherein:
the customized message content is a result of a modification by the one or more information devices of the webpage operator of a selected suggested message content from a plurality of suggested message contents provided to the one or more information devices of the webpage operator by the one or more information devices of the message generator.
3. The method of claim 1, wherein:
the message-generator-selected message template identifier is one of a plurality of message template identifiers provided to the one or more information devices of the webpage operator by the one or more information devices of the message generator.
4. The method of claim 1, wherein:
each of the plurality of message-generator-selected message template identifiers corresponds to a message template provided to the one or more information devices of the webpage operator by the one or more information devices of the message generator.
5. The method of claim 1, wherein:
each of the webpage user, the webpage operator, the message generator, and the fulfillment provider is distinct from one another.
6. The method of claim 1, wherein:
each of the one or more information devices of the webpage user, the one or more information devices of the webpage operator, and the one or more information devices of the message generator physically is distinct from one another.
7. The method of claim 1, further comprising:
responsive to the webpage user following an instruction to initiate a purchase of a product, of a message generator, that is described by the automatically-created message, sending information to a fulfillment provider, the information sufficient to initiate fulfillment of the purchase.
8. The method of claim 1, further comprising:
receiving, by the one or more information devices of the webpage operator, from the one or more information devices of the message generator, a plurality of suggested message contents.
9. The method of claim 1, further comprising:
receiving, by the one or more information devices of the webpage operator, from the one or more information devices of the message generator, a plurality of suggested message contents, each suggested message content from the plurality of suggested message contents having a corresponding message identifier.
10. The method of claim 1, further comprising:
receiving, by the one or more information devices of the webpage operator, from the one or more information devices of the message generator, a plurality of message templates.
11. The method of claim 1, further comprising:
receiving, by the one or more information devices of the webpage operator, from the one or more information devices of the message generator, a plurality of message templates, each message template from the plurality of message templates having a corresponding message template identifier.
12. The method of claim 1, further comprising:
modifying, at the one or more information devices of the webpage operator, a selected suggested message content from a plurality of suggested message contents to form the customized message content.
13. The method of claim 1, further comprising:
obtaining the data from the one or more information devices of the webpage user.
14. The method of claim 1, further comprising:
automatically providing the data to the one or more information devices of the message generator.
15. The method of claim 1, further comprising:
based on the data, automatically requesting, from the one or more information devices of the message generator, the message-generator-selected message identifier and the message-generator-selected message template identifier.
16. The method of claim 1, further comprising:
in accord with the message tag, automatically merging, at the one or more information devices of the webpage operator, the customized message content that corresponds to the message-generator-selected message identifier with the message template that corresponds to the message-generator-selected message template identifier.
17. A non-transitory machine-readable medium comprising machine instructions configured to cause an internet-based checkout process of a webpage operator to render, to a webpage user, message content selected by a message generator and customized by the webpage operator, the checkout process configured to sell any of a plurality of products of the webpage operator, the instructions configured for activities comprising:
responsive to the webpage user initiating the checkout process; for at least one product from the plurality of products of the webpage operator, automatically providing data obtained from one or more information devices of the webpage user to one or more information devices of the message generator; and
automatically causing an automatically-created message to be rendered to the webpage user during the checkout process via the one or more information devices of the webpage user;
wherein:
the automatically-created message is created by one or more information devices of the webpage operator via an automatic merger of a customized message content that corresponds to a message-generator-selected message identifier with a message template that corresponds to a message-generator-selected message template identifier;
a message tag corresponding to the message-generator-selected message identifier defines where the customized message content appears in the automatically-created message;
the message tag is provided by the message generator; and
the message-generator-selected message identifier and the message-generator-selected message template identifier are automatically provided by one or more information devices of the message generator to the one or more information devices of the webpage operator responsive to receipt of the data obtained from the one or more information devices of the webpage user by the one or more information devices of the webpage operator.
18. A system configured to cause an internet-based checkout process of a webpage operator to render, to a webpage user, message content selected by a message generator and customized by the webpage operator, the checkout process configured to sell any of a plurality of products of the webpage operator, the system comprising:
a message processing circuit configured to, responsive to the webpage user initiating the checkout process; for at least one product from the plurality of products of the webpage operator, automatically provide data obtained from one or more information devices of the webpage user to one or more information devices of the message generator; and
a message rendering circuit configured to automatically cause an automatically-created message to be rendered to the webpage user during the checkout process via the one or more information devices of the webpage user;
wherein:
the automatically-created message is created by one or more information devices of the webpage operator via an automatic merger of a customized message content that corresponds to a message-generator-selected message identifier with a message template that corresponds to a message-generator-selected message template identifier;
a message tag corresponding to the message-generator-selected message identifier defines where the customized message content appears in the automatically-created message;
the message tag is provided by the message generator; and
the message-generator-selected message identifier and the message-generator-selected message template identifier are automatically provided by one or more information devices of the message generator to the one or more information devices of the webpage operator responsive to receipt of the data obtained from the one or more information devices of the webpage user by the one or more information devices of the webpage operator.