Computerized system and method for providing an augmented message content display

The disclosed systems and methods provide a novel framework that provides mechanisms for enabling message senders to dictate, control and/or create dynamic immersive content consumption experiences for recipients of their messages. The disclosed framework provides message senders with previously non-existent functionality to control the experience and environment within which their messages are consumed. Conventional systems provide recipients with capabilities to consume messages and/or supplemental content; however, these capabilities are driven and controlled by the hosting messaging platform and/or the third party entity that is availed opportunities to provide supplemental content. The disclosed framework prevents such experiences by providing capabilities to the message sender that involves control not only over the experience of the sender's messages but also control over the experience of the environment in which the messages are consumed by their recipients.

FIELD

The present disclosure relates to providing senders of messages with functionality for controlling how message recipients receive and/or are capable of consuming their messages and/or supplemental content related to their messages.

BACKGROUND

Current messaging platforms, such as electronic mail (“e-mail” or “email”, used interchangeably), are capable of providing recipient users with avenues to receive supplemental content related to the messages they are receiving. However, existing mechanisms by which the messages and the supplemental content are provided to recipients are dictated by the messaging platform that decides how/when third party content is made available to the user.

SUMMARY

The present disclosure provides a framework that provides novel mechanisms for enabling message senders (i.e., sending users) to dictate, control and/or create dynamic immersive content for recipients (e.g., recipient users) of their messages. The disclosed framework provides systems and methods that provide message senders with previously non-existent functionality to control the environment within which their messages are consumed.

Conventional systems provide recipients with capabilities to consume messages and/or supplemental content; however, these capabilities are driven and controlled by the hosting messaging platform and/or, in part, by third party entities that are given opportunities to provide supplemental content (e.g., ads). This can reduce a recipient user's experience with a message platform and can lead to wasted computational resources that result from platform abandonment. Mixed messaging as well as user confusion can also be caused when control of messages is passed on to other parties that are not the sender. For example, a user may receive a message about a widget from vendor X, and other content displayed for a similar widget from vendor Y. This can distract the user from the original message, and/or can drive the user's experience in an undesired direction.

The disclosed framework provides a technical solution that provides capabilities to the message sender that grants them control not only over their messages, but also control over the environment in which the messages are consumed by the recipients. This allows for increased user satisfaction which maximizes the utilization of computational and network resources by avoiding wasted messages, as well as enables the sender to use expanded capabilities to encourage the recipient to share the message with other users they frequently communicate with.

According to some embodiments, while the discussion herein will focus on messages communicated on and/or over a messaging platform, for example email messages via an email platform, it should be understood that any other type or form of known or to be known electronic messages or content, and/or platforms (or messaging applications) can be utilized without departing from the scope of the instant disclosure. Thus, the disclosed framework can be used when users are viewing and/or interacting with any type of content on a network, such as for example, but not limited to, messages, web pages, articles, application pages, social media posts, and the like, or some combination thereof.

In accordance with one or more embodiments, the present disclosure provides computerized methods for a novel framework that provides senders of messages with functionality for controlling how message recipients receive and/or are capable of consuming messages and supplemental content related to the messages.

In accordance with one or more embodiments, the present disclosure provides a non-transitory computer-readable storage medium for carrying out the above mentioned technical steps of the framework's functionality. The non-transitory computer-readable storage medium has tangibly stored thereon, or tangibly encoded thereon, computer readable instructions that when executed by a device (e.g., application server, messaging server, ad server, content server and/or client device, and the like) cause at least one processor to perform a method for a novel and improved framework that provides senders of messages with functionality for controlling how message recipients receive and/or are capable of consuming messages and supplemental content related to the messages.

In accordance with one or more embodiments, a system is provided that comprises one or more computing devices configured to provide functionality in accordance with such embodiments. In accordance with one or more embodiments, functionality is embodied in steps of a method performed by at least one computing device. In accordance with one or more embodiments, program code (or program logic) executed by a processor(s) of a computing device to implement functionality in accordance with one or more such embodiments is embodied in, by and/or on a non-transitory computer-readable medium.

