System and method for creating a consistent personalized web experience across multiple platforms and channels

Abstract

This disclosure relates generally to a system and method for creating unified personalized content for an individual user receiving communications from a given website across separate platforms and channels.

Description

BACKGROUND

This disclosure is particularly directed towards a platform for orchestrating and delivering a one-to-one personalized experience across all channels and platforms by which a user can access Internet content, acting as the connective tissue that creates a consistent experience across all points of a user’s experience with a given party online.

Personalization of content to a user’s preference is an area that is used for a number of purposes. Computer companies, such as FACEBOOK for example, collect data about users and use those data to customize a user’s experience with the platform. In the past, that customization has been fairly limited: certain locations on a webpage can accept advertisements and other embedded images, and data are used to customize those locations on the webpage, or data can be used to target advertisements to a user.

This type of customization is fairly limited, though, and can create differences in a user’s experience. For example, a user could receive emails about certain sales, but upon accessing the website those sales are not prominently displayed. Or, a user might receive a text message about a promotion that is not easily accessible on the webpage. What is needed is a method to personalize Internet content to make it more appealing to the user of the website based on the data collected, while maintaining a uniform experience across a variety of channels or platforms. This can be done by creating a system that draws from the same source for all communication with a user, therefore unifying the experience for the user across all platforms and channels of communication. In addition, in one embodiment, the system can be used to create a pageless experience, creating an individualized landing page for each user accessing the website.

The features and advantages of the disclosure will be set forth in the description that follows, and in part will be apparent from the description, or may be learned by the practice of the disclosure without undue experimentation. The features and advantages of the disclosure may be realized and obtained by means of the instruments and combinations particularly pointed out herein.

SUMMARY OF THE DISCLOSURE

A purpose of the instant disclosure is to create a system that collects information to orchestrate and deliver a personalized experience to a user accessing internet content across all different channels and on all different platforms, acting as connective tissue that creates a consistent experience across all points of a user’s access to the content.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an embodiment of a system and method for creating a consistent personalized web experience across multiple platforms and channels showing the system communicating with a variety of channels in an e-commerce context.

FIG. 2 is a block diagram showing an embodiment of the system showing the access to multiple element webservices to provide a content deliverable to any channel/platform showing a tied experience between onsite content and offsite content.

FIG. 3 shows the construction of the element webservices.

FIG. 4 is a diagram demonstrating the ordering of elements to produce a pageless content deliverable and showing individual use elements and possible pageless experiences.

FIG. 5 is a block diagram showing the layout structure of the system.

FIG. 6 is a block diagram showing the content delivery structure of the system.

FIG. 7 is a block diagram showing the layout and functioning of an embodiment of the system.

DETAILED DESCRIPTION

For the purposes of promoting an understanding of the principles in accordance with this disclosure, reference will now be made to illustrative embodiments of the invention. It will nevertheless be understood that no limitation of the scope of the disclosure is thereby intended. Any alterations and further modifications of the inventive features illustrated herein, and any additional applications of the principles of the disclosure as illustrated herein, which would normally occur to one skilled in the relevant art and having possession of this disclosure, are to be considered within the scope of the disclosure claimed.

Before the devices, systems, processes and methods will be disclosed and described, it is to be understood that this disclosure is not limited to the particular configurations, process steps, and materials disclosed herein, as such configurations, process steps, and materials may vary somewhat. It is also to be understood that the terminology employed herein is used for the purpose of describing particular illustrative embodiments only and is not intended to be limiting since the scope of the disclosure will be limited only by the appended claims and equivalents thereof.

In describing and claiming the subject matter of the disclosure, the following terminology will be used in accordance with the definitions set out below.

It must be noted that, as used in this specification and the appended claims, the singular forms “a”, “an”, and “the” include plural referents unless the context clearly dictates otherwise.

As used herein, the terms “comprising,” “including,” “containing,” “characterized by,” “having” and grammatical equivalents thereof are inclusive or open-ended terms that do not exclude additional, unrecited elements or method steps.

The system and method disclosed herein solve the problem of creating a customized experience across all different platforms that a user might see, such as advertisements, emails on various subjects, a website, and other communications from a given company user to a number of individual users. Illustrative embodiments of the instant invention create a webservice that can be accessed through multiple channels and platforms, each platform drawing from the same elements customized to a given user. This webservice is used to generate information for all different platforms that the user communicates with, creating a customized experience and customized content that is consistent across all channels through which a user might have contact with a given company. These channels could include text messages, emails, advertisements, and websites, for example.

