Patent Description:
As can be appreciated, the one or more intermediary steps undesirably introduce additional time, expense, and complexity into the process of viewing and accessing permitted content elements within software applications. Furthermore, because permitted content elements may be manually input to a software application by a device operator, a chance of element omission is undesirably increased, because the operator may not recollect all permitted content elements or may erroneously input one or more content elements.

The inability of previous approaches to automatically integrate permitted content elements into software applications can undesirably preclude a device operator from accessing the permitted content elements. Therefore, there is a long-felt but unmet need for a system or method that automatically integrates permitted content elements into software applications.

Briefly described, and according to one embodiment, aspects of the present disclosure generally relate to systems and processes for transmitting interactive content.

According to a first aspect, a process for transmitting interactive content including: A) transmitting content to a computing device associated with particular data, the content including a call to a beacon service and a secure identifier associated with the particular data; B) generating an association between the secure identifier and at least one public identifier based on the beacon service; C) identifying a subset of a plurality of permissible content elements based on a spend history corresponding to the particular data of an external computing system, wherein each of the plurality of permissible content elements are associated with a respective entity and each respective entity includes a plurality of respective locations; D) activating at least one permissible content element of the subset of the plurality of permissible content elements and storing the activated at least one permissible content element as at least one permitted content element; E) generating a plurality of deployment criteria associated with the at least one permitted content element based on the plurality of respective locations for the respective entity corresponding to the at least one permitted content element; F) receiving mapping metadata corresponding to an application, the mapping metadata including the at least one public identifier, the mapping metadata including at least one of: an origination location, a plurality of locations along a pathway, and a terminal location; G) determining whether the plurality of deployment criteria are satisfied for the at least one permitted content element based on the mapping metadata; and H) in response to the plurality of deployment criteria being satisfied, causing the at least one permitted content element to be rendered on a display of the application at a position corresponding to one of the plurality of respective locations.

According to a second apsect, the process for transmitting interactive content of the first aspect or any other aspect, wherein causing the at least one permitted content element to be rendered on the display of the application includes causing at least one media object associated with the at least one permitted content element to be rendered on the display.

According to a third aspect, the process for transmitting interactive content of the first aspect or any other aspect, further including: A) receiving, via the application, an indication that the at least one permitted content element is to be rendered on the display; and B) customizing a rendering of the at least one permitted content element.

According to a fourth aspect, the process for transmitting interactive content of the first aspect or any other aspect, wherein the steps of receiving mapping metadata, determining whether the plurality of deployment criteria are satisfied, and causing the at least one permitted content element to be rendered on the display of the application are performed by the application.

According to a fifth aspect, the process for transmitting interactive content of the fourth aspect or any other aspect, further including populating the application with the at least one permitted content element and the plurality of deployment criteria.

According to a sixth aspect, the process for transmitting interactive content of the first aspect or any other aspect, wherein the steps of receiving mapping metadata, determining whether the plurality of deployment criteria are satisfied, and causing the at least one permitted content element to be rendered on the display of the application are performed by an interchange platform and the process for transmitting interactive content further includes populating the interchange platform with the at least one permitted content element and the plurality of deployment criteria.

According to a seventh aspect, the process for transmitting interactive content of the first aspect or any other aspect, wherein the at least one of: an origination location, a plurality of locations along a pathway, and a terminating location includes at least one location associated with a global location system.

According to an eighth aspect, the process for transmitting interactive content of the first aspect or any other aspect, wherein the mapping metadata is received from an interchange platform and causes the at least one permitted content element to be rendered on the display includes: A) determining a proffer amount based on metadata associated with the at least one permitted content element; B) in response to receiving the metadata, transmitting a proffer for the proffer amount to the interchange platform.

According to a ninth aspect, the process for transmitting interactive content of the first aspect or any other aspect, wherein determining whether the plurality of deployment criteria are satisfied includes determining whether at least one of the plurality respective locations for the at least one permitted content element is within a predetermined separation length from the pathway.

According to a tenth aspect, the process for transmitting interactive content of the first aspect or any other aspect, wherein determining whether the plurality of deployment criteria are satisfied includes determining whether at least one of the plurality respective locations for the at least one permitted content element is within a predetermined detour time from the pathway.

According to an eleventh aspect, the process for transmitting interactive content of the first aspect or any other aspect, wherein the external computing system and the application are controlled by a single operator.

According to a twelfth aspect, the process for transmitting interactive content of the first aspect, wherein the computing device executes the application.

According to a thirteenth aspect, a computer system including: A) a first portion of a distributed architecture coupled for intercommunication to an external computing system and located behind a firewall, wherein the first portion is configured to: <NUM>) transmit content to a computing device associated with particular data, the content including a call to a beacon service and the secure identifier; <NUM>) identify a subset of a plurality of permissible content elements based on a spend history corresponding to the particular data of the external computing system, wherein each of the plurality of permissible content elements are associated with a respective entity and each respective entity includes a plurality of respective locations; and <NUM>) activate at least one permissible content element of the subset of the plurality of permissible content elements and storing the activated at least one permissible content element as at least one permitted content element; and B) a second portion of the distributed architecture located outside of the firewall coupled for intercommunication to the first portion of the distributed architecture, wherein the second portion is configured to: <NUM>) generate an association between the secure identifier and at least one public identifier based on the beacon service; <NUM>) generate a plurality of deployment criteria associated with the at least one permitted content element based on the plurality of respective locations for the respective entity corresponding to the at least one permitted content element; <NUM>) receive mapping metadata from an application including the at least one public identifier, the mapping metadata including at least one of: an origination location, a plurality of locations along a pathway, and a terminating location; <NUM>) verify that the plurality of deployment criteria are satisfied for the at least one permitted content element based on the mapping metadata; and <NUM>) in response to the plurality of deployment criteria being satisfied, cause the at least one permitted content element to be rendered on a display of the application at a position corresponding to one of the plurality of respective locations.

According to a fourteenth aspect, the computer system of the thirteenth aspect or any other aspect, wherein the second portion is further configured to verify that the plurality of deployment criteria are satisfied for the at least one permitted content element further based on correlating a current time to scheduling data of the respective entity corresponding to the at least one permitted content element.

According to a fifteenth aspect, the computer system of the thirteenth aspect or any other aspect, wherein the plurality of deployment criteria includes at least one of: a time span, a set of particular days, a geofence, and a weather condition.

According to a sixteenth aspect, a system for transmitting interactive content including: A) a data store including data describing: <NUM>) a plurality of permitted content elements associated with a secure identifier, wherein the secured identifier corresponds to particular data; and <NUM>) a respective entity for each of the plurality of permitted content elements, wherein each respective entity includes a plurality of respective locations; and B) at least one computing device in communication with the data store, the at least one computing device being configured to: <NUM>) generate an association between the secure identifier and at least one public identifier; <NUM>) generate a plurality of deployment criteria associated with the plurality of permitted content elements based on the plurality of respective locations for the respective entity; <NUM>) receive mapping metadata and the at least one public identifier, the mapping metadata including at least one of: an origination location, a plurality of locations along a pathway, and a terminating location; <NUM>) identify the plurality of permitted content elements based on the association between the secured identifier and the at least one public identifier; <NUM>) in response to identifying the plurality of permitted content elements, verify that the plurality of deployment criteria are satisfied for at least one of the plurality of permitted content elements based on the mapping metadata; and <NUM>) cause the at least one of the plurality of permitted content elements to be rendered on a display at a position corresponding to one of the plurality of respective locations.

According to a seventeenth aspect, the system for transmitting interactive content of the sixteenth aspect or any other aspect, wherein the at least one computing device is further configured to: A) verify that the at least one of the plurality of permitted content elements was utilized; and B) in response to verifying that the at least one of the plurality of permitted content elements was utilized, adjust at least one of the plurality of criteria.

According to an eighteenth aspect, the system for transmitting interactive content of the sixteenth aspect or any other aspect, wherein the at least one computing device is further configured to: A) identify an article associated with one of the plurality of permitted content elements; and B) verify that the article is available at a particular one of the plurality of respective locations from the respective entity associated with the one of the plurality of permitted content elements; and cause the at least one of the plurality of permitted content elements to be rendered on the display based on verifying that the article is available.

According to a nineteenth aspect, the system for transmitting interactive content of the sixteenth aspect or any other aspect, wherein the at least one computing device is further configured to: A) generate a communication corresponding to the data; and B) transform media corresponding to the at least one of the plurality of permitted content elements to be rendered by adding the communication to the media.

According to a twentieth aspect, the system for transmitting interactive content of sixteenth aspect or any other aspect, wherein the at least one computing device is further configured to verify that the plurality of deployment criteria are satisfied by determining whether at least one of the plurality respective locations is within a predetermined radius from the origination location.

The accompanying drawings illustrate one or more embodiments and/or aspects of the disclosure and, together with the written description, serve to explain the principles of the disclosure. Wherever possible, the same reference numbers are used throughout the drawings to refer to the same or like elements of an embodiment, and wherein:.

For the purpose of promoting an understanding of the principles of the present disclosure, reference will now be made to the embodiments illustrated in the drawings and specific language will be used to describe the same. It will, nevertheless, be understood that no limitation of the scope of the disclosure is thereby intended; any alterations and further modifications of the described or illustrated embodiments, and any further applications of the principles of the disclosure as illustrated therein are contemplated as would normally occur to one skilled in the art to which the disclosure relates. All limitations of scope should be determined in accordance with and as expressed in the claims.

Whether a term is capitalized is not considered definitive or limiting of the meaning of a term. As used in this document, a capitalized term shall have the same meaning as an uncapitalized term, unless the context of the usage specifically indicates that a more restrictive meaning for the capitalized term is intended. However, the capitalization or lack thereof within the remainder of this document is not intended to be necessarily limiting unless the context clearly indicates that such limitation is intended.

Aspects of the present disclosure generally relate to systems and processes for transmitting interactive content. According to one embodiment, the present systems and processes allow for automatic display of permitted content elements in a navigation application running on a computing device (referred to herein as a "Touch Point"), the permitted content elements corresponding to a spend history associated with a user of the computing device.

As used herein, "content elements" may generally refer to electronic offers, promotions, advertisements, or awards for goods and/or services.