DESCRIPTION OF EMBODIMENTS

For purposes of this disclosure, a “wireless network” should be understood to couple client devices with a network. A wireless network may employ stand-alone ad-hoc networks, mesh networks, Wireless LAN (WLAN) networks, cellular networks, or the like. A wireless network may further employ a plurality of network access technologies, including Wi-Fi, Long Term Evolution (LTE), WLAN, Wireless Router (WR) mesh, or 2nd, 3rd, 4thor 5thgeneration (2G, 3G, 4G or 5G) cellular technology, mobile edge computing (MEC), Bluetooth, 802.11b/g/n, or the like. Network access technologies may enable wide area coverage for devices, such as client devices with varying degrees of mobility, for example.

In short, a wireless network may include virtually any type of wireless communication mechanism by which signals may be communicated between devices, such as a client device or a computing device, between or within a network, or the like.

A client device may vary in terms of capabilities or features. Claimed subject matter is intended to cover a wide range of potential variations, such as a web-enabled client device or previously mentioned devices may include a high-resolution screen (HD or 4K for example), one or more physical or virtual keyboards, mass storage, one or more accelerometers, one or more gyroscopes, global positioning system (GPS) or other location-identifying type capability, or a display with a high degree of functionality, such as a touch-sensitive color 2D or 3D display, for example.

As discussed herein, reference to an “advertisement” should be understood to include, but not be limited to, digital media content embodied as a media item that provides information provided by another user, service, third party, entity, and the like. Such digital ad content can include any type of known or to be known media renderable by a computing device, including, but not limited to, video, text, audio, images, and/or any other type of known or to be known multi-media item or object. In some embodiments, the digital ad content can be formatted as hyperlinked multi-media content that provides deep-linking features and/or capabilities. Therefore, while some content is referred to as an advertisement, it is still a digital media item that is renderable by a computing device, and such digital media item comprises content relaying promotional content provided by a network associated party.

As discussed in more detail below, according to some embodiments, information associated with, derived from, or otherwise identified from, during or as a result of a message delivery and/or created message experience, as discussed herein, can be used for monetization purposes and targeted advertising when providing, delivering or enabling such devices access to content or services over a network. Providing targeted advertising to users associated with such discovered content can lead to an increased click-through rate (CTR) of such ads and/or an increase in the advertiser's ROI for serving such content provided by third parties (e.g., digital advertisement content provided by an advertiser, where the advertiser can be a third party advertiser, or an entity directly associated with or hosting the systems and methods discussed herein).

Certain embodiments will now be described in greater detail with reference to the figures. In general, with reference toFIG.1, a system100in accordance with an embodiment of the present disclosure is shown.FIG.1shows components of a general environment in which the systems and methods discussed herein may be practiced. Not all the components may be required to practice the disclosure, and variations in the arrangement and type of the components may be made without departing from the spirit or scope of the disclosure. As shown, system100ofFIG.1includes local area networks (“LANs”)/wide area networks (“WANs”)—network105, wireless network110, mobile devices (client devices)102-104and client device101.FIG.1additionally includes a variety of servers, such as content server106, application (or “App”) server108and third party server130.

One embodiment of mobile devices102-104may include virtually any portable computing device capable of receiving and sending a message over a network, such as network105, wireless network110, or the like. Mobile devices102-104may also be described generally as client devices that are configured to be portable. Thus, mobile devices102-104may include virtually any portable computing device capable of connecting to another computing device and receiving information, as discussed above.

Mobile devices102-104also may include at least one client application that is configured to receive content from another computing device. In some embodiments, mobile devices102-104may also communicate with non-mobile client devices, such as client device101, or the like. In one embodiment, such communications may include sending and/or receiving messages, searching for, viewing and/or sharing memes, photographs, digital images, audio clips, video clips, or any of a variety of other forms of communications.