In one embodiment of a system, method, and product for creating and delivering a personalized one-to-one experience for a user receiving communication from a given company shown in FIG. 1, a system comprises a personalization structure 101 and an Asset Data Platform 102, which are stored on a non-transitory computer readable medium. The instructions stored on the non-transitory computer readable medium comprise instructions that cause the system to take certain actions and access certain elements whenever the system must communicate with the user. The asset data platform 102 contains a variety of assets that can be used to generate personalized pages. Assets may be gathered from a variety of sources, and may be identifiers, attributes, or events. Attributes include colors, styles, locations, or other information linked to a particular user, along with a confidence factor for each attribute. Events include a full history of each item including when, where, from whom, to whom, where on the page it was shared, and other information. The asset data platform 102 may have access to external sources in creating, identifying, and classifying assets.

In an illustrative embodiment of the system, the personalization structure creates customer specific recommended content that is used to create a personalized landing page at the user level 103. A customized landing page is created when requested through a variety of channels. These may be push channels, such as email 104, web notifications 105, or a push through an application 106; or they may be pull channels, such as a web search 107 (as through a search engine such as Google) or a social media request 108 (as through FACEBOOK). While these channels may be accessed in different ways, the system utilizes the same data to create a personalized experience that is unified throughout a variety of different systems and channels to communicate with the system or the company user which utilizes the system.

In an illustrative embodiment of the system, the company user 110 provides events, customer identities, and customer attributes, as well as other necessary information to a Customer Data Platform (CDP) 111, such as mParticle or another similar CDP. The CDP may provide certain events to a data storage and analysis program 112, such as the commercially available Snowflake. This system in turn provides user level data to a machine-learning processing platform 113, such as Databricks. The machine learning data generated by the machine-learning platform is returned to the CDP 111 to give more data about a user and provide a better system for communicating with that user. When operating through push channels, the CDP 111 may provide data, including customer events, to a customer engagement structure 114, such as braze. This structure provides information to and requests the push channels, email, and web notifications.

The CDP 111 may also provide targeted audience information to search engines 107 or social media 108. This information, like that provided to Push channels, is used to generate personalized user-level landing pages. The CDP 111 may also provide information to an advertising and bidding program 115 such as Beeswax, which provides realtime bidding to obtain slots for paid advertising which can be accessed by the user. In addition, the paid advertising may provide real-time engagement data to a linking platform 116. In an illustrative embodiment, Branch is the linking platform and provides identity matched engagement data back to the CDP, which can then be used in the machine learning system to generate a more sophisticated and accurate model for providing information.

In an illustrative embodiment of the invention, the system and method create individualized, personalized communication across multiple channels. In an illustrative embodiment, this system and method comprises a non-transitory computer readable medium that may comprise a company server, a user computer, and a network connection. The company server may be accessible to the user computer through a network connection. It will be appreciated that the company server may comprise multiple servers linked together as in a server farm, and that the user computer may be an access device, which includes a smart phone, a computer, or a server or multiple servers through which a user may communicate with the company user via a network connection, such as the Internet.

FIG. 2 shows an illustrative embodiment of a system that creates a consistent, personalized web experience across multiple platforms and channels. The invention may include a personalization structure 201, which may be a program stored on a non-transitory computer medium. The personalization structure 201 is designed to create a personalized, one-to-one experience for any user communicating with a company user. The structure 201 receives a request from a channel or platform 202, which is accessing either onsite content 203 (such as the website of the company user, or a search of content on the website), or offsite content 204 (such as an email, a text message, or even a banner ad on another website). The request from the channel or platform 202 communicating with the personalization structure 201 may include a variety of different requests and formats, such as a search by an individual user, an email communication, a phone communication or text, instant messaging, a request to access a website, a request for product landing page, or even a request from the company user’s own website to generate an email communication. These examples are given only by way of example and are not meant to limit the type of communication that may be accomplished. The personalization structure 201 may be programmed to communicate with any type of communication through which a computer may receive communication.

Upon receiving a request from a channel or platform 202 to provide information, the personalization structure 201 makes a request to draw the required elements 206 to generate content deliverable to the channel or platform 202. The elements required are generated by element webservices 207, each of which has the logic required to fulfill the request to provide a personalized content deliverable. This may require the element webservice 207 to access outside webservices to provide customer propensities, product services, desired images, and other requirements to provide a fully personalized content deliverable. Each element webservice may have appropriate logic and machine-learning systems required for it to provide personalized content to a given user.

Upon receiving the elements required to create a content deliverable, the personalization structure 201 utilizes element ordering logic and machine learning 205 to create and deliver personalized content in real-time for offsite and onsite channels and platforms. Whichever type of deliverable is required draws on the same element webservices to generate the content for the required deliverable. This creates a unified user experience whether the user is accessing onsite content 203 from the company user’s website, or offsite content 204 that is requested by or directed to an individual user from the company user. The personalization structure uses the provided logic and machine learning 205 to create personalized content from a variety of elements 106 that the structure has access to in order to create a personalized experience that remains uniform across different channels of communication and across different platforms for communication.