As used herein, "permissible content elements" may generally refer to content elements that can be activated, permitted, and/or selected, for example, by inputs to a Touch Point (as described herein) or other devices rendering the permissible content elements. In one or more embodiments, permissible content elements are associated with a user (and particular data thereof, such as a user account, identifier(s), etc.) based on a spend history corresponding to transactions made by the user (e.g., transaction data). According to one embodiment, a permissible content element is associated with an entity (e.g., a business providing the good or service to which the permissible content element pertains) and at least one physical location associated with the entity (e.g., a place of business, such as a store).

As used herein, "permitted content elements" may generally refer to permissible content elements that have been activated, permitted, or selected by an input to a Touch Point or other device (or in at least one embodiment, viewed or displayed via a Touch Point). In various embodiments, a permissible content element becomes a permitted content element when a Touch Point performs one or more actions including, but not limited to: <NUM>) displaying the permissible content element in a communication portal or navigation application initiated by the Touch Point (e.g., and, in some embodiments, in coordination with one or more other system elements) in response to a request from a user operating the Touch Point; and <NUM>) receiving an input from a user that activates and/or selects the permissible content element displayed in the communication portal or navigation application.

The following paragraph provides an exemplary scenario of the present systems and processes, according to one embodiment of the present disclosure.

In one example, a Touch Point receives an input from a user requesting a communication portal with a transactional environment. The Touch Point transmits the request to an institution server of the transactional environment that provides the communication portal to the Touch Point, the communication portal including an instruction and a secure identifier that causes the Touch Point to call to a beacon service and provide the secure identifier and a public or device identifier stored in memory. The transactional environment, via receipt of the call at the beacon service, associates the secure identifier and the public or device identifier. The transactional environment injects permissible content elements (each associated with an entity and at least one physical location thereof) into the communication portal, the permissible content elements corresponding to a spend history associated with the user. The Touch Point renders the permissible content elements on the display and receives an input from the user that causes activation of one of the permissible content elements. Upon receipt of the activating or selecting input, the permissible content element is stored as a permitted content element (e.g., the transition being recorded at one or more content element databases in response to communications between the Touch Point and other system elements).

In the same example, the Touch Point receives an input from the user causing the Touch Point to execute a navigation application. The Touch Point executes and runs the navigation application and the system receives mapping metadata and the public identifier from the navigation application, the mapping metadata including an origination location, locations along a pathway and/or a terminal location. The system processes the mapping metadata and determines that deployment criteria associated with the permitted content element are satisfied. In response to determining the deployment criteria to be satisfied, the system causes the Touch Point to render the permitted content element (or a different content element based on the permitted content element) on a display of the navigation application. Thus, in the example described above, the system automatically deploys a permitted content element to a user's navigation application based on satisfaction of deployment criteria by mapping metadata, the permitted content element being associated with a spend history of the user and corresponding to a physical location of an entity associated with the permitted content element.

Referring now to the figures, for the purposes of example and explanation of the fundamental processes and components of the disclosed systems and methods, reference is made to <FIG>, which illustrates an exemplary system <NUM> for transmitting interactive content. As will be understood and appreciated, the exemplary system <NUM> shown in <FIG> represents merely one approach or embodiment of the present system, and other aspects are used according to various embodiments of the present system.

According to one embodiment, the system <NUM> may include an architecture of distributed computing resources divided into at least a first portion and a second portion. In various embodiments, a first portion of the system <NUM> includes, but is not limited to, a transaction environment <NUM> (including other elements described herein) and a second portion includes, but is not limited to, an offer management system (OMS) <NUM>, demand-side platform <NUM>, interchange platform <NUM>, publisher web server <NUM>, navigation application <NUM>, Touch Point <NUM>, and an external data information system <NUM> (including other elements described herein). One or more communication firewalls <NUM> secure and control transmissions between elements of the first and second portions.

In one or more embodiments, the system <NUM> includes an external computing system, such as a transaction environment <NUM>. According to one embodiment, the external computing system includes a system that performs transactional and navigational processes. In at least one embodiment, the transaction environment <NUM> includes an offer placement system (OPS) <NUM> including at least one processor and at least one data store (e.g., including one or more databases). In various embodiments, the OPS <NUM> receives and aggregates de-identified transactions (e.g., organized into transaction histories) associated with a user or particular data associated with a user or user account. According to one embodiment, the particular data is data associated with one or more user accounts and/or one or more operators of Touch Points <NUM> and/or data associated with a patron of a particular institution in control of the transaction environment <NUM> (e.g., a banking institution). In one or more embodiments, the particular data includes spend data (e.g., transactional data and/or metadata) sourced from a spend history associated with d a user. In at least one embodiment, the OPS <NUM> organizes the particular data (or associated data and metadata, such as de-identified transactions) of a plurality of users into segments according to one or more techniques described in <CIT>, which is incorporated herein by reference as if set forth in its entirety.

In at least one embodiment, the OPS <NUM> provides aggregated, de-identified transactions to an offer management system (OMS) <NUM>. In one or more embodiments, the OMS <NUM> includes one more processors, servers, and data stores (e.g., including one or more databases). According to one embodiment, the OMS <NUM> includes one or more secured databases (e.g., in a secured data store) that contain identified data associated with each of the one or more users and/or particular data thereof. In at least one embodiment, the identified data includes, but is not limited to, phone numbers, device identifiers, email addresses, and other information associated with the one or more users or their respective particular data. In various embodiments, the one or more secured databases may be inaccessible to entities and other third-parties in communication with the OMS <NUM>.

In at least one embodiment, the OMS <NUM> processes the de-identified transactions and associated particular data (according to selections received from one or more entities) from the OMS <NUM>. In one or more embodiments, the OMS <NUM> performs actions including, but not limited to, identifying a subset of a plurality of permissible content elements based on a history (e.g., a spend history, such as a transaction history) corresponding to the one or more users (and/or particular data thereof, such as user profiles) associated with the transaction environment <NUM>, each of the plurality of permissible content elements being associated with a respective entity and each respective entity including at least one respective location (e.g., a physical place of business).

In one or more embodiments, the system <NUM> includes one or more institution transaction processors <NUM> that transmit de-identified transaction data and metadata to the OPS <NUM>. For example, the one or more institution transaction processors <NUM> transmit one or more histories (e.g., dataset) of de-identified transactions to the OPS <NUM>. In the same example, the OPS <NUM> aggregates and transmits one or more de-identified histories to the OMS <NUM> that provides a campaign portal for entities (such as advertisers) to establish and manage campaigns for permissible content element deployment to a segment generated by the OMS <NUM> and associated with a subset of the one or more histories. Continuing the same example, the OMS <NUM> generates segments for targeted interactive content delivery campaigns for one or more entities by processing the one or more de-identified histories with regard to segment criteria from the one or more entities to identify a subset of the users (e.g., and particular data thereof) whose associated spend history (and/or other information) satisfy the segment criteria.

According to one embodiment, a segment includes a plurality of de-identified users or particular data (e.g., user accounts or identifiers) to which an entity desires to transmit permissible content elements. In various embodiments, as described in the incorporated U. patent applications, the segment is generated based on particular criteria. In one or more embodiments, each segment includes a segment identifier and data included in the segment includes a public identifier and a secure identifier. In at least one embodiment, a secure identifier is associated with a third-party institution (e.g., bank, credit union, etc.) of the user corresponding to the particular data. According to one embodiment, the third-party institution also provides and/or controls the navigation application <NUM>. In various embodiments, the navigation application <NUM> is not provided by the third-party institution, but is provided by a different party, such as, for example, Google® or the company providing the OMS <NUM>. In at least one embodiment, a public identifier is an identifying string that has been securely synched or otherwise associated with the secure identifier according to one or more techniques described herein and in <CIT>, which is incorporated herein by reference as if set forth in its entirety.

In various embodiments, the transaction environment <NUM> includes an institution server <NUM>. In at least one embodiment, the institution server <NUM> is a plurality of institution servers <NUM>, as can be appreciated. In one or more embodiments, the institution server <NUM> is communicably coupled to a Touch Point <NUM>, and communications therebetween are secured and controlled by a firewall <NUM>. According to one embodiment, the institution server <NUM> generates an electronic communication portal (not shown) accessible from and rendered on the Touch Point <NUM>. In at least one embodiment, the communication portal allows the user associated with the Touch Point <NUM> to access and view a transaction or spend history in a secure and private manner. In at least one embodiment, the communication portal is a banking portal.

In at least one embodiment, as described in the incorporated U. patent applications, the system <NUM> injects permissible content elements into the communication portal rendered on a display of the Touch Point <NUM>. According to one embodiment, the Touch Point <NUM> is operative to receive inputs from the user that cause activation, permission, or selection of one or more of the permissible content elements. In at least one embodiment, an input that causes activation or selection of a permissible content element as referred to as a permission indication. In various embodiments, a permission indication is generated by the Touch Point <NUM> in response to one or more of: <NUM>) receiving input selecting a permissible content element; <NUM>) receiving input activating a permissible content element; and <NUM>) displaying a permissible content element in a communication portal or navigation application <NUM> in response receipt of a request from the user.

In various embodiments, the institution server <NUM> receives and transmits permission indications for permissible content elements to the OPS <NUM> and/or OMS <NUM> (or one or more other elements of the system <NUM> described herein). According to one embodiment, the permission indication causes the activated or selected permissible content element to convert to a permitted content element. In one or more embodiments, the conversion is recorded in a content elements database <NUM>. As described herein, in at least one embodiment, the permitted content element is a content element that is rendered by the Touch Point <NUM> on a display of a navigation application <NUM> when the system <NUM> determines that deployment criteria associated with the permitted content element have been satisfied (e.g., based on mapping metadata associated with the navigation application <NUM>). In some embodiments, the display of the navigation application <NUM> can refer to a display device corresponding to a computing device that executes the navigation application <NUM>. In other embodiments, the display of the navigation application <NUM> can correspond to another display device, such as a display device that is mirroring with a computing device that executes the navigation application <NUM> or another display device that renders content of the navigation application <NUM>.