Client devices101-104may be capable of sending or receiving signals, such as via a wired or wireless network, or may be capable of processing or storing signals, such as in memory as physical memory states, and may, therefore, operate as a server.

Wireless network110is configured to couple mobile devices102-104and its components with network105. Wireless network110may include any of a variety of wireless sub-networks that may further overlay stand-alone ad-hoc networks, and the like, to provide an infrastructure-oriented connection for mobile devices102-104.

Network105is configured to couple content server106, application server108, or the like, with other computing devices, including, client device101, and through wireless network110to mobile devices102-104. Network105is enabled to employ any form of computer readable media or network for communicating information from one electronic device to another.

The content server106may include a device that includes a configuration to provide any type or form of content via a network to another device. Devices that may operate as content server106include personal computers, desktop computers, multiprocessor systems, microprocessor-based or programmable consumer electronics, network PCs, servers, and the like. Content server106can further provide a variety of services that include, but are not limited to, email services, instant messaging (IM) services, streaming and/or downloading media services, advertising services, search services, photo services, web services, social networking services, news services, third-party services, audio services, video services, SMS services, MMS services, FTP services, voice over IP (VOIP) services, or the like.

Third party server130can comprise a server that stores online advertisements for presentation to users. In some embodiments, various monetization techniques or models may be used in connection with sponsored advertising, including advertising associated with user data, as discussed below, where ads can be modified and/or added to content based on information related to the recipient user(s), the content included in the messages, and/or information related to and/or provided by the message sender.

In some embodiments, users are able to access services provided by servers106,108and/or130. This may include in a non-limiting example, authentication servers, search servers, email servers, social networking services servers, SMS servers, IM servers, MMS servers, exchange servers, photo-sharing services servers, and travel services servers, via the network105using their various devices101-104.

In some embodiments, applications, such as, but not limited to, mail applications (e.g., Yahoo! Mail®, Gmail®, and the like), instant messaging applications, blog, photo or social networking applications (e.g., Facebook®, Twitter®, Instagram®, and the like), search applications (e.g., Yahoo!® Search), news applications (e.g., Yahoo! Sports®, ESPN®, Huffington Post®, CNN®, and the like), and the like, can be hosted by the application server108, or content server106and the like.

Thus, the application server108, for example, can store various types of applications and application related information including application data and user profile information (e.g., identifying and behavioral information associated with a user). It should also be understood that content server106can also store various types of data related to the content and services provided by content server106in an associated content database107, as discussed in more detail below (e.g. database320ofFIG.3). Embodiments exist where the network105is also coupled with/connected to a Trusted Search Server (TSS) which can be utilized to render content in accordance with the embodiments discussed herein. Embodiments exist where the TSS functionality can be embodied within servers106,108and/or130.

Moreover, althoughFIG.1illustrates servers106,108and130as single computing devices, respectively, the disclosure is not so limited. For example, one or more functions of servers106,108and/or130may be distributed across one or more distinct computing devices. Moreover, in one embodiment, servers106,108and/or130may be integrated into a single computing device, without departing from the scope of the present disclosure.

FIG.2is a schematic diagram illustrating a client device showing an example embodiment of a client device that may be used within the present disclosure. Client device200may include many more or less components than those shown inFIG.2. However, the components shown are sufficient to disclose an illustrative embodiment for implementing the present disclosure. Client device200may represent, for example, client devices discussed above in relation toFIG.1.

As shown in the figure, Client device200includes a processing unit (CPU)222in communication with a mass memory230via a bus224. Client device200also includes a power supply226, one or more network interfaces250, an audio interface252, a display254, a keypad256, an illuminator258, an input/output interface260, a haptic interface262, an optional global positioning systems (GPS) receiver264and a camera(s) or other optical, thermal or electromagnetic sensors266. Device200can include one camera/sensor266, or a plurality of cameras/sensors266, as understood by those of skill in the art. Power supply226provides power to Client device200.