The element webservices that generate the required elements for a content deliverable are stored in a non-transitory computer readable medium. This medium is accessible to the personalization structure, and contains in memory a cache of Element Webservices, shown in FIG. 3. Each Element Webservice 301 comprises data and logic needed to build personalized content for a given element in real-time, which may include accessing information from other locations. In an illustrative embodiment, each element webservice also has access to machine learning systems and logic that allow it to improve its creation of content deliverables over time. For example, in one embodiment, an Element Webservice will pull data from the asset data platform 302 to bring in an image or other deliverable 303. The asset data platform (ADP) may be generated as a table of assets with access to outside programs to aid in classifying and identifying various assets.

An Element Webservice could also pull data from customer propensities 304 based on actual or predicted behavior of the user on other websites 305, or past behavior of the user on that specific website 305. This may include, for example the user’s shopping habits, or other data that may be available either through a commercial source online, or through the data stored by the company user. The Element Webservice 301 can also access information about the source of the user’s inquiry 307: in the case of an e-commerce type use, this could be data about a particular product, which is collected through a system provided by the company user to collect those data 306. Another illustrative example of an Element Webservice would collect information about a particular user 309. This information may be imported into the given Element Webservice 301 through a program 308 created to collect and distribute data about particular customers. This program 308 may be created by the company user, or it may be through a commercially available program, and could include information such as age, interests, or other biographical data. In an illustrative embodiment, the element webservice may be designed to gather information from a commercially available customer data platform (CDP), such as mParticle, or a similar data collection program.

An Element Webservice 301 can also access other additional data 311 determined to be necessary to create a content deliverable. This information may be collected from a variety of databases, accessed through the appropriate application programming interface (API), or from information collected in the databases of the company user 310. None of the given examples are meant to limit the Element Webservice to a particular type of data, or to a given program, as the Element Webservice can be made to access whatever type of data is needed and available to personalize the experience for a given user. An individual element webservice has access to the data needed to create an element for a content deliverable, where the content deliverable is the vehicle by which the company user is communicating with the individual user. For example, and not by limitation, a content deliverable may be sent to a user via email, and may be the particular communication in an email directed at the user. Alternatively, a content deliverable could comprise only a portion of an email that must be inserted to personalize the email to an individual user, such as a pregenerated paragraph encouraging the user to examine items abandoned by the user in a previous visit to the website.

Each element webservice 301 is a self-contained structure that also includes all of the logic structures required to allow the element webservice to access all relevant data to create a content deliverable. The element webservice is accessible to the personalization structure as shown in FIG. 2, ref. no. 312. Each element webservice can be accessed to generate an element in response to requests from a user to access content available from the company user. In an illustrative embodiment of the current invention, the personalization structure can also be used to create a “pageless experience,” wherein a user accesses the Internet content through an individualized landing page created in real time and customized to the user rather than through a uniform webpage. This pageless experience combines multiple elements by using the organization logic and machine learning 205 to generate the optimum organization for the user for a given content deliverable, which may be an individualized landing page, a personalized email, or another personalized content deliverable.

FIG. 4 shows an example of a system and method that will order different elements when a platform requests an experience that utilizes multiple elements, such as a pageless experience. The personalization structure 401 creates a pageless experience by determining the best order of content elements to deliver for a given context, platform, and customer. The ordering utilizes element ordering logic until machine learning has enough information to act, and then machine learning aids in ordering elements properly. This process takes place to deliver a content deliverable to a proper channel or platform when that content deliverable requires multiple elements 402. The eligible elements in this process 403 are collected and the logic to order these elements is defined based on the best information available for a given user. In some cases this logic may lead to an element being excluded from the final deliverable 404. The personalization structure 401 arranges the eligible elements into ordered elements 405, which are communicated to the requesting platform 406 along with the order and organization in which the elements are to be displayed. The ordering logic is enhanced by machine learning programs such that the order and presentation of the elements is done in the optimal manner for a given situation (considering the platform, the customer, and the context).

A pageless experience, which combines two or more elements, may be requested in a variety of situations. For example, a customized PLA landing page may be generated as a pageless experience. A product listing ad is an advertisement that includes a product image along with a clickable link to direct a user to a landing page for a specific product. Using the personalization structure, a PLA landing page may be generated as a pageless experience customized to an individual user. A pageless experience may also be used to generate an abandonment email or a Pinterest landing page, which is customized to an individual user.

In another illustrative embodiment, the personalization structure may access only a single element to insert that element into a particular place in response to a request from the channel or platform. A variety of Element Webservices are available to personalize the particular communication. One type of Element Webservice may create an individual use element related to a product of the company user. For example, an element may be created that is related to cross sell products or products similar to a product a user has accessed. An element might be created that shows a product featured by the company user, or “Buyer’s Pick” products or “Top Products,” which feature products that are distinguished in other ways. An element might be created to show certain products displayed in the media or that are popular on a social media site. Other elements might be created for specifically when a user accesses content in a certain way. Other elements might be tailored to a user’s particular affiliations, such as an element that gives information on a shopping club or rewards program, or that creates an element based on the history of the user, such as an abandoned cart element. Still other elements might include information for an email or particular events that the company user wishes to promote.