In one example, the institution server <NUM> receives, from the OPS <NUM>, permissible content elements associated with a segment. In the same example, the institution server <NUM> receives a request from a Touch Point <NUM> for access to a communication portal. Continuing the same example, the request includes a secure identifier associated with a particular subset of a plurality of users (and particular data thereof) in the segment, thereby allowing the institution server <NUM> to uniquely identify and associate the subset of the users and particular data and the Touch Point <NUM>. In the same example, the subset of the users and particular data is associated with a user of the Touch Point <NUM>. Continuing with the same example, the institution server <NUM> transmits the request to the OPS <NUM>, generates the requested communication portal, and automatically injects (e.g., via a script, such as JavaScript™ loaded from a script server) the permissible content elements into the communication portal. In the same example, the permissible content elements are provided by the OPS <NUM> and are included by the OPS <NUM> based on a spend history of the user associated with the subset of the users and particular data.

Continuing the same example, when the user associated with the subset of the users and particular data requests the communication portal (e.g., via the Touch Point <NUM>), the Touch Point <NUM> renders the communication portal on a display of the Touch Point <NUM>, including the permissible content elements as interactive elements. In the same example, when the user selects or activates one or more of the permissible content elements, the Touch Point <NUM> automatically transmits a permission indication to the institution server <NUM> (or one or more other elements of the system <NUM> described herein). Continuing the same example, the institution server <NUM> transmits the permission indication to the OPS <NUM> and/or OMS <NUM> that causes conversion of the selected or activated one or more permissible content elements to one or more permitted content elements, the conversion being recorded or stored in a content elements database <NUM>.

Alternatively, or in addition, selection by the user (associated with the subset of the users and particular data) of the one or more permissible content elements causes the Touch Point <NUM> to automatically call to a beacon service <NUM>. According to one embodiment, the call to the beacon service <NUM> includes, but is not limited to, the Touch Point <NUM> accessing a single pixel webpage and providing a secure identifier and a public identifier thereto (for identifier association processes described herein). In at least one embodiment, the call to the beacon service <NUM> is transmitted to the OMS <NUM>, thereby causing the system to match various identifiers associated with the user and thereby match one or more permitted content elements with the various identifiers associated with the user. In some embodiments, associating the one or more permitted content elements with various identifiers may enable the system to serve the one or more permitted content elements (or a related content element) to the user via a different application or computing system (while the user remains anonymous).

According to one embodiment, as discussed herein, a permissible content element is an electronic offer or promotion for a good or service (e. g that may be loaded onto or associated with a debit or credit card of a user) that provides a reward and/or a particular rate or discount for good or service described in the offer. As described herein, permissible content elements are rendered within an application, on displays of Touch Points <NUM> or other electronic devices that include or are connected to displays. In one or more embodiments, the permissible content elements are selectable or activateable. In various embodiments, upon receiving an input (e.g., a touch or click) selecting or activating a permissible content element, the Touch Point <NUM> causes transmission of a permission indication, to the system <NUM>. In one or more embodiments, transmission of the permission indication includes, but is not limited to: <NUM>) transmitting a permission signal to the OMS <NUM>; and <NUM>) updating one or more permission fields in the content database <NUM> associated with the permitted content element to indicate the received permission. According to one embodiment, a communication portal transmits the permission indication to the institution server <NUM>, the institution server <NUM> provides the permission indication to the OPS <NUM>, and the OPS <NUM> provides the permission indication to the OMS <NUM> (e.g., which causes a content elements database <NUM> to convert a corresponding permissible content element to a permitted content element).

According to one embodiment, permissible content elements are generated and selectively transmitted based on a history of transactions (or other recorded actions and information) associated with a user. In at least one embodiment, the transaction environment <NUM> includes a transactions database <NUM> and a de-identified transactions database <NUM> from which the history of transactions may be accessed, updated, and maintained. In various embodiments, an institution transaction processor <NUM> performs de-identification processes on transactions of the transactions database <NUM> to generate and populate the de-identified transactions database <NUM> with the de-identified transactions. In one or more embodiments, the transactions database <NUM> and de-identified transactions database <NUM> are each representative of a plurality of databases <NUM> and a plurality of databases <NUM> as can be appreciated.

In at least one embodiment, the institution transaction processor <NUM> provides the de-identified transactions to the institution server <NUM> that transmits the de-identified transactions to the OPS <NUM>. In at least one embodiment, transmissions between the OPS <NUM> and the institution server <NUM> are secured by a de-identification firewall <NUM> that prevents transmission of personally identifying transaction data between any elements of the system <NUM> other than the institution server <NUM> and institution transaction processor <NUM>. In various embodiments, the OPS <NUM> provides the de-identified transactions and particular data associated therewith to the OMS <NUM>. In at least one embodiment, the OMS <NUM> generates or receives one or more permissible content elements for the user associated with the particular data based on the de-identified transactions associated therewith, as well as deployment criteria, media, and customization data received from an entity. In one or more embodiments, the OPS <NUM> receives permissible content elements from the OMS <NUM> and transmit the permissible content elements to the institution server <NUM> for inclusion in communication portals generated thereby.

In at least one embodiment, the system <NUM> includes a content elements database <NUM> that stores and organizes content elements, including permissible content elements generated by the OMS <NUM>, as well as permitted content elements (e.g., permissible content elements for which a permission indication has been received). In various embodiments, the content elements database <NUM> organizes the permissible and permitted content elements based on users, particular data and/or public identifiers, secure identifiers, and/or segment identifiers associated therewith. In at least one embodiment, the OMS <NUM> is operative to transmit permissible and/or permitted content elements from the content elements database <NUM> to one or more of the OPS <NUM>, the Touch Point <NUM>, the demand-side platform <NUM>, and/or other elements of the system <NUM>. According to one embodiment, transmissions from the OMS <NUM> include segment, device, secure, and/or public identifiers associated with the permissible and/or permitted content elements being transmitted.

In one or more embodiments, the system <NUM> includes a deployment criteria database <NUM> that stores and organizes deployment criteria generated or received by the OMS <NUM> (e.g., in response to receiving criteria selections from entities in communication therewith). As described herein, the OMS <NUM> compares mapping metadata to associated deployment criteria from the deployment criteria database <NUM> and, upon determining that the associated deployment criteria are satisfied, transmits associated permitted content elements to one or more of the publisher web server <NUM>, the navigation application <NUM>, the Touch Point <NUM>, a demand-side platform (DSP) <NUM>, an interchange platform <NUM>, and/or other elements of the system <NUM>.

In at least one embodiment, the system <NUM> includes the demand-side platform (DSP) <NUM> operative to communicate with the interchange platform <NUM> and the OMS <NUM>. In various embodiments, the DSP <NUM> receives permitted content elements from the OMS <NUM> and generates and communicates bids or proffers to the interchange platform <NUM>. According to one embodiment, the interchange platform <NUM> is an advertisement exchange platform. In at least one embodiment, the proffers are directed towards obtaining a right (e.g., an advertisement right) to provide a permitted content element to the navigation application <NUM> running on the Touch Point <NUM> (or other electronic device) that is associated with the user (e.g., or data or identifiers associated with the user) and permitted content elements. According to one embodiment, a proffer may include a predetermined amount (e.g., a bid) for purchasing permission to publish a permitted content element (or any content element) on a display of the navigation application <NUM>. In one or more embodiments, the predetermined amount may be an amount stored in a database of the DSP <NUM> (not shown) and associated with the entity that dictated deployment criteria determined to be satisfied by the OMS <NUM>, navigation application <NUM>, DPS <NUM>, or interchange platform <NUM> (based on received mapping metadata). In at least one embodiment, the predetermined amount may be set based on a selection received from the entity during a permissible content campaign process executed by the OMS <NUM> for the entity (e.g., the same process by which the OMS <NUM> received the permissible content elements and associated deployment criteria).

In various embodiments, the content elements database <NUM> is organized based on received permission indications corresponding to the one or more users (e.g., or particular data thereof) associated with the stored permissible content elements. According to one embodiment, upon the system <NUM> receiving a permission indication from a Touch Point <NUM> for a particular permissible content element, the content elements database <NUM> converts the particular permissible content element to a particular permitted content element by updating metadata thereof.

In one example, the content elements database <NUM> include one or more multi-dimensional data arrays for organizing permissible content elements. In the same example, the one or more multi-dimensional data arrays include axes for permissible content identifiers, segment identifiers, public identifiers, and/or secure identifiers, and other information. Also, in the same example, fields of the one or more multi-dimensional data arrays include Boolean operators for indicating whether a permission indication has been received for a permissible content element associated with a user (or particular data thereof). As described herein, permissible content elements for which permission has been received are generally referred to as permitted content elements. In some embodiments, the Boolean operators are stored in bit arrays in sets (e.g., 64bit, <NUM> bit, or <NUM> bit sets).

In at least one embodiment, the OMS <NUM> performs a permissible content campaign process based on selections received from an entity. In one or more embodiments, the OMS <NUM> generates (or receive from the entity) permissible content elements and selections for deployment criteria and/or a proffer. In at least one embodiment, the OMS <NUM> stores the permissible content elements in the content elements database <NUM> and the deployment criteria in the deployment criteria database <NUM>, along with segment, secure, and/or public identifiers associated with users (and particular data thereof) to which the entity desires to provide the permissible content elements. In various embodiments, the OMS <NUM> stores the proffer amount and/or provides the proffer amount to the DSP <NUM> that stores the proffer amount in the database thereof, along with the identifiers associated with the permissible content elements. According to one embodiment, when the OMS <NUM> determines that the associated deployment criteria have been satisfied (e.g., based on received mapping metadata), the OMS <NUM> causes the DSP <NUM> to retrieve and transmit the stored, associated proffer amount and permitted content elements, to the interchange platform <NUM>. In at least one embodiment, the interchange platform <NUM> confirms purchase of the publishing permissions (at the proffer amount) with the DPS <NUM> and the DPS <NUM> instructs OMS <NUM> to deploy the permitted content element to the Touch Point <NUM> of each of the users (or particular data) of the segment associated with the deployment criteria that were determined to be satisfied.