Client device200may optionally communicate with a base station (not shown), or directly with another computing device. Network interface250is sometimes known as a transceiver, transceiving device, or network interface card (NIC).

Audio interface252can be arranged to produce and receive audio signals such as, for example, the sound of a human voice. Display254can, but is not limited to, a include a touch sensitive screen arranged to receive input from an object such as a stylus or a digit from a human hand. Keypad256can comprise any input device arranged to receive input from a user. Illuminator258may provide a status indication and/or provide light.

Client device200also comprises input/output interface260for communicating with external devices. Input/output interface260can utilize one or more communication technologies, such as USB, infrared, Bluetooth™, or the like. Haptic interface262is arranged to provide tactile feedback to a user of the client device.

Optional GPS transceiver264can determine the physical coordinates of Client device200on the surface of the Earth. In some embodiments however, Client device200may through other components, provide other information that may be employed to determine a physical location of the device, including for example, a MAC address, Internet Protocol (IP) address, or the like.

Mass memory230includes a RAM232, a ROM234, and other storage means. Mass memory230stores a basic input/output system (“BIOS”)240for controlling low-level operation of Client device200. The mass memory also stores an operating system241for controlling the operation of Client device200

Memory230further includes one or more data stores, which can be utilized by Client device200to store, among other things, applications242and/or other information or data. For example, data stores may be employed to store information that describes various capabilities of Client device200. The information may then be provided to another device based on any of a variety of events, including being sent as part of a header (e.g., index file of the HLS stream) during a communication, sent upon request, or the like. At least a portion of the capability information may also be stored on a disk drive or other storage medium (not shown) within Client device200.

Applications242may include computer executable instructions which, when executed by Client device200, transmit, receive, and/or otherwise process audio, video, images, and enable telecommunication with a server and/or another user of another client device. Applications242may further include search client245that is configured to send, to receive, and/or to otherwise process a search query and/or search result.

Having described the components of the general architecture employed within the disclosed systems and methods, the components' general operation with respect to the disclosed systems and methods will now be described below.

FIG.3is a block diagram illustrating the components for performing the systems and methods discussed herein.FIG.3includes message delivery engine300, network315and database320. The message delivery engine300can be a special purpose machine or processor and could be hosted by a network server (e.g., messaging server, cloud web services server(s)), application server, content server, social networking server, web server, search server, content provider, third party server, user's computing device, and the like, or any combination thereof.

According to some embodiments, message delivery engine300can be embodied as a stand-alone application that executes on a networking server. In some embodiments, the message delivery engine300can function as an application installed on the user's device, and in some embodiments, such application can be a web-based application accessed by the user device over a network. In some embodiments, the message delivery engine300can be configured and/or installed as an augmenting script, program or application (e.g., a plug-in or extension) to another application or portal data structure.

The database320can be any type of database or memory, and can be associated with a content server on a network (e.g., content server, a search server or application server) or a user's device (e.g., device101-104or device200fromFIGS.1-2). Database320comprises a dataset of data and metadata associated with local and/or network information related to users, services, applications, content and the like.

In some embodiments, such information can be stored and indexed in the database320independently and/or as a linked or associated dataset. An example of this is look-up table (LUT). As discussed above, it should be understood that the data (and metadata) in the database320can be any type of information and type, whether known or to be known, without departing from the scope of the present disclosure.

According to some embodiments, database320can store data for users, e.g., user data. According to some embodiments, the stored user data can include, but is not limited to, information associated with a user's profile, user interests, user behavioral information, user patterns, user attributes, user preferences or settings, user demographic information, user location information, user biographic information, and the like, or some combination thereof.

In some embodiments, the user data can also include user device information, including, but not limited to, device identifying information, device capability information, voice/data carrier information, Internet Protocol (IP) address, applications installed or capable of being installed or executed on such device, and/or any, or some combination thereof. It should be understood that the data (and metadata) in the database320can be any type of information related to a user, content, a device, an application, a service provider, a content provider, whether known or to be known, without departing from the scope of the present disclosure.