FIG. 5 shows an illustrative embodiment of a process of delivering content from a request for content to the creation of content itself. This process takes place in real time in a situation where the personalization is used. In the first step 501, a request for a content deliverable is made of the system. This request is received and a content deliverable is generated in step 2, ref. no. 502. Finally, in step 3, the content is put into an appropriate format and delivered to its destination 503.

In step 1, ref. no. 501, a request for a content deliverable is made. This request may be a request for a pageless experience, such as a landing page 504 or an email 505, or it may be request for a single element to fit into an already-generated template 506.

In step 2, ref. no. 502, the request for a content deliverable is received by the layout endpoint 511 in the layout structure 510. The layout endpoint 511 provides information to the layout decision structure 512. The layout decision structure 512 draws information from a variety of sources to generate the best layout for a given customer. In the case of a single element request, the structure may be pregenerated for the most effective layout to present a single element. The layout decision structure may draw information from configuration programs or machine learning systems 513 to generate a properly formed layout 520, viewport detection programs 514 to ensure that the created layout fits the size of the user’s screen, and fallback elements 515. The combination of these elements is used to create an optimal layout for the content deliverable for a particular user. In addition, the layout decision structure 512 may draw and provide information from a customer attribute service 507, which draws information from and provides data to external data sources 508 such as commercial customer information services, an example being mParticle. The customer attribute service can also draw information from the element web services 530, and gather that information to provide to the layout decision structure 512. The layout decision structure 512 uses this information to generate a template/page layout 520.

After a template/page layout 520 is generated, the Element web-services 530 are called to provide content for the generated page. This generated page may be an email, a landing page, or any other customized communication between the company user and an individual user. The element webservices may include similar ideas to a current purchase, a featured product, a link to buying guides, an advertisement or standard product, or any other content that would be optimal to have in a given communication with a given user. Each piece of content is generated by a particular element webservice and is located in the template/page layout in a particular location, which is determined by the layout decision structure to be optimal for the given user. Once the element web services 530 have filled in the template, the content deliverable is delivered to the platform that requested it in step 3, ref. no. 503. The content may be provided to a variety of Application Programming Interfaces (APIs) to create a deliverable that is appropriate for the communication channel and platform. These interfaces may include a communication database 541, such as Oracle database, or to a system that allows voice communication 542, such as OREC engine. The information may be provided to a passive data structure 543, or to other APIs 544, for communication to an appropriate channel. The deliverable may also be provided to an asset data platform 545, which may store the information for later use within the system. Each element webservice 530 is a self-contained structure that also includes all of the logic structures required to allow the element webservice to access all relevant data to create a content deliverable, which can be delivered to whichever channel or method of communication which it must go through.

In addition, the system may receive content to be generated into an email 551. The content is sent through an email image structure 552 that has access both to the element webservices 530 and the asset data platform 545 to obtain specific data on the recipient of the email and generate an email personalized to a particular recipient.

FIG. 6 shows an arrangement of a delivery structure that may be used in an embodiment of a system for creating a consistent experience across multiple platforms and channels. The system may include a layout structure 601, an image structure 602, and a customer attribute service 603. A content request is received by the layout structure 601. This content request may be a request for a pageless experience 604, or a request for an individual element 605. The layout structure 601 creates a template and provides information to the customer attribute service 603, which may provide customer information to an external customer database platform such as mParticle 606 to request information about the customer. These data may further be provided to a data storage and analysis program 607 such as Snowflake, which may also provide additional information to create a content deliverable. This information can be provided back to the customer attribute service and used to determine which elements should be used. The layout structure 601 also provides information to the element web services 608, which provide information to the asset data platform 609. The Asset Data Platform 609 uses the information provided by the layout 601 through the element webservices 608 to create content appropriate to the user interface used to make the request 610. The element web services also provide information to product data API’s 611, another communication engine, such as the OREC engine 612, or other databases or APIs 613, which can assist in creating the personalized content by placing the content into an appropriate format for communicating with an individual user.

In addition, the image structure 602 may receive a request for real-time email content 614, which is provided to the asset data platform 609 and the element web services 608 to provide an appropriate response for the user interface, in this case a real-time email request. This may be to provide information for an email that is left ungenerated until it is opened, at which point the most timely, customer appropriate information is used to fill in the email. Both the image structure 602 and the layout structure 601 may produce data that can be monitored in real time through a data tracking program such as Kinesis 615. This program tracks the exhaust data from the system and provides it to the data storage and analysis program 607 to better create customized content.