In at least one embodiment, the navigation application <NUM> refers to a location-based software application running on an electronic device, such as, for example, the Touch Point <NUM>, tablets, personal computers, or any other suitable electronic device configured to receive and transmit electronic information. In at least one embodiment, the navigation application <NUM> is operated by a third-party, or may be a "native" navigation application <NUM>. As used herein, "native" generally refers to a quality of being substantially controlled and operated by the system <NUM> (e.g., or a system operating the system <NUM>). In one or more embodiments, the navigation application <NUM> is in communication with, via an application programming interface (API) <NUM>, the publisher web server <NUM> that facilitates communication between the navigation application <NUM> and other elements of the system <NUM>.

In at least one embodiment, the API <NUM> is a native or a third-party API. In one example, the API <NUM> is a third-party API <NUM> operated by the same third-party operating the navigation application <NUM>. In another example, the API <NUM> is a native API operated by the same party substantially operating and controlling the system <NUM>. According to one embodiment, the API <NUM> provides software routines, protocols, and tools for communicating with and configuring actions of the navigation application <NUM>.

In various embodiments, the system <NUM> includes an external data information system <NUM>. In at least one embodiment, the external data information system <NUM> performs functions including, but not limited to communicating with third-party systems (not shown) of entities to determine availability of goods and/or services, to determine whether a user has accessed the goods and/or services and storing transaction data (e.g., SKU-level transaction data). According to one embodiment, the external data information system <NUM> includes, but is not limited to, a transaction detail (TDS) system <NUM> communicably coupled to a retail transactions database <NUM> and a third-party segment database <NUM>. In one or more embodiments, the TDS system <NUM> de-identifies transactional data from the retail transactions database <NUM> and provide the de-identified transactional data to the OMS <NUM>. According to one embodiment, TDS system <NUM> receives transmissions from the third-party systems and populate the retail transactions database <NUM> and third-party segment database <NUM> with data included therein. In at least one embodiment, the transmission data includes, but is not limited to, the transactional data and/or segment data. In at least one embodiment, the TDS system <NUM> provides the segment data to the OMS <NUM> for use in segment and permissible content generation processes described herein. In various embodiments, the segment data includes, for example, particular transaction categories, patterns, or other traits for a desired subset of a plurality of users and/or particular data thereof (such as user accounts), the desired subset being a subset of the users which an entity would like to target with permissible content elements.

In at least one embodiment, the Touch Point <NUM> is any electronic device capable of running the navigation application <NUM>. In one or more embodiments, the Touch Point <NUM> includes, but is not limited to, mobile devices, tablets, portable computers, and global positioning system (GPS) devices, among others. In at least one embodiment, the Touch Point <NUM> includes or is communicably coupled to a display. In various embodiments, the display includes, for example, one or more devices such as liquid crystal display (LCD) displays, gas plasma-based flat panel displays, organic light emitting diode (OLED) displays, electrophoretic ink (E ink) displays, LCD projectors, or other types of display devices, etc..

In at least one embodiment, the Touch Point <NUM> includes a device identifier, such as, for example, a hardware address, MAC address, mobile advertising identifier, or other identifier that allows the system <NUM> to uniquely identify the Touch Point <NUM>. According to one embodiment, the device identifier is generated by the system <NUM> (for example, by the OMS <NUM>) and transmitted to and stored at the Touch Point <NUM>. In one or more embodiments, the Touch Point <NUM> includes cookie data, the cookie data having been provided to the Touch Point <NUM> during an interaction with a content element (such as an offer or advertisement) in an internet-based environment. In at least one embodiment, the cookie data includes a public identifier generated by the system <NUM> to uniquely identify users and/or particular data associated with the Touch Point <NUM>.

In one or more embodiments, the system <NUM> includes a beacon service <NUM> that facilitates pairing or associating of a secured identifier with a public identifier. In at least one embodiment, the beacon service receives beacon calls from the Touch Point <NUM>, for example, in instances where the Touch Point <NUM> receives a transmission from the institution server <NUM> that causes the Touch Point <NUM> to transmit a secure identifier and a public identifier in a transmission to the beacon service <NUM>. In various embodiments, the transmission from the institution server <NUM> is referred to as a "beacon" and includes, but is not limited to, an instruction for the Touch Point <NUM> to make a request to the beacon service <NUM>, the instruction including the secure identifier. In one example, the beacon is a single pixel image HTML code with a URL pointing to the beacon service <NUM>. Further description of the beacon service <NUM> and functions thereof are provided in <CIT>, incorporated herein by reference as if set forth in its entirety.

In at least one embodiment, the transaction environment <NUM> and navigation application <NUM> are provided and/or controlled by a single entity (or other entity providing services to the user). In one or more embodiments, as shown in <FIG>, the transaction environment <NUM> transmits and receives information to and from the navigation application <NUM>. In one example, one or more institution servers <NUM> communicate, through a firewall <NUM>, with the navigation application <NUM> or a Touch Point <NUM> in communication therewith. In another example, an offer placement system (OPS) communicates, via a publisher web server <NUM> and/or an API <NUM>, with the navigation application <NUM>.

In one or more embodiments, the transaction environment <NUM> transmits one or more permissible content elements to the navigation application <NUM> running on the Touch Point <NUM>, the Touch Point <NUM> and/or navigation application <NUM> being associated with particular data (e.g., a user account) of a user. According to one embodiment, the navigation application <NUM> causes the Touch Point <NUM> to render, on a display, the one or more permissible content elements, including fields for receiving selection or activation inputs therefor. In at least one embodiment, the navigation application <NUM> receives a selection or activation input for one of the one or more permissible content elements (e.g., causing conversion to a permitted content element). In at least one embodiment, in response to receiving the selection or activation input, the navigation application <NUM> causes the Touch Point <NUM> to render a display of the navigation application <NUM> including at least one location of an entity associated with the permitted content element. According to one embodiment, the navigation application <NUM> transmits the permission input to the transaction environment <NUM> that applies an offer associated with the permitted content element to a credit card, debit card, payment account, etc. of a user, thereby allowing the user to access the offer at the at least one location.

Turning to <FIG>, as will be understood by one having ordinary skill in the art, the steps and processes shown in <FIG> may operate concurrently and continuously, are generally asynchronous and independent, and are not necessarily performed in the order shown. In various embodiment, the steps of <FIG> correspond to steps of a method performed by one or more components of the system <NUM> (<FIG>).

<FIG> shows a flowchart of an exemplary content permission process <NUM>. At step <NUM>, the process <NUM> includes receiving a request for access to a communication portal. In at least one embodiment, the request is received at an institution server <NUM> from a Touch Point <NUM> associated with a. In various embodiments, in response to the request, the institution server <NUM> transmits a secure identifier and executable code to the Touch Point <NUM> that causes the Touch Point <NUM> to "call" (e.g., access) a beacon web address (e.g., a single pixel HTML address) associated with a beacon service <NUM>. According to one embodiment, the secure identifier is generated and transmitted by the OPS <NUM> to the institution server <NUM> that transmits the secure identifier the Touch Point <NUM>. In at least one embodiment, the secure identifier is used by the system <NUM> to uniquely identify the user and/or the particular data associated with the user.

In one or more embodiments, a beacon "call" (e.g., transmission) from the Touch Point <NUM> to the beacon service <NUM> (e.g., received at the beacon web address) includes the secure identifier and a public identifier stored on the Touch Point <NUM>. As will be understood from discussions herein, a public identifier is an identifier dropped on the Touch Point <NUM> during a cookie interaction (e.g., as a result of the Touch Point <NUM> receiving a cookie in response to the Touch Point <NUM> accessing particular web-based content), is a mobile device identifier (e.g., advertising identifier), and/or previous beacon call. In various embodiments, the beacon call is received from the Touch Point <NUM> at the beacon service <NUM>. In one or more embodiments, the beacon service provides the secure identifiers and public identifiers to the OMS <NUM>.

As will be understood from discussions herein, the system <NUM> may be configured to track a user (anonymously) across multiple devices via identifier matching. For example, each time a user accesses a communications portal (e.g., via a log in), a secure identifier is associated with the device used by the user to access the communications portal (e.g., via the process discussed above). If the user accesses the communications portal with multiple devices, the system <NUM> may match the secure identifier (which stays constant) with multiple public identifiers (e.g., device identifiers), thereby associating multiple devices with a secure identifier.

In various embodiments, the request causes the institution transaction processer <NUM> to retrieve transactions associated with the secure identifier from the transactions database <NUM> for inclusion by the institution server <NUM> within the communication portal provided to and rendered on the corresponding Touch Point <NUM>.

At step <NUM>, the process <NUM> includes associating the secure identifier and public identifier at the OMS <NUM>, thereby uniquely identifying the user and particular data associated with the Touch Point <NUM> that performed the call to the beacon service <NUM>. Because the OMS <NUM> associates the transaction-related secure identifier with the external (e.g., content-related) public identifier, the system <NUM> can target the user (or particular data thereof, such as a user account) with permissible content elements through platforms outside of the transaction environment <NUM>. For example, prior to identifier association, the system <NUM> may only target the user with permissible content elements (based on a transaction history of the user) in a communication portal provided by the institution server <NUM>. In the same example, following identifier association, the system <NUM> may target the user and/or their particular data with permissible contents based on the transaction history on platforms including but not limited to: <NUM>) publicly accessible websites; <NUM>) software applications, including mobile device applications; and <NUM>) other platforms external to the transaction environment <NUM>.

At step <NUM>, the process <NUM> includes transmitting permissible content elements to the Touch Point <NUM> by including the permissible content elements in the communication portal. According to one embodiment, the OPS <NUM> and OMS <NUM> performs segment and campaign generation processes based on a de-identified transaction history associated with the user or their particular data. Based on the de-identified transaction history, the OMS <NUM> identifies a subset of a plurality of permissible content elements with which to target the user (or user account thereof) by including the subset of permissible content elements in the communication portal provided to the Touch Point <NUM> associated with the user (e.g., via the OPS). In at least one embodiment, the subset of the plurality of permissible content elements are identified based on one or more segments associated with the user or their particular data (e.g., as a result of segment generation processes).