According to some embodiments, database320can store data and metadata associated with users, searches, actions, clicks, conversions, recommendations, messages, images, videos, text, products, items and services from an assortment of media, applications and/or service providers and/or platforms, and the like. Accordingly, any other type of known or to be known attribute or feature associated with a user, message, data item, media item, login, logout, website, application, communication (e.g., a message) and/or its transmission over a network, a user and/or content included therein, or some combination thereof, can be saved as part of the data/metadata in datastore320.

As discussed above, with reference toFIG.1, the network315can be any type of network such as, but not limited to, a wireless network, a local area network (LAN), wide area network (WAN), the Internet, or a combination thereof. The network315facilitates connectivity of the message delivery engine300, and the database of stored resources320. Indeed, as illustrated inFIG.3, the message delivery engine300and database320can be directly connected by any known or to be known method of connecting and/or enabling communication between such devices and resources.

The principal processor, server, or combination of devices that comprise hardware programmed in accordance with the special purpose functions herein is referred to for convenience as message delivery engine300, and includes bot module302, network content module304, alternate content module306and experience module308. It should be understood that the engine(s) and modules discussed herein are non-exhaustive, as additional or fewer engines and/or modules (or sub-modules) may be applicable to the embodiments of the systems and methods discussed. The operations, configurations and functionalities of each module, and their role within embodiments of the present disclosure will be discussed below.

Turning toFIG.4, Process400is disclosed which details non-limiting example embodiments of the disclosed systems and methods. According to some embodiments, Process400provides mechanisms where a sender can leverage a bot (or similar type of software application) while sending a message to a recipient, where the type of bot used (or instructions provided by the bot) can dictate how the message can be consumed by the recipient and/or the recipient's experience while consuming the message.

According to some embodiments, as discussed in more detail below, based on the bot being used by the sender via the message, engine300can perform various types of actions or operations (used interchangeably), such as: i) provide supplemental, network-located content (e.g., Steps408-410, as discussed below), ii) provide access to uploaded, alternate content stored in an associated alternate content database (e.g., Steps412-414, as discussed below), and/or iii) create and provide an interactive, adaptive user interface (UI) or displayable UI portion that depicts interface objects related to the message content and/or enables the recipient to share the message with the recipient's contacts (e.g., Steps416-418, as discussed below).

In some embodiments, engine300can perform one of actions i-iii, and/or a combination of these actions so as to provide a fully immersive experience for a user. In some embodiments, the type and/or quantity of actions can be dictated by the bot information included in the message. For example, if Apple® sends a message to a recipient related to the latest iPhone®, when the recipient opens the message, an advertisement for downloadable applications can be displayed (e.g., Steps408-410), a skin can be downloaded and displayed in the background of the window displaying the message (e.g., Steps412-414), and a pop-up window can be displayed providing functionality for sharing the message (and/or advertisement) with other users (e.g., Steps416-418).

In some embodiments, only a portion or one of these actions can be provided by engine300, as dictated by the bot information included and/or associated with the message, as discussed below. In some embodiments, the bot information can reference a single bot and/or multiple bots, where each bot can have its own separate functionality.

Thus, as discussed below, according to some embodiments, when commercial or marketing emails are sent from commercial entities to recipients, the entities can control how their content is consumed by the recipient. While the discussion herein will be based on sending commercial emails from commercial entities (e.g., vendors) to recipient users (e.g., marketing emails, for example), it should be construed as limiting, as other types of emails, whether machine generated or user generated, can be communicated and managed by any type of sender, whether a commercial or personal user, without departing from the scope of the instant disclosure.

According to some embodiments, Steps402-406of Process400can be performed by bot module302of message delivery engine300; Steps408-410can be performed by network content module304; Steps412-414can be performed by alternate content module306; Steps416-418can be performed by experience module308.