FIG. 7 shows an illustrative embodiment of a personalization structure and a method of using it that forms a part of a system and method for creating a consistent, personalized web experience across multiple channels and platforms, as it might be used in an e-commerce setting. First, the server receives a request for a landing page 701. The request is sent to the layout structure 702 and to request a URL 710. Upon requesting a URL the landing page contextual request is generated 711. This request may be based upon multiple factors. The first is the channel, which is based on the platform being used, such as email, a website, a push advertising request, or another method of communicating with a user. The second is the channel Type, which is based on the context of the request, is the request for a product landing page, a Pinterest site, a wto, a broadcast site, or another type of communication. Another contextual item is the Key Value pairs. This is based on the contextual values for the structure, such as the style, the product options, the room, the taxonomy; and variables that are identifiable to the individual user, such as a customer id, ehid, and other customer variables. A URL structure can be generated, using the variables to create a unique URL for a particular landing page that the user accesses.

To generate the landing page itself, the request for a landing page also is provided to the layout structure 702. This structure comprises an endpoint 721, which receives the request and provides it to the layout decider 722. The layout decider accesses a viewport detection service 723, which determines the appropriate elements to display the layout on a given screen. The layout decider 722 also has access to a configuration service 724. The configuration is run by logic through the database containing information on a user’s propensities (or propensities of users in general). The database also has a machine learning system and a testing system that take over from the configuration service 724 when there is enough data and training in the machine learning system to do so. The layout decider 722 also has access to fallback elements 726 to use as well. Once the layout of the landing page 727 is generated it may make a URL request 728. The URL request for multiple recs is based on a variety of factors 729. This includes the element used, such as site sales, a featured products, etc. It can also be based on factors such as the asset size and key value pairs. The asset size variable depends on the size of the final assets, which provides one size per element. The key value pairs pass key values pulled from the original request URL. This generates a URL structure of the format =root?FP/1,SS/10&keyvaluepairs.

Once the site is generated it goes through a similar structure 703, starting at a new endpoint 731. From the endpoint another multiple rec request may be made for a URL 732, and the generated page will go through a deduplicating process 733 to eliminate duplicate product Ids across all final recs. The deduplicating process can also deduplicate the page based on other factors as well. After going through the deduplicating process 733, the layout pate may generate a number of rec endpoints 734 as elements. At this point, an a la carte rec request 735 may be made for a URL related to a single rec endpoint. The a la carte request depends on factors such as which element is being accessed (site sales, featured product, etc.), a count of the recs expected in the response, key value pairs, which is contextual values and customer identifiable variables, and the asset sizes, which is the size of the final assets.

The Rec endpoints 734 are provided to the logic layer 736. The logic layer is provided with a series of configurations 737, which control the logic layer until the machine learning system 738 has enough data to control the logic layer. The logic layer consists of individualized components for each rec endpoint. These components can include suppressions, a rec # coefficient, rec logic, and operational controls. The Suppressions may suppress OOS from a given user’s landing page. It may also suppress recently purchased items from the user’s landing page or restricted taxonomies from the user’s landing page. The Rec# Coefficient may ensure that the count of returned recs matches or exceeds the original recs count in the original request. In an illustrative embodiment this may be initially set at 2.0, which leads to a 100% increase in the rec count. The Rec logic is provided to know what each rec endpoint (or element), the requirements for each rec endpoint, and where to access the data for each rec endpoint. This system may also include controls for the viewport to make image size requests of the ADP. Finally, the operational controls may be controlled via configurations programs until the machine learning system has enough data to take over.

Once the layout goes through the logic layer it is a layout provided with the proper elements to fill it in and create a personalized landing page based on the same elements that will be used to create an email or an advertisement to the same user, creating a unified, personalized experience for the user. The finished page may be provided to the asset data platform, a CDP, a passive data structure, other APIs, or a database system, such as Oracle Database.

In an illustrative embodiment of the service, each element’s content shares the same origin, the Element Webservices, which ties together offsite and onsite personalization. In an illustrative embodiment, the service can deliver content for a variety of channels. For example, when an email is sent out, the webservice can generate an image when the email is opened. To do this, the service draws from the elements, which may be personalized based on information on each person accessing the email. When that same user is on a website and the website calls for an ad from the company user, the elements that are drawn from to create the advertisement for the website are the same elements that were used to create the email. Since the elements are accessible across a variety of channels, including the email, the website, advertisement pages, etc., the experience the user gets from the totality of communications with the company user is one that is targeted precisely to each individual user.

In an illustrative embodiment, the elements can also be combined in an order specifically targeted at a given user to create a “pageless” experience, which creates an individualized landing page and individualized display for each user. This individualization uses the user’s preferences, shopping history, and any other elements of information about the user to create the content. The individualized landing page draws from the same cache of elements stored on the server that creates emails, targeted advertisements, and other communications from the company user to an individual user.