As can be appreciated, the steps <NUM>-<NUM> occur at sufficient speeds such that rendering of the communication portal and inclusion of the permissible content elements with the communication portal is perceived, by the corresponding user, to have occurred substantially instantaneously. In other words, it will be understood by one of ordinary skill in the art that the steps <NUM>-<NUM> typically occurs on a below one millisecond time-frame, below one hundred millisecond time-frame, or below five hundred millisecond time-frame, such that there is little or no delay apparent to a user viewing the display of the Touch Point <NUM>.

At step <NUM>, the process <NUM> includes: <NUM>) receiving activation or selection of at least one permissible content elements; and <NUM>) converting the at least one permissible content element to at least one permitted content element based on receiving a permission indication associated with the activation or selection of the at least one permissible content elements from a Touch Point <NUM>. In one or more embodiments, receiving the activation or selection includes, but is not limited to, receiving a permission signal from the Touch Point <NUM> at the institution server <NUM> (e.g., via the provided communication portal) in response to receiving input selecting the one or more permissible content elements. In at least one embodiment, the permission signal includes identifiers for each of the at least one permitted content elements, as well as one or more of the secure identifier and the public identifier associated with the user and/or particular data thereof. According to one embodiment, the permission signal is provided by the institution server <NUM> to the OPS <NUM> and/or OMS <NUM> that causes the content element database <NUM> to activate the one or more permissible (now permitted) content elements, activation including updating one or more data fields associated with the user or their particular data to indicate that the one or more permissible content elements are permitted content elements.

For example, a user of the Touch Point <NUM> (and associated with particular data) requests access to and is provided, via the Touch Point <NUM>, a communication portal including a subset of a plurality of permissible content elements. In the same example, the Touch Point <NUM> receives input from the user selecting or activating a permissible content element of the subset of permissible content elements, thereby providing permission for the an offer, discount, etc. to be added to, or associated with, the user's debt card, credit card, or bank account.

Continuing with this example, the system then causes the permissible (now permitted; selected) content element to be rendered on a display of a navigation application <NUM> running on the Touch Point <NUM> (e.g., upon satisfaction of deployment criteria, as described herein). Continuing the same example, the institution server <NUM> receives a permission signal from the Touch Point <NUM>, the permission signal including identifiers associated with the permitted content element (e.g., and stored in metadata thereof). In the same example, the OMS <NUM> receives the identifiers and causes the content elements database <NUM> to activate the one or more permissible (now permitted) content elements by updating one or more fields associated with the user (and/or the one or more permissible content elements) to indicate that the one or more permissible content element are now permitted content elements.

At step <NUM>, the process <NUM> includes generating deployment criteria that, when satisfied, causes the one or more permitted content elements to be rendered on a display of the navigation application <NUM> on the Touch Point <NUM>. According to one embodiment, the deployment criteria are generated at the OMS <NUM> in response to receiving deployment criteria selections from one or more entities associated with the one or more permitted content elements. As described herein, each of the one or more entities is associated with one or more physical locations, and the content elements database <NUM> include the one or more physical locations (e.g., at which offers from one or more entity-associated, permissible content elements can be redeemed). In various embodiments, the generation of deployment criteria occurs during a content campaign process that provided the permitted (formerly permissible) content elements to the system <NUM>. Thus, it is understood that generation of the deployment criteria may occur prior to other processes and steps of the process <NUM>.

In at least one embodiment, the deployment criteria includes, but is not limited to, temporal criteria, locational criteria, availability criteria, and other criteria. In one or more embodiments, the temporal criteria includes, but is not limited to: <NUM>) an operating window corresponding to hours of operation of one or more entity locations (e.g., places of business) associated with the one or more permitted content elements; <NUM>) holiday and weekend criteria that may be satisfied when a current calendar date does or does not fall on one or more of: federal holidays, religious holidays, and one or more particular calendar days designated by the entity associated with the one or more permitted content elements; <NUM>) a predetermined detour time corresponding to a maximum period of time required to travel to one of the one or more entity locations from one or more of an origination location, a terminating location, and a current location of the Touch Point <NUM> (e.g., travel occurring along a known network of roadways); <NUM>) a predetermined expiration date (e.g., upon which goods or services indicated in the one or more permitted content elements will become unavailable) and <NUM>) other temporal criteria.

In at least one embodiment, the locational criteria includes, but is not limited to: <NUM>) a separation length corresponding to a maximum travel distance or maximum radius between the one or more entity locations and one or more of the origination location, terminating location, and the current location of the Touch Point <NUM>; <NUM>) proximity of the one or more entity locations to a geofence of predetermined size associated with one or more of the origination location, terminating location and the current location of the Touch Point <NUM>; <NUM>) proximity of the Touch Point <NUM> to a geofence of predetermined size associated with each of the one or more entity locations; <NUM>) weather criteria that may be satisfied when current or predicted weather conditions exclude severe weather conditions such as ice, snow, wind, fire, flood, etc., the weather conditions being associated with one or more of the current location, origination location, and terminating location of the Touch Point <NUM> and the one or more entity locations; and <NUM>) other locational criteria.

In various embodiments, the availability criteria includes, but is not limited to, the availability of a good or service (indicated in the one or more permitted content elements) at the one or more entity locations, the availability criteria being satisfied when the good or service is currently available. According to one embodiment, satisfaction of the availability criteria are determined at an external data information system <NUM> as described herein.

In at least one embodiment, the OMS <NUM> generates a criteria identifier for each of the deployment criteria generated at step <NUM>. In at least one embodiment, the criteria identifiers are utilized to store and organize the deployment criteria in one or more databases of the system <NUM>, and to track satisfaction of the deployment criteria as described herein.

Following step <NUM>, the process <NUM> includes performing an interactive content transmission process <NUM>, <NUM>, or <NUM>, as described herein to cause at least one permitted content element to be rendered on a display of the navigation application <NUM> on the Touch Point <NUM>.

<FIG> shows a flowchart of an exemplary interactive content transmission process <NUM>. As described herein, the process <NUM> generally refers to a process for transmitting interactive content to a third-party-operated navigation application <NUM> via an API (opposed to an ad exchange, which is discussed with reference to <FIG>).

According to one embodiment, step <NUM> is initiated upon launch of the navigation application <NUM> on a Touch Point <NUM>. In one or more embodiments, the launch of the navigation application <NUM> causes the Touch Point <NUM> to establish communications with the OMS <NUM> and the publisher web server <NUM> via the API <NUM>, which may be a third-party API <NUM> or a native API <NUM> as described herein. In at least one embodiment, the publisher web server <NUM> requests one or more of a secure identifier, public identifier, and device identifier from the Touch Point <NUM>. In various embodiments, the Touch Point <NUM> transmits the requested identifier(s) to the publisher web server <NUM> that provides the identifier(s) to the OMS <NUM>. In at least one embodiment, the OMS <NUM> uses the identifier(s) to identify a user and particular data associated therewith. After identifying the user and particular data, the OMS <NUM> retrieves one or more permitted content elements and corresponding deployment criteria associated with the user and/or their particular data.

According to one embodiment, following the launch, the navigation application <NUM> requires receipt of a confirmation input before causing the communication with the OMS <NUM> and the publisher web server <NUM>. For example, upon launch, the navigation application <NUM> renders a confirmation window for receiving a confirmation input. In one or more embodiments, the confirmation is rendered on a display of the Touch Point <NUM>, output via a speaker, or rendered in another manner. In the same example, upon receiving the confirmation input at the confirmation window (e.g., from the user associated with the Touch Point <NUM> and the particular data), the navigation application <NUM> initiates the communication.

At step <NUM>, the process <NUM> includes configuring the one or more permitted content elements. Configuring the one or more permitted content elements includes, but is not limited to, the OMS <NUM> transmitting the one or more permitted content elements to the navigation application <NUM> running on the Touch Point <NUM>. According to one embodiment, the transmission of the one or more permitted content elements occurs at a publisher web server <NUM> in communication with the navigation application <NUM> via an API <NUM>. In at least one embodiment, the one or more permitted content elements include media to be included in renderings of the one or more permitted content elements. Because the one or more permitted content elements and/or media thereof require a latency period to transmit to the Touch Point <NUM>, transmission of the one or more permitted content elements may be performed prior to rendering of the one or more permitted content elements to reduce the duration of the latency period between determining satisfaction of deployment criteria and rendering the one or more permitted content elements on a display of the navigation application <NUM> on the Touch Point <NUM>. In at least one embodiment, the transmission includes segment identifiers and/or content element identifiers for each of the one or more permitted content elements, the segment and/or content element identifiers being sourced from the segment and/or content element identifiers used for organizing content elements within the content element database <NUM> and/or segments within one or more other databases of the system <NUM>. In at least one embodiment, the transmission includes customization data (as described herein) associated with the one or more permitted content elements.

In some embodiments, step <NUM> includes transmitting the deployment criteria generated at step <NUM> to the navigation application <NUM>. Transmission of the deployment criteria to the navigation application <NUM> is performed, for example, in embodiments of the system <NUM> where the navigation application <NUM> determines whether or not the deployment criteria are satisfied based on mapping metadata.

At step <NUM>, the process <NUM> includes receiving mapping metadata and/or one or more identifiers or other data identifying a user. In various embodiments, the mapping metadata is received from the navigation application <NUM>, via the Touch Point <NUM> and API <NUM>, at the publisher web server <NUM>. In at least one embodiment, the publisher web server <NUM> provides the mapping metadata to the OMS <NUM> for satisfaction determining purposes. In one or more embodiments, the mapping metadata includes, but is not limited to: <NUM>) locational metadata describing one or more of the origination location, terminating location, and current location along the pathway of the Touch Point <NUM> (e.g., the pathway generated by the navigation application <NUM> in response to receiving selections requesting navigation between the origination and terminating locations); and <NUM>) metadata describing a current and/or predicted weather condition associated with one or more of the origination location, terminating location, and current location along the pathway of the Touch Point <NUM> and the one or more entity locations. According to one embodiment, the locational data is data sourced from a global positioning system (GPS) or another satellite-based positioning system.