Process400begins with Step402where a message from a sender can be received. The message can be addressed to a recipient(s), and can include content, which can include, but is not limited to, text, images, Uniform Resource Locators (URLs), videos, videos, multimedia content and/or any other type of known or to be known digitally renderable content that can be displayed within a UI or window that is displaying a message.

According to embodiments of the instant disclosure, the received message of Step402further includes and/or references bot information. Bot information corresponds to the bot the sender is using to control the message upon delivery and/or interaction by the recipient (e.g., when the message is delivered to the recipient's inbox and/or when the recipient opens the message). In some embodiments, the bot information can include, but is not limited to, bot embedded code within the message, a bot address (e.g., an associated IP address of the bot), and/or other information related to a bot software application that identifies a type of bot and indicates functionality to be executed on the device of the recipient, as discussed below.

In some embodiments, the bot information can be embedded into the message, included in or referenced by the message header, included in or referenced by the message body, appended to the message as an attachment or augmented script to be executed upon delivery and/or interaction, and the like.

In Step404, upon receiving the message from the sender (and prior to delivery to the recipient), engine300can analyze the message and identify the bot information. In some embodiments, engine300can utilize any type of computational analysis and/or mining technique or algorithm to parse the message and identify the bot information included therein. For example, engine300can utilize a neural network algorithm, parser, entropy algorithm, and/or any other type of algorithm or computerized mechanism to parse a message and identify (or extract) bot information therefrom.

In Step406, engine300determines a type of action (or operation) to perform based on the bot information. In some embodiments, Step406is performed prior to delivery of the message to an inbox of the recipient. In some embodiments, the determination can be based on the computational analysis techniques used to identify the bot information from Step404.

In some embodiments, the determination can indicate whether to retrieve content from a network location (e.g., Steps408-410, discussed below), retrieve alternate content from an associated alternate content database (e.g., Steps412-414, discussed below), and/or enable sharing of the message (and/or its associated content, such as the advertisement from Steps408-410) (e.g., Steps416-418, as discussed below).

In some embodiments, the determination can further indicate when to perform the actions. In some embodiments, the bot information can indicate a timing of when to perform an action. In some embodiments, such timing can be associated with delivery of the message (e.g., when the message is populated in the recipient's inbox). In some embodiments, the timing can be associated with the recipient opening the message. In some embodiments, a particular type of action can be performed upon delivery and another can be performed upon opening of the message.

In some embodiments, Step406can include determining the type of action(s) and a timing of when to perform the action(s), then delivering the message to the recipient and monitoring for activity by the recipient related to the message according to the timing. Thus, in some embodiments, Steps408,412and/or416are performed (and their subsequent steps) according to the timing of the action. That is, in some embodiments, these steps can be performed when the recipient opens the message, and in some embodiments, they can be performed when the message is delivered to the recipient's inbox.

In some embodiments, Process400can proceed to Step408when engine300determines in Step406that the bot information identifies a network address corresponding to supplemental content. In some embodiments, the supplemental content can be any type of digitally renderable content, and can be identifiable via a URL included and/or embedded in a portion of the message as part of the bot information.

In Step408, engine300identifies the URL, navigates to that networked resource, and retrieves the content located at that network location. Then, in Step410, engine300generates a display of the retrieved content. The generated display can be within another window, interface or UI portion, as an overlay of the message window, in the background of the message window, in a sidebar, on a display of a paired device or other Internet of Things (IoT) connected device, as an augmented reality (AR) or virtual reality (VR) display, and the like, or some combination thereof.

By way of a non-limiting example, vendor X sends a message with bot information referenced in the message's header that references a URL. Upon the recipient opening the message, engine300can retrieve the content from the URL and display the retrieved content within an adjacent window to the message. This, therefore, enables the sender, here vendor X, to control which type and form of supplemental content is being displayed along with their message.

In some embodiments, Process400can proceed to Step412when engine300determines in Step406that the bot information includes instructions to retrieve alternate content that has been uploaded by the sender to an associated alternate content database. In some embodiments, the instructions can include a resource identifier (ID) for purposes of identifying the content within the database. The alternate content can be any type of digital content, such as, but not limited to, images, text, video, skins, and/or any other type of media or multi-media renderable by a device and/or displayable within a UI, and may be sponsored or unsponsored.

In Step412, engine300searches for and retrieves the content referenced by the bot information of the message from the alternate content database. Then, in Step414, in a similar manner as discussed above in relation to Step410, the retrieved content can be displayed.

Thus, in Steps412-414, engine300enables senders to take advantage of network capabilities of current user devices, such as 5G compatibility, by offloading content to an alternate content database (rather than sending it as part of the message), and causing the recipient's device to request and retrieve the content upon opening the message. This, among other technical advantages, can lead to reduced processing and resource usage by the handling server as the content being referenced is offloaded to another location that the recipient's client device locate and retrieve through an expenditure of its own resources (e.g., the client devices must expend processing capabilities to access the content, rather than the server expending the resources to provide the content).

By way of a non-limiting example, vendor X sends a message to a user about their recent purchase of a widget. The message includes bot information that references a video explaining how to construct and use the widget. Upon the recipient opening the message, the video is retrieved and can be auto-rendered in an adjacent window to the message's window.

In some embodiments, Process400can proceed to Step416when engine300determines in Step406that the bot information includes instructions for enabling the recipient to share the message. These instructions can be used in order to “nudge” the recipient to share the message in an effort to leverage the recipient's network to provide viral campaigning for the sender. In some embodiments, the instructions can comprise code, program logic and/or other executable objects (e.g., scripts) that can cause an interface object and/or UI to be displayed for sharing the message with other users.

In Step416, engine300analyzes contact information for the user, and identifies a set of contacts. In some embodiments, the set of contacts can be identified based on a criteria associated with, but not limited to, context of the message (e.g., context of the message content included in the message), interests of the contacts (e.g., from profile information of each contact), frequency of interaction with the recipient, recency of interaction with the recipient, demographics of the contacts, geographical information of the contacts, and the like, or some combination thereof. In some embodiments, a number of the contacts in the set can be based on a threshold so that only a top n number of contacts are identified.

For example, if user Bob receives an email about a widget, and his top3contacts are his two friends and his 15 year old son, while the son is a top contact, he may not be interested in widgets at this point in his life (but the two friends are interested based on their profile information); therefore, his son could be excluded from the identified contacts.

In Step418, engine300can then provide an interactive display that enables the recipient to share the message with the identified contacts. In some embodiments, Step418can involve a “share” button or interactive interface object(s) being displayed within, adjacent to and/or in association with the message. In some embodiments, the object/button of Step418can act as a “create message” button within an inbox that enables messages to be composed, addressed and sent to those identified contacts, where in some embodiments, the messages can be formatted as “forwarded” messages and in some embodiments, can be created as “new” messages that include at least a portion of the original message's content.

According to some embodiments, engine300can track the shares of the message and charge the message sender based on a variety of factors, such as, but not limited to, open rate, CTR, conversion rate, share rate, and the like.

In some embodiments, as discussed above, Process400can operate for other types/forms of content. For example, in addition to a recipient user viewing a message, the actions/operations of Process400can be triggered upon a user viewing an article on a web page. Thus, in this example, the provider of the web page and/or source of the article can function in the same capacity as the sender, and the bot information can be included within and/or associated with the web page, in a similar manner as discussed above.

For the purposes of this disclosure the term “user”, “subscriber” “consumer” or “customer” should be understood to refer to a user of an application or applications as described herein and/or a consumer of data supplied by a data provider. By way of example, and not limitation, the term “user” or “subscriber” can refer to a person who receives data provided by the data or service provider over the Internet in a browser session, or can refer to an automated software application which receives the data and stores or processes the data.