In another illustrative embodiment, the elements can be combined in an order specifically targeted at a given user on any channel or platform through which the individual user communicates with the company user. For example, just as an individualized landing page and display can be created for each user, using the user’s preferences, shopping history, and any other information about the user to create the content of the landing page, so too can the same information be used to create an email, ordering the elements of the email dynamically for each individual user. This individualization uses the user’s preferences, shopping history, and any other elements of information about the user to create the content, which can be anything to communicate information, from the website landing page, to an email, to a text message. The content draws from the same cache of elements stored on the server that creates emails, targeted advertisements, and other communications from the company user to an individual user. Any channel or platform that can accept multiple types of content for one experience can be individualized for a specific user, combining the user’s information from the same cache of elements used to create the landing page. This helps create consistency across all channels and platforms used by each particular user.

In an illustrative embodiment, the different elements can be accessed from a variety of channels and platforms. When a given channel or platform must communicate with user, for example through an email or a text message, or on a given website, the channel sends a request to the system. The system then accesses the cached elements. The channel can make a request for a single element, for example, an “item-in-cart” element, for an email following up on an unpurchased item in the user’s cart. The element contains all the logic and data needed to create a deliverable to the given channel. In another illustrative embodiment, for example when the email is more general or when the user accesses the website, the channel can request information from multiple elements, such as user propensities, past purchases, past viewed websites, and other elements and from the logic in the system create a content deliverable that gives a customized page for the user to access, whether by accessing an actual webpage or through content embedded in an email.

In an illustrative embodiment, the system can also include a machine-learning algorithm as known in the art, which incorporates a user’s responses to the displayed content to determine the contents of elements for an individual user. As such, each element can become personalized for an individual user and can contain the content best needed to appeal to the user. In addition, one illustrative embodiment allows the system to use machine learning to determine which elements should be included in a pageless experience for an individual user.

One illustrative embodiment of a system for supporting and creating consistent personalized content to a user of a webservice across multiple channels and platforms of communication with the user comprises: a server capable of responding to requests from multiple platforms and channels; a cache of multiple Element Webservices stored in memory of a server, each Element Webservice having access to all data and logic necessary to build a personalized content deliverable in real-time, the personalized content deliverable being an element; a non-transitory computer readable medium containing in memory instructions, wherein the instructions causing the system to execute the following steps upon receiving a request for a content deliverable:

• Determine they type of request, whether for a single Element Webservice or for a pageless deliverable;
• Access the requested element webservices;
• If the request is for a single element webservice, deliver the data in the element webservice to the platform making the request;
• If the request is for a pageless content deliverable, create a layout for the content deliverable, determine the optimal order of elements and which elements are best to contain in the deliverable, then order the elements in the proper order and deliver the pageless content deliverable to the server making the request.

Another embodiment of the system also incorporates a machine learning algorithm to incorporate past data into the future use of the specific order of elements webservices and appropriate elements to access, as well as incorporating machine learning training, such as using training sets and possible future reactions, as well as other types of machine learning training known in the art.

Another embodiment of the system also comprises an Asset Data Platform, which comprises various assets that can be drawn on by element webservices to create a given element. The asset data platform may comprise data including images, colors, fonts, sounds, colors, specific shapes or interfaces, or other types of assets which are required to create a content deliverable.

Another illustrative embodiment of the system grants Element Webservices access to a database giving information on a user’s propensities based on past behavior and predicted future behavior and creates an element based on those user propensities. This database may be a database compiled by the company user providing the content deliverables, or it may be a commercially available database wherein the company user pays a fee for access to information about users and data.

Another illustrative embodiment of the system allows an Element Webservice to access data on a particular product and creates an element showing information about the particular product.

In yet another illustrative embodiment of the system, an Element Webservice has access to a Customer Data Platform that provides identification of a user and attributes of that user and creates an element based on the information from the Customer Data Platform.

Another illustrative embodiment of the system comprises an Element Webservice, which has access to any API which provides information needed to create a particular element to create a content deliverable. This may include information on a customer, product, or particular channel, as well as geographic information, or other information which can help customize a particular element to a given user.

Another illustrative embodiment of the invention comprises a system for creating consistent personalized content to a user of a webservice across multiple channels and platforms of communication with the user. This system may include a cache of element webservices stored in a computer readable non transitory medium linked to a network to provide accessibility to the other elements of the system, wherein each Element Webservice comprises data and logic needed to build personalized content for a given element in real-time. The system also includes a layout structure, wherein the layout structure receives requests for content and generates an appropriate layout for content built by the Element Webservice to fill and provides the layout to the element webservices. Another part of the system is an image structure, which receives requests for real time email content and generates image requests to be sent to the element webservices. The system also includes a customer attribute service containing information collected by the webservice on individual users.

Upon receiving a request for an individual element, the system takes the following steps: Receive the request for an individual element at the layout structure; Create a template at the layout structure and provide the template to the customer attribute service and the element webservices; Cause the element webservices to generate the requested element and insert the element into the template created; and Provide the filled template to an appropriate API to fulfill the request.