In at least one embodiment, the system may receive data identifying a user or particular identifier with the mapping metadata from the Touch Point <NUM>, including, but not limited to: <NUM>) one or more of the secure identifier, public identifier, and device identifier associated with the particular data, thereby providing indication that the mapping metadata is associated with the particular data; <NUM>) segment and/or content element identifiers associated with the one or more permitted content elements stored within the navigation application <NUM>; and <NUM>) criteria identifiers corresponding to the deployment criteria associated with the one or more permitted content elements.

In various embodiments, the OMS <NUM> stores the mapping metadata in temporary memory of the system <NUM>, where the mapping metadata may remain until the system <NUM> has determined whether or not the deployment criteria are satisfied based on the mapping metadata. As will be understood from discussions herein, the mapping metadata may be matched or associated with a user, user data, and/or one or more identifiers discussed herein at the OMS <NUM>.

At step <NUM>, the system <NUM> determines whether the deployment criteria are satisfied based on the mapping metadata. According to one embodiment, if the system <NUM> determines the deployment criteria to be satisfied, the process <NUM> proceeds to the next step of executing a permitted content element deployment process <NUM> as described herein. In at least one embodiment, if the system <NUM> determines that any (or at least some or a predefined number) of the deployment criteria are unsatisfied, the process <NUM> returns to step <NUM> (or step <NUM> as also described herein at <FIG>).

In at least one embodiment, the OMS <NUM> retrieves the deployment criteria associated with each of the one or more permitted content elements. In one or more embodiments, the OMS <NUM> performs comparisons between the mapping metadata and the deployment criteria to determine satisfaction of each criterion therein. In at least one embodiment, the OMS <NUM> calculates metrics including but not limited to: <NUM>) a separation length, travel distance, or radius between each of the one or more entity locations and one or more of the origination location, terminating location, and current location along a pathway of the Touch Point <NUM>; and <NUM>) a proximity of the Touch Point <NUM> or the one or more entity locations to each of one or more geofences (previously configured by the OMS <NUM> based on entity inputs) associated with one or more of the origination location, terminating location, and current location along the pathway of the Touch Point <NUM> and the one or more entity locations. According to one embodiment, one or more of the detour time, separation length, travel distance, radii, and proximities are calculated by the navigation application <NUM> and included in the mapping metadata.

In various embodiments, the OMS <NUM> retrieves the data describing the current and/or predicted weather conditions and determine whether the current and/or predicted weather conditions exclude severe weather conditions or some other preconfigured weather condition. In some embodiments, if the OMS <NUM> determines the current or predicted weather conditions exclude the preconfigured weather condition, the OMS <NUM> determines the weather deployment criteria to be satisfied.

In one or more embodiments, if the calculated detour time is less than a deployment criteria detour time, the OMS <NUM> determines the detour time deployment criteria to be satisfied. In at least one embodiment, if the calculated separation length, travel distance, or radius are within a deployment criteria travel distance or radius, the OMS <NUM> determines the corresponding separation length, travel distance, or radius deployment criteria to be satisfied. In various embodiments, if one or more of the origination location, terminating location, and current location along the pathway of the Touch Point <NUM> are within at least one of the one or more geofences associated with the one or more entity locations, the OMS <NUM> determines the (entity location) geofence deployment criteria to be satisfied. In further embodiments, if at least one of the one or more entity locations are within the one or more geofences associated with one or more of the origination location, terminating location, and current location along the pathway, the OMS <NUM> determines the (Touch Point <NUM>) geofence deployment criteria to be satisfied.

In various embodiments, based on the content element identifiers, the OMS <NUM> communicates, via the transaction environment <NUM> and firewall <NUM>, with a transaction detail system <NUM> to determine whether or not goods or services associated with the one or more permitted content elements are currently available. In at least one embodiment, the OMS <NUM> determines whether the goods or services will be available upon arrival of the Touch Point <NUM> at the one or more entity locations at a particular time equal to the current time plus the calculated detour time. If the goods or services are available (currently and/or upon the arrival), the OMS <NUM> determines the availability deployment criteria to be satisfied.

In one or more embodiments, the OMS <NUM> evaluates a current date and time to determine satisfaction of temporal deployment criteria. In at least one embodiment, the OMS <NUM> retrieves a time stamp from the mapping metadata and identifies one or more of: <NUM>) whether or not the current date occurs on a holiday, weekend, and/or other indicated dates provided by the one or more entities during deployment criteria generation; <NUM>) whether or not the current date and time occur within the window of operation associated with each of the one or more entity locations; and <NUM>) whether or not the current date occurs on or before the predetermined expiration date. According to one embodiment, if the OMS <NUM> determines that the current date and time fall within the expiration and the window of operation of at least one of the one or more entity locations, and does not fall on a holiday, weekend, or other indicated dates, the OMS <NUM> determines the corresponding temporal criteria to be satisfied.

In various embodiments, the OMS <NUM> calculates a detour time between each of the one or more entity locations and one or more of the origination location, terminating location, and current location along a pathway of the Touch Point <NUM>. In at least one embodiment, the OMS <NUM> compares the calculated detour time to the predetermined detour time of the deployment criteria and, if the calculated detour time is less than or equal to the predetermined detour time, the OMS <NUM> determines the detour time temporal deployment criteria to be satisfied.

It will be understood that the determination of satisfaction of deployment criteria may be performed only with respect to deployment criteria associated with the one or more permitted content elements. Thus, in some embodiments, one or more of the deployment criteria described herein may be omitted from evaluation. It will also be understood that, in some embodiments, the OMS <NUM> performs deployment criteria determinations in a piece-wise and/or filtering manner to advantageously reduce a time and/or computing cost of determining the deployment criteria to be unsatisfied. For example, the OMS <NUM> may first determine satisfaction of availability criteria, then temporal criteria, then locational criteria, the OMS <NUM> being configured to find the deployment criteria wholly unsatisfied if any of the availability, temporal, or locational criteria are unsatisfied. In the same example, if the OMS <NUM> determines that one or more of the availability criteria are unsatisfied, the OMS <NUM> determines that the deployment criteria are not satisfied and return to step <NUM> (or step <NUM> as described herein). In another example, the OMS <NUM> determines satisfaction all deployment criteria simultaneously. While each and every permutation of deployment criteria determination process sequencing are not described herein, additional permutations of deployment criteria determination process sequencing as would be understood from discussions herein are contemplated.

According to one embodiment, upon the OMS <NUM> determining the deployment criteria to be satisfied, the OMS <NUM> transmits a deployment criteria satisfaction indication (e.g., a signal, transmission, etc.) to one or more of the DSP <NUM>, the interchange platform <NUM>, the publisher web server <NUM>, and the navigation application <NUM>. In one or more embodiments, the process <NUM> (or <NUM>, or <NUM>) may proceed to performing the process <NUM> only after receipt of the deployment criteria satisfaction indication.

In one or more embodiments, the process <NUM> (or <NUM>, or <NUM>) may proceed even if the deployment criteria are not entirely satisfied. In at least one embodiment, the deployment criteria include a dissatisfaction threshold that, when not met or exceeded, causes the OMS <NUM> to determine the deployment criteria to be satisfied and to transmit the deployment criteria satisfaction indication regardless of one or more of the deployment criteria being determined unsatisfied. In one or more embodiments, the step <NUM> includes incrementing a dissatisfaction threshold following each instance in which the OMS <NUM> determines one of the deployment criteria to be unsatisfied. According to one embodiment, the dissatisfaction threshold is configured during deployment criteria generation processes occurring between the OMS <NUM> and the one or more entities. In various embodiments, the dissatisfaction threshold allows the system <NUM> to transmit permitted content elements to users or user accounts based on mapping metadata that does not satisfy each and every aspect of deployment criteria, but satisfies a subset of the deployment criteria sufficient to merit transmission of the permitted content elements.

Following step <NUM>, the process <NUM> includes performing a permitted content element deployment process <NUM> as described herein.

<FIG> shows a flowchart of an exemplary interactive content transmission process <NUM>. As described herein, the process <NUM> generally refers to a process for transmitting interactive content to a third-party-operated navigation application <NUM> via an interchange platform <NUM>.

At step <NUM>, the process <NUM> includes configuring the one or more permitted content elements as described herein. In at least one embodiment, configuring the permitted content elements includes providing the deployment criteria and various identifiers associated with the one or more permitted content elements to a demand-side platform and/or interchange platform <NUM> described herein.

At step <NUM>, the process <NUM> includes receiving mapping metadata and identifying particular data and/or a user therefrom as described herein. According to one embodiment, in the process <NUM>, the mapping metadata is received at the DSP <NUM> and/or interchange platform <NUM>. In at least one embodiment, the DSP <NUM> and/or interchange platform <NUM> receives the deployment criteria from the OMS <NUM>. In at least one embodiment, the DSP <NUM> and/or interchange platform <NUM> is operative to receive one or more identifiers (public, secure, device, or other identifiers) from the Touch Point <NUM> and provide these identifiers to the OMS <NUM> (or another system <NUM> element) for purposes of tracking interactions of the Touch Point <NUM> with the one or more permitted content elements (and/or the corresponding entity locations thereof).

At step <NUM>, the process <NUM> includes determining that deployment criteria are satisfied based on the mapping metadata as described herein. According to one embodiment, the DSP <NUM> and/or the interchange platform <NUM> performs the processes of determining whether the deployment criteria are satisfied based on the mapping metadata. In at least one embodiment, if the interchange platform <NUM> determines the deployment criteria to be satisfied, the interchange platform <NUM> automatically requests a proffer from the DSP <NUM>, the request including the deployment criteria satisfaction indication and one or more of the secure, public, device, content element, and/or device identifiers (e.g., for tracking purposes and for identifying the user and/or particular data associated with the Touch Point <NUM>).

At step <NUM>, the process <NUM> includes generating and providing a proffer at an interchange platform for publishing permissions to render the one or more content elements on a display of the navigation application <NUM> on the Touch Point <NUM>. According to one embodiment, the interchange platform <NUM> is an advertisement exchange platform. In various embodiments, a proffer amount is used to generate the proffer. In at least one embodiment, the proffer amount is included in metadata of the one or more content elements and stored in the content element database <NUM>. In one or more embodiments, if deployment criteria for multiple permitted content elements are satisfied, the system <NUM> retrieves a proffer amount and generate a proffer for each of the permitted content elements.

In one or more embodiments, the DSP <NUM> transmits the proffer and proffer amount to the interchange platform <NUM> that determines whether or not the proffer is successful for purchasing the publishing permissions for the one or more permitted content elements. In at least one embodiment, if the proffer is successful, the process <NUM> proceeds and includes performing the permitted content element deployment process <NUM> as described herein. In at least one embodiment, if the proffer is unsuccessful, the process <NUM> returns to step <NUM>.

<FIG> shows a flowchart of an exemplary interactive content transmission process <NUM>. As described herein, the process <NUM> generally refers to a process for transmitting interactive content to a native navigation application <NUM> in communication with the publisher web server <NUM>.

At step <NUM>, the process <NUM> includes identifying a user and/or particular data associated therewith and retrieving permitted content elements associated with the user and/or particular data. According to one embodiment, the step <NUM> is initiated upon launch of a native navigation application <NUM> on a Touch Point <NUM>.

In various embodiments, the launch of the navigation application <NUM> causes the Touch Point <NUM> to establish communications with the OMS <NUM> and/or the publisher web server <NUM> via the API <NUM>. In at least one embodiment, the publisher web server <NUM> requests one or more of a secure identifier, public identifier, and device identifier from the Touch Point <NUM>. In one or more embodiments, the Touch Point <NUM> transmits the requested identifier(s) to the publisher web server <NUM> that provides the identifier(s) to the OMS <NUM>. In at least one embodiment, the OMS <NUM> uses the identifier(s) to identify the user and/or particular data. After identifying the user and/or particular data, the OMS <NUM> retrieves one or more permitted content elements and corresponding deployment criteria associated with the user or particular data.

According to one embodiment, following the launch, the navigation application <NUM> requires receipt of a confirmation input before causing the communication with the OMS <NUM> and the publisher web server <NUM>. For example, upon launch, the navigation application <NUM> causes the Touch Point <NUM> to render, on a display, a confirmation window for receiving a confirmation input. In the same example, upon receiving the confirmation input at the confirmation window (e.g., from an input of the user on the Touch Point <NUM>), the navigation application <NUM> initiates communication with the OMS <NUM> and the publisher web server <NUM>.

At step <NUM>, the process <NUM> includes populating the navigation application <NUM> with the one or more permitted content elements, media, customization data and/or deployment criteria associated therewith. According to one embodiment, step <NUM> may be omitted, for example, in instances where deployment criteria satisfaction determinations are to be performed by the OMS <NUM> and/or in instances where the one or more permitted content elements are to be transmitted to the application <NUM> only upon the deployment criteria being satisfied.

In one or more embodiments, the OMS <NUM> transmits the one or more permitted content elements and/or the deployment criteria (and associated identifiers thereof) to the navigation application <NUM> for storage and future processing purposes.

At step <NUM>, the process <NUM> includes receiving mapping metadata as described herein. According to one embodiment, receipt of the mapping metadata includes the navigation application generating and storing the mapping metadata as described herein.

At step <NUM>, the process <NUM> includes determining that deployment criteria are satisfied based on the mapping metadata. According to one embodiment, the navigation application 121performs the processes of determining satisfaction of the deployment criteria described herein. In one or more embodiments, if the navigation application <NUM> determines that the deployment criteria have been sufficiently satisfied, the process <NUM> proceeds and includes performing the permitted content element deployment process <NUM> as described herein. In at least one embodiment, if the navigation application <NUM> determines that the deployment criteria have not been sufficiently satisfied, the process <NUM> returns to step <NUM>.

With reference to <FIG>, shown is a flowchart of an exemplary permitted content element deployment process <NUM>.

At step <NUM>, the process <NUM> includes receiving a deployment criteria satisfaction indication. In one or more embodiments, as described herein, the deployment criteria satisfaction indication is received at one or more of the OMS <NUM>, navigation application <NUM>, DSP <NUM>, interchange platform <NUM>, and other elements of the system <NUM>. In various embodiments, the deployment criteria satisfaction indication is a transmission, signal, or other electronic communication that triggers performance of the process <NUM>. In at least one embodiment, the deployment criteria satisfaction indication includes, but is not limited to, one or more of the secure, public, and device identifiers corresponding to the user and/or particular data associated with the one or more permitted content elements for which deployment criteria have been satisfied.

At step <NUM>, the process <NUM> includes determining that the one or more permitted content elements are stored in the navigation application <NUM> or a Touch Point <NUM> associated with the identifier(s) and the navigation application <NUM>. According to one embodiment, the OMS <NUM>, DSP <NUM>, or interchange platform <NUM> transmits a request to the navigation application <NUM> to query itself and/or the Touch Point <NUM> and determine if the one or more permitted content elements are stored therein. In one or more embodiments, the navigation application <NUM> determines whether media associated with the one or more permitted content elements is stored therein or in the Touch Point <NUM>. In at least one embodiment, the navigation application <NUM> provides one or more indications to the OPS <NUM>, DSP <NUM>, or interchange platform <NUM> indicating: <NUM>) whether or not the one or more permitted content elements are stored; and <NUM>) whether or not the media associated with the one or more permitted content elements are stored.

According to one embodiment, if the system <NUM> determines that the one or more permitted content elements are stored in the navigation application <NUM> or Touch Point <NUM>, the process <NUM> proceeds to step <NUM>. In at least one embodiment, if the system <NUM> determines that the permitted content elements are not stored, the process <NUM> proceeds to step <NUM>.

At step <NUM>, the process <NUM> includes transmitting the one or more permitted content elements (associated with the criteria satisfaction indication and identifier(s) received at step <NUM>) to the navigation application <NUM>. According to one embodiment, the OMS <NUM> and publisher web server <NUM> retrieves and transmits the one or more permitted content elements to the navigation application <NUM> for storage and rendering on the display thereof.

At step <NUM>, the process <NUM> includes customizing the one or more permitted content elements and/or the media associated therewith. According to one embodiment, at steps <NUM>, <NUM>, <NUM> or <NUM>, the OMS <NUM> retrieves or executes a program to generate customization data. In at least one embodiment, the customization data is included in the transmission of the one or more permitted content elements performed at steps <NUM>, <NUM> or <NUM>. In various embodiments, the customization data include, for example, text strings to be included in renderings of the one or more permitted content elements and/or the media on the display of the navigation application <NUM>. In at least one embodiment, the customization data includes, but is not limited to, one or more of: <NUM>) text strings; <NUM>) audio in a suitable audio file format, such as, for example,. MP3; <NUM>) one or more images in a suitable image file format, such as, for example,. RAW; <NUM>) one or more videos or animations in suitable animation file format, such as, for example,. MP4; <NUM>) coloration data for assigning colors to features of the one or more permitted content elements. In one or more embodiments, the customization data include information from the mapping metadata and/or deployment criteria associated with the one or more permitted content items.

Upon receiving or retrieving the customization data, the navigation application <NUM> modifies data of the one or more permitted content elements to include the customization data and generate one or more customized content elements. In one example, at step <NUM>, the navigation application <NUM> modifies a permitted content element "Buy # Get # Free" to a customized content element "Buy <NUM> Get <NUM> Free," based on the customization data. In another example, the navigation application modifies a permitted content element "<NUM>% Off!" to a customized content element "<NUM>% Off Until <NUM> PM!" based on the customization data and deployment criteria. In another example, the navigation application <NUM> modifies a permitted content element "<NUM>% Off!" to a customized content element "<NUM>% Off! You are only <NUM> Minutes Away!" based on the customization data and mapping metadata.

In some embodiments, the navigation application <NUM> stores a static or fixed component in a background layer of the display while writing a customized message in an alpha layer on the display. In at least one embodiment, the alpha layer corresponds to a transparent layer rendered over the background layer. For example, the navigation application <NUM> determines customized content of "You are only <NUM> Minutes Away!" and the alpha layer based on the customized content. In one or more embodiments, a video is written to the background layer, while the customized content is written to the alpha layer. In some embodiments, a custom filter is applied to the customized content or the background layer. In various embodiments, the customized content is animated. In some embodiments, a video is generated based on the customized content. In at least one embodiment, a processor, such as a graphics processor, merges or rasterizes two or more the layers together when rendering the content to the display.

In at least one embodiment, the customization data may be selectively utilized by navigation application <NUM> according to one or more temporal parameters or other parameters. For example, the navigation application <NUM> may determine that a current time is after sunset, and may utilize customization data that causes a feature of the one or more customized content elements to be rendered with a white-colored background. In the same example, the one or more customized content elements may be better distinguished from a darker background color of the display of the navigation application <NUM>.

At step <NUM>, the process <NUM> includes rendering the one or more permitted (e.g., and, in some embodiments, customized) content elements on the display of the navigation application <NUM> on the Touch Point <NUM>. According to one embodiment, the navigation application <NUM> may await receipt of a rendering input to the Touch Point <NUM> before rendering the one or more permitted content elements. Upon receipt of rendering input selecting the button, the navigation application <NUM> causes the Touch Point <NUM> to render the one or more permitted content elements as selectable objects on the display.

According to one embodiment, the navigation application <NUM> causes the Touch Point <NUM> to render the one or more permitted content elements as flags or pins. In at least one embodiment, the navigation application <NUM> renders each of the one or more permitted content elements on the display at a position corresponding to the entity location associated with the permitted content element. For example, the display includes a map and the navigation application <NUM> displays one or more flags positioned on the map at positions corresponding to the entity location associated with the permitted content element (e.g., with the permitted content element also displayed).

In one example, the navigation application <NUM> includes a button, or other input field, selection of which causes the navigation application <NUM> to overlay the one or more permitted content elements onto the display.

According to one embodiment, each of the one or more rendered content elements is selectable via receipt of input on the Touch Point <NUM>. Receipt of input selecting one of the rendered content elements causes the navigation application <NUM> to perform actions including, but not limited to: <NUM>) launching a dialog window including additional description of the entity, goods, services, and/or other information associated with the rendered content element; <NUM>) launching a selection field for receiving a navigation input, receipt of the navigation input causing the navigation application <NUM> to automatically update a current pathway to include the entity location associated with the rendered content element.