Upon receiving a request for a multiple element experience, such as a customized landing page or another pageless experience the system takes the following steps: Receive the request for an individual element at the layout structure; Create a template at the layout structure by accessing information specific to a user and generating a template customized to the user making the request for a multiple element experience; Provide the template to the customer attribute service and the element webservices; cause the Element Webservices to generate the requested elements and insert the elements into the template created; provide the filled template to an appropriate API to be fulfill the request.

Upon receiving a request for real-time email content, the system takes the following steps: receive the request for real-time email content at the image structure; provide an image and data on the request to the asset data platform and the element webservices; cause the element web service to generate the requested element for an email and provide the requested element and email images to the asset data platform; provide the requested real-time email content, including the image and generated element to the user interface in real-time as the user opens an email.

In another illustrative embodiment of the invention, the layout structure further comprises: A layout endpoint that receives a request for a content deliverable; a layout decision structure that receives the request for a content deliverable from the layout endpoint, collects information, and accesses logic structures to create a layout for a content deliverable; a configuration program containing instructions on how to generate an appropriate layout for a given content deliverable; a viewport detection structure that detects the size of a viewscreen upon which the request will be viewed and ensures that the layout is the appropriate size.

In another illustrative embodiment of the invention, the configuration program further comprises a machine learning structure that is used to generate an appropriate layout for a given content deliverable.

Another illustrative embodiment of the system includes a layout structure that further has access to external data sources, such as a customer information service or a customer database platform; and wherein the layout structure accesses the external data source to contribute to the creation of a layout that is tailored to the user making the request for a content deliverable.

In yet a further illustrative embodiment of the system, each element webservice has access to machine learning programs and external services such as a customer data platform (CDP), which allow it to create personalized content deliverables for the template from the layout structure.

Another illustrative embodiment of the invention is expressed as a method for creating consistent personalized content to a user of a webservice across multiple channels and platforms of communication with the user, wherein the method comprises: providing a cache of element webservices, wherein each element webservice comprises data and logic needed to build personalized content for a given element in real-time; receiving a request for a content deliverable; creating an appropriate layout for the content deliverable, wherein the layout contains space for information for each requested element; generating the requested content from the element webservices, wherein each element webservice uses the data and logic it contains to build personalized content for a given element in real time; inserting the requested content from the element webservices into the layout, creating a finished content deliverable; and providing the content deliverable to the requesting user.

Another illustrative embodiment of this method also comprises the step of determining an optimal order of elements and which elements are best to contain in the deliverable, then further ordering the elements in the proper order and delivering the content.

Another illustrative embodiment of the method also comprises the step of accessing a machine-learning program while creating the layout, allowing for the system to create content layouts and utilize both past and training layouts to create an appropriate layout for a given user.

In yet another illustrative embodiment of the method, each element webservice also has access to machine learning systems, allowing each element webservice to create personalized content using information on the past creation of personalized content and projected user responses to created content for a particular element which factors into the creation of a content deliverable.

Claims

1. A system for supporting and creating consistent personalized content to a user of a webservice across multiple channels and platforms of communication with the user, said system comprising: a server capable of responding to requests from multiple platforms and channels;a cache of multiple element webservices stored in memory of a server, each element webservice having access to all data and logic necessary to build a personalized content deliverable in real-time, said personalized content deliverable being an element;wherein each element webservice is capable of generating content usable by multiple types of content deliverable customized to multiple offsite and onsite channels and platforms;a non-transitory computer readable medium containing in memory instructions, said instructions causing the system to execute the following upon receiving a request for a content deliverable;determine the type of request, whether for a single element webservice or for a pageless deliverable;generate a template in which to deliver the content deliverable, which is appropriate for the type of content deliverable requested,wherein the appropriate template generated for a single element webservice is a structure pregenerated to provide the most effective layout to present the single element;wherein the system generates an appropriate template for a pageless content deliverable for each individual user by using a combination of one or more of the following elements: the type of deliverable requested; configuration programs, machine learning systems providing information on generating a properly formed layout for a template, viewport detection programs ensuring that the created template fits the size of the user’s screen, and an external customer attribute service drawing information from external data sources and the element web services about individual users;access the requested element webservice and cause the element webservices to generate the requested content to be delivered in the content deliverable, wherein the content from a given element webservice includes a portion of an email, a product description, an image, or another element of a communication with the user;if the request is for a single element webservice, deliver the data in the element webservice to the platform making the request in the pregenerated template;if the request is for a pageless content deliverable, determine the optimal order of elements and which elements are best to contain in the deliverable, then order the elements in the generated template to create a pageless content deliverable and deliver the pageless content deliverable to the server making the request;wherein the system draws information from the same element web services regardless of the type of communication generated;wherein the system draws information from the same element webservices regardless of the type of platform from which the user is communicating.

2. The system of claim 1 which also incorporates a machine learning algorithm to incorporate past data into the future use of the specific order of elements webservices and appropriate elements to access.

3. The system of claim 1 also comprising an Asset Data Platform that comprises data, information, and images that can be drawn on by element webservices to create a given element.