It will be understood by one of ordinary skill in the art that the steps <NUM>-<NUM>, the step <NUM> of the process <NUM>, and the steps of the process <NUM>, <NUM>, or <NUM> are performed on a millisecond time-frame, such that there is little or no delay between the system <NUM> receiving permission for the one or more permissible (then permitted) content elements and rendering the one or more permitted content elements on the display of the navigation application <NUM>.

At step <NUM>, the process <NUM> includes monitoring for interaction with the one or more rendered, permitted content elements. In various embodiments, the interaction monitoring is performed by one or more of the navigation application <NUM>, OPS <NUM>, OMS <NUM>, and other elements of the system <NUM>. In at least one embodiment, the interaction monitoring includes, but is not limited to: <NUM>) monitoring a current location of the Touch Point <NUM> to determine if the user associated therewith has accessed the one or more entity locations associated with the one or more permitted content elements; <NUM>) monitoring transactions via the transactional detail system (TDS) <NUM> to determine if the user has purchased the goods and/or services associated with the one or more permitted content elements; and <NUM>) other monitoring processes, such as for example, monitoring for inputs made to the navigation application <NUM> selecting any of the one or more permitted content elements.

According to one embodiment, any of the one or more permitted content elements may be de-rendered from the display based on determinations of the interaction monitoring process. A rendered, permitted content element is de-rendered for determinations including, but not limited to: <NUM>) the user has traveled to one of the entity locations (e.g., as detected based on a location of the Touch Point <NUM> provided in mapping metadata); <NUM>) the user has accessed the goods or services associated with the content element; <NUM>) the deployment criteria associated with the permitted content element becomes unsatisfied (for example, an operational window of an entity location associated with the permitted content element passes, etc.); and <NUM>) the navigation application <NUM> receives a de-rendering input (e.g., from the system <NUM>, the one or more entities, an operator of the Touch Point <NUM>, etc.).

In one or more embodiments, the interaction monitoring includes transmitting or activating reminders (e.g., stored in metadata of the one or more rendered content elements) for accessing the one or more rendered content elements. Activation of the reminders are temporally, location, or availability-based, or may be a combination thereof. For example, a reminder for a particular rendered content element may become activated when the navigation application <NUM> (or other system <NUM> element) determines that the Touch Point <NUM> is within a predetermined temporal or physical proximity of an entity location associated with the particular rendered content element. In the same example, the reminder may include an electronic notification, push alert, or other indication rendered on the display of the navigation application <NUM>. According to one embodiment, the reminder is transmitted directly to the Touch Point <NUM> or another application running thereon (e.g., as opposed to being transmitted to the navigation application <NUM>).

In at least one embodiment, the reminder may be a text message, email, or other electronic communication. In one or more embodiments, the reminder is generated by the OMS <NUM> using identified data corresponding to the user and/or their particular data associated with the one or more rendered content elements. In one example, the OMS <NUM> processes mapping metadata from the navigation application <NUM> while the display thereof renders permitted content elements. In the same example, the OMS <NUM> determines, based on the mapping metadata, that the Touch Point <NUM> running the navigation application <NUM> is approaching an entity location associated with one of the rendered content elements. Continuing the same example, the OMS <NUM> generates and transmits a text message to the Touch Point <NUM>, the text message indicating that the Touch Point <NUM> is near the entity location. In the same example, a phone number associated with the Touch Point <NUM> and used for transmitting the text message is retrieved by the OMS <NUM> from an identified data stored in a secured database thereof. Also, in the same example, the OMS <NUM> retrieves the identified data (associated with the user and/or their particular data) by indexing the secured database using a device identifier, public identifier, and/or a secure identifier associated with the user and/or particular data.

From the foregoing, it will be understood that various aspects of the processes described herein are software processes that execute on computer systems that form parts of the system. Accordingly, it will be understood that various embodiments of the system described herein are generally implemented as specially-configured computers including various computer hardware components and, in many cases, significant additional features as compared to conventional or known computers, processes, or the like, as discussed in greater detail herein. Embodiments within the scope of the present disclosure also include computer-readable media for carrying or having computer-executable instructions or data structures stored thereon. Such computer-readable media can be any available media which can be accessed by a computer, or downloadable through communication networks. By way of example, and not limitation, such computer-readable media can comprise various forms of data storage devices or media such as RAM, ROM, flash memory, EEPROM, CD-ROM, DVD, or other optical disk storage, magnetic disk storage, solid state drives (SSDs) or other data storage devices, any type of removable non-volatile memories such as secure digital (SD), flash memory, memory stick, etc., or any other medium which can be used to carry or store computer program code in the form of computer-executable instructions or data structures and which can be accessed by a computer.

When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a computer, the computer properly views the connection as a computer-readable medium. Thus, any such a connection is properly termed and considered a computer-readable medium. Computer-executable instructions comprise, for example, instructions and data which cause a computer to perform one specific function or a group of functions.

Those skilled in the art will understand the features and aspects of a suitable computing environment in which aspects of the disclosure may be implemented. Although not required, some of the embodiments of the claimed systems and processes may be described in the context of computer-executable instructions, such as program modules or engines, as described earlier, being executed by computers in networked environments. Such program modules are often reflected and illustrated by flow charts, sequence diagrams, exemplary screen displays, and other techniques used by those skilled in the art to communicate how to make and use such computer program modules. Generally, program modules include routines, programs, functions, objects, components, data structures, application programming interface (API) calls to other computers whether local or remote, etc. that perform particular tasks or implement particular defined data types, within the computer. Computer-executable instructions, associated data structures and/or schemas, and program modules represent examples of the program code for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represent examples of corresponding acts for implementing the functions described in such steps.

Those skilled in the art will also appreciate that the claimed and/or described systems and methods may be practiced in network computing environments with many types of computer system configurations, including personal computers, smartphones, tablets, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, networked PCs, minicomputers, mainframe computers, and the like. Embodiments of the claimed systems and processes are practiced in distributed computing environments where tasks are performed by local and remote processing devices that are linked (either by hardwired links, wireless links, or by a combination of hardwired or wireless links) through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

An exemplary system for implementing various aspects of the described operations, which is not illustrated, includes a computing device including a processing unit, a system memory, and a system bus that couples various system components including the system memory to the processing unit. The computer will typically include one or more data storage devices for reading data from and writing data to. The data storage devices provide nonvolatile storage of computer-executable instructions, data structures, program modules, and other data for the computer.

Computer program code that implements the functionality described herein typically comprises one or more program modules that may be stored on a data storage device. This program code, as is known to those skilled in the art, usually includes an operating system, one or more application programs, other program modules, and program data. A user may enter commands and information into the computer through keyboard, touch screen, pointing device, a script containing computer program code written in a scripting language or other input devices (not shown), such as a microphone, etc. These and other input devices are often connected to the processing unit through known electrical, optical, or wireless connections.

The computer that effects many aspects of the described processes will typically operate in a networked environment using logical connections to one or more remote computers or data sources, which are described further below. Remote computers may be another personal computer, a server, a router, a network PC, a peer device or other common network node, and typically include many or all of the elements described above relative to the main computer system in which the systems and processes are embodied. The logical connections between computers include a local area network (LAN), a wide area network (WAN), virtual networks (WAN or LAN), and wireless LANs (WLAN) that are presented here by way of example and not limitation. Such networking environments are commonplace in office-wide or enterprise-wide computer networks, intranets, and the Internet.

When used in a LAN or WLAN networking environment, a computer system implementing aspects of the present disclosure is connected to the local network through a network interface or adapter. When used in a WAN or WLAN networking environment, the computer may include a modem, a wireless link, or other mechanisms for establishing communications over the wide area network, such as the Internet. In a networked environment, program modules depicted relative to the computer, or portions thereof, may be stored in a remote data storage device. It will be appreciated that the network connections described or shown are exemplary and other mechanisms of establishing communications over wide area networks or the Internet may be used.

While various aspects have been described in the context of a preferred embodiment, additional aspects, features, and methodologies of the claimed systems and processes will be readily discernible from the description herein, by those of ordinary skill in the art. Many embodiments and adaptations of the disclosure and claimed systems and processes other than those herein described, as well as many variations, modifications, and equivalent arrangements and methodologies, will be apparent from or reasonably suggested by the disclosure and the foregoing description thereof, without departing from the substance or scope of the claims. Furthermore, any sequence(s) and/or temporal order of steps of various processes described and claimed herein are those considered to be the best mode contemplated for carrying out the claimed systems and processes. It should also be understood that, although steps of various processes may be shown and described as being in a preferred sequence or temporal order, the steps of any such processes are not limited to being carried out in any particular sequence or order, absent a specific indication of such to achieve a particular intended result. In most cases, the steps of such processes may be carried out in a variety of different sequences and orders, while still falling within the scope of the claimed systems and processes. In addition, some steps may be carried out simultaneously, contemporaneously, or in synchronization with other steps.

The embodiments were chosen and described in order to explain the principles of the claimed systems and processes and their practical application so as to enable others skilled in the art to utilize the systems (and/or processes) and various embodiments and with various modifications as are suited to the particular use contemplated.

Claim 1:
A process for transmitting interactive content comprising:
transmitting content to a computing device associated with particular data, the content comprising a call to a beacon service and a secure identifier associated with the particular data;
generating an association between the secure identifier and at least one public identifier based on the beacon service;
identifying a subset of a plurality of permissible content elements based on a spend history corresponding to the particular data of an external computing system, wherein each of the plurality of permissible content elements are associated with a respective entity and each respective entity comprises a plurality of respective locations;
activating at least one permissible content element of the subset of the plurality of permissible content elements and storing the activated at least one permissible content element as at least one permitted content element;
generating a plurality of deployment criteria associated with the at least one permitted content element based on the plurality of respective locations for the respective entity corresponding to the at least one permitted content element;
receiving mapping metadata corresponding to an application, the mapping metadata comprising the at least one public identifier and at least one of: an origination location, a plurality of locations along a pathway, and a terminal location;
determining whether the plurality of deployment criteria are satisfied for the at least one permitted content element based on the mapping metadata; and
in response to the plurality of deployment criteria being satisfied, causing the at least one permitted content element to be rendered on a display of the application at a position corresponding to one of the plurality of respective locations.