4. The system of claim 1 wherein an element webservice has access to a database giving information on a user’s propensities based on past behavior and predicted future behavior and creates an element based on those user propensities.

5. The system of claim 1 wherein an element webservice accesses data on a particular product and creates an element based on the particular product.

6. The system of claim 1 wherein an element webservice has access to a Customer Data Platform that provides identification of a user and attributes of that user and creates an element based on the information from the Customer Data Platform.

7. The system of claim 1 wherein an element webservice has access to any API which provides information needed to create a particular element to create a content deliverable.

8. A system for creating consistent personalized content to a user of a webservice across multiple channels and platforms of communication with the user, said system comprising: a cache of element webservices stored in a computer readable non transitory medium linked to a network to provide accessibility to the other elements of the system;wherein each element webservice comprises data and logic needed to build personalized content for a given element in real-time;wherein each element webservice is capable of generating content applicable to multiple types of content deliverable customized to multiple offsite and onsite channels and platforms;a layout structure, wherein said layout structure receives requests for content and generates an appropriate layout for content built by the element webservice to fill and provides said layout to the element webservices;an image structure which receives requests for real time email content and generates image requests to be sent to the element webservices;a customer attribute service containing information collected by the webservice on individual users;instructions stored in a non-transitory computer medium which cause the system to take the following steps upon receiving a request for an individual element; receive the request for an individual element at the layout structure;create a template at the layout structure and provide said template to the customer attribute service and the element webservices;cause the element webservices to generate the requested element and insert the element into the template created wherein the element from a given element webservice can be applied to multiple types of content deliverable;provide the filled template to an appropriate API to fulfill the request;instructions stored in a non-transitory computer medium which cause the system to take the following steps upon receiving a request for a multiple element experience; receive the request for an individual element at the layout structure;create a template at the layout structure by accessing information specific to a user and generating a template customized to the user making the request for a multiple element experience;provide said template to the customer attribute service and the element webservices;cause the element webservices to generate the requested elements and insert the elements into the template created wherein the element from a given element webservice can be applied to multiple types of content deliverable;provide the filled template to an appropriate API to fulfill the request;instructions stored in a non-transitory computer medium which cause the system to take the following steps upon receiving a request for real-time email content; receive the request for real-time email content at the image structure;provide an image and data on the request to the asset data platform and the element webservices;cause the element web service to generate the requested element for an email and provide the requested element and email images to the asset data platform wherein the element from a given element webservice can be applied to multiple types of content deliverable;provide the requested real-time email content, including the image and generated element to the user interface in real-time as the user opens an email.

9. The system of claim 8 wherein the layout structure further comprises: a layout endpoint which receives a request for a content deliverable;a layout decision structure which receives the request for a content deliverable from the layout endpoint, collects information, and accesses logic structures to create a layout for a content deliverable;a configuration program containing instructions on how to generate an appropriate layout for a given content deliverable;a viewport detection structure which detects the size of a viewscreen upon which the request will be viewed and ensures that the layout is the appropriate size.

10. The system of claim 9 wherein the configuration program further comprises a machine learning structure which is used to generate an appropriate layout for a given content deliverable.

11. The system of claim 9 wherein the layout structure further has access to external data sources, such as a customer information service or customer database platform; and wherein the layout structure accesses the external data source to contribute to the creation of a layout which is tailored to the user making the request for a content deliverable.

12. The system of claim 8 wherein each element webservice further has access to machine learning programs and external services such as a customer data platform (CDP) which allow it to create personalized content deliverables to a template from the layout structure.

13. A method for creating consistent personalized content to a user of a webservice across multiple channels and platforms of communication with the user, said method comprising: providing a cache of element webservices, wherein each element webservice comprises data and logic needed to build personalized content for a given element in real-time;wherein each element webservice is capable of generating content applicable to multiple types of content deliverable customized to multiple offsite and onsite channels and platforms;receiving a request for a content deliverable;creating an appropriate layout for the content deliverable, wherein the layout contains space for information for each requested element;generating the requested content from the element webservices, wherein each element webservice uses the data and logic it contains to build personalized content for a given element in real time;inserting the requested content from the element webservices into the layout, creating a finished content deliverable;wherein upon receiving an additional request from a previous user from a different platform or channel, the system will draw from the same element webservices to create content, providing a unified response to the user across different platforms and channels;providing the content deliverable to the requesting user.

14. The method of claim 13 also comprising the step of determining an optimal order of elements and which elements are best to contain in the deliverable, then further ordering the elements in the proper order and delivering the content.

15. The method of claim 13 also comprising the step of accessing a machine-learning program while creating the layout, allowing for the system to create content layouts and utilize both past and training layouts to create an appropriate layout for a given user.

16. The method of claim 13 wherein each element webservice also has access to machine learning systems, allowing each element webservice to create personalized content using information on the past creation of personalized content and projected user responses to created content to factor into the creation of a content deliverable.