US20130332283A1 - Devices, methods, and computer-readable media for redemption of merchant offers - Google Patents
Devices, methods, and computer-readable media for redemption of merchant offers Download PDFInfo
- Publication number
- US20130332283A1 US20130332283A1 US13/840,237 US201313840237A US2013332283A1 US 20130332283 A1 US20130332283 A1 US 20130332283A1 US 201313840237 A US201313840237 A US 201313840237A US 2013332283 A1 US2013332283 A1 US 2013332283A1
- Authority
- US
- United States
- Prior art keywords
- coupon
- merchant
- offers
- user
- location
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0207—Discounts or incentives, e.g. coupons or rebates
- G06Q30/0222—During e-commerce, i.e. online transactions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0207—Discounts or incentives, e.g. coupons or rebates
- G06Q30/0225—Avoiding frauds
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0207—Discounts or incentives, e.g. coupons or rebates
- G06Q30/0239—Online discounts or incentives
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0241—Advertisements
- G06Q30/0242—Determining effectiveness of advertisements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0241—Advertisements
- G06Q30/0251—Targeted advertisements
- G06Q30/0255—Targeted advertisements based on user history
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0241—Advertisements
- G06Q30/0251—Targeted advertisements
- G06Q30/0255—Targeted advertisements based on user history
- G06Q30/0256—User search
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0241—Advertisements
- G06Q30/0251—Targeted advertisements
- G06Q30/0267—Wireless devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0241—Advertisements
- G06Q30/0251—Targeted advertisements
- G06Q30/0269—Targeted advertisements based on user profile or attribute
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
Definitions
- This invention relates generally to merchant offers for goods and services and, more particularly, to redemption of certain offers such as online coupons.
- Offer-discovery systems provide a service by which merchants inform customers of offers, for example deals (e.g., discounts, favorable shipping terms, or rebates) or coupons (e.g., printable coupons for in-store use or coupon codes for use online).
- deals e.g., discounts, favorable shipping terms, or rebates
- coupons e.g., printable coupons for in-store use or coupon codes for use online.
- the systems store information about offers from a relatively large number of merchants and provide an interface by which customers can identify offers in which the customer is likely to be interested.
- Merchants have found the offer-discovery systems to be a relatively effective form of marketing, as cost-sensitive consumers are drawn to such systems due to their relatively comprehensive listings of offers.
- Such offers may include coupons, such as include traditional in-store coupons, and online coupons typically obtained via the Internet, such as from merchant websites, e-mail distributions, etc.
- a customer typically provides an identifier, such as a coupon code, when purchasing goods and services from a merchant's online store.
- an identifier such as a coupon code
- a customer may forget about the existence of the coupon and, as a result, fail to take advantage of the offer presented by the coupon.
- it may be challenging for a customer to remember the identifier presented by the coupon and to use the online coupon in the manner specified by the online store.
- the advent of smaller computing devices having different or limited interfaces may increase the challenges faces by customers attempting to use online coupons.
- Various embodiments of devices, computer-implemented methods, and computer-readable media for redemption of merchant offers are provided herein.
- Applicants recognize the need for improved techniques for redemption of merchant offers such as online coupons to reduce or eliminate the burdens on a user.
- users may be unable to remember the existence of a merchant offer, such as coupon, or memorize the information necessary to use the merchant offer.
- Embodiments address some or all of these recognized needs, but embodiments are not limited to just those systems that address these needs, as various engineering and cost tradeoffs are envisioned and some embodiments address other needs.
- a computer-implemented method includes providing an online coupon in a native application for the mobile user device, the online coupon having a coupon code in a user interface element located at first location defined by a first set of coordinates of a touchscreen of the mobile user device.
- the computer-implemented method further includes receiving a selection to use the online coupon for a transaction with a merchant and providing in the user interface a webpage associated with the merchant.
- the computer-implemented method also includes executing, with a processor of the mobile user device, a visual movement of the user interface element from the first location to a second location, the second location defined by a second set of coordinate of the touchscreen of the mobile user devices.
- a non-transitory computer-readable medium having executable computer code stored thereon includes instructions that, when executed, cause one or more processors to perform the following: providing an online coupon in a native application for the mobile user device, the online coupon having a coupon code within a user interface element located at first location defined by a first set of coordinates of a touchscreen of the mobile user device.
- the executable computer further includes instructions that cause one or more processors to perform the following: receiving a selection to use the online coupon for a transaction with a merchant and providing in the user interface a webpage associated with the merchant.
- the executable computer further includes instructions that cause one or more processors to perform the following: executing, with a processor of the mobile user device, a visual movement of the user interface element from the first location to a second location, the second location defined by a second set of coordinate of the touchscreen of the mobile user devices.
- a mobile user device includes a processor, a touchscreen communicatively coupled to the processor, and a non-transitory tangible computer-readable memory communicatively coupled to the processor.
- the memory has executable computer code stored thereon, the executable computer having instructions that, when executed, cause one or more processors to perform the following: providing an online coupon in a native application for the mobile user device, the online coupon having a coupon code within a user interface element located at first location defined by a first set of coordinates of a touchscreen of the mobile user device.
- the executable computer further includes instructions that cause one or more processors to perform the following: receiving a selection to use the online coupon for a transaction with a merchant and providing in the user interface a webpage associated with the merchant.
- the executable computer further includes instructions that cause one or more processors to perform the following: executing, with a processor of the mobile user device, a visual movement of the user interface element from the first location to a second location, the second location defined by a second set of coordinate of the touchscreen of the mobile user devices.
- a computer-implemented method includes providing a coupon code associated with a merchant in a native application for the mobile user device, the coupon code in a user interface element located at a first location defined by a first set of coordinates of a touchscreen of the mobile user device and providing (e.g., requesting and rendering) in the native application a webpage associated with the merchant, the webpage having an input field for receiving user input associated with a coupon, the input field located at a second location at a second set of coordinates of the touchscreen.
- the computer-implemented method further includes receiving a touch on the touchscreen at the first location and receiving a gesture on the touchscreen, the gesture including a movement from the first location to the second location.
- the computer-implemented method also includes executing, with a processor of the mobile user device, a visual movement of the user interface element having the coupon code from the first location to the second location along a path coincident with the gesture, receiving a release of the touch at the second location, and setting, the value of the input field of the webpage to text corresponding to the coupon code.
- a non-transitory computer-readable medium having executable computer code stored thereon includes instructions that, when executed, cause one or more processors to perform the following: providing a coupon code associated with a merchant in a native application for the mobile user device, the coupon code in a user interface element located at a first location defined by a first set of coordinates of a touchscreen of the mobile user device and providing in the native application a webpage associated with the merchant, the webpage having an input field for receiving user input associated with a coupon, the input field located at a second location at a second set of coordinates of the touchscreen.
- the executable computer further includes instructions that cause one or more processors to perform the following: receiving a touch on the touchscreen at the first location and receiving a gesture on the touchscreen, the gesture including a movement from the first location to the second location.
- the executable computer further also instructions that cause one or more processors to perform the following: executing, with a processor of the mobile user device, a visual movement of the user interface element having the coupon code from the first location to the second location along a path coincident with the gesture, receiving a release of the touch at the second location, and setting the value of the input field of the webpage to text corresponding to the coupon code.
- a mobile user device includes a processor, a touchscreen communicatively coupled to the processor, and a non-transitory tangible computer-readable memory communicatively coupled to the processor.
- the memory has executable computer code stored thereon, the executable computer having instructions that, when executed, cause one or more processors to perform the following: providing a coupon code associated with a merchant in a native application for the mobile user device, the coupon code in a user interface element located at a first location defined by a first set of coordinates of a touchscreen of the mobile user device and providing in the native application a webpage associated with the merchant, the webpage having an input field for receiving user input associated with a coupon, the input field located at a second location at a second set of coordinates of the touchscreen.
- the executable computer code further includes instructions that cause one or more processors to perform the following: receiving a touch on the touchscreen at the first location and receiving a gesture on the touchscreen, the gesture including a movement from the first location to the second location.
- the executable computer further also instructions that cause one or more processors to perform the following: executing, with a processor of the mobile user device, a visual movement of the user interface element having the coupon code from the first location to the second location along a path coincident with the gesture, receiving a release of the touch at the second location, and setting the value of the input field of the webpage to text corresponding to the coupon code.
- a computer-implemented method includes providing a coupon in a native application for the mobile user device, the coupon having a coupon code in a user interface element located at first location defined by a first set of coordinates of a touchscreen of the mobile user device and receiving a selection to use the coupon for a transaction with a merchant. Additionally, the computer-implemented method includes providing a webpage associated with the merchant in the application and providing, with a processor of the mobile user device, the coupon code in the user interface element at a second location defined by a second set of coordinates of the touchscreen, the second set of coordinates located at a header portion of a display of the application, wherein the header portion is positioned vertically above the webpage.
- FIG. 1 illustrates an example of an offer-discovery system in accordance with some embodiments
- FIG. 2 illustrates an example of a process by which an offers engine in the offer-discovery system of FIG. 1 , in some embodiments, obtains and processes data related to offers;
- FIG. 3 illustrates an example of a process by which a user device in the offer-discovery system of FIG. 1 , in some embodiments, obtains and presents to users data related to offers;
- FIGS. 4A-4H are diagrams illustrating screens of a mobile user device executing a native application for online coupon redemption in accordance with an embodiment of the present invention
- FIG. 5 is a block diagram illustrating user actions and a first portion of a redemption process in accordance with an embodiment of the present invention
- FIG. 6 is a block diagram illustrating user actions and a first portion of a redemption process in accordance with an embodiment of the present invention
- FIG. 7 is a block diagram of a process for implementing drag-and-drop in a redemption process in accordance with an embodiment of the present invention.
- FIG. 8 is a block diagram of a mobile user device in accordance with an embodiment of the present invention.
- FIG. 1 shows an embodiment of an offer-discovery system 10 .
- the exemplary system 10 includes an offers engine 12 that, in some embodiments, is capable of reducing the burden on users attempting to identify offers relevant to them from among a relatively large pool of offers (e.g., more than 100, more than 1,000, or more than 10,000).
- the offers engine 12 maintains device-independent user profiles (or portions of user profiles) by which offers interfaces may be relatively consistently configured across multiple user devices with which the user interacts with the offers engine 12 .
- the offers engine 12 includes a number of features expected to facilitate relatively quick identification of relevant offers by a user, features that include cached storage of data related to likely relevant offers, faceted presentation of offers by which users can select among offers within various categories, and a number of other techniques described below for assisting with offer identification.
- the offers engine 12 is also expected to facilitate relatively low operating costs by, in some embodiments, automating parts of the process by which offer related data is acquired from sources, such as affiliate networks merchants, administrators, or users, and automating parts of the process by which transaction data indicative of acceptance, settlement, or clearing of offers is obtained and processed.
- the offers engine 12 includes a control module 14 , an application program interface (API) server 16 , a web server 18 , an ingest module 20 , an administration module 22 , a data store 24 , and a cache server 23 . These components, in some embodiments, communicate with one another in order to provide the functionality of the offers engine 12 described herein.
- API application program interface
- the data store 24 may store data about offers and users' interactions with those offers; the cache server 23 may expedite access to this data by storing likely relevant data in relatively high-speed memory, for example, in random-access memory or a solid-state drive; the web server 20 may serve webpages having offers interfaces by which users discover relevant offers; the API server 16 may serve data to various applications that process data related to offers; the ingest module 20 may facilitate the intake of data related to offers from affiliate networks, users, administrators, and merchants; and the administration module 22 may facilitate curation of offers presented by the API server 16 and the web server 18 .
- control module 14 may bidirectionally communicate with each of these components or direct the components to communicate with one another. Communication may occur by transmitting data between separate computing devices (e.g., via transmission control protocol/internet protocol (TCP/IP) communication over a network), by transmitting data between separate applications or processes on one computing device; or by passing values to and from functions, modules, or objects within an application or process, e.g., by reference or by value.
- TCP/IP transmission control protocol/internet protocol
- the offers engine 12 of this embodiment presents offers to users; receives data from users about their interaction with the offers (for example, the user's favorite offers or offer attributes; statistics about the offers the user has identified, accepted, or otherwise provided data about; or the identity of other users with whom the user communicates about offers and the content of those communications; provided that users opt to have such data obtained); customizes the presentation of offers based on this received data; and facilitates the processing of compensation from merchants (either directly or through affiliate networks) as a result of users accepting (or taking a specific action, like clicking or viewing, in some embodiments or use cases) offers.
- This interaction with users may occur via a website viewed on a desktop computer, tablet, or a laptop of the user.
- such interaction occurs via a mobile website viewed on a smart phone, tablet, or other mobile user device, or via a special-purpose native application executing on a smart phone, tablet, or other mobile user device.
- Presenting and facilitating interaction with offers across a variety of devices is expected to make it easier for users to identify and recall relevant offers at the time the user is interested in those offers, which is often different from the time at which the user first discovers the offers.
- some embodiments allow users to store data indicative of offers relevant to that user using one device, such as a desktop computer in the user's home, and then view those offers at a later time, such as on a native mobile application when in a retail store.
- the illustrated embodiment of FIG. 1 includes a number of components with which the offers engine 12 communicates: mobile user devices 28 and 30 ; a desk-top user device 32 ; a third party server 34 ; an administrator device 36 ; merchant servers 38 , 40 , and 42 ; and affiliate-network servers 44 and 46 .
- Each of these devices communicates with the offers engine 12 via a network 48 , such as the Internet or the Internet in combination with various other networks, like local area networks, cellular networks, or personal area networks.
- the mobile user devices 28 and 30 may be smart phones, tablets, gaming devices, or other hand-held networked computing devices having a display, a user input device (e.g., buttons, keys, voice recognition, or a single or multi-touch touchscreen), memory (such as a tangible, machine-readable, non-transitory memory), a network interface, a portable energy source (e.g., a battery), and a processor (a term which, as used herein, includes one or more processors) coupled to each of these components.
- the memory of the mobile user devices 28 and 30 may store instructions that when executed by the associated processor provide an operating system and various applications, including a web browser 50 or a native mobile application 52 .
- the native application 52 is operative to provide an offers interface that communicates with the offers engine 12 and facilitates user interaction with data from the offers engine 12 .
- the web browser 50 may be configured to receive a website from the offers engine 12 having data related to deals and instructions (for example, instructions expressed in JavaScriptTM) that when executed by the browser (which is executed by the processor) cause the mobile user device to communicate with the offers engine 12 and facilitate user interaction with data from the offers engine 12 .
- the native application 52 and the web browser 50 upon rendering a webpage from the offers engine 12 , may generally be referred to as client applications of the offers engine 12 , which in some embodiments may be referred to as a server.
- Embodiments, however, are not limited to client/server architectures, and the offers engine 12 , as illustrated, may include a variety of components other than those functioning primarily as a server.
- the desk-top user device 32 may also include a web browser 54 that serves the same or similar role as the web browser 50 in the mobile user device 30 .
- the desk-top user device 32 may include a monitor; a keyboard; a mouse; memory; a processor; and a tangible, non-transitory, machine-readable memory storing instructions that when executed by the processor provide an operating system and the web browser.
- Third-party offer server 34 may be configured to embed data from the offers engine 12 in websites or other services provided by the third-party offer server 34 .
- third-party offer server 34 may be a server of a social networking service upon which users post comments or statistics about offers with which the user has interacted, or the users may use the offer server 34 to recommend offers to others or identify offers to avoid.
- third-party offer server 34 may include various services for publishing content to the Web, such as blogs, tweets, likes, dislikes, ratings, and the like.
- third-party offer server 34 provides services by which third-parties curate offers hosted by the offers engine 12 .
- Merchant servers 38 , 40 , and 42 host websites or other user accessible content interfaces by which users can accept offers hosted by the offers engine 12 .
- the merchant servers 38 , 40 , and 42 host retail websites that present a plurality of items for sale by the merchant, a subset of which may include items to which offers apply, thereby generally making the item for sale more desirable to cost-sensitive consumers than under the terms presented by the merchant in the absence of the offer.
- the offers may include free or discounted shipping, a discounted price, a bulk discount, a rebate, a referral award, or a coupon, such as a coupon acceptable by presenting a coupon code during checkout on the merchant website, or a printable or displayable coupon (e.g., on the screen of a mobile device) for in-store use, the printable or otherwise displayable coupon having, in some cases, a machine readable code (e.g., a bar code or QR code for display and scanning, or a code passed via near-field communication or BluetoothTM).
- a machine readable code e.g., a bar code or QR code for display and scanning, or a code passed via near-field communication or BluetoothTM.
- the merchant website includes a checkout webpage having an interface for the user to enter payment information and a coupon code
- the merchant website may validate the coupon code entered by the user and, upon determining that the coupon code is valid, adjust the terms presented to the user for acceptance in accordance with the offer.
- Some merchants may limit the number of uses of a given coupon, limit the duration over which the coupon is valid, or apply other conditions to use of the coupon, each of which may add to the burden faced by users seeking to find valid coupons applicable to an item the user wishes to purchase. As noted above, some embodiments of the offers engine 12 are expected to mitigate this burden.
- the merchant servers 38 , 40 , and 42 provide data about offers to the offers engine 12 or (i.e., and/or, as used herein, unless otherwise indicated) data about transactions involving offers.
- the transaction data may provide the basis for payments by the merchant directly to the operator of the offers engine 12 . For example, payments may be based on a percentage of transactions to which offers were applied, a number of sales to which offers were applied, or a number of users who viewed or selected or otherwise interacted with an offer by the merchant.
- affiliate-network servers 44 and 46 are engaged when the entity operating the offers engine 12 does not have a direct affiliate-marketing relationship with the merchant making a given offer.
- merchants compensate outside entities, such as third-party publishers, for certain activities related to sales by that merchant and spurred by the outside entity.
- merchants compensate an affiliate, such as the entity operating the offers engine 12 , in cases in which it can be shown that the affiliate provided a given coupon code to a given user who then used that coupon code in a transaction with the merchant. Demonstrating this connection to the merchant is one of the functions of the affiliate-networks.
- affiliate-networks are used, in some use cases, because many coupon codes are not affiliate specific and are shared across multiple affiliates, as the merchant often desires the widest distribution of a relatively easily remembered coupon code. Accordingly, in some use cases, the merchant, affiliate network, and affiliate cooperate to use client-side storage to indicate the identity of the affiliate that provided a given coupon code to a user.
- client-side storage to indicate the identity of the affiliate that provided a given coupon code to a user.
- a webpage offers interface is presented by the offers engine 12 in the web browsers 50 or 54
- that webpage is configured by the offers engine 12 to include instructions to engage the affiliate network server 44 or 46 when a user selects an offer, for example, by clicking on, touching, or otherwise registering a selection of an offer.
- the website provided by the offers engine 12 responds to such a selection by, in some embodiments, transmitting a request to the appropriate affiliate-network server 44 or 46 (as identified by, for example, an associated uniform resource locator (URL) in the webpage) for a webpage or portion of a webpage (e.g., browser-executable content).
- a request to the appropriate affiliate-network server 44 or 46 as identified by, for example, an associated uniform resource locator (URL) in the webpage
- URL uniform resource locator
- the request to the affiliate-network server may include (e.g., as parameters of the URL) an identifier of the affiliate, the offer, and the merchant, and the returned content from the affiliate-network server may include instructions for the web browser 50 or 54 to store in memory (e.g., in a cookie, or other form of browser-accessible memory, such as a SQLite database or in a localStorage object via a localStorage.setItem command) an identifier of the affiliate that provided the offer that was selected.
- memory e.g., in a cookie, or other form of browser-accessible memory, such as a SQLite database or in a localStorage object via a localStorage.setItem command
- the webpage from the offers engine 12 may further include browser instructions to navigate to the website served by the merchant server 38 , 40 , or 42 of the merchant associated with the offer selected by the user, and in some cases to the webpage of the item or service associated with the offer selected by the user.
- the merchant server 38 , 40 , or 42 may transmit to the user device upon which the item was purchased browser instructions to request content from the affiliate network server 44 or 46 , and this requested content may retrieve from the client-side memory the identifier of the affiliate, such as the operator of the offers engine 12 , who provided the information about the offer to the user.
- the affiliate network may then report to the merchant the identity of the affiliate who should be credited with the transaction, and the merchant may compensate the affiliate (or the affiliate network may bill the merchant, and the affiliate network may compensate the affiliate), such as the operator of the offers engine 12 .
- the affiliate network in this example acts as an intermediary, potentially avoiding the need for cross-domain access to browser memory on the client device, a feature which is generally not supported by web browsers for security reasons.
- Some embodiments may, however, store in client-side browser-accessible memory an identifier of the affiliate upon user selection of the offer, with this value designated as being accessible via the merchant's domain, and provide the value to the merchant upon a merchant request following acceptance of the offer, without passing the identifier through an affiliate network, using a browser plug-in for providing cross-domain access to browser memory or a browser otherwise configured to provide such access.
- the native application 52 includes or is capable of instantiating a web browser, like the web browser 50 , in response to a user selecting an offer presented by the native application 52 .
- the web browser instantiated by the native application 52 may be initialized by submitting the above-mentioned request for content to the affiliate-network server 44 or 46 , thereby storing an identifier of the affiliate (i.e., the entity operating the offers engine 12 in this example) in client-side storage (e.g., in a cookie, localStorage object, or a database) of the mobile user device 28 , and thereby navigating that browser to the merchant website.
- client-side storage e.g., in a cookie, localStorage object, or a database
- the operator of the offers engine 12 has a direct relationship with the merchant issuing the offer, and the selection of an offer within the native application 52 or the desktop or mobile website of the offers engine 12 (generally referred to herein as examples of an offer interface) may cause the user device to request a website from the associated merchant with an identifier of the affiliate included in the request, for example as a parameter of a URL transmitted in a GET request to the merchant server 38 , 40 , or 42 for the merchant's website.
- Administrator device 36 may be a special-purpose application or a web-based application operable to administer operation of the offers engine 12 , e.g., during use by employees or agents of the entity operating the offers engine 12 .
- the administration module 22 may communicate with the administrator device 36 to present an administration interface at the administrator device 36 by which an administrator may configure offers interfaces presented to users by the offers engine 12 .
- the administrator may enter offers into the offers engine 12 ; delete offers from the offers engine 12 ; identify offers for prominent placement within the offers interface (e.g., for initial presentation prior to user interaction); moderate comments on offers; view statistics on offers, merchants, or users; add content to enhance the presentation of offers; or categorize offers.
- the offers engine 12 operates in the illustrated environment by communicating with a number of different devices and transmitting instructions to various devices to communicate with one another.
- the number of illustrated merchant servers, affiliate network servers, third-party servers, user devices, and administrator devices is selected for explanatory purposes only, and embodiments are not limited to the specific number of any such devices illustrated by FIG. 1 .
- the offers engine 12 of some embodiments includes a number of components introduced above that facilitate the discovery of offers by users.
- the illustrated API server 16 may be configured to communicate data about offers via an offers protocol, such as a representational-state-transfer (REST)-based API protocol over hypertext transfer protocol (HTTP).
- REST representational-state-transfer
- HTTP hypertext transfer protocol
- Examples of services that may be exposed by the API server 18 include requests to modify, add, or retrieve portions or all of user profiles, offers, or comments about offers.
- API requests may identify which data is to be modified, added, or retrieved by specifying criteria for identifying records, such as queries for retrieving or processing information about particular categories of offers, offers from particular merchants, or data about particular users.
- the API server 16 communicates with the native application 52 of the mobile user device 28 or the third-party offer server 34 .
- the illustrated web server 18 may be configured to receive requests for offers interfaces encoded in a webpage (e.g. a collection of resources to be rendered by the browser and associated plug-ins, including execution of scripts, such as JavaScriptTM, invoked by the webpage).
- the offers interface may include inputs by which the user may request additional data, such as clickable or touchable display regions or display regions for text input. Such inputs may prompt the browser to request additional data from the web server 18 or transmit data to the web server 18 , and the web server 18 may respond to such requests by obtaining the requested data and returning it to the user device or acting upon the transmitted data (e.g., storing posted data or executing posted commands).
- the requests are for a new webpage or for data upon which client-side scripts will base changes in the webpage, such as XMLHttpRequest requests for data in a serialized format, e.g. JavaScriptTM object notation (JSON) or extensible markup language (XML).
- the web server 18 may communicate with web browsers, such as the web browser 50 or 54 executed by user devices 30 or 32 .
- the webpage is modified by the web server 18 based on the type of user device, e.g., with a mobile webpage having fewer and smaller images and a narrower width being presented to the mobile user device 30 , and a larger, more content rich webpage being presented to the desk-top user device 32 .
- An identifier of the type of user device may be encoded in the request for the webpage by the web browser (e.g., as a user agent type in an HTTP header associated with a GET request), and the web server 18 may select the appropriate offers interface based on this embedded identifier, thereby providing an offers interface appropriately configured for the specific user device in use.
- the illustrated ingest module 20 may be configured to receive data about new offers (e.g., offers that are potentially not presently stored in the data store 24 ), such as data feeds from the affiliate network servers 44 and 46 , identifications of offers from user devices 28 , 30 , or 32 , offers identified by third-party offer server 34 , offers identified by merchant servers 38 , 40 , or 42 , or offers entered by an administrator via the administrator device 36 .
- the ingest module 20 may respond to receipt of a record identifying a potentially new offer by querying the data store 24 to determine whether the offer is presently stored. Upon determining that the offer is not presently stored by the data store 24 , the ingest module 20 may transmit a request to the data store 24 to store the record.
- the data about new offers may be an affiliate data-feed from an affiliate network containing a plurality of offer records (e.g., more than 100), each record identifying offer terms, a merchant, a URL of the merchant associated with the offer, a product description, and an offer identifier.
- the ingest module 22 may periodically query such data-feeds from the affiliate-network servers 44 or 46 , parse the data-feeds, and iterate through (or map each entry to one of a plurality of processes operating in parallel) the records in the data-feeds. Bulk, automated processing of such data-feeds is expected to lower operating costs of the offers engine 12 .
- the administration module 22 may provide an interface by which an administrator operating the administrator device 36 curates and contextualizes offers. For example, the administration module 22 may receive instructions from administrator that identify offers to be presented in the offer interface prior to user interaction with the offer interface, or offers to be presented in this initialized offers interface for certain categories of users, such as users having certain attributes within their user profile. Further, in some embodiments, the administration module 22 may receive data descriptive of offers from the administrator, such as URLs of images relevant to the offer, categorizations of the offer, normalized data about the offer, and the like.
- the illustrated data store 24 stores data about offers and user interactions with those offers.
- the data store 24 may include various types of data stores, including relational or non-relational databases, document collections, hierarchical key-value pairs, or memory images, for example.
- the data store 24 includes a user data store 56 , a session data store 58 , an offers data store 60 , and an analytics data store 62 .
- These data stores 56 , 58 , 60 , and 62 may be stored in a single database, document, or the like, or may be stored in separate data structures.
- the illustrated user data store 56 includes a plurality of records, each record being a user profile and having a user identifier, a list of offers (e.g., identifiers of offers) identified by the user as favorites, a list of categories of offers identified by the user as favorites, a list of merchants identified by the user as favorites, account information for interfacing with other services to which the user subscribes (e.g., a plurality of access records, each record including an identifier of a service, a URL of the service, a user identifier for the service, an OAuth access token credential issued by the service at the user's request, and an expiration time of the credential), a user password for the offers engine 12 , a location of the user device or the user (e.g., a zip code of the user), and a gender of the user.
- a list of offers e.g., identifiers of offers
- account information for interfacing with other services to which the user subscribes e.g., a pluralit
- each user profile includes a list of other users identified by the user of the user profile as being people in whose commentary on, or curation of, offers the user is interested, thereby forming an offers-interest graph.
- users have control of their data, including what is stored and who can view the data, and can choose to opt-in to the collection and storage of such user data to improve their experience with the offers engine 12 .
- the session data store 58 stores a plurality of session records, each record including information about a session a given user is having or has had with the offers engine 12 .
- the session records may specify a session identifier, a user identifier, and state data about the session, including which requests have been received from the user and what data has been transmitted to the user.
- Session records may also indicate the IP address of the user device, timestamps of exchanges with the user device, and a location of the user device (e.g., retail store or aisle in a retail store in which the user device is located).
- the illustrated offers data store 60 includes a plurality of offer records, each offer record may identify a merchant, offers by that merchant, and attributes of the relationship with the merchant, e.g., whether there is a direct relationship with the merchant by which the merchant directly compensates the operator of the offers engine 12 or whether the merchant compensates the operator of the offers engine 12 via an affiliate network and which affiliate network.
- the offers by each merchant may be stored in a plurality of merchant-offer records, each merchant-offer record may specify applicable terms and conditions of the offer, e.g., whether the offer is a discount, includes free or discounted shipping, requires purchase of a certain number of items, is a rebate, or is a coupon (which is not to suggest that these designations are mutually exclusive).
- the record may further indicate whether the coupon is for in-store use (e.g. whether the coupon is associated with a printable image for presentation at a point-of-sale terminal, a mobile device-displayable image, or other mediums) or whether the coupon is for online use and has a coupon code, in which case the coupon code is also part of the merchant-offer record.
- the merchant-offer records may also include an expiration date of the offer, comments on the offer, rankings of the offer by users, a time at which the offer was first issued or entered into the offers engine 12 , and values (e.g., binary values) indicating whether users found the offer to be effective, with each value or ranking being associated with a timestamp, in some embodiments.
- the values and rankings may be used to calculate statistics indicative of the desirability of the offer and likely success of accepting the offer.
- the timestamps associated with the values, rankings, and time of issuance or entry into the offers engine 12 may also be used to weight rankings of the offer, with older values being assigned less weight than newer values and older offers being ranked lower than newer offers, all other things being equal, as many offers expire or have a limited number of uses.
- the illustrated analytics data store 62 may store a plurality of records about historical interactions with the offers engine 12 , such as aggregate statistics about the performance of various offers.
- the analytics data store 62 stores a plurality of transaction records, each transaction record identifying an offer that was accepted by a user at a merchant, the merchant, the time of presentation of the offer to the user, and an indicator of whether the merchant has compensated the entity operating the offers engine 12 for presentation of the offer to the user. Storing and auditing these transaction records is expected to facilitate relatively accurate collection of payments owed by merchants and identification of future offers likely to lead to a relatively high rates of compensation for prominent presentation based on past performance of offers having similar attributes.
- the cache server 23 stores a subset of the data in the data store 24 that is among the more likely data to be accessed in the near future.
- the cache server 23 may store cached data in relatively high speed memory, such as random access memory or a solid-state drive.
- the cached data may include offers entered into the offers engine 12 within a threshold period of time, such as offers that are newer than one day.
- the cache data may include offers that are accessed with greater than a threshold frequency, such as offers that are accessed more than once a day, or offers accessed within the threshold, such as offers accessed within the previous day. Caching such offer data is expected to facilitate faster access to offer data than systems that do not cache offer data.
- the illustrated control module 14 controls the operation of the other components of the offers engine 12 , receiving requests for data or requests to add or modify data from the API server 16 , the web server 18 , the ingest module 20 , and the administration module 22 , and instructing the data store 24 to modify, retrieve, or add data in accordance with the request.
- the control module 14 may further instruct the cache server 23 to modify data mirrored in the cache server 23 .
- the cache server 23 may be updated hourly, and inconsistent data may potentially be maintained in the cache server 23 in order to conserve computing resources.
- the illustrated components of the offers engine 12 are depicted as discrete functional blocks, but embodiments are not limited to systems in which the functionality described herein is organized as illustrated by FIG. 1 .
- the functionality provided by each of the components of the offers engine 12 may be provided by software or hardware modules that are differently organized than is presently depicted, for example such software or hardware may be intermingled, broken up, distributed (e.g. within a data center or geographically), or otherwise differently organized.
- the functionality described herein may be provided by one or more processors of one or more computers executing code stored on a tangible, non-transitory, machine readable medium.
- FIG. 2 is a flowchart of a process 64 for acquiring data related to offers within some embodiments of the offer engine 12 discussed above.
- the process 64 begins with receiving offer data describing a plurality of offers from affiliate networks, merchants, and users, as illustrated by block 66 . This step may be performed by the above-mentioned ingest module 20 .
- the received offer data may be received from one or all of these sources.
- the received offer data may be received via an offer interface by which users associated with these sources enter data about offers, or the received offer data may be received in a predefined format, such as a serialized data format, in an automatic data feed pushed or pulled periodically or in response to the availability of new data from affiliate networks or merchants.
- Receiving the offer data may include determining whether the offer data is redundant to offer data already received and normalizing the offer data.
- the process 64 includes normalizing and enriching the offer data.
- Normalizing may include normalizing field names of the data and normalizing the way in which dates are expressed, for example.
- Enriching may include associating images with the offers for presentation with the offers and adding metadata to the offers to assist users searching for offers.
- the received offer data is stored in an offer data store, as indicated by block 68 .
- Storing the offer data in the offer data store may include identifying a merchant to which the offer pertains and storing the offer in a merchant-offer record associated with that merchant. Further, some embodiments may include inserting the offer in order in a sorted list of offers for relatively fast retrieval of offers using a binary search algorithm or other techniques to facilitate relatively quick access to data that has been preprocessed (e.g., using a prefix trie).
- storing the received offer may further include updating hash tables by which the offer may be retrieved according to various parameters, each hash table being associated with one parameter and including a hash key value calculated based on the parameter and paired with an address of the offer.
- hash tables are expected to facilitate relatively fast access to a given offer as the need to iterate through potentially all offers meeting certain criteria may be potentially avoided.
- the process 64 further includes receiving a request from a user device for offers, as indicated by block 70 .
- the request may specify criteria for identifying offers, such as categories of offers, search terms for offers, or requests for offers designated as favorites.
- the present embodiment includes identifying offers in the offer data store responsive to the user request, as indicated by block 72 .
- Identifying offers in the offer data store may be performed by the above-mentioned controller 14 ( FIG. 1 ) by constructing a query to the offer data store 60 based on a request received from the web server 18 or the API server 16 .
- the query may be transmitted to the offer data store 60 , or to the cache server 23 , each of which may return responsive records.
- Transmitting the identified offers may include transmitting the identified offers in an offer interface, such as a webpage, or an API transmission to a native mobile application, for example by the web server 18 , or the API server 16 of FIG. 1 , respectively.
- the device receiving the identified offers may, in response, perform a process described below with reference to FIG. 3 by which additional offers are requested or an offer is selected and a purchase is executed.
- This process of FIG. 3 and steps 70 through 74 of FIG. 2 may be repeated numerous times, in some use cases, before advancing to the next steps. Further, the steps 66 through 68 may be repeated numerous times independently of (e.g., concurrent with) the performance of steps 70 through 74 of FIG. 2 (which is not to suggest that other steps described herein may not also be executed independently). That is, the process 64 may undergo step 60 and 68 , for example, 50 times within a given time, while performing steps 70 through 74 500 times within that given time, and performing the remaining steps of process 64 a single time.
- a user device undergoing the process of FIG. 3 may indicate to an offers engine that the user has selected an offer (e.g., by clicking on or touching a selectable element in an offers interface associated with the offer).
- the offers engine may direct the user device to an affiliate-network server or a merchant server associated with the offer, as illustrated by block 75 .
- this embodiment of the process 64 includes receiving from merchants or affiliate networks transaction data identifying offers accepted via the user device, as illustrated by block 76 .
- the transaction data may be pulled from these sources, for example, by the ingest module 20 of FIG. 1 , periodically, or in response to some threshold number of transactions having occurred.
- the receipt transaction data may be stored in an analytics data store, as indicated by block 78 .
- this data may be stored in the analytics data store 62 of FIG. 1 .
- Storing the transaction data is expected to facilitate the identification of attributes of relatively profitable offers, as the transaction data indicates which offers historically yielded compensable transactions. Further, storing the transaction data is expected to facilitate relatively accurate auditing of payments from merchants or affiliate networks.
- FIG. 3 is a flowchart of an embodiment of a process 80 that provides an example of an offer interface at a user device.
- the process 80 may be performed by the above-mentioned native application 52 or web browser 50 or 54 in cooperation with the offers engine 12 .
- Some embodiments of process 80 begin with receiving, at a user device, instructions that cause the user device to display an offers interface, as indicated by block 82 .
- the received instructions may be in the form of a downloaded native application, such as one downloaded from an application store hosted by a provider of mobile devices, or the received instructions may be in the form of a website received from the offers engine 12 and rendered in a browser of the user device.
- the process 80 further includes receiving, at the user device, a plurality of offers, as indicated by block 84 , and displaying, at the user device, the offers in the offer interface, as indicated by block 86 .
- the offers may be received at approximately the same time the instructions of step 82 are received, for example along with a webpage, or the offers may be received at a later date, for example during a session subsequent to downloading the native application.
- the offers interface may include inputs by which the user may search, filter, or otherwise browse offers having various attributes. Some of these interfaces are described below with reference to steps performed to determine whether the user has engaged these inputs. In some embodiments, determining whether the user has engaged these inputs may be performed by an event handler executed by the user device, the event handler causing the user device to perform the corresponding, below-described requests to the offers engine 12 based on the type of event, e.g., whether the user touched, clicked, or otherwise selected a particular button on the offers interface.
- Illustrated process 80 includes determining whether the user is searching for offers, as indicated by block 88 .
- the user may express their intention to search for offers by entering search terms in a text entry box and selecting a button to request a search in accordance with the entered search term.
- the user device may transmit a request for offers satisfying the entered search criteria, as indicated by block 90 .
- the transmitted request may be in the form of a GET request or an API call to the web server 18 or the API server 16 of the offers engine 12 of FIG. 1 .
- the process 80 further includes determining whether the user requests offers within a collection of offers, as indicated by block 92 .
- the offers interface may include selectable inputs that identify the collections, such as clickable collection names, collection selection buttons, or collection selection tabs. Examples of collections include categories of goods or services, such as sporting goods, house-wares, groceries, and the like; collections of modes of coupon redemption, such as in-store coupon redemption and online coupon redemption; collections based on offer statistics, such as newest offers, most popular offers, highest ranked offers; collections of offers designated by a user or other users; or collections based the value conferred by the offer, such as discounts, free shipping, rebates, and referral fees.
- the user device may transmit a request for offers within the collection to the offers engine 12 , as indicated by block 94 , which may return data responsive to the request.
- the process 80 includes determining whether the user requests offers previously designated by the user, as indicated by block 96 .
- the offers interface may include an input by which a user can designate an offer, such as designating offers as being a user favorite, designating offers as being ranked in a particular fashion, or designating offers as likely being of interest to some other user, such as users adjacent one another in a social graph.
- the offers interface may include an input for a user to make designations, such as a user selectable input labeled “add to my favorites,” or “add to my wallet,” and an input for a user to request offers having a designation, such as a user selectable input labeled “view my favorites.” or “view my wallet.”
- the process 80 includes transmitting a request for the offers previously designated by the user, as indicated by block 88 .
- the transmission may be made to the offers engine 12 , to the API server 16 or the web server 18 , as described above with reference to FIG. 1 , and may include an identification of the designation and the user.
- the process 80 further includes determining whether the user requests offers previously designated by another user, as indicated by block 100 .
- the offers interface may include an input by which a user makes such a request, such as a user selectable input labeled “offers recommended by my friends.”
- the process 80 transmits a request for offers previously designated by the other user (or users), as indicated by block 102 . Again, the transmission may be to the offers engine 12 of FIG. 1 , which may store or otherwise have access to offers designated by other users and a social graph of the user by which responsive offers are identified.
- the offers interface may include an input by which the user may view identifiers of other users and add the other users to an offer-interest graph of the user.
- This offer interest graph may be referenced by the offers engine 12 to identify offers in response to the request of step 102 .
- the process 80 further includes, in some embodiments, receiving, at the user device, one or more offers responsive to the request, as indicated by block 104 , and displaying the responsive offers on the offers interface, as indicated by block 106 .
- a selection from the user is received via the offers interface, thereby identifying an offer among the displayed offers, as indicated by block 108 .
- each of the offers may be displayed with an associated input by which the user selects the offer, such as a touchable or clickable button, region, or text.
- the selection may cause the offers interface to request additional data from the offers engine, such as instructions from the offers engine to navigate to an affiliate-network server associated with the offer or to navigate to a merchant server associated with the offer.
- such instructions may be present within the offers interface, e.g., in the form of URLs linking to these servers.
- the process 80 further includes determining whether the selected offer is compensable through an affiliate network, as indicated by block 110 .
- This determination may be made by the offers engine 12 , in some embodiments, for each of the offers being displayed prior to transmission of the offers to the user device.
- each offer may be associated with a designation indicating whether the offer is compensable in this fashion, and the designation may be transmitted along with the offer, for instance, by associating the offer with HTML or JavaScriptTM that so designate the offer, or by including a field including the designation in a response to an API call for each offer.
- the user device in some embodiments, may take different actions depending on the designation associated with the selected offer.
- the process 80 of this embodiment includes determining whether the selected offer is compensable directly from the merchant associated with the offer, as indicated by block 112 .
- the determination of block 112 may be performed, in some embodiments, by the offers engine 12 for each of the offers being displayed prior to transmission of the displayed offers, and each displayed offer may be associated with a designation based on the results of the determination, such as different HTML or JavaScriptTM or a different field value in an API response. The user device may take different actions depending on this designation.
- the process 80 may proceed to block 118 described below.
- the process 80 may proceed to request the website of the merchant issuing the selected offer with a request that identifies the affiliate from whom the selected offer was obtained, as indicated by block 114 .
- the request may be in the form of a URL having as a parameter an identifier of the entity operating the offer engine 12 , thereby indicating to the merchant that the affiliate should be compensated in accordance with an arrangement between the merchant and the affiliate.
- the process 80 of the present embodiment proceeds to step 120 described below.
- the process 80 proceeds to transmit a request to the affiliate-network server for instructions to store data identifying an affiliate from whom the selected offer was obtained, as indicated by block 116 .
- This request may be a request for content from the affiliate-network server that is not displayed to the user, or is not displayed to the user for an appreciable amount of time (e.g., less than 500 ms), and the request may include an identifier of the affiliate, the merchant, and the offer.
- the requested content may cause the user device to store in persistent memory of the browser of the user device (e.g., memory that lasts between sessions, such as a cookie or a database of the browser) an identifier of the affiliate operating the offers engine 12 .
- This value may be retrieved later by the affiliate-network at the instruction of the merchant upon the user accepting the offer, for example by the user using a coupon code associated with the offer at the merchant, thereby allowing the merchant (or the affiliate network) to identify the appropriate party to compensate for the sale.
- the process 80 Upon transmitting the request the affiliate network server, the process 80 further includes requesting the website of the merchant issuing the selected offer, as indicated by block 118 , and transmitting acceptance of the offer to the merchant via the merchant's website, as indicated by block 120 . Accepting the offer, as noted above, may cause the merchant to compensate the affiliate operating the offers engine 12 .
- the process 80 of FIG. 3 is expected to facilitate relatively fast access to offers that are likely to be relevant to a user, as each of the determinations of step 88 , 92 , 96 , and 100 provide different paths by which the user can specify offers in which the user is likely to be interested. Further, the determinations of step 110 and 112 provide dual mechanisms by which the operator of the offers engine 12 can be compensated, thereby potentially increasing revenue.
- a native application interacts with the offers engine above to provide offers to users.
- Embodiments of the native application include functionality to enable users to redeem certain types of offers, e.g., online coupons.
- a native application may provide for easier and faster redemption of offers and may eliminate or reduce complicated user actions to redeem online coupons.
- FIGS. 4A-4H depict screens of a native application, such as native application 52 ( FIG. 1 ), executing on a mobile user device, such as mobile user device 28 , illustrating redemption of online coupons, the native application operating in accordance with an embodiment of the present invention.
- FIG. 4A depicts a screen 400 of a native application 402 in accordance with an embodiment of the present invention.
- the screen 400 and other screens described below may be presented in a user interface of the mobile user device that may receive inputs from a user and provide outputs on a display.
- the user interface may include a touchscreen, software modules, or any combination thereof.
- inputs may be received as touches on the touchscreen, such as from a digit of a user, a stylus, etc.
- the screen 400 may include various user interface elements to display information to a user, and in some instances, receive user input.
- the screen 400 may include a header portion 404 , a coupon type toggle 406 , an offer display area 408 , and a navigation bar 410 .
- These user interface elements may be located at various locations defined by sets of coordinates of the touchscreen, such as x-coordinates associated with a horizontal position and y-coordinates associated with a vertical position.
- the header portion 404 may be located at the top portion of the screen 400 (e.g., above the coupon type toggle 406 and the offer display area 408 ).
- the navigation bar 410 may be displayed below the offer display area 408 .
- the information in the header portion 404 may be displayed in other areas, such as a footer portion, and the navigation bar 408 may be located in other areas of the application, such as a header portion.
- the header portion 404 may display a title indicating the contents of the screen 400 presented to the user, as selected by the coupon type toggle 406 .
- the header portion 404 includes the text “Top Coupons,” indicating to a user that top-ranked coupons are currently being presented.
- the coupon type toggle 406 may include a toggle button or other user interface element that enables a user to toggle between different types of coupons.
- the coupon type toggle 406 may enable a user to toggle between “Online” coupons and “In Store” coupons.
- the navigation bar 408 may include navigation controls, e.g., buttons 412 , such as a “Home” button 412 A and a “Profile” button 412 B.
- buttons 412 such as a “Home” button 412 A and a “Profile” button 412 B.
- the “Profile” button 412 B enables a user to access a user profile associated with the application.
- the coupon area display area 408 may present offers, e.g., online coupons 414 , for viewing and selection by a user.
- the online coupons 414 may be top-ranked coupons determined by ranking criteria, such as user ratings, success rate, or other ranking criteria.
- the online coupons 414 may include any number of coupons associated with merchants providing goods, services, or a combination thereof.
- Each electronic coupon 414 may be presented with information describing the coupon, such as a merchant graphic 416 , a success rate banner 418 , and a coupon summary 420 .
- the merchant graphic 416 may include text, an image (e.g., a merchant logo), or combination thereof identifying the merchant associated with the coupon.
- the success rate banner 418 may indicate a success rate for a coupon that indicates the percentage of instances in which the coupon was successfully used. In some embodiments, for example, the success rate may be determined based on user feedback on coupon usage.
- the coupon summary 420 may include information about the coupon, such as the goods, services, or both associated with the coupon, the discount or other offer provided by the coupon, the expiration date, any other suitable information, or a combination thereof.
- a first electronic coupon 414 A may be presented with a merchant graphic 416 A (“Merchant1”) and may include a success rate banner 418 A indicating the success rate of the coupon (“100% success”).
- the coupon 414 A may be presented with a coupon summary 420 A summarizing the discount provided by the coupon (“40% Off Save up to 40% on select diapers from Acme Co . . . ”).
- the coupon summary 420 A may include the expiration date of the coupon (“Exp. Jun. 40, 2012”).
- the other coupons 414 B and 414 C illustrated in FIG. 4A may include similar information, such as merchant graphic 416 B, success rate banner 418 B, coupon summary 420 B, and so on.
- the coupons 414 may include coupons for any type of offer, such as offers for free goods, services, or both, as indicated by the coupon summary 420 C for electronic coupon 414 C (“20 Free Tokens”).
- a user may select (e.g., touch) one of the online coupons 414 .
- a user may select any portion of the coupon 414 A, such as the merchant graphic 416 A, the coupon summary 420 A, etc.
- details about the coupon may be presented to enable a user to use the coupon (i.e., redeem the coupon) with a transaction with a merchant.
- FIG. 4B depicts another screen 422 of a mobile user device in accordance with an embodiment of the present invention. The screen 422 may be presented in response to a user selection of an electronic coupon, such as selection of the coupon 414 A depicted in FIG. 4A . As shown in FIG.
- the header portion 404 may change to include the name of the merchant (“Merchant1 Coupon”) to indicate contents of the screen 422 .
- the screen 422 may include a coupon detail area 424 , a social network portion 426 , and the navigation bar 410 described above.
- the coupon detail area 424 presents detailed information about the selected electronic coupon 414 A.
- a merchant graphic 427 may be presented.
- the coupon detail area 424 may include various controls, such as a save button 432 , a “Use Coupon” button 434 , and a “Share” button 436 .
- the controls may be any suitable user interface control, such as toggles, icons, switches, sliders, etc.
- the merchant graphic 427 may display text, images (e.g., logos), or any combination thereof associated with the merchant
- the success rate banner 428 may display a determined success rate for the selected coupon 416 A, such as a success rate based on user feedback.
- the coupon detail area 424 displays a coupon code box 436 having an identifier, e.g., a coupon code 438 (“PMPRSYT8”), associated with the coupon 414 A.
- the coupon code 446 may be displayed in the coupon code box 436 or other element of a user interface.
- the coupon code 438 may be a relatively short text string (e.g., shorter than 25 characters or 5 words) selected to be both distinct and memorable to users. In some cases, an image or other visibly distinctive user-manipulable body of data serves the role of the coupon code 438 .
- the movement of the coupon code box 436 may be animated to indicate various transitions within the native application 402 , potentially making the operation of the native application more intuitive to users.
- the coupon detail area 424 includes various user interface elements to receive inputs from a user.
- the save button 432 presented in the coupon detail area 424 enables a user to save a coupon for later use.
- the share button 436 enables a user to share coupons, such as sharing across social networking services, microblogging services, or other services.
- a user may select (e.g., touch) the “Use Coupon” button 434 .
- the “Use Coupon” button 434 upon selection of the “Use Coupon” button 434 , another screen may be presented that enables a user to access the website of the merchant associated with the selected coupon 414 A.
- Corresponding event handlers of the native application may detect the user interactions described herein (e.g., on Touch, onClick, on Move, touch events, and the like) and, in response, effectuate the described functionality.
- the feedback portion 426 depicted in the screen 422 may include information from other users and a user's profile.
- the feedback and profile may be provided within the native application 402 .
- the feedback portion 426 may present a comment indicator 440 that indicates if other users have commented on the selected coupon 416 A and provides the number of such comments.
- the feedback portion 426 may include user profile information 428 , such as a picture 442 associated with a user's profile and other profile information.
- a user may select the “Use Coupon” button 434 to use the selected coupon 414 A for a purchase of goods and services.
- the coupon code box 436 may visually move from a first location 443 shown in the screen 422 to a second location. This movement is illustrated by the arrows depicted in FIGS. 4B-4D .
- the coupon code box 436 may move (e.g., translate) along the path indicated by arrow 444 .
- the coupon code box 436 may move in towards the header portion 404 , translating through changing x and y coordinates.
- the coupon code box 436 may move along a generally linear path, a generally arcuate path, or any combination thereof. In other embodiments, the coupon code box 436 may move to any other locations, such as a footer or other locations within the screen 422 . Additionally, in some embodiments, the coupon code box 436 may only be provided at the second location without animation of a visual movement.
- FIG. 4C further depicts the screen 422 and illustrates a stage in the animation of the coupon code box 436 in accordance with an embodiment of the present invention.
- the coupon code box 436 may move from the first location 443 and along the path indicated by arrow 444 towards a second location at the header portion 404 .
- the coupon code box 436 may continue to move (e.g., translate) towards the header portion 404 , as indicated by arrow 446 .
- FIG. 4D depicts a screen 453 of a mobile user device that illustrates the completion of the animation of the coupon code box 436 in accordance with an embodiment of the present invention.
- the screen 453 includes a merchant website 454 displayed by the mobile user device.
- the website of the merchant associated with coupon may be presented to enable a user to purchase goods or services from the merchant using the coupon.
- the native application 402 may be include or be capable of instantiating a web browser, e.g., a webview object, and the merchant website may be retrieved via an affiliate networking redemption process by which the web browser requests content from an affiliate network server, the request including an identifier of the provider of the native application, and the affiliate network returning content operative to store an affiliate identifier in a cookie (or other persistent, browser-accessible storage) accessible to the affiliate network operator and instructions to redirect the browser to the merchant website.
- an identifier of the provider of the native application may be appended to a URL of the merchant website to signal that the provider should be compensated.
- web content such as the merchant website 454
- web content may be retrieved from the Internet via a network accessible by a mobile user device executing the native application 402 , as described above.
- the presentation of web content in the native application 402 may be referred to as a “web view.”
- FIG. 4D depicts the end of the animation of the coupon code box 436 .
- the coupon code box 436 moves (e.g., translates) in a generally vertical direction to a second location 455 until the coupon code box 436 is located in the header portion.
- the coupon code box 436 may be resized. Any previous text, images or other elements in the header portion 404 may be removed or replaced upon progression to the screen 453 .
- the header portion 404 of the screen 453 may also include a “Done” button 456 .
- the screen 453 includes a web navigation bar 458 located below the merchant website 454 . As described below, the web navigation bar 458 may include controls for browsing the web content, e.g., the merchant website 454 , presented in the application 402 .
- Depicting the coupon code 438 in a different location after a user selects the use coupon button 434 is expected to make coupon use more intuitive, as the user has a visual indication that a coupon code 438 has been selected, and that the native application is storing the coupon code 438 for use.
- Depicting an animated movement to such a location e.g., simulating movement of a physical item, is expected to make the native application appear responsive to the user and create a sense that the coupon code 438 is more like a tangible physical item to be accorded elevated importance in the mind of the user.
- the movement may be of constant speed, or movement may change speed, simulating for example generally constant acceleration and deceleration with an intervening duration of constant speed.
- animated movement may simulate damped vibrating movements as the coupon code 438 settles into the second position.
- the coupon code 438 may also rotate or perform other movements as it translates to accentuate the effect.
- the coupon code 438 may also change size, e.g., linearly enlarging over some duration prior to movement to simulate elevation normal to the screen, followed by translation to the second position, and a similar reduction in size to simulate lowering into the second position.
- Some embodiments may calculate parameters of, and render, a drop shadow as the coupon code 438 attains and moves through such the simulated elevated height toward the second location, following the coupon code 438 with the drop shadow, and adjusting and removing the drop shadow as the coupon code 438 is elevated and lowers.
- coupon code 438 may distort the coupon code 438 during movement, translating, for example an upper left corner initially faster than a lower right corner, and calculating and rendering a skew transform of increasing severity over some duration on an image of the coupon code 438 .
- the coupon code 438 may track a user gesture toward the header, remaining, for example under the touch of the user as the user drags the code upward and snapping in to place once a threshold proximity to the second position is attained.
- a help balloon 460 may be presented that includes text to aid the user in using the coupon code 438 .
- the help balloon 460 may include instructions or other text that describes how to move the coupon code box 436 , as illustrated below in FIGS. 4E-4H .
- the help balloon 460 includes text “DRAG this coupon code into the redemption box” to instruct a user how to move the coupon code box 436 in the manner described below.
- the help balloon 460 may also include a “Close” button 462 to enable a user to close the help balloon 460 and remove it from display in the application 402 .
- the help balloon 460 may be presented when screen 453 is displayed.
- the help balloon 460 may be displayed in response to a user input, such as touch located at or near the coupon code box 436 , a cursor located at or near the coupon code box 436 , etc.
- the help balloon 460 may include a chat window that will provide the user to engage an online chat application to receive and respond to communications such as text communications.
- the help balloon 460 may include a text input that posts user-entered questions to the offers engine (e.g., asynchronous with an XMLHttpRequest), which may respond with answers to the questions, e.g., with text displayed in-line with the user-entered question.
- responses are identified by 1) parsing keywords from the user-entered question, for instance by removing stopwords, 2) searching a plurality of frequently-asked-question records for answers, associated keywords, or associated questions including the parsed keywords, 3) ranking responsive candidate answers, for instance based on the number of corresponding keywords, and 4) sending the highest ranking answer to the client device, which may execute instructions associated with the help balloon 460 that display the response.
- answers to user questions are manually entered or selected by a human operator via the above-described administrator interface, or manually entered answers are provided when an automated selection based on keywords fails or fails to provide an answer after more than a threshold number of exchanges with the user.
- the merchant website 454 may include a variety of web content that enables a user to search or browse for goods, services, or both and select and order such goods and servers. For example, a user may select the “Use Coupon” button 443 to access the merchant website 454 to order goods and services associated with the selected coupon 414 A. As shown in FIG. 4D , for example, web content of the merchant website 454 may include a search field 464 , search button 466 , and a merchant storefront 468 . It should be appreciated that the web content depicted in FIG. 4D is merely an example and merchant websites may include a wide variety of web content, designs, and functionality.
- Such functionality may include, for example, the ability to search the merchant website 454 by entering a search query into the search field 464 and selecting (e.g., touching, clicking, etc.) the search button 466 .
- the merchant storefront 468 may display goods, services, or both offered by the merchant and available for order by a user.
- a user may use the search field 464 to find the goods, services, or both associated with the selected coupon.
- the goods or services may be presented to the user in the merchant storefront 468 in response to a selection of the “Use Coupon” button 443 .
- FIG. 4E depicts a screen 472 of the application 402 illustrating a checkout page 474 of the merchant website 454 in accordance with an embodiment of the present invention.
- web content such as the checkout page 474 may be retrieved from the Internet via a network accessible by a mobile user device executing the application 402 , and this web content may be displayed within the application 402 in the manner described above.
- the header portion 404 includes the coupon code box 436 and the “Done” button 454 .
- the header portion 404 may retain the coupon code box 436 to ensure the coupon code box 436 is accessible until a user has completed a transaction, e.g., an order for goods, services, or both, with the merchant.
- a user may exit the display of web content in the application 402 by selecting the “Done” button 454 and returning to previous screens of the application 402 .
- the merchant checkout page may include various web content that enables a user to view and enter order information and complete an order for goods, services, or both.
- the merchant checkout page 474 may include an order information portion 476 , a code entry portion 478 , and a checkout button 480 .
- the order information portion 476 enables a user to enter a shipping address, a billing address, payment information, and the like.
- the checkout button 478 (“Place Your Order”), a user may submit an order for fulfillment by the merchant.
- the code entry portion 478 may enable a user to enter coupon codes, promotional codes, gift card codes, or any other codes that may be applied to an order.
- the code entry portion 478 may include an input field 482 (e.g., a text field that receives text input) and a submission button 484 (“Apply”). By entering a coupon code or other code into the input field 482 and selecting the submission button 484 , a user may submit a coupon code to apply a coupon associated with the merchant.
- the input field 482 may accept images or other input.
- the application 402 provides for easy and intuitive entry of the coupon code 438 of the selected coupon 414 A via a gesture within the user interface.
- a user may drag and drop the coupon code box 436 over the input field 482 to have the coupon code 438 entered in the input field 482 .
- FIGS. 4F-4H are described with reference to an input field of a checkout webpage associated with a merchant, it should be appreciated that the same techniques may apply to input fields located in any webpage associated with a merchant that may receive a coupon code and for which a user desired to enter the code.
- a shopping cart webpage, a product webpage, or other merchant webpages may have an input field that may be processed in the manner described above, such that a user may drag-and-drop a coupon code box to enter a coupon code in the input field.
- FIG. 4F depicts the screen 472 illustrating the selection and animation of the coupon code box 436 in accordance with an embodiment of the present invention.
- a user may select (e.g. touch, click, etc.) the coupon code box 436 and drag the coupon code box 436 from a first position 486 towards the input field 482 , such as along the path indicated by arrow 487 .
- the selection may include a touch referred to as a “long press,” generating a long-press event in the native application that the above-mentioned event handler handles to initiate the following drag and drop operation.
- a visual copy 488 of the coupon code box 436 may be animated along the path indicated by arrow 487 to indicate the movement of the coupon code box 436 .
- the animation may follow one of the animation routines described above, including tracing the position of a touch as the touch is dragged across the screen.
- the visual copy 488 of the coupon code box may be dragged to or near the input field 482 and dropped (e.g., by releasing a touch), generating a touch-up or touch-end event to which the native application responds to effectuate the subsequent operations.
- FIG. 4G depicts the screen 472 further illustrating animation of the drag-and-drop of the visual copy 488 to a second location 490 located at or near the input field 482 , in accordance with an embodiment of the invention. As shown in FIG.
- the visual copy 488 (e.g., an area of the screen, such as a rectangle, depicting the code) may be animated and visually move (e.g., translate) along the path indicated by arrow 491 as a user drags the visual copy 488 toward the input field 482 .
- a user may deselect the visual copy 488 (such as by releasing a touch, releasing a click, etc.).
- the coupon code 438 of the coupon code box 436 may be entered into the input field 482 , entering the text depicted in the visual copy 488 .
- FIG. 4H further depicts the screen 472 and illustrates entry of the coupon code 438 in the input field 482 in response the gesture described above and in accordance with an embodiment of the present invention.
- the visual copy 488 may disappear and a value 492 (e.g., a text value) corresponding to the coupon code 438 may entered (e.g., pasted) into the input field 482 .
- a user may then select the submission button 484 to apply the coupon code to the order.
- the coupon code may be entered into the input field 482 by dragging and dropping the visual copy 488 of the coupon code box 436 to a location at or near the text box 482 .
- a user may submit the order to the merchant by selecting the “Place Your Order” button 478 .
- the native application may have access to inputs, e.g., inputs of text type in forms of the rendered merchant webpage.
- the native application may employ a variety of techniques to identify the appropriate document object model (DOM) element corresponding to the text input. For instance, merchants may designate a coupon code text entry element with a specific class or other identifier that the native application uses to get the appropriate element from the DOM for insertion of the coupon code text, e.g., by changing a value attribute of the element.
- DOM document object model
- the native application may identify the corresponding DOM element based on correspondence between the screen location of the touch-release event and the location of text inputs on the screen, generating an inventory of text input DOM elements and their offsetTop and offsetLeft coordinates, and selecting the closest text input to the touch-up event location to receive the coupon code.
- the candidate text inputs are filtered based on their context, removing, for instance, those text inputs in div boxes having text relating to an address or name and favoring those text inputs in div boxes having text with the string “coupon.”
- FIG. 5 depicts a first portion of user actions 500 and a first portion 502 of a coupon redemption process in accordance with an embodiment of the present invention.
- Some or all steps of the process portion 502 may be implemented as executable computer code stored on a non-transitory tangible computer-readable storage medium and executed by one or more processors of a special-purpose machine, e.g., a computing device programmed to execute the code.
- a user may select a coupon from a coupon list (block 504 ) presented in a native application, as shown above in FIG. 4A , and the coupon selection may be received (box 508 ).
- a coupon list block 504
- the coupon selection may be received (box 508 ).
- the selected coupon may be provided with a coupon code box having a coupon code associated with the selected coupon (block 508 ). If a user decides to use the coupon, the user may select a use coupon button (block 510 ) and the selection of the button may be received (block 512 ). Additionally, a value corresponding to the coupon code of the coupon code box may be copied to a clipboard accessible by the application (block 513 ). As illustrated above in FIGS. 4C and 4D , a visual movement of the coupon code box from a first location to a second location at the header portion of the application may be animated and the elements in the header portion may be replaced by the coupon code box (block 514 ).
- the merchant website may be provided within the native application (block 516 ), e.g., in a web view within the native application.
- a merchant website may be requested from one or more merchant webservers.
- a help balloon may be provided adjacent to the coupon code box with instructions or other text to describe how to use the application (block 518 ).
- the redemption process may continue with a second portion depicted in FIG. 6 , as indicated by connector block A.
- FIG. 6 depicts user actions 600 and a second portion 602 of a coupon redemption process in accordance with an embodiment of the present invention.
- Some or all steps of the process portion 602 may be implemented as executable computer code stored on a non-transitory tangible computer-readable storage medium and executed by one or more processors of a special-purpose machine, e.g., a computing device programmed to execute the code.
- the second portion 602 of the redemption process may continue from the first portion 404 described above and illustrated in FIG. 4 For example, after a user selects to use a coupon, a user may search and browse a merchant website to purchase goods, services, or both associated with the coupon.
- a user may select a checkout page within the merchant website to complete an order for goods, services, or both (block 604 ).
- a merchant checkout page may be provided within a native application (block 606 ), e.g., in a web view, as described above and illustrated in FIG. 4E .
- a user may drag-and-drop a coupon code box to an input field within the merchant checkout page, as described above and illustrated in FIGS. 4F and 4G .
- a user may select (e.g., touch) the coupon code box in the header portion of the application (block 608 )).
- the user may drag the coupon code box over the input field within the checkout page (block 612 ).
- a visual copy of the coupon code box may be animated from a first location to a second location along the drag path performed by the user (block 614 ).
- a user may then complete the drag-and-drop by dropping the visual copy of the coupon code box at or near the input field within the checkout page (block 616 ).
- the visual copy of the coupon code box may be then be removed and the value corresponding to the coupon code may be entered into the input field (block 618 ), as described above and illustrated in FIG. 4H .
- a user may submit the coupon code for redemption and continue the checkout to complete the order (block 620 ).
- redemption of offers, such as a selected coupon may occur through an affiliate network or directly from a merchant.
- FIG. 7 depicts a process 700 for implementing the drag-and-drop of a coupon code box to an input field in accordance with an embodiment of the present invention.
- the process 700 may be implemented within the second portion 602 of the redemption process described above and illustrated in FIG. 6 .
- Some or all steps of the process 700 may be implemented as executable computer code stored on a non-transitory tangible computer-readable storage medium and executed by one or more processors of a special-purpose machine, e.g., a computing device programmed to execute the code.
- Offers may be obtained from the above-mentioned offers engine of FIG.
- a touch on a coupon code box presented in a native application may be received at a first location, e.g., at a header portion of the native application (block 702 ).
- the value of a coupon code of the coupon code box may be copied to a clipboard and a visual copy of the coupon code box may be generated (block 704 ).
- a gesture e.g., a drag
- a visual movement of the visual copy of the coupon code box along the drag path may be animated (block 708 ).
- a touch release at a second location may be received (block 710 ).
- the location of the input field may be determined by finding the coordinates of the second location (block 712 ). For example, in some embodiment the location of the input field may be determined from a document object model (DOM) associated with the webpage. Based on this located input field, the input field may be set to a value corresponding to the coupon code associated with the coupon code box (block 714 ). Finally, the touch release may be animated to indicate that the coupon code is successfully entered in the input field (block 716 ). For example, the visual copy may be removed from the user interface and the value displayed in the input field of the webpage associated with the merchant.
- DOM document object model
- FIG. 8 depicts a mobile user device 800 in accordance with an embodiment of the present invention.
- Various sections of systems and computer-implemented methods described herein may include or be executed on one or more computers similar to mobile user device 800 . Further, processes and modules described herein may be executed by one or more processing systems similar to that of mobile user device 800 .
- the mobile user device 800 may include various internal and external components that contribute to the function of the device and which may allow the mobile user device 800 to function in accordance with the techniques discussed herein. It should further be noted that FIG. 8 depicts merely one example of a particular implementation and is intended to illustrate the types of components and functionalities that may be present in mobile user device 800 .
- Mobile user device 800 may include any combination of devices or software that may perform or otherwise provide for the performance of the techniques described herein.
- mobile user device 800 may include a tablet, a mobile phone, such as a smartphone, a video game device, and other hand-held networked computing devices.
- Mobile user device 800 may also be connected to other devices that are not illustrated, or may operate as a stand-alone system.
- the functionality provided by the illustrated components may in some embodiments be combined in fewer components or distributed in additional components. Similarly, in some embodiments, the functionality of some of the illustrated components may not be provided or other additional functionality may be available.
- the mobile user device 800 may allow a user to connect to and communicate through a network (e.g., the Internet, a local area network, a wide area network, etc.) and may provide communication over a satellite-based positioning system (e.g., GPS).
- a network e.g., the Internet, a local area network, a wide area network, etc.
- satellite-based positioning system e.g., GPS
- the mobile user device 800 may allow a user to communicate using e-mail, text messaging, instant messaging, or using other forms of electronic communication, and may allow a user to obtain the location of the device from the satellite-based positioning system, such as the location on an interactive map.
- the mobile user device 800 may include a processor 802 (e.g., one or more processors) coupled to a memory 804 , a display 806 , and a network interface 808 via an interface 810 .
- the mobile user device 800 may include other components not shown in FIG. 8 , such as a power source (e.g., a battery), I/O ports, expansion card interfaces, hardware buttons, etc.
- the display 806 may include a liquid crystal display (LCD) or an organic light emitting diode (OLED) display.
- LCD liquid crystal display
- OLED organic light emitting diode
- the display 806 may display a user interface (e.g., a graphical user interface), and may also display various function and system indicators to provide feedback to a user, such as power status, call status, memory status, etc. These indicators may be in incorporated into the user interface displayed on the display 806 .
- the display 806 may include or be provided in conjunction with touch sensitive elements through which a user may interact with the user interface.
- touch-sensitive display may be referred to as a “touchscreen” and may also be known as or called a touch-sensitive display.
- a user interface may provide for interaction via touch-sensitive elements of the display 806 .
- the display 806 may include a capacitive touchscreen, a resistive touchscreen, or any other suitable touchscreen technology.
- the processor 802 may provide the processing capability required to execute the operating system, programs, user interface, and any functions of the mobile user device 800 .
- the processor 802 may include one or more processors that may include “general-purpose” microprocessors and special purpose microprocessors, such as one or more reduced instruction set (RISC) processors, such as those implementing the Advanced RISC Machine (ARM) instruction set. Additionally, the processor 802 may include single-core processors and multicore processors and may include graphics processors, video processors, and related chip sets.
- a processor may receive instructions and data from a memory (e.g., system memory 804 ). Processes, such as those described herein may be performed by one or more programmable processors executing computer code to perform functions by operating on input data and generating corresponding output.
- the memory 804 may include volatile memory and non-volatile memory accessible by the processor 802 and other components of the mobile user device 800 .
- the memory 804 may include volatile memory, such as random access memory (RAM), and non-volatile memory, such as ROM, flash memory, a hard drive, any other suitable optical, magnetic, or solid-state storage medium, or a combination thereof.
- RAM random access memory
- non-volatile memory such as ROM, flash memory, a hard drive, any other suitable optical, magnetic, or solid-state storage medium, or a combination thereof.
- the memory 804 may store a variety of information and may be used for a variety of purposes.
- the memory 804 may store executable code, such as the firmware for the mobile user device 800 , an operating system for the mobile user device 800 , and any other programs.
- the executable computer code may include instructions executable by a processor, such as processor 802 , and the computer may include instructions for implementing one or more techniques described herein with regard to various processes.
- the memory 804 may store an executable native application 812 having a coupon redemption process 814 , such as that described above.
- the executable native application 812 may enable a user to view offers, such as online coupons, and select and redeem online coupons using the user actions described above.
- the executable code may be written in a programming language, including compiled or interpreted languages, or declarative or procedural language, and may be composed into a unit suitable for use in a computing environment, including as a stand-alone program, a module, a component, a subroutine.
- Such code program may be stored in a section of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or sections of code). Additionally, the copies of the executable code may be stored in both non-volatile and volatile memories, such as in a non-volatile memory for long-term storage and a volatile memory during execution of the code.
- the interface 810 may include multiple interfaces and may couple various components of the mobile user device 800 to the processor 802 and memory 804 .
- the interface 810 , the processor 802 , memory 804 , and one or more other components of the mobile user device 800 may be implemented on a single chip, such as a system-on-a-chip (SOC). In other embodiments, these components, their functionalities, or both may be implemented on separate chips.
- the interface 810 may be configured to coordinate I/O traffic between processor 802 , memory 804 , network interface 806 , and other internal and external components of the mobile user device 800 .
- the interface 810 may include functionality for interfacing via various types of peripheral buses, such as a variant of the Peripheral Component Interconnect (PCI) bus standard, the Universal Serial Bus (USB) standard, and the like.
- PCI Peripheral Component Interconnect
- USB Universal Serial Bus
- the mobile user device 800 depicted in FIG. 8 also includes a network interface 808 , such as a wired network interface, wireless (e.g., radio frequency) receivers, etc.
- the network interface 808 may receive and send electromagnetic signals and communicate with communications networks and other communications devices via the electromagnetic signals.
- the network interface 808 may include known circuitry for performing these functions, including an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth.
- SIM subscriber identity module
- the network interface 804 may communicate with networks (e.g., network XXX), such as the Internet, an intranet, a cellular telephone network, a wireless local area network (LAN), a metropolitan area network (MAN), or other devices by wireless communication.
- the network interface 808 may suitable any suitable communications standard, protocol and technology, including Ethernet, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), a 4G network (e.g., based upon the IMT-2000 standard), high-speed downlink packet access (HSDPA), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), a 4G network (e.g., IMT Advanced, Long-Term Evolution Advanced (LTE Advanced), etc.), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for email (e
- instructions stored on a computer-readable medium separate from mobile user device 800 may be transmitted to mobile user device 800 via transmission media or signals such as electrical, electromagnetic, or digital signals, conveyed via a communication medium such as a network or a wireless link.
- Various embodiments may further include receiving, sending or storing instructions or data implemented in accordance with the foregoing description upon a computer-accessible medium. Accordingly, the present invention may be practiced with other computer system configurations.
- a computer-accessible/readable storage medium may include a non-transitory storage media such as magnetic or optical media, (e.g., disk or DVD/CD-ROM), volatile or non-volatile media such as RAM (e.g. SDRAM, DDR, RDRAM, SRAM, etc.), ROM, etc., as well as transmission media or signals such as electrical, electromagnetic, or digital signals, conveyed via a communication medium such as network and/or a wireless link.
- non-transitory storage media such as magnetic or optical media, (e.g., disk or DVD/CD-ROM), volatile or non-volatile media such as RAM (e.g. SDRAM, DDR, RDRAM, SRAM, etc.), ROM, etc.
- transmission media or signals such as electrical, electromagnetic, or digital signals, conveyed via a communication medium such as network and/or a wireless link.
Abstract
Description
- The present application is a non-provisional of, and thus claims the benefit of, each of the following pending U.S. provisional patent applications, each of which is hereby incorporated by reference for all purposes: provisional application 61/707,527, filed Sep. 28, 2012; provisional application 61/665,740, filed Jun. 28, 2012; provisional application 61/658,408, filed Jun. 12, 2012; provisional application 61/658,404, filed Jun. 11, 2012; and provisional application 61/658,387, filed Jun. 11, 2012.
- 1. Field of the Invention
- This invention relates generally to merchant offers for goods and services and, more particularly, to redemption of certain offers such as online coupons.
- 2. Description of the Related Art
- Offer-discovery systems provide a service by which merchants inform customers of offers, for example deals (e.g., discounts, favorable shipping terms, or rebates) or coupons (e.g., printable coupons for in-store use or coupon codes for use online). Typically, the systems store information about offers from a relatively large number of merchants and provide an interface by which customers can identify offers in which the customer is likely to be interested. Merchants have found the offer-discovery systems to be a relatively effective form of marketing, as cost-sensitive consumers are drawn to such systems due to their relatively comprehensive listings of offers. Such offers may include coupons, such as include traditional in-store coupons, and online coupons typically obtained via the Internet, such as from merchant websites, e-mail distributions, etc. To use an online coupon, a customer typically provides an identifier, such as a coupon code, when purchasing goods and services from a merchant's online store. However, a customer may forget about the existence of the coupon and, as a result, fail to take advantage of the offer presented by the coupon. Additionally, it may be challenging for a customer to remember the identifier presented by the coupon and to use the online coupon in the manner specified by the online store. And, the advent of smaller computing devices having different or limited interfaces may increase the challenges faces by customers attempting to use online coupons.
- Various embodiments of devices, computer-implemented methods, and computer-readable media for redemption of merchant offers are provided herein. Applicants recognize the need for improved techniques for redemption of merchant offers such as online coupons to reduce or eliminate the burdens on a user. Thus, Applicants recognize users may be unable to remember the existence of a merchant offer, such as coupon, or memorize the information necessary to use the merchant offer. Embodiments address some or all of these recognized needs, but embodiments are not limited to just those systems that address these needs, as various engineering and cost tradeoffs are envisioned and some embodiments address other needs.
- In some embodiments, a computer-implemented method is provided that includes providing an online coupon in a native application for the mobile user device, the online coupon having a coupon code in a user interface element located at first location defined by a first set of coordinates of a touchscreen of the mobile user device. The computer-implemented method further includes receiving a selection to use the online coupon for a transaction with a merchant and providing in the user interface a webpage associated with the merchant. The computer-implemented method also includes executing, with a processor of the mobile user device, a visual movement of the user interface element from the first location to a second location, the second location defined by a second set of coordinate of the touchscreen of the mobile user devices.
- In other embodiments, a non-transitory computer-readable medium having executable computer code stored thereon is provided. The executable computer code includes instructions that, when executed, cause one or more processors to perform the following: providing an online coupon in a native application for the mobile user device, the online coupon having a coupon code within a user interface element located at first location defined by a first set of coordinates of a touchscreen of the mobile user device. The executable computer further includes instructions that cause one or more processors to perform the following: receiving a selection to use the online coupon for a transaction with a merchant and providing in the user interface a webpage associated with the merchant. Additionally, the executable computer further includes instructions that cause one or more processors to perform the following: executing, with a processor of the mobile user device, a visual movement of the user interface element from the first location to a second location, the second location defined by a second set of coordinate of the touchscreen of the mobile user devices.
- Additionally, in some embodiments, a mobile user device is provided that includes a processor, a touchscreen communicatively coupled to the processor, and a non-transitory tangible computer-readable memory communicatively coupled to the processor. The memory has executable computer code stored thereon, the executable computer having instructions that, when executed, cause one or more processors to perform the following: providing an online coupon in a native application for the mobile user device, the online coupon having a coupon code within a user interface element located at first location defined by a first set of coordinates of a touchscreen of the mobile user device. The executable computer further includes instructions that cause one or more processors to perform the following: receiving a selection to use the online coupon for a transaction with a merchant and providing in the user interface a webpage associated with the merchant. Additionally, the executable computer further includes instructions that cause one or more processors to perform the following: executing, with a processor of the mobile user device, a visual movement of the user interface element from the first location to a second location, the second location defined by a second set of coordinate of the touchscreen of the mobile user devices.
- Additionally, in some embodiments, a computer-implemented method is provided that includes providing a coupon code associated with a merchant in a native application for the mobile user device, the coupon code in a user interface element located at a first location defined by a first set of coordinates of a touchscreen of the mobile user device and providing (e.g., requesting and rendering) in the native application a webpage associated with the merchant, the webpage having an input field for receiving user input associated with a coupon, the input field located at a second location at a second set of coordinates of the touchscreen. The computer-implemented method further includes receiving a touch on the touchscreen at the first location and receiving a gesture on the touchscreen, the gesture including a movement from the first location to the second location. The computer-implemented method also includes executing, with a processor of the mobile user device, a visual movement of the user interface element having the coupon code from the first location to the second location along a path coincident with the gesture, receiving a release of the touch at the second location, and setting, the value of the input field of the webpage to text corresponding to the coupon code.
- In other embodiments, a non-transitory computer-readable medium having executable computer code stored thereon is provided. The executable computer includes instructions that, when executed, cause one or more processors to perform the following: providing a coupon code associated with a merchant in a native application for the mobile user device, the coupon code in a user interface element located at a first location defined by a first set of coordinates of a touchscreen of the mobile user device and providing in the native application a webpage associated with the merchant, the webpage having an input field for receiving user input associated with a coupon, the input field located at a second location at a second set of coordinates of the touchscreen. The executable computer further includes instructions that cause one or more processors to perform the following: receiving a touch on the touchscreen at the first location and receiving a gesture on the touchscreen, the gesture including a movement from the first location to the second location. The executable computer further also instructions that cause one or more processors to perform the following: executing, with a processor of the mobile user device, a visual movement of the user interface element having the coupon code from the first location to the second location along a path coincident with the gesture, receiving a release of the touch at the second location, and setting the value of the input field of the webpage to text corresponding to the coupon code.
- Additionally, in some embodiments, a mobile user device is provided that includes a processor, a touchscreen communicatively coupled to the processor, and a non-transitory tangible computer-readable memory communicatively coupled to the processor. The memory has executable computer code stored thereon, the executable computer having instructions that, when executed, cause one or more processors to perform the following: providing a coupon code associated with a merchant in a native application for the mobile user device, the coupon code in a user interface element located at a first location defined by a first set of coordinates of a touchscreen of the mobile user device and providing in the native application a webpage associated with the merchant, the webpage having an input field for receiving user input associated with a coupon, the input field located at a second location at a second set of coordinates of the touchscreen. The executable computer code further includes instructions that cause one or more processors to perform the following: receiving a touch on the touchscreen at the first location and receiving a gesture on the touchscreen, the gesture including a movement from the first location to the second location. The executable computer further also instructions that cause one or more processors to perform the following: executing, with a processor of the mobile user device, a visual movement of the user interface element having the coupon code from the first location to the second location along a path coincident with the gesture, receiving a release of the touch at the second location, and setting the value of the input field of the webpage to text corresponding to the coupon code.
- Finally, in some embodiments, a computer-implemented method is provided that includes providing a coupon in a native application for the mobile user device, the coupon having a coupon code in a user interface element located at first location defined by a first set of coordinates of a touchscreen of the mobile user device and receiving a selection to use the coupon for a transaction with a merchant. Additionally, the computer-implemented method includes providing a webpage associated with the merchant in the application and providing, with a processor of the mobile user device, the coupon code in the user interface element at a second location defined by a second set of coordinates of the touchscreen, the second set of coordinates located at a header portion of a display of the application, wherein the header portion is positioned vertically above the webpage.
-
FIG. 1 illustrates an example of an offer-discovery system in accordance with some embodiments; -
FIG. 2 illustrates an example of a process by which an offers engine in the offer-discovery system ofFIG. 1 , in some embodiments, obtains and processes data related to offers; -
FIG. 3 illustrates an example of a process by which a user device in the offer-discovery system ofFIG. 1 , in some embodiments, obtains and presents to users data related to offers; -
FIGS. 4A-4H are diagrams illustrating screens of a mobile user device executing a native application for online coupon redemption in accordance with an embodiment of the present invention; -
FIG. 5 is a block diagram illustrating user actions and a first portion of a redemption process in accordance with an embodiment of the present invention; -
FIG. 6 is a block diagram illustrating user actions and a first portion of a redemption process in accordance with an embodiment of the present invention; -
FIG. 7 is a block diagram of a process for implementing drag-and-drop in a redemption process in accordance with an embodiment of the present invention; and -
FIG. 8 is a block diagram of a mobile user device in accordance with an embodiment of the present invention. - While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail. The drawings may not be to scale. It should be understood, however, that the drawings and detailed description thereto are not intended to limit the invention to the particular form disclosed, but to the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the present invention as defined by the appended claims.
-
FIG. 1 shows an embodiment of an offer-discovery system 10. Theexemplary system 10 includes anoffers engine 12 that, in some embodiments, is capable of reducing the burden on users attempting to identify offers relevant to them from among a relatively large pool of offers (e.g., more than 100, more than 1,000, or more than 10,000). To this end and others, theoffers engine 12 maintains device-independent user profiles (or portions of user profiles) by which offers interfaces may be relatively consistently configured across multiple user devices with which the user interacts with theoffers engine 12. Further, theoffers engine 12, in some embodiments, includes a number of features expected to facilitate relatively quick identification of relevant offers by a user, features that include cached storage of data related to likely relevant offers, faceted presentation of offers by which users can select among offers within various categories, and a number of other techniques described below for assisting with offer identification. Theoffers engine 12 is also expected to facilitate relatively low operating costs by, in some embodiments, automating parts of the process by which offer related data is acquired from sources, such as affiliate networks merchants, administrators, or users, and automating parts of the process by which transaction data indicative of acceptance, settlement, or clearing of offers is obtained and processed. - These and other benefits are described in greater detail below, after introducing the components of the
system 10 and describing their operation. It should be noted, however, that not all embodiments necessarily provide all of the benefits outlined herein, and some embodiments may provide all or a subset of these benefits or different benefits, as various engineering and cost tradeoffs are envisioned. - In the illustrated embodiment, the
offers engine 12 includes acontrol module 14, an application program interface (API)server 16, aweb server 18, an ingestmodule 20, anadministration module 22, adata store 24, and acache server 23. These components, in some embodiments, communicate with one another in order to provide the functionality of theoffers engine 12 described herein. As described in greater detail below, in some embodiments, thedata store 24 may store data about offers and users' interactions with those offers; thecache server 23 may expedite access to this data by storing likely relevant data in relatively high-speed memory, for example, in random-access memory or a solid-state drive; theweb server 20 may serve webpages having offers interfaces by which users discover relevant offers; theAPI server 16 may serve data to various applications that process data related to offers; the ingestmodule 20 may facilitate the intake of data related to offers from affiliate networks, users, administrators, and merchants; and theadministration module 22 may facilitate curation of offers presented by theAPI server 16 and theweb server 18. The operation of thesecomponents control module 14, which may bidirectionally communicate with each of these components or direct the components to communicate with one another. Communication may occur by transmitting data between separate computing devices (e.g., via transmission control protocol/internet protocol (TCP/IP) communication over a network), by transmitting data between separate applications or processes on one computing device; or by passing values to and from functions, modules, or objects within an application or process, e.g., by reference or by value. - Among other operations, the
offers engine 12 of this embodiment presents offers to users; receives data from users about their interaction with the offers (for example, the user's favorite offers or offer attributes; statistics about the offers the user has identified, accepted, or otherwise provided data about; or the identity of other users with whom the user communicates about offers and the content of those communications; provided that users opt to have such data obtained); customizes the presentation of offers based on this received data; and facilitates the processing of compensation from merchants (either directly or through affiliate networks) as a result of users accepting (or taking a specific action, like clicking or viewing, in some embodiments or use cases) offers. This interaction with users may occur via a website viewed on a desktop computer, tablet, or a laptop of the user. And in some cases, such interaction occurs via a mobile website viewed on a smart phone, tablet, or other mobile user device, or via a special-purpose native application executing on a smart phone, tablet, or other mobile user device. Presenting and facilitating interaction with offers across a variety of devices is expected to make it easier for users to identify and recall relevant offers at the time the user is interested in those offers, which is often different from the time at which the user first discovers the offers. In particular, some embodiments allow users to store data indicative of offers relevant to that user using one device, such as a desktop computer in the user's home, and then view those offers at a later time, such as on a native mobile application when in a retail store. - To illustrate an example of the environment in which the
offers engine 12 operates, the illustrated embodiment ofFIG. 1 includes a number of components with which theoffers engine 12 communicates:mobile user devices top user device 32; athird party server 34; anadministrator device 36;merchant servers network servers offers engine 12 via anetwork 48, such as the Internet or the Internet in combination with various other networks, like local area networks, cellular networks, or personal area networks. - The
mobile user devices mobile user devices web browser 50 or a nativemobile application 52. Thenative application 52, in some embodiments, is operative to provide an offers interface that communicates with theoffers engine 12 and facilitates user interaction with data from theoffers engine 12. Similarly, theweb browser 50 may be configured to receive a website from theoffers engine 12 having data related to deals and instructions (for example, instructions expressed in JavaScript™) that when executed by the browser (which is executed by the processor) cause the mobile user device to communicate with theoffers engine 12 and facilitate user interaction with data from theoffers engine 12. Thenative application 52 and theweb browser 50, upon rendering a webpage from theoffers engine 12, may generally be referred to as client applications of theoffers engine 12, which in some embodiments may be referred to as a server. Embodiments, however, are not limited to client/server architectures, and theoffers engine 12, as illustrated, may include a variety of components other than those functioning primarily as a server. - The desk-
top user device 32 may also include aweb browser 54 that serves the same or similar role as theweb browser 50 in themobile user device 30. In addition, the desk-top user device 32 may include a monitor; a keyboard; a mouse; memory; a processor; and a tangible, non-transitory, machine-readable memory storing instructions that when executed by the processor provide an operating system and the web browser. - Third-
party offer server 34 may be configured to embed data from theoffers engine 12 in websites or other services provided by the third-party offer server 34. For example, third-party offer server 34 may be a server of a social networking service upon which users post comments or statistics about offers with which the user has interacted, or the users may use theoffer server 34 to recommend offers to others or identify offers to avoid. In another example, third-party offer server 34 may include various services for publishing content to the Web, such as blogs, tweets, likes, dislikes, ratings, and the like. In another example, third-party offer server 34 provides services by which third-parties curate offers hosted by theoffers engine 12. -
Merchant servers offers engine 12. In some embodiments, and in some use cases, themerchant servers - Some merchants may limit the number of uses of a given coupon, limit the duration over which the coupon is valid, or apply other conditions to use of the coupon, each of which may add to the burden faced by users seeking to find valid coupons applicable to an item the user wishes to purchase. As noted above, some embodiments of the
offers engine 12 are expected to mitigate this burden. - Further, in some embodiments, the
merchant servers offers engine 12 or (i.e., and/or, as used herein, unless otherwise indicated) data about transactions involving offers. In use cases in which the operator of theoffers engine 12 has a direct affiliate-marketing relationship with one of the merchants of themerchant servers offers engine 12. For example, payments may be based on a percentage of transactions to which offers were applied, a number of sales to which offers were applied, or a number of users who viewed or selected or otherwise interacted with an offer by the merchant. - Affiliate-
network servers offers engine 12 does not have a direct affiliate-marketing relationship with the merchant making a given offer. In many affiliate marketing programs, merchants compensate outside entities, such as third-party publishers, for certain activities related to sales by that merchant and spurred by the outside entity. For example, in some affiliate marketing programs, merchants compensate an affiliate, such as the entity operating theoffers engine 12, in cases in which it can be shown that the affiliate provided a given coupon code to a given user who then used that coupon code in a transaction with the merchant. Demonstrating this connection to the merchant is one of the functions of the affiliate-networks. - Affiliate-networks are used, in some use cases, because many coupon codes are not affiliate specific and are shared across multiple affiliates, as the merchant often desires the widest distribution of a relatively easily remembered coupon code. Accordingly, in some use cases, the merchant, affiliate network, and affiliate cooperate to use client-side storage to indicate the identity of the affiliate that provided a given coupon code to a user. To this end, in some embodiments, when a webpage offers interface is presented by the
offers engine 12 in theweb browsers offers engine 12 to include instructions to engage theaffiliate network server offers engine 12 responds to such a selection by, in some embodiments, transmitting a request to the appropriate affiliate-network server 44 or 46 (as identified by, for example, an associated uniform resource locator (URL) in the webpage) for a webpage or portion of a webpage (e.g., browser-executable content). The request to the affiliate-network server may include (e.g., as parameters of the URL) an identifier of the affiliate, the offer, and the merchant, and the returned content from the affiliate-network server may include instructions for theweb browser - The webpage from the offers engine 12 (or the content returned by the
affiliate network server 44 or 46) may further include browser instructions to navigate to the website served by themerchant server merchant server affiliate network server offers engine 12, who provided the information about the offer to the user. The affiliate network may then report to the merchant the identity of the affiliate who should be credited with the transaction, and the merchant may compensate the affiliate (or the affiliate network may bill the merchant, and the affiliate network may compensate the affiliate), such as the operator of theoffers engine 12. Thus, the affiliate network in this example acts as an intermediary, potentially avoiding the need for cross-domain access to browser memory on the client device, a feature which is generally not supported by web browsers for security reasons. (Some embodiments may, however, store in client-side browser-accessible memory an identifier of the affiliate upon user selection of the offer, with this value designated as being accessible via the merchant's domain, and provide the value to the merchant upon a merchant request following acceptance of the offer, without passing the identifier through an affiliate network, using a browser plug-in for providing cross-domain access to browser memory or a browser otherwise configured to provide such access.) - A similar mechanism may be used by the
native application 52 for obtaining compensation from merchants. In some embodiments, thenative application 52 includes or is capable of instantiating a web browser, like theweb browser 50, in response to a user selecting an offer presented by thenative application 52. The web browser instantiated by thenative application 52 may be initialized by submitting the above-mentioned request for content to the affiliate-network server offers engine 12 in this example) in client-side storage (e.g., in a cookie, localStorage object, or a database) of themobile user device 28, and thereby navigating that browser to the merchant website. In other use cases, the operator of theoffers engine 12 has a direct relationship with the merchant issuing the offer, and the selection of an offer within thenative application 52 or the desktop or mobile website of the offers engine 12 (generally referred to herein as examples of an offer interface) may cause the user device to request a website from the associated merchant with an identifier of the affiliate included in the request, for example as a parameter of a URL transmitted in a GET request to themerchant server -
Administrator device 36 may be a special-purpose application or a web-based application operable to administer operation of theoffers engine 12, e.g., during use by employees or agents of the entity operating theoffers engine 12. In some embodiments, theadministration module 22 may communicate with theadministrator device 36 to present an administration interface at theadministrator device 36 by which an administrator may configure offers interfaces presented to users by theoffers engine 12. In some embodiments, the administrator may enter offers into theoffers engine 12; delete offers from theoffers engine 12; identify offers for prominent placement within the offers interface (e.g., for initial presentation prior to user interaction); moderate comments on offers; view statistics on offers, merchants, or users; add content to enhance the presentation of offers; or categorize offers. - Thus, the
offers engine 12, in some embodiments, operates in the illustrated environment by communicating with a number of different devices and transmitting instructions to various devices to communicate with one another. The number of illustrated merchant servers, affiliate network servers, third-party servers, user devices, and administrator devices is selected for explanatory purposes only, and embodiments are not limited to the specific number of any such devices illustrated byFIG. 1 . - The
offers engine 12 of some embodiments includes a number of components introduced above that facilitate the discovery of offers by users. For example, the illustratedAPI server 16 may be configured to communicate data about offers via an offers protocol, such as a representational-state-transfer (REST)-based API protocol over hypertext transfer protocol (HTTP). Examples of services that may be exposed by theAPI server 18 include requests to modify, add, or retrieve portions or all of user profiles, offers, or comments about offers. API requests may identify which data is to be modified, added, or retrieved by specifying criteria for identifying records, such as queries for retrieving or processing information about particular categories of offers, offers from particular merchants, or data about particular users. In some embodiments, theAPI server 16 communicates with thenative application 52 of themobile user device 28 or the third-party offer server 34. - The illustrated
web server 18 may be configured to receive requests for offers interfaces encoded in a webpage (e.g. a collection of resources to be rendered by the browser and associated plug-ins, including execution of scripts, such as JavaScript™, invoked by the webpage). In some embodiments, the offers interface may include inputs by which the user may request additional data, such as clickable or touchable display regions or display regions for text input. Such inputs may prompt the browser to request additional data from theweb server 18 or transmit data to theweb server 18, and theweb server 18 may respond to such requests by obtaining the requested data and returning it to the user device or acting upon the transmitted data (e.g., storing posted data or executing posted commands). In some embodiments, the requests are for a new webpage or for data upon which client-side scripts will base changes in the webpage, such as XMLHttpRequest requests for data in a serialized format, e.g. JavaScript™ object notation (JSON) or extensible markup language (XML). Theweb server 18 may communicate with web browsers, such as theweb browser user devices web server 18 based on the type of user device, e.g., with a mobile webpage having fewer and smaller images and a narrower width being presented to themobile user device 30, and a larger, more content rich webpage being presented to the desk-top user device 32. An identifier of the type of user device, either mobile or non-mobile, for example, may be encoded in the request for the webpage by the web browser (e.g., as a user agent type in an HTTP header associated with a GET request), and theweb server 18 may select the appropriate offers interface based on this embedded identifier, thereby providing an offers interface appropriately configured for the specific user device in use. - The illustrated ingest
module 20 may be configured to receive data about new offers (e.g., offers that are potentially not presently stored in the data store 24), such as data feeds from theaffiliate network servers user devices party offer server 34, offers identified bymerchant servers administrator device 36. In some embodiments, the ingestmodule 20 may respond to receipt of a record identifying a potentially new offer by querying thedata store 24 to determine whether the offer is presently stored. Upon determining that the offer is not presently stored by thedata store 24, the ingestmodule 20 may transmit a request to thedata store 24 to store the record. In some cases, the data about new offers may be an affiliate data-feed from an affiliate network containing a plurality of offer records (e.g., more than 100), each record identifying offer terms, a merchant, a URL of the merchant associated with the offer, a product description, and an offer identifier. The ingestmodule 22 may periodically query such data-feeds from the affiliate-network servers offers engine 12. - The
administration module 22 may provide an interface by which an administrator operating theadministrator device 36 curates and contextualizes offers. For example, theadministration module 22 may receive instructions from administrator that identify offers to be presented in the offer interface prior to user interaction with the offer interface, or offers to be presented in this initialized offers interface for certain categories of users, such as users having certain attributes within their user profile. Further, in some embodiments, theadministration module 22 may receive data descriptive of offers from the administrator, such as URLs of images relevant to the offer, categorizations of the offer, normalized data about the offer, and the like. - The illustrated
data store 24, in some embodiments, stores data about offers and user interactions with those offers. Thedata store 24 may include various types of data stores, including relational or non-relational databases, document collections, hierarchical key-value pairs, or memory images, for example. In this embodiment, thedata store 24 includes auser data store 56, asession data store 58, an offersdata store 60, and ananalytics data store 62. Thesedata stores - In this embodiment, the illustrated
user data store 56 includes a plurality of records, each record being a user profile and having a user identifier, a list of offers (e.g., identifiers of offers) identified by the user as favorites, a list of categories of offers identified by the user as favorites, a list of merchants identified by the user as favorites, account information for interfacing with other services to which the user subscribes (e.g., a plurality of access records, each record including an identifier of a service, a URL of the service, a user identifier for the service, an OAuth access token credential issued by the service at the user's request, and an expiration time of the credential), a user password for theoffers engine 12, a location of the user device or the user (e.g., a zip code of the user), and a gender of the user. In some embodiments, each user profile includes a list of other users identified by the user of the user profile as being people in whose commentary on, or curation of, offers the user is interested, thereby forming an offers-interest graph. In some embodiments, users have control of their data, including what is stored and who can view the data, and can choose to opt-in to the collection and storage of such user data to improve their experience with theoffers engine 12. - In this embodiment, the
session data store 58 stores a plurality of session records, each record including information about a session a given user is having or has had with theoffers engine 12. The session records may specify a session identifier, a user identifier, and state data about the session, including which requests have been received from the user and what data has been transmitted to the user. Session records may also indicate the IP address of the user device, timestamps of exchanges with the user device, and a location of the user device (e.g., retail store or aisle in a retail store in which the user device is located). - The illustrated offers
data store 60, in some embodiments, includes a plurality of offer records, each offer record may identify a merchant, offers by that merchant, and attributes of the relationship with the merchant, e.g., whether there is a direct relationship with the merchant by which the merchant directly compensates the operator of theoffers engine 12 or whether the merchant compensates the operator of theoffers engine 12 via an affiliate network and which affiliate network. The offers by each merchant may be stored in a plurality of merchant-offer records, each merchant-offer record may specify applicable terms and conditions of the offer, e.g., whether the offer is a discount, includes free or discounted shipping, requires purchase of a certain number of items, is a rebate, or is a coupon (which is not to suggest that these designations are mutually exclusive). In records in which the offer is a coupon, the record may further indicate whether the coupon is for in-store use (e.g. whether the coupon is associated with a printable image for presentation at a point-of-sale terminal, a mobile device-displayable image, or other mediums) or whether the coupon is for online use and has a coupon code, in which case the coupon code is also part of the merchant-offer record. The merchant-offer records may also include an expiration date of the offer, comments on the offer, rankings of the offer by users, a time at which the offer was first issued or entered into theoffers engine 12, and values (e.g., binary values) indicating whether users found the offer to be effective, with each value or ranking being associated with a timestamp, in some embodiments. The values and rankings may be used to calculate statistics indicative of the desirability of the offer and likely success of accepting the offer. The timestamps associated with the values, rankings, and time of issuance or entry into theoffers engine 12 may also be used to weight rankings of the offer, with older values being assigned less weight than newer values and older offers being ranked lower than newer offers, all other things being equal, as many offers expire or have a limited number of uses. - The illustrated
analytics data store 62 may store a plurality of records about historical interactions with theoffers engine 12, such as aggregate statistics about the performance of various offers. In some embodiments, theanalytics data store 62 stores a plurality of transaction records, each transaction record identifying an offer that was accepted by a user at a merchant, the merchant, the time of presentation of the offer to the user, and an indicator of whether the merchant has compensated the entity operating theoffers engine 12 for presentation of the offer to the user. Storing and auditing these transaction records is expected to facilitate relatively accurate collection of payments owed by merchants and identification of future offers likely to lead to a relatively high rates of compensation for prominent presentation based on past performance of offers having similar attributes. - The
cache server 23 stores a subset of the data in thedata store 24 that is among the more likely data to be accessed in the near future. To facilitate relatively fast access, thecache server 23 may store cached data in relatively high speed memory, such as random access memory or a solid-state drive. The cached data may include offers entered into theoffers engine 12 within a threshold period of time, such as offers that are newer than one day. In another example, the cache data may include offers that are accessed with greater than a threshold frequency, such as offers that are accessed more than once a day, or offers accessed within the threshold, such as offers accessed within the previous day. Caching such offer data is expected to facilitate faster access to offer data than systems that do not cache offer data. - The illustrated
control module 14, in some embodiments, controls the operation of the other components of theoffers engine 12, receiving requests for data or requests to add or modify data from theAPI server 16, theweb server 18, the ingestmodule 20, and theadministration module 22, and instructing thedata store 24 to modify, retrieve, or add data in accordance with the request. Thecontrol module 14 may further instruct thecache server 23 to modify data mirrored in thecache server 23. In some embodiments, thecache server 23 may be updated hourly, and inconsistent data may potentially be maintained in thecache server 23 in order to conserve computing resources. - The illustrated components of the
offers engine 12 are depicted as discrete functional blocks, but embodiments are not limited to systems in which the functionality described herein is organized as illustrated byFIG. 1 . The functionality provided by each of the components of theoffers engine 12 may be provided by software or hardware modules that are differently organized than is presently depicted, for example such software or hardware may be intermingled, broken up, distributed (e.g. within a data center or geographically), or otherwise differently organized. The functionality described herein may be provided by one or more processors of one or more computers executing code stored on a tangible, non-transitory, machine readable medium. -
FIG. 2 is a flowchart of aprocess 64 for acquiring data related to offers within some embodiments of theoffer engine 12 discussed above. In this embodiment, theprocess 64 begins with receiving offer data describing a plurality of offers from affiliate networks, merchants, and users, as illustrated byblock 66. This step may be performed by the above-mentioned ingestmodule 20. As noted above, the received offer data may be received from one or all of these sources. The received offer data may be received via an offer interface by which users associated with these sources enter data about offers, or the received offer data may be received in a predefined format, such as a serialized data format, in an automatic data feed pushed or pulled periodically or in response to the availability of new data from affiliate networks or merchants. Receiving the offer data may include determining whether the offer data is redundant to offer data already received and normalizing the offer data. - The
process 64, in some embodiments, includes normalizing and enriching the offer data. Normalizing may include normalizing field names of the data and normalizing the way in which dates are expressed, for example. Enriching may include associating images with the offers for presentation with the offers and adding metadata to the offers to assist users searching for offers. - Next, in the present embodiment, the received offer data is stored in an offer data store, as indicated by
block 68. Storing the offer data in the offer data store may include identifying a merchant to which the offer pertains and storing the offer in a merchant-offer record associated with that merchant. Further, some embodiments may include inserting the offer in order in a sorted list of offers for relatively fast retrieval of offers using a binary search algorithm or other techniques to facilitate relatively quick access to data that has been preprocessed (e.g., using a prefix trie). In some embodiments, storing the received offer may further include updating hash tables by which the offer may be retrieved according to various parameters, each hash table being associated with one parameter and including a hash key value calculated based on the parameter and paired with an address of the offer. Such hash tables are expected to facilitate relatively fast access to a given offer as the need to iterate through potentially all offers meeting certain criteria may be potentially avoided. - In some embodiments, the
process 64 further includes receiving a request from a user device for offers, as indicated byblock 70. The request may specify criteria for identifying offers, such as categories of offers, search terms for offers, or requests for offers designated as favorites. - Next, the present embodiment includes identifying offers in the offer data store responsive to the user request, as indicated by
block 72. Identifying offers in the offer data store may be performed by the above-mentioned controller 14 (FIG. 1 ) by constructing a query to theoffer data store 60 based on a request received from theweb server 18 or theAPI server 16. The query may be transmitted to theoffer data store 60, or to thecache server 23, each of which may return responsive records. - Next, the identified offers are transmitted to the user device, as indicated by
block 74. Transmitting the identified offers may include transmitting the identified offers in an offer interface, such as a webpage, or an API transmission to a native mobile application, for example by theweb server 18, or theAPI server 16 ofFIG. 1 , respectively. - The device receiving the identified offers may, in response, perform a process described below with reference to
FIG. 3 by which additional offers are requested or an offer is selected and a purchase is executed. This process ofFIG. 3 and steps 70 through 74 ofFIG. 2 may be repeated numerous times, in some use cases, before advancing to the next steps. Further, thesteps 66 through 68 may be repeated numerous times independently of (e.g., concurrent with) the performance ofsteps 70 through 74 ofFIG. 2 (which is not to suggest that other steps described herein may not also be executed independently). That is, theprocess 64 may undergostep steps 70 through 74 500 times within that given time, and performing the remaining steps of process 64 a single time. - In some embodiments, a user device undergoing the process of
FIG. 3 may indicate to an offers engine that the user has selected an offer (e.g., by clicking on or touching a selectable element in an offers interface associated with the offer). In response, the offers engine may direct the user device to an affiliate-network server or a merchant server associated with the offer, as illustrated byblock 75. - Next, this embodiment of the
process 64 includes receiving from merchants or affiliate networks transaction data identifying offers accepted via the user device, as illustrated byblock 76. The transaction data may be pulled from these sources, for example, by the ingestmodule 20 ofFIG. 1 , periodically, or in response to some threshold number of transactions having occurred. - Next, in this embodiment, the receipt transaction data may be stored in an analytics data store, as indicated by
block 78. In some embodiments, this data may be stored in theanalytics data store 62 ofFIG. 1 . Storing the transaction data is expected to facilitate the identification of attributes of relatively profitable offers, as the transaction data indicates which offers historically yielded compensable transactions. Further, storing the transaction data is expected to facilitate relatively accurate auditing of payments from merchants or affiliate networks. -
FIG. 3 is a flowchart of an embodiment of aprocess 80 that provides an example of an offer interface at a user device. Theprocess 80 may be performed by the above-mentionednative application 52 orweb browser offers engine 12. - Some embodiments of
process 80 begin with receiving, at a user device, instructions that cause the user device to display an offers interface, as indicated byblock 82. The received instructions may be in the form of a downloaded native application, such as one downloaded from an application store hosted by a provider of mobile devices, or the received instructions may be in the form of a website received from theoffers engine 12 and rendered in a browser of the user device. - In some embodiments, the
process 80 further includes receiving, at the user device, a plurality of offers, as indicated byblock 84, and displaying, at the user device, the offers in the offer interface, as indicated byblock 86. The offers may be received at approximately the same time the instructions ofstep 82 are received, for example along with a webpage, or the offers may be received at a later date, for example during a session subsequent to downloading the native application. - The offers interface may include inputs by which the user may search, filter, or otherwise browse offers having various attributes. Some of these interfaces are described below with reference to steps performed to determine whether the user has engaged these inputs. In some embodiments, determining whether the user has engaged these inputs may be performed by an event handler executed by the user device, the event handler causing the user device to perform the corresponding, below-described requests to the
offers engine 12 based on the type of event, e.g., whether the user touched, clicked, or otherwise selected a particular button on the offers interface. -
Illustrated process 80 includes determining whether the user is searching for offers, as indicated by block 88. With the offers interface, the user may express their intention to search for offers by entering search terms in a text entry box and selecting a button to request a search in accordance with the entered search term. Upon selecting this button, the user device may transmit a request for offers satisfying the entered search criteria, as indicated byblock 90. The transmitted request may be in the form of a GET request or an API call to theweb server 18 or theAPI server 16 of theoffers engine 12 ofFIG. 1 . - In some embodiments, the
process 80 further includes determining whether the user requests offers within a collection of offers, as indicated byblock 92. The offers interface may include selectable inputs that identify the collections, such as clickable collection names, collection selection buttons, or collection selection tabs. Examples of collections include categories of goods or services, such as sporting goods, house-wares, groceries, and the like; collections of modes of coupon redemption, such as in-store coupon redemption and online coupon redemption; collections based on offer statistics, such as newest offers, most popular offers, highest ranked offers; collections of offers designated by a user or other users; or collections based the value conferred by the offer, such as discounts, free shipping, rebates, and referral fees. Upon determining that the user has requested offers within a collection, the user device may transmit a request for offers within the collection to theoffers engine 12, as indicated byblock 94, which may return data responsive to the request. - In some embodiments, the
process 80 includes determining whether the user requests offers previously designated by the user, as indicated byblock 96. In some embodiments, the offers interface may include an input by which a user can designate an offer, such as designating offers as being a user favorite, designating offers as being ranked in a particular fashion, or designating offers as likely being of interest to some other user, such as users adjacent one another in a social graph. The offers interface may include an input for a user to make designations, such as a user selectable input labeled “add to my favorites,” or “add to my wallet,” and an input for a user to request offers having a designation, such as a user selectable input labeled “view my favorites.” or “view my wallet.” Upon determining that the user made such a request, theprocess 80 includes transmitting a request for the offers previously designated by the user, as indicated by block 88. The transmission may be made to theoffers engine 12, to theAPI server 16 or theweb server 18, as described above with reference toFIG. 1 , and may include an identification of the designation and the user. - The
process 80, in some embodiments, further includes determining whether the user requests offers previously designated by another user, as indicated byblock 100. The offers interface, in some embodiments, may include an input by which a user makes such a request, such as a user selectable input labeled “offers recommended by my friends.” Upon determining that the user has made such a request, theprocess 80 transmits a request for offers previously designated by the other user (or users), as indicated byblock 102. Again, the transmission may be to theoffers engine 12 ofFIG. 1 , which may store or otherwise have access to offers designated by other users and a social graph of the user by which responsive offers are identified. Further, the offers interface may include an input by which the user may view identifiers of other users and add the other users to an offer-interest graph of the user. This offer interest graph may be referenced by theoffers engine 12 to identify offers in response to the request ofstep 102. - The
process 80 further includes, in some embodiments, receiving, at the user device, one or more offers responsive to the request, as indicated byblock 104, and displaying the responsive offers on the offers interface, as indicated byblock 106. - In some embodiments and some use cases, a selection from the user is received via the offers interface, thereby identifying an offer among the displayed offers, as indicated by
block 108. In some embodiments, each of the offers may be displayed with an associated input by which the user selects the offer, such as a touchable or clickable button, region, or text. The selection, in some embodiments, may cause the offers interface to request additional data from the offers engine, such as instructions from the offers engine to navigate to an affiliate-network server associated with the offer or to navigate to a merchant server associated with the offer. In other embodiments, such instructions may be present within the offers interface, e.g., in the form of URLs linking to these servers. - The
process 80 further includes determining whether the selected offer is compensable through an affiliate network, as indicated byblock 110. This determination may be made by theoffers engine 12, in some embodiments, for each of the offers being displayed prior to transmission of the offers to the user device. For example, each offer may be associated with a designation indicating whether the offer is compensable in this fashion, and the designation may be transmitted along with the offer, for instance, by associating the offer with HTML or JavaScript™ that so designate the offer, or by including a field including the designation in a response to an API call for each offer. The user device, in some embodiments, may take different actions depending on the designation associated with the selected offer. - Upon determining that the selected offer is not compensable through an affiliate network, the
process 80 of this embodiment includes determining whether the selected offer is compensable directly from the merchant associated with the offer, as indicated byblock 112. Again, the determination ofblock 112 may be performed, in some embodiments, by theoffers engine 12 for each of the offers being displayed prior to transmission of the displayed offers, and each displayed offer may be associated with a designation based on the results of the determination, such as different HTML or JavaScript™ or a different field value in an API response. The user device may take different actions depending on this designation. - Upon determining that the selected offer is not compensable directly from the merchant, the
process 80 may proceed to block 118 described below. Upon determining that the selected offer is compensable, theprocess 80, in this embodiment, may proceed to request the website of the merchant issuing the selected offer with a request that identifies the affiliate from whom the selected offer was obtained, as indicated byblock 114. The request may be in the form of a URL having as a parameter an identifier of the entity operating theoffer engine 12, thereby indicating to the merchant that the affiliate should be compensated in accordance with an arrangement between the merchant and the affiliate. Upon performance ofstep 114, theprocess 80 of the present embodiment proceeds to step 120 described below. - As indicated by
block 110, upon determining that the selected offer is compensable through an affiliate network, theprocess 80 proceeds to transmit a request to the affiliate-network server for instructions to store data identifying an affiliate from whom the selected offer was obtained, as indicated byblock 116. This request may be a request for content from the affiliate-network server that is not displayed to the user, or is not displayed to the user for an appreciable amount of time (e.g., less than 500 ms), and the request may include an identifier of the affiliate, the merchant, and the offer. The requested content may cause the user device to store in persistent memory of the browser of the user device (e.g., memory that lasts between sessions, such as a cookie or a database of the browser) an identifier of the affiliate operating theoffers engine 12. This value may be retrieved later by the affiliate-network at the instruction of the merchant upon the user accepting the offer, for example by the user using a coupon code associated with the offer at the merchant, thereby allowing the merchant (or the affiliate network) to identify the appropriate party to compensate for the sale. - Upon transmitting the request the affiliate network server, the
process 80 further includes requesting the website of the merchant issuing the selected offer, as indicated byblock 118, and transmitting acceptance of the offer to the merchant via the merchant's website, as indicated byblock 120. Accepting the offer, as noted above, may cause the merchant to compensate the affiliate operating theoffers engine 12. - The
process 80 ofFIG. 3 is expected to facilitate relatively fast access to offers that are likely to be relevant to a user, as each of the determinations ofstep step offers engine 12 can be compensated, thereby potentially increasing revenue. - In some embodiments, as described further below, a native application interacts with the offers engine above to provide offers to users. Embodiments of the native application include functionality to enable users to redeem certain types of offers, e.g., online coupons. In such embodiments, a native application may provide for easier and faster redemption of offers and may eliminate or reduce complicated user actions to redeem online coupons. Accordingly,
FIGS. 4A-4H depict screens of a native application, such as native application 52 (FIG. 1 ), executing on a mobile user device, such asmobile user device 28, illustrating redemption of online coupons, the native application operating in accordance with an embodiment of the present invention. -
FIG. 4A depicts ascreen 400 of anative application 402 in accordance with an embodiment of the present invention. Thescreen 400 and other screens described below may be presented in a user interface of the mobile user device that may receive inputs from a user and provide outputs on a display. In some embodiments, the user interface may include a touchscreen, software modules, or any combination thereof. In such embodiments, inputs may be received as touches on the touchscreen, such as from a digit of a user, a stylus, etc. Thescreen 400 may include various user interface elements to display information to a user, and in some instances, receive user input. For example, thescreen 400 may include aheader portion 404, acoupon type toggle 406, anoffer display area 408, and anavigation bar 410. These user interface elements may be located at various locations defined by sets of coordinates of the touchscreen, such as x-coordinates associated with a horizontal position and y-coordinates associated with a vertical position. As shown inFIG. 4A , theheader portion 404 may be located at the top portion of the screen 400 (e.g., above thecoupon type toggle 406 and the offer display area 408). Similarly, in some embodiments thenavigation bar 410 may be displayed below theoffer display area 408. In other embodiments, the information in theheader portion 404 may be displayed in other areas, such as a footer portion, and thenavigation bar 408 may be located in other areas of the application, such as a header portion. - The
header portion 404 may display a title indicating the contents of thescreen 400 presented to the user, as selected by thecoupon type toggle 406. For example, theheader portion 404 includes the text “Top Coupons,” indicating to a user that top-ranked coupons are currently being presented. Thecoupon type toggle 406 may include a toggle button or other user interface element that enables a user to toggle between different types of coupons. For example, as shown inFIG. 4A , thecoupon type toggle 406 may enable a user to toggle between “Online” coupons and “In Store” coupons. Thenavigation bar 408 may include navigation controls, e.g., buttons 412, such as a “Home”button 412A and a “Profile”button 412B. For example, by selecting the “Home” button 410A, a user may return to a home screen of a native application. Similarly, the selection of the “Profile”button 412B enables a user to access a user profile associated with the application. - The coupon
area display area 408 may present offers, e.g., online coupons 414, for viewing and selection by a user. For example, as indicated by the header portion 404 (“Top Coupons”), the online coupons 414 may be top-ranked coupons determined by ranking criteria, such as user ratings, success rate, or other ranking criteria. The online coupons 414 may include any number of coupons associated with merchants providing goods, services, or a combination thereof. Each electronic coupon 414 may be presented with information describing the coupon, such as a merchant graphic 416, a success rate banner 418, and a coupon summary 420. The merchant graphic 416 may include text, an image (e.g., a merchant logo), or combination thereof identifying the merchant associated with the coupon. The success rate banner 418 may indicate a success rate for a coupon that indicates the percentage of instances in which the coupon was successfully used. In some embodiments, for example, the success rate may be determined based on user feedback on coupon usage. The coupon summary 420 may include information about the coupon, such as the goods, services, or both associated with the coupon, the discount or other offer provided by the coupon, the expiration date, any other suitable information, or a combination thereof. - For example, as shown in
FIG. 4A , a firstelectronic coupon 414A may be presented with a merchant graphic 416A (“Merchant1”) and may include asuccess rate banner 418A indicating the success rate of the coupon (“100% success”). Thecoupon 414A may be presented with acoupon summary 420A summarizing the discount provided by the coupon (“40% Off Save up to 40% on select diapers from Acme Co . . . ”). Additionally, thecoupon summary 420A may include the expiration date of the coupon (“Exp. Jun. 40, 2012”). Theother coupons 414B and 414C illustrated inFIG. 4A may include similar information, such as merchant graphic 416B, success rate banner 418B, coupon summary 420B, and so on. Additionally, the coupons 414 may include coupons for any type of offer, such as offers for free goods, services, or both, as indicated by thecoupon summary 420C forelectronic coupon 414C (“20 Free Tokens”). - To use a coupon, a user may select (e.g., touch) one of the online coupons 414. For example, a user may select any portion of the
coupon 414A, such as the merchant graphic 416A, thecoupon summary 420A, etc. Upon selection of a coupon, details about the coupon may be presented to enable a user to use the coupon (i.e., redeem the coupon) with a transaction with a merchant.FIG. 4B depicts anotherscreen 422 of a mobile user device in accordance with an embodiment of the present invention. Thescreen 422 may be presented in response to a user selection of an electronic coupon, such as selection of thecoupon 414A depicted inFIG. 4A . As shown inFIG. 4B , theheader portion 404 may change to include the name of the merchant (“Merchant1 Coupon”) to indicate contents of thescreen 422. Thescreen 422 may include acoupon detail area 424, asocial network portion 426, and thenavigation bar 410 described above. - The
coupon detail area 424 presents detailed information about the selectedelectronic coupon 414A. For example, a merchant graphic 427,success rate banner 428, andcoupon detail 430 may be presented. Additionally, thecoupon detail area 424 may include various controls, such as asave button 432, a “Use Coupon”button 434, and a “Share”button 436. In some embodiments, the controls may be any suitable user interface control, such as toggles, icons, switches, sliders, etc. As described above, the merchant graphic 427 may display text, images (e.g., logos), or any combination thereof associated with the merchant, and thesuccess rate banner 428 may display a determined success rate for the selectedcoupon 416A, such as a success rate based on user feedback. - Additionally, the
coupon detail area 424 displays acoupon code box 436 having an identifier, e.g., a coupon code 438 (“PMPRSYT8”), associated with thecoupon 414A. Thecoupon code 446 may be displayed in thecoupon code box 436 or other element of a user interface. Thecoupon code 438 may be a relatively short text string (e.g., shorter than 25 characters or 5 words) selected to be both distinct and memorable to users. In some cases, an image or other visibly distinctive user-manipulable body of data serves the role of thecoupon code 438. As described in detail below, the movement of thecoupon code box 436 may be animated to indicate various transitions within thenative application 402, potentially making the operation of the native application more intuitive to users. - As mentioned above, the
coupon detail area 424 includes various user interface elements to receive inputs from a user. Thesave button 432 presented in thecoupon detail area 424 enables a user to save a coupon for later use. Theshare button 436 enables a user to share coupons, such as sharing across social networking services, microblogging services, or other services. To use the selectedcoupon 414A, a user may select (e.g., touch) the “Use Coupon”button 434. As described below, upon selection of the “Use Coupon”button 434, another screen may be presented that enables a user to access the website of the merchant associated with the selectedcoupon 414A. Corresponding event handlers of the native application may detect the user interactions described herein (e.g., on Touch, onClick, on Move, touch events, and the like) and, in response, effectuate the described functionality. - The
feedback portion 426 depicted in thescreen 422 may include information from other users and a user's profile. The feedback and profile may be provided within thenative application 402. Thefeedback portion 426 may present acomment indicator 440 that indicates if other users have commented on the selectedcoupon 416A and provides the number of such comments. Additionally, thefeedback portion 426 may includeuser profile information 428, such as apicture 442 associated with a user's profile and other profile information. - As mentioned above, a user may select the “Use Coupon”
button 434 to use the selectedcoupon 414A for a purchase of goods and services. Upon selection of the “Use Coupon”button 434, thecoupon code box 436 may visually move from afirst location 443 shown in thescreen 422 to a second location. This movement is illustrated by the arrows depicted inFIGS. 4B-4D . As shown inFIG. 4B , after a user selects the “Use Coupon”button 434, thecoupon code box 436 may move (e.g., translate) along the path indicated byarrow 444. In some embodiments, thecoupon code box 436 may move in towards theheader portion 404, translating through changing x and y coordinates. Thecoupon code box 436 may move along a generally linear path, a generally arcuate path, or any combination thereof. In other embodiments, thecoupon code box 436 may move to any other locations, such as a footer or other locations within thescreen 422. Additionally, in some embodiments, thecoupon code box 436 may only be provided at the second location without animation of a visual movement. -
FIG. 4C further depicts thescreen 422 and illustrates a stage in the animation of thecoupon code box 436 in accordance with an embodiment of the present invention. As shown inFIG. 4B , thecoupon code box 436 may move from thefirst location 443 and along the path indicated byarrow 444 towards a second location at theheader portion 404. During the animation, thecoupon code box 436 may continue to move (e.g., translate) towards theheader portion 404, as indicated byarrow 446. - After completion of the move, the
coupon code box 436 may be located at a second location at theheader portion 404. Accordingly,FIG. 4D depicts ascreen 453 of a mobile user device that illustrates the completion of the animation of thecoupon code box 436 in accordance with an embodiment of the present invention. Additionally, as shown inFIG. 4D , thescreen 453 includes amerchant website 454 displayed by the mobile user device. As shown in this figure, after a user selects the “Use Coupon”button 434, the website of the merchant associated with coupon may be presented to enable a user to purchase goods or services from the merchant using the coupon. As mentioned above, thenative application 402 may be include or be capable of instantiating a web browser, e.g., a webview object, and the merchant website may be retrieved via an affiliate networking redemption process by which the web browser requests content from an affiliate network server, the request including an identifier of the provider of the native application, and the affiliate network returning content operative to store an affiliate identifier in a cookie (or other persistent, browser-accessible storage) accessible to the affiliate network operator and instructions to redirect the browser to the merchant website. Or an identifier of the provider of the native application may be appended to a URL of the merchant website to signal that the provider should be compensated. Thus, web content, such as themerchant website 454, may be retrieved from the Internet via a network accessible by a mobile user device executing thenative application 402, as described above. In some embodiments, for example, the presentation of web content in thenative application 402 may be referred to as a “web view.” - As noted above,
FIG. 4D depicts the end of the animation of thecoupon code box 436. As shown inFIG. 4D , thecoupon code box 436 moves (e.g., translates) in a generally vertical direction to asecond location 455 until thecoupon code box 436 is located in the header portion. Additionally, in some embodiments, thecoupon code box 436 may be resized. Any previous text, images or other elements in theheader portion 404 may be removed or replaced upon progression to thescreen 453. Theheader portion 404 of thescreen 453 may also include a “Done”button 456. Additionally, thescreen 453 includes aweb navigation bar 458 located below themerchant website 454. As described below, theweb navigation bar 458 may include controls for browsing the web content, e.g., themerchant website 454, presented in theapplication 402. - Depicting the
coupon code 438 in a different location after a user selects theuse coupon button 434 is expected to make coupon use more intuitive, as the user has a visual indication that acoupon code 438 has been selected, and that the native application is storing thecoupon code 438 for use. Depicting an animated movement to such a location, e.g., simulating movement of a physical item, is expected to make the native application appear responsive to the user and create a sense that thecoupon code 438 is more like a tangible physical item to be accorded elevated importance in the mind of the user. The movement may be of constant speed, or movement may change speed, simulating for example generally constant acceleration and deceleration with an intervening duration of constant speed. In some cases, animated movement may simulate damped vibrating movements as thecoupon code 438 settles into the second position. In some cases thecoupon code 438 may also rotate or perform other movements as it translates to accentuate the effect. Thecoupon code 438 may also change size, e.g., linearly enlarging over some duration prior to movement to simulate elevation normal to the screen, followed by translation to the second position, and a similar reduction in size to simulate lowering into the second position. Some embodiments may calculate parameters of, and render, a drop shadow as thecoupon code 438 attains and moves through such the simulated elevated height toward the second location, following thecoupon code 438 with the drop shadow, and adjusting and removing the drop shadow as thecoupon code 438 is elevated and lowers. Other embodiments may distort thecoupon code 438 during movement, translating, for example an upper left corner initially faster than a lower right corner, and calculating and rendering a skew transform of increasing severity over some duration on an image of thecoupon code 438. In some embodiments, thecoupon code 438 may track a user gesture toward the header, remaining, for example under the touch of the user as the user drags the code upward and snapping in to place once a threshold proximity to the second position is attained. - In some embodiments, a
help balloon 460 may be presented that includes text to aid the user in using thecoupon code 438. Thehelp balloon 460 may include instructions or other text that describes how to move thecoupon code box 436, as illustrated below inFIGS. 4E-4H . For example, as shown inFIG. 4D , thehelp balloon 460 includes text “DRAG this coupon code into the redemption box” to instruct a user how to move thecoupon code box 436 in the manner described below. Thehelp balloon 460 may also include a “Close”button 462 to enable a user to close thehelp balloon 460 and remove it from display in theapplication 402. In some embodiments, thehelp balloon 460 may be presented whenscreen 453 is displayed. Additionally, or alternatively, thehelp balloon 460 may be displayed in response to a user input, such as touch located at or near thecoupon code box 436, a cursor located at or near thecoupon code box 436, etc. In one embodiment, thehelp balloon 460 may include a chat window that will provide the user to engage an online chat application to receive and respond to communications such as text communications. For instance, thehelp balloon 460 may include a text input that posts user-entered questions to the offers engine (e.g., asynchronous with an XMLHttpRequest), which may respond with answers to the questions, e.g., with text displayed in-line with the user-entered question. In some cases, responses are identified by 1) parsing keywords from the user-entered question, for instance by removing stopwords, 2) searching a plurality of frequently-asked-question records for answers, associated keywords, or associated questions including the parsed keywords, 3) ranking responsive candidate answers, for instance based on the number of corresponding keywords, and 4) sending the highest ranking answer to the client device, which may execute instructions associated with thehelp balloon 460 that display the response. In some cases, answers to user questions are manually entered or selected by a human operator via the above-described administrator interface, or manually entered answers are provided when an automated selection based on keywords fails or fails to provide an answer after more than a threshold number of exchanges with the user. - The
merchant website 454 may include a variety of web content that enables a user to search or browse for goods, services, or both and select and order such goods and servers. For example, a user may select the “Use Coupon”button 443 to access themerchant website 454 to order goods and services associated with the selectedcoupon 414A. As shown inFIG. 4D , for example, web content of themerchant website 454 may include asearch field 464,search button 466, and amerchant storefront 468. It should be appreciated that the web content depicted inFIG. 4D is merely an example and merchant websites may include a wide variety of web content, designs, and functionality. Such functionality may include, for example, the ability to search themerchant website 454 by entering a search query into thesearch field 464 and selecting (e.g., touching, clicking, etc.) thesearch button 466. Additionally, themerchant storefront 468 may display goods, services, or both offered by the merchant and available for order by a user. In some embodiments, a user may use thesearch field 464 to find the goods, services, or both associated with the selected coupon. In other embodiments, the goods or services may be presented to the user in themerchant storefront 468 in response to a selection of the “Use Coupon”button 443. - As described above, a user may use the merchant website to order goods and services associated with the selected coupon, such as by adding the goods and services to a virtual “shopping cart” and selecting an option to checkout.
FIG. 4E depicts ascreen 472 of theapplication 402 illustrating acheckout page 474 of themerchant website 454 in accordance with an embodiment of the present invention. As described above, web content such as thecheckout page 474 may be retrieved from the Internet via a network accessible by a mobile user device executing theapplication 402, and this web content may be displayed within theapplication 402 in the manner described above. As shown inFIG. 4E , theheader portion 404 includes thecoupon code box 436 and the “Done”button 454. That is, theheader portion 404 may retain thecoupon code box 436 to ensure thecoupon code box 436 is accessible until a user has completed a transaction, e.g., an order for goods, services, or both, with the merchant. Alternatively, a user may exit the display of web content in theapplication 402 by selecting the “Done”button 454 and returning to previous screens of theapplication 402. - The merchant checkout page may include various web content that enables a user to view and enter order information and complete an order for goods, services, or both. For example, the
merchant checkout page 474 may include anorder information portion 476, acode entry portion 478, and acheckout button 480. Theorder information portion 476 enables a user to enter a shipping address, a billing address, payment information, and the like. By selecting the checkout button 478 (“Place Your Order”), a user may submit an order for fulfillment by the merchant. Thecode entry portion 478 may enable a user to enter coupon codes, promotional codes, gift card codes, or any other codes that may be applied to an order. Thecode entry portion 478 may include an input field 482 (e.g., a text field that receives text input) and a submission button 484 (“Apply”). By entering a coupon code or other code into theinput field 482 and selecting thesubmission button 484, a user may submit a coupon code to apply a coupon associated with the merchant. In some embodiments, theinput field 482 may accept images or other input. - As described below in
FIGS. 4F-4H , theapplication 402 provides for easy and intuitive entry of thecoupon code 438 of the selectedcoupon 414A via a gesture within the user interface. As shown inFIGS. 4F-4H , a user may drag and drop thecoupon code box 436 over theinput field 482 to have thecoupon code 438 entered in theinput field 482. Thus, a user does not need to memorize the coupon code or manually type the code directly into theinput field 482. AlthoughFIGS. 4F-4H are described with reference to an input field of a checkout webpage associated with a merchant, it should be appreciated that the same techniques may apply to input fields located in any webpage associated with a merchant that may receive a coupon code and for which a user desired to enter the code. For example, a shopping cart webpage, a product webpage, or other merchant webpages may have an input field that may be processed in the manner described above, such that a user may drag-and-drop a coupon code box to enter a coupon code in the input field. -
FIG. 4F depicts thescreen 472 illustrating the selection and animation of thecoupon code box 436 in accordance with an embodiment of the present invention. As shown inFIG. 4F , a user may select (e.g. touch, click, etc.) thecoupon code box 436 and drag thecoupon code box 436 from a first position 486 towards theinput field 482, such as along the path indicated by arrow 487. In some embodiments, the selection may include a touch referred to as a “long press,” generating a long-press event in the native application that the above-mentioned event handler handles to initiate the following drag and drop operation. During the drag, avisual copy 488 of thecoupon code box 436 may be animated along the path indicated by arrow 487 to indicate the movement of thecoupon code box 436. The animation may follow one of the animation routines described above, including tracing the position of a touch as the touch is dragged across the screen. - Next, as shown in
FIG. 4G , thevisual copy 488 of the coupon code box may be dragged to or near theinput field 482 and dropped (e.g., by releasing a touch), generating a touch-up or touch-end event to which the native application responds to effectuate the subsequent operations.FIG. 4G depicts thescreen 472 further illustrating animation of the drag-and-drop of thevisual copy 488 to asecond location 490 located at or near theinput field 482, in accordance with an embodiment of the invention. As shown inFIG. 4G , the visual copy 488 (e.g., an area of the screen, such as a rectangle, depicting the code) may be animated and visually move (e.g., translate) along the path indicated byarrow 491 as a user drags thevisual copy 488 toward theinput field 482. After thevisual copy 488 has been dragged over theinput field 482, a user may deselect the visual copy 488 (such as by releasing a touch, releasing a click, etc.). - After deselection of the
visual copy 488 at thesecond location 490, thecoupon code 438 of thecoupon code box 436 may be entered into theinput field 482, entering the text depicted in thevisual copy 488.FIG. 4H further depicts thescreen 472 and illustrates entry of thecoupon code 438 in theinput field 482 in response the gesture described above and in accordance with an embodiment of the present invention. After a user deselects (e.g., releases a touch) thevisual copy 488 at thesecond location 490 at or near theinput field 482, thevisual copy 488 may disappear and a value 492 (e.g., a text value) corresponding to thecoupon code 438 may entered (e.g., pasted) into theinput field 482. A user may then select thesubmission button 484 to apply the coupon code to the order. Thus, the coupon code may be entered into theinput field 482 by dragging and dropping thevisual copy 488 of thecoupon code box 436 to a location at or near thetext box 482. After application of the coupon code, a user may submit the order to the merchant by selecting the “Place Your Order”button 478. - Thus, the native application may have access to inputs, e.g., inputs of text type in forms of the rendered merchant webpage. The native application may employ a variety of techniques to identify the appropriate document object model (DOM) element corresponding to the text input. For instance, merchants may designate a coupon code text entry element with a specific class or other identifier that the native application uses to get the appropriate element from the DOM for insertion of the coupon code text, e.g., by changing a value attribute of the element. Or the native application may identify the corresponding DOM element based on correspondence between the screen location of the touch-release event and the location of text inputs on the screen, generating an inventory of text input DOM elements and their offsetTop and offsetLeft coordinates, and selecting the closest text input to the touch-up event location to receive the coupon code. In some cases, the candidate text inputs are filtered based on their context, removing, for instance, those text inputs in div boxes having text relating to an address or name and favoring those text inputs in div boxes having text with the string “coupon.”
-
FIG. 5 depicts a first portion ofuser actions 500 and afirst portion 502 of a coupon redemption process in accordance with an embodiment of the present invention. Some or all steps of theprocess portion 502 may be implemented as executable computer code stored on a non-transitory tangible computer-readable storage medium and executed by one or more processors of a special-purpose machine, e.g., a computing device programmed to execute the code. Initially, a user may select a coupon from a coupon list (block 504) presented in a native application, as shown above inFIG. 4A , and the coupon selection may be received (box 508). Next, as described above inFIG. 4B , the selected coupon may be provided with a coupon code box having a coupon code associated with the selected coupon (block 508). If a user decides to use the coupon, the user may select a use coupon button (block 510) and the selection of the button may be received (block 512). Additionally, a value corresponding to the coupon code of the coupon code box may be copied to a clipboard accessible by the application (block 513). As illustrated above inFIGS. 4C and 4D , a visual movement of the coupon code box from a first location to a second location at the header portion of the application may be animated and the elements in the header portion may be replaced by the coupon code box (block 514). Next, after a user has selected to use a selected coupon, the merchant website may be provided within the native application (block 516), e.g., in a web view within the native application. For example, as described above, a merchant website may be requested from one or more merchant webservers. Additionally, in some embodiments, a help balloon may be provided adjacent to the coupon code box with instructions or other text to describe how to use the application (block 518). The redemption process may continue with a second portion depicted inFIG. 6 , as indicated by connector block A. -
FIG. 6 depictsuser actions 600 and asecond portion 602 of a coupon redemption process in accordance with an embodiment of the present invention. Some or all steps of theprocess portion 602 may be implemented as executable computer code stored on a non-transitory tangible computer-readable storage medium and executed by one or more processors of a special-purpose machine, e.g., a computing device programmed to execute the code. As shown by connector block A inFIG. 6 , thesecond portion 602 of the redemption process may continue from thefirst portion 404 described above and illustrated inFIG. 4 For example, after a user selects to use a coupon, a user may search and browse a merchant website to purchase goods, services, or both associated with the coupon. Subsequently, a user may select a checkout page within the merchant website to complete an order for goods, services, or both (block 604). In response, a merchant checkout page may be provided within a native application (block 606), e.g., in a web view, as described above and illustrated inFIG. 4E . - Next a user may drag-and-drop a coupon code box to an input field within the merchant checkout page, as described above and illustrated in
FIGS. 4F and 4G . To initiate the drag-and-drop, a user may select (e.g., touch) the coupon code box in the header portion of the application (block 608)). Next, the user may drag the coupon code box over the input field within the checkout page (block 612). Accordingly, a visual copy of the coupon code box may be animated from a first location to a second location along the drag path performed by the user (block 614). A user may then complete the drag-and-drop by dropping the visual copy of the coupon code box at or near the input field within the checkout page (block 616). The visual copy of the coupon code box may be then be removed and the value corresponding to the coupon code may be entered into the input field (block 618), as described above and illustrated inFIG. 4H . After the coupon code is entered into the input field, a user may submit the coupon code for redemption and continue the checkout to complete the order (block 620). As described above inFIG. 3 , redemption of offers, such as a selected coupon, may occur through an affiliate network or directly from a merchant. -
FIG. 7 depicts aprocess 700 for implementing the drag-and-drop of a coupon code box to an input field in accordance with an embodiment of the present invention. For example, theprocess 700 may be implemented within thesecond portion 602 of the redemption process described above and illustrated inFIG. 6 . Some or all steps of theprocess 700 may be implemented as executable computer code stored on a non-transitory tangible computer-readable storage medium and executed by one or more processors of a special-purpose machine, e.g., a computing device programmed to execute the code. Offers may be obtained from the above-mentioned offers engine ofFIG. 1 , and initially, a touch on a coupon code box presented in a native application may be received at a first location, e.g., at a header portion of the native application (block 702). In response, the value of a coupon code of the coupon code box may be copied to a clipboard and a visual copy of the coupon code box may be generated (block 704). Next, a gesture (e.g., a drag) of movement of the touch may be received as a user drags the coupon code box towards an input field of a webpage associated with a merchant (block 706). To visually indicate the steps described above to a user, a visual movement of the visual copy of the coupon code box along the drag path may be animated (block 708). When the coupon code box is at or near the input field, a touch release at a second location may be received (block 710). - Based on the location of the touch release, the location of the input field may be determined by finding the coordinates of the second location (block 712). For example, in some embodiment the location of the input field may be determined from a document object model (DOM) associated with the webpage. Based on this located input field, the input field may be set to a value corresponding to the coupon code associated with the coupon code box (block 714). Finally, the touch release may be animated to indicate that the coupon code is successfully entered in the input field (block 716). For example, the visual copy may be removed from the user interface and the value displayed in the input field of the webpage associated with the merchant.
-
FIG. 8 depicts a mobile user device 800 in accordance with an embodiment of the present invention. Various sections of systems and computer-implemented methods described herein, may include or be executed on one or more computers similar to mobile user device 800. Further, processes and modules described herein may be executed by one or more processing systems similar to that of mobile user device 800. The mobile user device 800 may include various internal and external components that contribute to the function of the device and which may allow the mobile user device 800 to function in accordance with the techniques discussed herein. It should further be noted thatFIG. 8 depicts merely one example of a particular implementation and is intended to illustrate the types of components and functionalities that may be present in mobile user device 800. - Mobile user device 800 may include any combination of devices or software that may perform or otherwise provide for the performance of the techniques described herein. For example, mobile user device 800 may include a tablet, a mobile phone, such as a smartphone, a video game device, and other hand-held networked computing devices. Mobile user device 800 may also be connected to other devices that are not illustrated, or may operate as a stand-alone system. In addition, the functionality provided by the illustrated components may in some embodiments be combined in fewer components or distributed in additional components. Similarly, in some embodiments, the functionality of some of the illustrated components may not be provided or other additional functionality may be available.
- In addition, the mobile user device 800 may allow a user to connect to and communicate through a network (e.g., the Internet, a local area network, a wide area network, etc.) and may provide communication over a satellite-based positioning system (e.g., GPS). For example, the mobile user device 800 may allow a user to communicate using e-mail, text messaging, instant messaging, or using other forms of electronic communication, and may allow a user to obtain the location of the device from the satellite-based positioning system, such as the location on an interactive map.
- As shown in
FIG. 8 , the mobile user device 800 may include a processor 802 (e.g., one or more processors) coupled to amemory 804, adisplay 806, and a network interface 808 via aninterface 810. It should be appreciated the mobile user device 800 may include other components not shown inFIG. 8 , such as a power source (e.g., a battery), I/O ports, expansion card interfaces, hardware buttons, etc. In some embodiments, thedisplay 806 may include a liquid crystal display (LCD) or an organic light emitting diode (OLED) display. Thedisplay 806 may display a user interface (e.g., a graphical user interface), and may also display various function and system indicators to provide feedback to a user, such as power status, call status, memory status, etc. These indicators may be in incorporated into the user interface displayed on thedisplay 806. In accordance with some embodiments, thedisplay 806 may include or be provided in conjunction with touch sensitive elements through which a user may interact with the user interface. Such a touch-sensitive display may be referred to as a “touchscreen” and may also be known as or called a touch-sensitive display. Thus, in such embodiments, a user interface may provide for interaction via touch-sensitive elements of thedisplay 806. In such an embodiment, thedisplay 806 may include a capacitive touchscreen, a resistive touchscreen, or any other suitable touchscreen technology. - The
processor 802 may provide the processing capability required to execute the operating system, programs, user interface, and any functions of the mobile user device 800. Theprocessor 802 may include one or more processors that may include “general-purpose” microprocessors and special purpose microprocessors, such as one or more reduced instruction set (RISC) processors, such as those implementing the Advanced RISC Machine (ARM) instruction set. Additionally, theprocessor 802 may include single-core processors and multicore processors and may include graphics processors, video processors, and related chip sets. A processor may receive instructions and data from a memory (e.g., system memory 804). Processes, such as those described herein may be performed by one or more programmable processors executing computer code to perform functions by operating on input data and generating corresponding output. - The memory 804 (which may include tangible non-transitory computer readable storage mediums) may include volatile memory and non-volatile memory accessible by the
processor 802 and other components of the mobile user device 800. Thememory 804 may include volatile memory, such as random access memory (RAM), and non-volatile memory, such as ROM, flash memory, a hard drive, any other suitable optical, magnetic, or solid-state storage medium, or a combination thereof. Thememory 804 may store a variety of information and may be used for a variety of purposes. For example, thememory 804 may store executable code, such as the firmware for the mobile user device 800, an operating system for the mobile user device 800, and any other programs. The executable computer code may include instructions executable by a processor, such asprocessor 802, and the computer may include instructions for implementing one or more techniques described herein with regard to various processes. For example, thememory 804 may store an executablenative application 812 having acoupon redemption process 814, such as that described above. The executablenative application 812 may enable a user to view offers, such as online coupons, and select and redeem online coupons using the user actions described above. The executable code may be written in a programming language, including compiled or interpreted languages, or declarative or procedural language, and may be composed into a unit suitable for use in a computing environment, including as a stand-alone program, a module, a component, a subroutine. Such code program may be stored in a section of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or sections of code). Additionally, the copies of the executable code may be stored in both non-volatile and volatile memories, such as in a non-volatile memory for long-term storage and a volatile memory during execution of the code. - The
interface 810 may include multiple interfaces and may couple various components of the mobile user device 800 to theprocessor 802 andmemory 804. In some embodiments, theinterface 810, theprocessor 802,memory 804, and one or more other components of the mobile user device 800 may be implemented on a single chip, such as a system-on-a-chip (SOC). In other embodiments, these components, their functionalities, or both may be implemented on separate chips. Theinterface 810 may be configured to coordinate I/O traffic betweenprocessor 802,memory 804,network interface 806, and other internal and external components of the mobile user device 800. Theinterface 810 may include functionality for interfacing via various types of peripheral buses, such as a variant of the Peripheral Component Interconnect (PCI) bus standard, the Universal Serial Bus (USB) standard, and the like. - The mobile user device 800 depicted in
FIG. 8 also includes a network interface 808, such as a wired network interface, wireless (e.g., radio frequency) receivers, etc. For example, the network interface 808 may receive and send electromagnetic signals and communicate with communications networks and other communications devices via the electromagnetic signals. The network interface 808 may include known circuitry for performing these functions, including an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. Thenetwork interface 804 may communicate with networks (e.g., network XXX), such as the Internet, an intranet, a cellular telephone network, a wireless local area network (LAN), a metropolitan area network (MAN), or other devices by wireless communication. The network interface 808 may suitable any suitable communications standard, protocol and technology, including Ethernet, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), a 4G network (e.g., based upon the IMT-2000 standard), high-speed downlink packet access (HSDPA), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), a 4G network (e.g., IMT Advanced, Long-Term Evolution Advanced (LTE Advanced), etc.), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for email (e.g., Internet message access protocol (IMAP) or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), Multimedia Messaging Service (MMS), Short Message Service (SMS), or any other suitable communication protocol. In some embodiments, for example, thenative application 810 may be transmitted to the mobile user device 800 over a network via the network interface 808. Additionally, a user may use thenative application 810 to retrieve online coupons and view web content received via the network interface 808. - Those skilled in the art will also appreciate that, while various items are illustrated as being stored in memory or on storage while being used, these items or sections of them may be transferred between memory and other storage devices for purposes of memory management and data integrity. Alternatively, in other embodiments some or all of the software components may execute in memory on another device and communicate with the illustrated computer system via inter-computer communication. Some or all of the system components or data structures may also be stored (e.g., as instructions or structured data) on a computer-readable medium or a portable article to be read by an appropriate drive, various examples of which are described above. In some embodiments, instructions stored on a computer-readable medium separate from mobile user device 800 may be transmitted to mobile user device 800 via transmission media or signals such as electrical, electromagnetic, or digital signals, conveyed via a communication medium such as a network or a wireless link. Various embodiments may further include receiving, sending or storing instructions or data implemented in accordance with the foregoing description upon a computer-accessible medium. Accordingly, the present invention may be practiced with other computer system configurations.
- Various embodiments may further include receiving, sending or storing instructions and/or data implemented in accordance with the foregoing description upon a computer-accessible medium. Generally speaking, a computer-accessible/readable storage medium may include a non-transitory storage media such as magnetic or optical media, (e.g., disk or DVD/CD-ROM), volatile or non-volatile media such as RAM (e.g. SDRAM, DDR, RDRAM, SRAM, etc.), ROM, etc., as well as transmission media or signals such as electrical, electromagnetic, or digital signals, conveyed via a communication medium such as network and/or a wireless link.
- Further modifications and alternative embodiments of various aspects of the invention will be apparent to those skilled in the art in view of this description. Accordingly, this description is to be construed as illustrative only and is for the purpose of teaching those skilled in the art the general manner of carrying out the invention. It is to be understood that the forms of the invention shown and described herein are to be taken as examples of embodiments. Elements and materials may be substituted for those illustrated and described herein, parts and processes may be reversed or omitted, and certain features of the invention may be utilized independently, all as would be apparent to one skilled in the art after having the benefit of this description of the invention. Changes may be made in the elements described herein without departing from the spirit and scope of the invention as described in the following claims. Headings used herein are for organizational purposes only and are not meant to be used to limit the scope of the description.
- As used throughout this application, the word “may” is used in a permissive sense (i.e., meaning having the potential to), rather than the mandatory sense (i.e., meaning must). The words “include”, “including”, and “includes” mean including, but not limited to. As used throughout this application, the singular forms “a”, “an” and “the” include plural referents unless the content clearly indicates otherwise. Thus, for example, reference to “an element” includes a combination of two or more elements. Unless specifically stated otherwise, as apparent from the discussion, it is appreciated that throughout this specification discussions utilizing terms such as “processing”, “computing”, “calculating”, “determining” or the like refer to actions or processes of a specific apparatus, such as a special purpose computer or a similar special purpose electronic processing/computing device. In the context of this specification, a special purpose computer or a similar special purpose electronic processing/computing device is capable of manipulating or transforming signals, typically represented as physical electronic or magnetic quantities within memories, registers, or other information storage devices, transmission devices, or display devices of the special purpose computer or similar special purpose electronic processing/computing device.
Claims (20)
Priority Applications (22)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/840,237 US20130332283A1 (en) | 2012-06-11 | 2013-03-15 | Devices, methods, and computer-readable media for redemption of merchant offers |
CA3129998A CA3129998A1 (en) | 2012-06-11 | 2013-06-11 | Devices, methods, and computer-readable media for redemption of merchant offers |
PCT/US2013/045139 WO2013188373A1 (en) | 2012-06-11 | 2013-06-11 | Devices, methods, and computer-readable media for redemption of merchant offers |
CA2876004A CA2876004A1 (en) | 2012-06-11 | 2013-06-11 | Devices, methods, and computer-readable media for redemption of merchant offers |
EP13733476.9A EP2859516A1 (en) | 2012-06-11 | 2013-06-11 | Determining offers for a geofenced geographic area |
AU2013274398A AU2013274398A1 (en) | 2012-06-11 | 2013-06-11 | Determining offers for a geofenced geographic area |
CA2876011A CA2876011A1 (en) | 2012-06-11 | 2013-06-11 | Determining offers for a geofenced geographic area |
PCT/US2013/045186 WO2013188409A1 (en) | 2012-06-11 | 2013-06-11 | Determining offers for a geofenced geographic area |
US13/928,833 US10664857B2 (en) | 2012-06-11 | 2013-06-27 | Determining offers for a geofenced geographic area |
US14/060,550 US9558507B2 (en) | 2012-06-11 | 2013-10-22 | Reminding users of offers |
US14/199,588 US10878439B2 (en) | 2012-06-11 | 2014-03-06 | Mobile-offer creation |
EP14724212.7A EP2973311A1 (en) | 2013-03-15 | 2014-03-15 | Cross-device service platform |
AU2014233259A AU2014233259A1 (en) | 2013-03-15 | 2014-03-15 | Cross-device service platform |
PCT/US2014/029953 WO2014145229A1 (en) | 2013-03-15 | 2014-03-15 | Cross-device service platform |
CA2906178A CA2906178A1 (en) | 2013-03-15 | 2014-03-15 | Cross-device service platform |
US15/383,644 US10074101B2 (en) | 2012-06-11 | 2016-12-19 | Reminding users of offers |
US15/858,172 US10776812B2 (en) | 2012-06-11 | 2017-12-29 | Reminding users of offers |
US16/595,283 US10915916B2 (en) | 2012-06-11 | 2019-10-07 | Devices, methods and computer-readable media for redemption of merchant offers |
US16/847,470 US11244337B2 (en) | 2012-06-11 | 2020-04-13 | Determining offers for a geofenced geographic area |
US16/995,895 US20200380552A1 (en) | 2012-06-11 | 2020-08-18 | Reminding users of offers |
US17/141,020 US20210125213A1 (en) | 2012-06-11 | 2021-01-04 | Devices, methods, and computer-readable media for redemption of merchant offers |
US17/565,103 US20220122112A1 (en) | 2012-06-11 | 2021-12-29 | Determining offers for a geofenced geographic area |
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201261658387P | 2012-06-11 | 2012-06-11 | |
US201261658404P | 2012-06-11 | 2012-06-11 | |
US201261658408P | 2012-06-12 | 2012-06-12 | |
US201261665740P | 2012-06-28 | 2012-06-28 | |
US201261707527P | 2012-09-28 | 2012-09-28 | |
US13/840,237 US20130332283A1 (en) | 2012-06-11 | 2013-03-15 | Devices, methods, and computer-readable media for redemption of merchant offers |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/836,808 Continuation-In-Part US10346867B2 (en) | 2012-06-11 | 2013-03-15 | Intents for offer-discovery systems |
Related Child Applications (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/836,110 Continuation-In-Part US20130332284A1 (en) | 2012-06-11 | 2013-03-15 | Cross-device offers platform |
US13/839,066 Continuation US9881315B2 (en) | 2012-06-11 | 2013-03-15 | Systems, methods, and computer-readable media for a customizable redemption header for merchant offers across browser instances |
US13/836,808 Continuation-In-Part US10346867B2 (en) | 2012-06-11 | 2013-03-15 | Intents for offer-discovery systems |
US16/595,283 Continuation US10915916B2 (en) | 2012-06-11 | 2019-10-07 | Devices, methods and computer-readable media for redemption of merchant offers |
Publications (1)
Publication Number | Publication Date |
---|---|
US20130332283A1 true US20130332283A1 (en) | 2013-12-12 |
Family
ID=49716028
Family Applications (19)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/840,237 Abandoned US20130332283A1 (en) | 2012-06-11 | 2013-03-15 | Devices, methods, and computer-readable media for redemption of merchant offers |
US13/836,808 Active 2037-01-23 US10346867B2 (en) | 2012-06-11 | 2013-03-15 | Intents for offer-discovery systems |
US13/837,790 Active 2034-04-21 US9639853B2 (en) | 2012-06-11 | 2013-03-15 | Devices, methods, and computer-readable media for redemption header for merchant offers |
US13/839,066 Active 2035-10-19 US9881315B2 (en) | 2012-06-11 | 2013-03-15 | Systems, methods, and computer-readable media for a customizable redemption header for merchant offers across browser instances |
US13/836,110 Abandoned US20130332284A1 (en) | 2012-06-11 | 2013-03-15 | Cross-device offers platform |
US13/928,833 Active 2037-01-21 US10664857B2 (en) | 2012-06-11 | 2013-06-27 | Determining offers for a geofenced geographic area |
US15/471,682 Active US9953335B2 (en) | 2012-06-11 | 2017-03-28 | Devices, methods, and computer-readable media for redemption header for merchant offers |
US15/849,050 Active 2034-01-03 US11068922B2 (en) | 2012-06-11 | 2017-12-20 | Systems, methods, and computer-readable media for a customizable redemption header for merchant offers across browser instances |
US15/853,016 Active US9965769B1 (en) | 2012-06-11 | 2017-12-22 | Devices, methods, and computer-readable media for redemption header for merchant offers |
US15/944,469 Active 2033-06-28 US10586243B2 (en) | 2012-06-11 | 2018-04-03 | Devices, methods, and computer-readable media for redemption header for merchant offers |
US16/219,649 Active US10304074B2 (en) | 2012-06-11 | 2018-12-13 | Devices, methods, and computer-readable media for redemption header for merchant offers |
US16/399,970 Active 2033-12-22 US11321728B2 (en) | 2012-06-11 | 2019-04-30 | Reducing latency in cross-device experiences with caching and hashing |
US16/430,373 Active 2033-07-16 US11151593B2 (en) | 2012-06-11 | 2019-06-03 | Intents for offer-discovery systems |
US16/554,457 Active US10586244B2 (en) | 2012-06-11 | 2019-08-28 | Devices, methods, and computer-readable media for redemption header for merchant offers |
US16/595,283 Active US10915916B2 (en) | 2012-06-11 | 2019-10-07 | Devices, methods and computer-readable media for redemption of merchant offers |
US16/698,132 Active 2033-11-29 US11386446B2 (en) | 2012-06-11 | 2019-11-27 | Devices, methods, and computer-readable media for redemption header for merchant offers |
US16/847,470 Active US11244337B2 (en) | 2012-06-11 | 2020-04-13 | Determining offers for a geofenced geographic area |
US17/141,020 Abandoned US20210125213A1 (en) | 2012-06-11 | 2021-01-04 | Devices, methods, and computer-readable media for redemption of merchant offers |
US17/565,103 Pending US20220122112A1 (en) | 2012-06-11 | 2021-12-29 | Determining offers for a geofenced geographic area |
Family Applications After (18)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/836,808 Active 2037-01-23 US10346867B2 (en) | 2012-06-11 | 2013-03-15 | Intents for offer-discovery systems |
US13/837,790 Active 2034-04-21 US9639853B2 (en) | 2012-06-11 | 2013-03-15 | Devices, methods, and computer-readable media for redemption header for merchant offers |
US13/839,066 Active 2035-10-19 US9881315B2 (en) | 2012-06-11 | 2013-03-15 | Systems, methods, and computer-readable media for a customizable redemption header for merchant offers across browser instances |
US13/836,110 Abandoned US20130332284A1 (en) | 2012-06-11 | 2013-03-15 | Cross-device offers platform |
US13/928,833 Active 2037-01-21 US10664857B2 (en) | 2012-06-11 | 2013-06-27 | Determining offers for a geofenced geographic area |
US15/471,682 Active US9953335B2 (en) | 2012-06-11 | 2017-03-28 | Devices, methods, and computer-readable media for redemption header for merchant offers |
US15/849,050 Active 2034-01-03 US11068922B2 (en) | 2012-06-11 | 2017-12-20 | Systems, methods, and computer-readable media for a customizable redemption header for merchant offers across browser instances |
US15/853,016 Active US9965769B1 (en) | 2012-06-11 | 2017-12-22 | Devices, methods, and computer-readable media for redemption header for merchant offers |
US15/944,469 Active 2033-06-28 US10586243B2 (en) | 2012-06-11 | 2018-04-03 | Devices, methods, and computer-readable media for redemption header for merchant offers |
US16/219,649 Active US10304074B2 (en) | 2012-06-11 | 2018-12-13 | Devices, methods, and computer-readable media for redemption header for merchant offers |
US16/399,970 Active 2033-12-22 US11321728B2 (en) | 2012-06-11 | 2019-04-30 | Reducing latency in cross-device experiences with caching and hashing |
US16/430,373 Active 2033-07-16 US11151593B2 (en) | 2012-06-11 | 2019-06-03 | Intents for offer-discovery systems |
US16/554,457 Active US10586244B2 (en) | 2012-06-11 | 2019-08-28 | Devices, methods, and computer-readable media for redemption header for merchant offers |
US16/595,283 Active US10915916B2 (en) | 2012-06-11 | 2019-10-07 | Devices, methods and computer-readable media for redemption of merchant offers |
US16/698,132 Active 2033-11-29 US11386446B2 (en) | 2012-06-11 | 2019-11-27 | Devices, methods, and computer-readable media for redemption header for merchant offers |
US16/847,470 Active US11244337B2 (en) | 2012-06-11 | 2020-04-13 | Determining offers for a geofenced geographic area |
US17/141,020 Abandoned US20210125213A1 (en) | 2012-06-11 | 2021-01-04 | Devices, methods, and computer-readable media for redemption of merchant offers |
US17/565,103 Pending US20220122112A1 (en) | 2012-06-11 | 2021-12-29 | Determining offers for a geofenced geographic area |
Country Status (5)
Country | Link |
---|---|
US (19) | US20130332283A1 (en) |
EP (1) | EP2859514A1 (en) |
AU (1) | AU2013274454A1 (en) |
CA (3) | CA2876174A1 (en) |
WO (2) | WO2013188373A1 (en) |
Cited By (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140222561A1 (en) * | 2013-02-04 | 2014-08-07 | Facebook, Inc. | Cross-Platform Advertisement Targeting |
US20140282620A1 (en) * | 2013-03-15 | 2014-09-18 | Frank Settemo NUOVO | System and method for triggering an event in response to receiving a device identifier |
US20150066654A1 (en) * | 2013-08-30 | 2015-03-05 | Linkedin Corporation | Techniques for facilitating content retargeting |
US8984782B1 (en) | 2010-03-16 | 2015-03-24 | Starlite Media, Llc | Shopping cart corrals with at least two advertisement panels arranged in a staggered fashion and method of providing same |
US20150135044A1 (en) * | 2013-11-08 | 2015-05-14 | Sony Computer Entertainment Inc. | Information processing apparatus, information processing method, computer program, and recording medium |
US9138081B1 (en) | 2009-06-24 | 2015-09-22 | Starlite Medite, LLC | Shopping cart corral for displaying one or more advertisements and method of providing same |
USD756461S1 (en) | 2010-03-16 | 2016-05-17 | Starlite Media, Llc | Pair of advertising panels affixed to the entry portion of a shopping cart corral |
US9367859B2 (en) | 2010-03-16 | 2016-06-14 | Starlite Media, Llc | Systems and methods for near field communication enabled shopping cart corrals |
US20160247182A1 (en) * | 2015-02-19 | 2016-08-25 | Target Brands, Inc. | On-line coupon use |
USD786975S1 (en) | 2015-02-27 | 2017-05-16 | Starlite Media, Llc | Pair of advertising panels with triangular marker for shopping cart corral |
USD786974S1 (en) | 2015-02-27 | 2017-05-16 | Starlite Media, Llc | Pair of advertising panels with rounded marker for shopping cart corral |
USD788226S1 (en) | 2015-02-27 | 2017-05-30 | Starlite Media, Llc | Pair of advertising panels with rectangular marker for shopping cart corral |
WO2017106051A1 (en) * | 2015-12-16 | 2017-06-22 | Alibaba Group Holding Limited | Method, system, and device for providing item information |
US20190199657A1 (en) * | 2017-12-13 | 2019-06-27 | Sage Global Services Limited | Chatbot system |
US10467648B1 (en) * | 2017-09-22 | 2019-11-05 | Inmar Clearing, Inc. | Coupon processing system including post-purchase coupon value assignment based upon physical coupon redemption and related methods |
US10475081B1 (en) * | 2017-09-22 | 2019-11-12 | Inmar Clearing, Inc. | Coupon processing system including instant redeemable coupon redemption based upon short message service short code and related methods |
US10592915B2 (en) * | 2013-03-15 | 2020-03-17 | Retailmenot, Inc. | Matching a coupon to a specific product |
US10706462B1 (en) * | 2017-09-22 | 2020-07-07 | Inmar Clearing, Inc. | Coupon processing system communicating digital coupon offer based upon user bid request and related methods |
US11120465B1 (en) * | 2017-01-20 | 2021-09-14 | Walgreen Co. | Omni-channel digital coupon clipping and redemption |
US11176567B1 (en) * | 2017-05-08 | 2021-11-16 | Walgreen Co. | Systems and methods for activating electronic coupons via third-party servers |
US11216865B2 (en) | 2018-03-29 | 2022-01-04 | Christos Parisis | Systems and methods for consumer-oriented behavior predictions and notifications |
US11663655B2 (en) * | 2019-07-03 | 2023-05-30 | Capital One Services, Llc | Augmenting online transaction statements using e-commerce receipts |
Families Citing this family (118)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10360543B2 (en) * | 2012-04-23 | 2019-07-23 | Grubhub Holdings Inc. | Scraping resistant system and method for placing orders through an internet shopping service |
US20130332283A1 (en) | 2012-06-11 | 2013-12-12 | Retailmenot, Inc. | Devices, methods, and computer-readable media for redemption of merchant offers |
US9595049B2 (en) | 2012-06-11 | 2017-03-14 | Retailmenot, Inc. | Cross-device geolocation sensing to geotarget offers |
US10325284B1 (en) * | 2012-06-29 | 2019-06-18 | Groupon, Inc. | Cadence management system for consumer promotions |
US9727891B2 (en) * | 2012-10-22 | 2017-08-08 | Marc Alan Mezzacca | System and method of automated delivery of relevance-checked benefit-conveying codes during online transaction |
US10692104B2 (en) * | 2012-10-30 | 2020-06-23 | Ycs Group, Llc | Managing vendor offers |
US20140129305A1 (en) * | 2012-11-02 | 2014-05-08 | Makeena, LLC | Systems and methods for shopping offer control and feedback |
US20170186027A1 (en) | 2012-11-08 | 2017-06-29 | Honey Science Corporation | Cross-site online shopping assistant |
US10540433B1 (en) * | 2012-12-03 | 2020-01-21 | Amazon Technologies, Inc. | Service for implementing form fields |
US9432806B2 (en) | 2012-12-04 | 2016-08-30 | Ebay Inc. | Dynamic geofence based on members within |
US9519926B2 (en) | 2012-12-05 | 2016-12-13 | Ebay Inc. | Buy now option from map view |
US10083462B2 (en) * | 2012-12-05 | 2018-09-25 | Capital One Services, Llc | Methods and systems for dynamically providing content |
US9449110B2 (en) * | 2013-01-31 | 2016-09-20 | Microsoft Technology Licensing, Llc | Geotiles for finding relevant results from a geographically distributed set |
US20140278948A1 (en) * | 2013-03-14 | 2014-09-18 | Retailmenot, Inc. | Methods and systems for generating electronic deal summary |
US9565139B2 (en) * | 2013-03-15 | 2017-02-07 | Comcast Cable Communications, Llc | Remote latency adjustment |
US9465522B2 (en) * | 2013-03-28 | 2016-10-11 | Linkedin Corporation | Providing a personalized navigation experience in a mobile application |
CN104111944B (en) * | 2013-04-19 | 2018-09-18 | 阿里巴巴集团控股有限公司 | Page processing method and device and page generation method and device |
US9135346B2 (en) * | 2013-06-07 | 2015-09-15 | Google Inc. | Index data for native applications |
US20150073906A1 (en) * | 2013-09-10 | 2015-03-12 | Mastercard International Incorporated | Method and system for optimizing location-based targeted ads served on a moble device |
US9870349B2 (en) | 2013-09-20 | 2018-01-16 | Yottaa Inc. | Systems and methods for managing loading priority or sequencing of fragments of a web object |
US9894476B2 (en) * | 2013-10-02 | 2018-02-13 | Federico Fraccaroli | Method, system and apparatus for location-based machine-assisted interactions |
US10318991B2 (en) * | 2013-10-08 | 2019-06-11 | Paypal, Inc. | Communication device interface for merchant check-in and shopping notifications |
US10134098B2 (en) * | 2013-11-11 | 2018-11-20 | Nomadix, Inc. | Traveler tracking system |
US11386465B1 (en) * | 2013-12-02 | 2022-07-12 | Groupon, Inc. | Method and apparatus for providing promotion vouchers |
US20220398634A1 (en) * | 2013-12-02 | 2022-12-15 | Groupon, Inc. | Method and apparatus for providing promotion vouchers |
US10901765B2 (en) | 2014-01-22 | 2021-01-26 | Nike, Inc. | Systems and methods of socially-driven product offerings |
US20150235268A1 (en) * | 2014-02-14 | 2015-08-20 | Retailmenot, Inc. | Event-based offers for a geofenced geographic area |
US9325654B2 (en) * | 2014-02-28 | 2016-04-26 | Aol Inc. | Systems and methods for optimizing message notification timing based on electronic content consumption associated with a geographic location |
WO2015148213A1 (en) * | 2014-03-22 | 2015-10-01 | Retailmenot, Inc. | Caching geolocated offers |
EP3123431A4 (en) | 2014-03-22 | 2017-08-30 | RetailMeNot, Inc. | Multi-stage geolocated offers |
US10318990B2 (en) * | 2014-04-01 | 2019-06-11 | Ebay Inc. | Selecting users relevant to a geofence |
US11023917B2 (en) | 2014-04-16 | 2021-06-01 | Retailmenot, Inc. | Time period distribution of offer codes |
US20150327061A1 (en) * | 2014-05-09 | 2015-11-12 | Annecto Inc. | System and method for geolocalized social networking |
CA2949348A1 (en) | 2014-05-16 | 2015-11-19 | Cardlytics, Inc. | System and apparatus for identifier matching and management |
US9584968B2 (en) | 2014-05-21 | 2017-02-28 | Aol Inc. | Systems and methods for deploying dynamic geo-fences based on content consumption levels in a geographic location |
DE112015002172T5 (en) * | 2014-06-06 | 2017-01-19 | Aintu Inc. | CROWD SOURCING COUPON INTRODUCTION INFORMATION |
US11477602B2 (en) | 2014-06-10 | 2022-10-18 | Verizon Patent And Licensing Inc. | Systems and methods for optimizing and refining message notification timing |
WO2015200414A1 (en) * | 2014-06-24 | 2015-12-30 | Retailmenot, Inc. | Cross-device geolocation sensing to geotarget offers |
US9646103B2 (en) | 2014-07-10 | 2017-05-09 | MyMojo Corporation | Client-side template engine and method for constructing a nested DOM module for a website |
CN105335423B (en) * | 2014-08-06 | 2020-02-07 | 阿里巴巴集团控股有限公司 | Method and device for collecting and processing user feedback of webpage |
CA2958888C (en) | 2014-08-28 | 2023-02-28 | Retailmenot, Inc. | Reducing the search space for recognition of objects in an image based on wireless signals |
US11113726B1 (en) * | 2014-09-26 | 2021-09-07 | Groupon, Inc. | Methods, apparatuses, and computer program products for providing a platform for negotiation and provision of promotions |
CN105528384B (en) * | 2014-10-27 | 2019-03-15 | 阿里巴巴集团控股有限公司 | The method for pushing and device of information |
US11068921B1 (en) | 2014-11-06 | 2021-07-20 | Capital One Services, Llc | Automated testing of multiple on-line coupons |
US11120461B1 (en) | 2014-11-06 | 2021-09-14 | Capital One Services, Llc | Passive user-generated coupon submission |
US20210019797A1 (en) * | 2015-01-09 | 2021-01-21 | Wells Fargo Bank, N.A. | Systems and methods for on demand and location-based offers |
CN104573025B (en) * | 2015-01-12 | 2018-09-04 | 北京京东尚科信息技术有限公司 | A kind of method and system improving page loading velocity |
CN106162544B (en) * | 2015-04-21 | 2019-09-03 | 阿里巴巴集团控股有限公司 | A kind of generation method and equipment of geography fence |
US11301219B2 (en) | 2015-05-22 | 2022-04-12 | Paypal, Inc. | Hosted sensitive data form fields for compliance with security standards |
US10482083B2 (en) | 2015-10-07 | 2019-11-19 | Capital One Services, Llc | Automated sequential site navigation |
US10210001B2 (en) * | 2015-11-04 | 2019-02-19 | Observepoint, Inc. | Automatic execution of objects in a user interface |
US20170148047A1 (en) * | 2015-11-25 | 2017-05-25 | Jack Desenvolvimento de Sistemas Ltda | Online Coupon Exchange Network |
US10748120B2 (en) * | 2016-01-21 | 2020-08-18 | Terry Lynn Sims | Display board with electronic display and methods for use therewith |
US10853833B2 (en) * | 2016-01-27 | 2020-12-01 | Dell Products, L.P. | System and method for special event high volume commerce experience and deals management |
US10360133B2 (en) | 2016-02-04 | 2019-07-23 | Observepoint Inc. | Analyzing analytic element network traffic |
CN105787755A (en) * | 2016-02-05 | 2016-07-20 | 腾讯科技(深圳)有限公司 | Information processing method, server and first terminal |
GB2561802A (en) | 2016-02-09 | 2018-10-24 | Observepoint Inc | Managing network communication protocols |
US10313351B2 (en) * | 2016-02-22 | 2019-06-04 | At&T Intellectual Property I, L.P. | Dynamic passcodes in association with a wireless access point |
US10643231B1 (en) | 2016-04-28 | 2020-05-05 | Wells Fargo Bank, N.A. | Incentives for physical activity |
CN106294648B (en) * | 2016-08-03 | 2021-07-27 | 腾讯科技(深圳)有限公司 | Processing method and device for page access path |
CN106294839B (en) * | 2016-08-20 | 2019-09-27 | 北京云艾科技有限公司 | A kind of link jump method and device |
US11157941B2 (en) * | 2016-09-08 | 2021-10-26 | International Business Machines Corporation | Adaptive coupon rendering based on shaking of emotion-expressing mobile device |
WO2018064294A1 (en) * | 2016-09-28 | 2018-04-05 | Michael John Wakerly | Mobile web browser providing contextual actions based on web page content |
WO2018071795A1 (en) | 2016-10-13 | 2018-04-19 | Rise Interactive Media & Analytics, LLC | Interactive data-driven graphical user interface for cross-channel web site performance |
US10417663B2 (en) | 2016-10-28 | 2019-09-17 | International Busienss Machines Corporation | Ephemeral geofence campaign system |
US9736636B1 (en) | 2016-10-28 | 2017-08-15 | International Business Machines Corporation | Geofence prioritization |
WO2019147351A1 (en) * | 2017-12-11 | 2019-08-01 | Dosh Holdings, Inc. | Matching offers transactions across heterogeneous, multi-entity distributed computing platforms and settlement |
US11538052B1 (en) | 2016-12-12 | 2022-12-27 | Dosh Holdings, Inc. | System for generating and tracking offers chain of titles |
US11526881B1 (en) | 2016-12-12 | 2022-12-13 | Dosh Holdings, Inc. | System for generating and tracking offers chain of titles |
US11488190B1 (en) | 2016-12-12 | 2022-11-01 | Dosh, Llc | System for sharing and transferring currency |
US11551249B1 (en) | 2016-12-12 | 2023-01-10 | Dosh Holdings, Inc. | System for identifying and applying offers to user transactions |
US9924315B1 (en) | 2017-01-03 | 2018-03-20 | International Business Machines Corporation | Dynamic geofence |
US9820097B1 (en) | 2017-01-05 | 2017-11-14 | International Business Machines Corporation | Geofence location detection |
US20180197220A1 (en) * | 2017-01-06 | 2018-07-12 | Dragon-Click Corp. | System and method of image-based product genre identification |
CN107146099B (en) * | 2017-04-14 | 2021-05-25 | 北京楚科信息技术有限公司 | Marketing method and marketing system |
WO2018217736A1 (en) * | 2017-05-22 | 2018-11-29 | Avis Budget Car Rental, LLC | Connected driver communications system and platform |
US11205188B1 (en) | 2017-06-07 | 2021-12-21 | Capital One Services, Llc | Automatically presenting e-commerce offers based on browse history |
WO2018226951A1 (en) | 2017-06-09 | 2018-12-13 | Walmart Apollo, Llc | Systems and methods for providing location-based time-limited services |
US11023345B1 (en) * | 2017-07-28 | 2021-06-01 | Groupon, Inc. | System and apparatus for automated evaluation of compatibility of data structures and user devices based on explicit user feedback |
US10171940B1 (en) | 2017-09-07 | 2019-01-01 | International Business Machines Corporation | Transportation activated geofence |
US11574322B2 (en) | 2017-10-19 | 2023-02-07 | Meta Platforms, Inc. | Identifying a location based on expected differences between online system users expected to be at the location and online system users previously at the location |
US11900928B2 (en) * | 2017-12-23 | 2024-02-13 | Soundhound Ai Ip, Llc | System and method for adapted interactive experiences |
US11461796B1 (en) | 2018-01-29 | 2022-10-04 | Wells Fargo Bank, N.A. | Systems and methods for multiple offer source aggregator |
US11206273B2 (en) * | 2018-01-31 | 2021-12-21 | Salesforce.Com, Inc. | Content management system connect |
JP6774448B2 (en) * | 2018-02-14 | 2020-10-21 | 日本電信電話株式会社 | Distributed device management system and distributed device management method |
US10706450B1 (en) | 2018-02-14 | 2020-07-07 | Amazon Technologies, Inc. | Artificial intelligence system for generating intent-aware recommendations |
US10783516B2 (en) | 2018-04-11 | 2020-09-22 | Capital One Services, Llc | Systems and methods for automatically identifying a checkout webpage and injecting a virtual token |
US20190340606A1 (en) * | 2018-05-07 | 2019-11-07 | Capital One Services, Llc | Merchant quality ratings in a financial computer network |
US11195205B2 (en) * | 2018-06-12 | 2021-12-07 | Capital One Services, Llc | Systems and methods for processing and providing transaction affinity profile information |
WO2020023563A1 (en) * | 2018-07-24 | 2020-01-30 | John Bruno | Geographical merchant consortium commerce system for contextual commerce |
CN109409954A (en) * | 2018-10-23 | 2019-03-01 | 广州逗号智能零售有限公司 | A kind of discount coupon methods of exhibiting and device |
US11115479B2 (en) * | 2019-01-10 | 2021-09-07 | Google Llc | Enhanced online privacy |
CN109993583B (en) * | 2019-04-02 | 2021-07-27 | 深圳市腾讯信息技术有限公司 | Information pushing method and device, storage medium and electronic device |
US11282103B2 (en) * | 2019-04-15 | 2022-03-22 | American Express Travel Related Services Company, Inc. | Automated transactional offers using a browser extension |
US11250462B2 (en) | 2019-04-18 | 2022-02-15 | Benjamin D. Smith | System and method for trading and tracking digitized coupons |
US11184447B2 (en) * | 2019-05-14 | 2021-11-23 | Swiftly Systems, Inc. | Systems and methods for efficient transmission of catalog data |
US11531952B1 (en) * | 2019-07-31 | 2022-12-20 | United Services Automobile Association (Usaa) | Secure and anonymized digital transactions |
EP3825946A1 (en) * | 2019-11-22 | 2021-05-26 | Amadeus S.A.S. | System and method for multi-stage generation of responses to data requests |
WO2021118133A1 (en) * | 2019-12-11 | 2021-06-17 | Samsung Electronics Co., Ltd. | Method and apparatus for providing machine learning-based recommendations in blockchain network |
US11227316B2 (en) * | 2020-01-23 | 2022-01-18 | Capital One Services, Llc | Vendor recommendation platform |
US11755720B2 (en) | 2020-01-31 | 2023-09-12 | Salesforce, Inc. | Secure membranes and cross namespace communication |
US11805160B2 (en) | 2020-03-23 | 2023-10-31 | Rovi Guides, Inc. | Systems and methods for concurrent content presentation |
US11057381B1 (en) * | 2020-04-29 | 2021-07-06 | Snowflake Inc. | Using remotely stored credentials to access external resources |
US10990253B1 (en) | 2020-05-26 | 2021-04-27 | Bank Of America Corporation | Predictive navigation and fields platform to reduce processor and network resources usage |
US11790364B2 (en) | 2020-06-26 | 2023-10-17 | Rovi Guides, Inc. | Systems and methods for providing multi-factor authentication for vehicle transactions |
US11599880B2 (en) | 2020-06-26 | 2023-03-07 | Rovi Guides, Inc. | Systems and methods for providing multi-factor authentication for vehicle transactions |
CN111800890B (en) * | 2020-06-30 | 2023-09-19 | 联想(北京)有限公司 | Processing method and input device |
IT202000016243A1 (en) | 2020-07-06 | 2022-01-06 | Webravo S R L | METHOD FOR MANAGING TRANSACTIONS IN ELECTRONIC COMMERCE SITES |
WO2022040776A1 (en) * | 2020-08-27 | 2022-03-03 | App-Pop-Up Inc. | A system for providing a mobile device with remote or proxy access to merchant aprs and/or automatic registration on merchant aprs based on location parameters |
US11729247B2 (en) | 2020-09-24 | 2023-08-15 | Capital One Services, Llc | Systems and methods for decentralized detection of software platforms operating on website pages |
US11770375B2 (en) * | 2020-11-12 | 2023-09-26 | Kindli, Inc. | Methods and apparatus for communication |
US11409829B2 (en) | 2020-12-21 | 2022-08-09 | Capital One Services, Llc | Methods and systems for redirecting a user from a third party website to a provider website |
US11477043B2 (en) * | 2021-03-17 | 2022-10-18 | Lenovo (Singapore) Pte. Ltd. | Method and device to manage browser instances based on link categorization |
WO2023287445A1 (en) * | 2021-07-12 | 2023-01-19 | Capital One Services, Llc | Methods and systems for automatic product comparison |
US11562416B1 (en) | 2021-07-12 | 2023-01-24 | Capital One Services, Llc | Methods and systems for automatic product comparison |
US11790388B2 (en) * | 2021-09-30 | 2023-10-17 | Rakuten Group, Inc. | System, method, and computer program for automatic coupon code fill in a mobile application |
US11915286B1 (en) * | 2021-12-09 | 2024-02-27 | Amazon Technologies, Inc. | Systems and method for attributing transactions from multiple websites to content producers |
CN115760234B (en) * | 2022-11-25 | 2023-08-25 | 中电金信软件有限公司 | Third party rights exchange method and device, electronic equipment and readable storage medium |
Family Cites Families (196)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030177347A1 (en) | 1995-11-22 | 2003-09-18 | Bruce Schneier | Methods and apparatus for awarding prizes based on authentication of computer generated outcomes using coupons |
US5970469A (en) * | 1995-12-26 | 1999-10-19 | Supermarkets Online, Inc. | System and method for providing shopping aids and incentives to customers through a computer network |
US6932270B1 (en) * | 1997-10-27 | 2005-08-23 | Peter W. Fajkowski | Method and apparatus for coupon management and redemption |
US6548967B1 (en) | 1997-08-26 | 2003-04-15 | Color Kinetics, Inc. | Universal lighting network methods and systems |
US6433801B1 (en) | 1997-09-26 | 2002-08-13 | Ericsson Inc. | Method and apparatus for using a touch screen display on a portable intelligent communications device |
US6758391B1 (en) * | 1997-11-18 | 2004-07-06 | The Code Corporation | Internet access of goods and services using graphical codes |
US7240021B1 (en) * | 1998-03-27 | 2007-07-03 | Walker Digital, Llc | System and method for tracking and establishing a progressive discount based upon a customer's visits to a retail establishment |
US7302402B2 (en) | 1998-03-30 | 2007-11-27 | International Business Machines Corporation | Method, system and program products for sharing state information across domains |
US20020010623A1 (en) | 1998-09-08 | 2002-01-24 | Hewlett-Packard Company | System and method for publishing, distributing and redeeming coupons on a network |
WO2000041121A1 (en) | 1999-01-07 | 2000-07-13 | Ccrewards.Com | Method and arrangement for issuance and management of digital coupons and sales offers |
US7953671B2 (en) | 1999-08-31 | 2011-05-31 | American Express Travel Related Services Company, Inc. | Methods and apparatus for conducting electronic transactions |
JP2003527627A (en) * | 1999-12-02 | 2003-09-16 | ゼド インコーポレイテッド | Data processing system for targeted content |
US20040078273A1 (en) * | 1999-12-08 | 2004-04-22 | Loeb Michael R. | Method and apparatus for relational linking based upon customer activities |
US20020010627A1 (en) | 2000-05-17 | 2002-01-24 | Gilles Lerat | System and method for creation, distribution, exchange, redemption and tracking of digitally signed electronic coupons |
US20080162298A1 (en) | 2000-06-15 | 2008-07-03 | American Express Travel Related Services Company, Inc. | Online ordering system and method |
US20020046109A1 (en) | 2000-07-24 | 2002-04-18 | Huw Leonard | Method and system for administering a customer loyalty reward program using a browser extension |
US6754662B1 (en) * | 2000-08-01 | 2004-06-22 | Nortel Networks Limited | Method and apparatus for fast and consistent packet classification via efficient hash-caching |
US7143143B1 (en) * | 2000-10-27 | 2006-11-28 | Microsoft Corporation | System and method for distributed caching using multicast replication |
US20020065713A1 (en) * | 2000-11-29 | 2002-05-30 | Awada Faisal M. | Coupon delivery via mobile phone based on location |
US20020165766A1 (en) | 2000-12-06 | 2002-11-07 | Enclip Inc., | System and method for informing end user of electronic coupons |
US7725350B2 (en) * | 2001-02-05 | 2010-05-25 | Daniel R. Schlee | Promotional data delivery system and method |
US20020107732A1 (en) | 2001-02-08 | 2002-08-08 | Boies Stephen J. | System and method for providing a consumer aggregation service |
US20030004802A1 (en) * | 2001-03-19 | 2003-01-02 | Jeff Callegari | Methods for providing a virtual coupon |
US20030074206A1 (en) * | 2001-03-23 | 2003-04-17 | Restaurant Services, Inc. | System, method and computer program product for utilizing market demand information for generating revenue |
IL142815A (en) * | 2001-04-25 | 2010-06-16 | Gal Trifon | Method for dynamically changing one web page by another web page |
US7302696B1 (en) | 2001-05-24 | 2007-11-27 | Digeo, Inc. | System and method to provide an interactive coupon channel a video casting network |
US8375411B2 (en) | 2001-06-27 | 2013-02-12 | Nokia Corporation | Cross-device sharing of reminders |
US7233933B2 (en) | 2001-06-28 | 2007-06-19 | Microsoft Corporation | Methods and architecture for cross-device activity monitoring, reasoning, and visualization for providing status and forecasts of a users' presence and availability |
US20030023482A1 (en) * | 2001-07-25 | 2003-01-30 | Messner Amy E. | Method and apparatus for redeeming of coupons via a wireless communication device |
WO2003017136A1 (en) * | 2001-08-16 | 2003-02-27 | Etagon Israel Ltd. | Using associative memory to perform database operations |
US6993596B2 (en) | 2001-12-19 | 2006-01-31 | International Business Machines Corporation | System and method for user enrollment in an e-community |
US7359976B2 (en) * | 2002-11-23 | 2008-04-15 | Microsoft Corporation | Method and system for improved internet security via HTTP-only cookies |
US20040133635A1 (en) | 2002-11-26 | 2004-07-08 | Axel Spriestersbach | Transformation of web description documents |
US20040210536A1 (en) | 2002-12-18 | 2004-10-21 | Tino Gudelj | Cross-domain transactions through simulated pop-ups |
US20040243519A1 (en) | 2003-06-02 | 2004-12-02 | Nokia Corporation | Prompted electronic mobile-service information communications with validation |
US7831693B2 (en) * | 2003-08-18 | 2010-11-09 | Oracle America, Inc. | Structured methodology and design patterns for web services |
US20060004631A1 (en) * | 2003-09-11 | 2006-01-05 | Roberts Gregory B | Method and system for generating real-time directions associated with product promotions |
US20050197893A1 (en) | 2004-02-24 | 2005-09-08 | Michael Landau | Coupon, price-comparison, and product-review information toolbar for use with a network browser or system/application interface |
US20050209996A1 (en) | 2004-03-17 | 2005-09-22 | Stewart Kelsey B | System and method for developing and implementing on-line marketing techniques |
CN101023419B (en) | 2004-05-14 | 2010-06-16 | 模比莱普斯有限公司 | Method of providing a web page with inserted content |
US8280819B2 (en) * | 2004-07-09 | 2012-10-02 | Ebay Inc. | Method and apparatus for securely displaying and communicating trusted and untrusted internet content |
US8015184B2 (en) | 2004-10-26 | 2011-09-06 | Yahoo! Inc. | Method and apparatus for a search-enabled remote control device |
US7461338B2 (en) * | 2005-01-07 | 2008-12-02 | Essociate, Inc. | Advertising markup language |
US8473334B2 (en) * | 2005-03-10 | 2013-06-25 | Sony Corporation | System and method for issuing and redeeming incentives on electronic data cards |
US7848765B2 (en) * | 2005-05-27 | 2010-12-07 | Where, Inc. | Location-based services |
US8732653B1 (en) | 2005-09-05 | 2014-05-20 | Yongyong Xu | System and method of providing resource modification in a virtual community |
US9201979B2 (en) * | 2005-09-14 | 2015-12-01 | Millennial Media, Inc. | Syndication of a behavioral profile associated with an availability condition using a monetization platform |
US8660891B2 (en) * | 2005-11-01 | 2014-02-25 | Millennial Media | Interactive mobile advertisement banners |
US20070073580A1 (en) | 2005-09-23 | 2007-03-29 | Redcarpet, Inc. | Method and system for delivering online sales promotions |
US20070162337A1 (en) * | 2005-11-18 | 2007-07-12 | Gary Hawkins | Method and system for distributing and redeeming targeted offers to customers |
US20070130000A1 (en) * | 2005-11-18 | 2007-06-07 | Ayman Assanassios | Marketing and rewards system and method |
US20070174116A1 (en) | 2006-01-23 | 2007-07-26 | Keith Chad C | Electronic coupon systems and methods to operate the same |
US7861176B2 (en) * | 2006-04-13 | 2010-12-28 | Touchcommerce, Inc. | Methods and systems for providing online chat |
US20070244746A1 (en) | 2006-04-18 | 2007-10-18 | Issen Daniel A | Correlating an advertisement click event with a purchase event |
US7783719B2 (en) | 2006-05-04 | 2010-08-24 | Jonathan Bernadotte Miller | Method of and system for crediting an online publisher in an affiliate marketing relationship |
US8559968B2 (en) * | 2006-05-12 | 2013-10-15 | At&T Intellectual Property I, L.P. | Location-based targeting |
US20080021771A1 (en) | 2006-05-31 | 2008-01-24 | Ling Wu | Systems and methods for defining pricing conditions in electronic sales application environments |
US8738441B2 (en) * | 2006-06-12 | 2014-05-27 | Zadspace, Inc. | Parcel advertising system and method |
US7860751B2 (en) * | 2006-06-27 | 2010-12-28 | Google Inc. | Cross domain customer interface updates |
US20080086524A1 (en) * | 2006-08-18 | 2008-04-10 | Akamai Technologies, Inc. | Method and system for identifying valid users operating across a distributed network |
US8694364B2 (en) * | 2006-08-23 | 2014-04-08 | The Retail Equation, Inc. | Return coupon holder |
US7818216B2 (en) * | 2006-08-28 | 2010-10-19 | Seraphim Lawhorn | Transaction system with centralized data storage and authentication |
EP2126815A4 (en) | 2006-09-13 | 2011-09-21 | Tdp Inc | Integrated system and method for managing electronic coupons |
US20100095220A1 (en) | 2006-09-28 | 2010-04-15 | Mobilaps Llc | Methods and systems for providing a mini-webpage within a webpage |
US8868740B2 (en) | 2006-09-29 | 2014-10-21 | Nomadix, Inc. | Systems and methods for injecting content |
US8700449B2 (en) | 2006-10-30 | 2014-04-15 | Maxlinear, Inc. | Targeted advertisement in the digital television environment |
US8209615B2 (en) | 2006-11-22 | 2012-06-26 | Qualcomm Incorporated | Apparatus and methods of linking to an application on a wireless device |
US9043222B1 (en) * | 2006-11-30 | 2015-05-26 | NexRf Corporation | User interface for geofence associated content |
US8230320B2 (en) | 2006-12-26 | 2012-07-24 | International Business Machines Corporation | Method and system for social bookmarking of resources exposed in web pages that don't follow the representational state transfer architectural style (REST) |
KR100837166B1 (en) | 2007-01-20 | 2008-06-11 | 엘지전자 주식회사 | Method of displaying an information in electronic device and the electronic device thereof |
US20080228568A1 (en) | 2007-03-16 | 2008-09-18 | Microsoft Corporation | Delivery of coupons through advertisement |
US20080255889A1 (en) | 2007-04-02 | 2008-10-16 | Dan Geisler | System and method for ticket selection and transactions |
WO2008147913A2 (en) | 2007-05-22 | 2008-12-04 | Vidsys, Inc. | Tracking people and objects using multiple live and recorded surveillance camera video feeds |
US10019570B2 (en) * | 2007-06-14 | 2018-07-10 | Microsoft Technology Licensing, Llc | Protection and communication abstractions for web browsers |
US20090030794A1 (en) | 2007-07-23 | 2009-01-29 | One On One Ads, Inc. | Online marketing tool using videos to promote printable coupons |
US20090037517A1 (en) * | 2007-08-02 | 2009-02-05 | Randall Wayne Frei | Method and system to share content between web clients |
AU2012200475B2 (en) | 2007-09-04 | 2015-09-03 | Apple Inc. | Portable multifunction device with interface reconfiguration mode |
US9619143B2 (en) | 2008-01-06 | 2017-04-11 | Apple Inc. | Device, method, and graphical user interface for viewing application launch icons |
US9898753B2 (en) | 2007-09-27 | 2018-02-20 | Excalibur Ip, Llc | Methods for cross-market brand advertising, content metric analysis, and placement recommendations |
US20090106296A1 (en) | 2007-10-19 | 2009-04-23 | Career Liaison, Llc | Method and system for automated form aggregation |
US9015692B1 (en) | 2007-10-23 | 2015-04-21 | Phunware, Inc. | Method and system for customizing content on a server for rendering on a wireless device |
US20090119172A1 (en) * | 2007-11-02 | 2009-05-07 | Soloff David L | Advertising Futures Marketplace Methods and Systems |
US20090198580A1 (en) | 2008-01-31 | 2009-08-06 | Horizon Capital Securities Limited | Distribution and Targeting of Advertising for Mobile Devices |
US20090248505A1 (en) | 2008-03-28 | 2009-10-01 | Microsoft Corporation | User-controlled profile for customized advertisements |
US11729576B2 (en) * | 2008-03-29 | 2023-08-15 | NEXRF Corp. | Targeted content delivery |
US9972020B1 (en) | 2008-04-11 | 2018-05-15 | United Services Automobile Association (Usaa) | Targeted, competitive offers while browsing |
US20090259535A1 (en) | 2008-04-11 | 2009-10-15 | Yahoo! Inc. | Coupon clipper |
US20090271690A1 (en) * | 2008-04-28 | 2009-10-29 | Yahoo! Inc. | Handling cross-domain web service calls |
US20090276701A1 (en) | 2008-04-30 | 2009-11-05 | Nokia Corporation | Apparatus, method and computer program product for facilitating drag-and-drop of an object |
US20090286544A1 (en) * | 2008-05-13 | 2009-11-19 | At&T Mobility Ii Llc | Administration of an access control list to femto cell coverage |
WO2009143084A1 (en) * | 2008-05-18 | 2009-11-26 | Zetawire, Inc. | Secured electronic transaction system |
US8209706B2 (en) * | 2008-06-27 | 2012-06-26 | Microsoft Corporation | Inter-frame messaging between different domains |
US7867852B2 (en) | 2008-08-08 | 2011-01-11 | Alpha And Omega Semiconductor Incorporated | Super-self-aligned trench-dmos structure and method |
US20100042517A1 (en) * | 2008-08-12 | 2010-02-18 | The Westem Union Company | Universal loyalty systems and methods |
US8438310B2 (en) * | 2008-10-01 | 2013-05-07 | Adp Dealer Services, Inc. | Systems and methods for configuring a website having a plurality of operational modes |
US9875477B2 (en) | 2008-10-08 | 2018-01-23 | Keep Holdings, Inc. | Managing internet advertising and promotional content |
US20110197237A1 (en) | 2008-10-10 | 2011-08-11 | Turner Steven E | Controlled Delivery of Content Data Streams to Remote Users |
US20100121710A1 (en) * | 2008-11-13 | 2010-05-13 | Spreezio, Inc. | System and method for location-based online shopping and just-in-time advertising |
US20100250653A1 (en) * | 2009-01-29 | 2010-09-30 | Brandon Hudgeons | Method and system for providing cross-domain communication |
US7984170B1 (en) * | 2009-01-29 | 2011-07-19 | Amazon Technologies, Inc. | Cross-domain communication in domain-restricted communication environments |
US7870482B2 (en) | 2009-01-30 | 2011-01-11 | International Business Machines Corporation | Web browser extension for simplified utilization of web services |
US8332270B2 (en) | 2009-02-19 | 2012-12-11 | Qualcomm Incorporated | System and method for utilizing a wireless communications device |
GB0902834D0 (en) | 2009-02-19 | 2009-04-08 | Aceplan Invest Ltd | Content access platform and methods and apparatus providing access to internet content for heterogeneous devices |
US20100228594A1 (en) * | 2009-03-04 | 2010-09-09 | Mark Chweh | Advertising and promotional system |
US8271868B2 (en) * | 2009-03-25 | 2012-09-18 | Microsoft Corporation | Inserting web content into a destination website |
US8799060B2 (en) | 2009-03-30 | 2014-08-05 | Transactis, Inc | Method for electronic coupon creation, deployment, transference, validation management, clearance, redemption and reporting system and and method for interactive participation of individuals and groups with coupons |
US8572675B2 (en) * | 2009-04-03 | 2013-10-29 | The Boeing Company | System and method for facilitating the provision of web services across different internet security domains |
US8650072B2 (en) | 2009-05-05 | 2014-02-11 | Groupon, Inc. | System and methods for providing location based discount retailing |
US9240015B2 (en) | 2009-05-08 | 2016-01-19 | A2Zlogix, Inc. | Method and system for synchronizing delivery of promotional material to computing devices |
US20100313252A1 (en) | 2009-06-08 | 2010-12-09 | Erie Trouw | System, method and apparatus for creating and using a virtual layer within a web browsing environment |
US9754274B1 (en) | 2009-06-09 | 2017-09-05 | Monetate, Inc. | Single tag method for webpage personal customization |
US8332763B2 (en) * | 2009-06-09 | 2012-12-11 | Microsoft Corporation | Aggregating dynamic visual content |
US20110022312A1 (en) * | 2009-07-23 | 2011-01-27 | Fmr Llc | Generating and Tracking Activity Patterns for Mobile Devices |
US10423967B2 (en) * | 2009-07-28 | 2019-09-24 | Oohdoo, Inc. | System and method for providing advertising content via mobile device docking station |
AU2009217429B2 (en) | 2009-08-07 | 2015-08-13 | Retailmenot, Inc. | Method and system for facilitating access to a promotional offer |
US20110040875A1 (en) | 2009-08-14 | 2011-02-17 | Martin Scholz | System And Method For Inter-domain Information Transfer |
US20110047017A1 (en) | 2009-08-21 | 2011-02-24 | Valassis Communications, Inc. | Offer Management Method And System |
US8266714B2 (en) * | 2009-08-28 | 2012-09-11 | Microsoft Corporation | Access control in a multi-principal browser |
US20110060652A1 (en) * | 2009-09-10 | 2011-03-10 | Morton Timothy B | System and method for the service of advertising content to a consumer based on the detection of zone events in a retail environment |
US20110137732A1 (en) * | 2009-09-17 | 2011-06-09 | Airnet Group. Inc. | Broadcast messaging and feedback communications apparatus and method |
US9049258B2 (en) | 2009-09-17 | 2015-06-02 | Border Stylo, LLC | Systems and methods for anchoring content objects to structured documents |
US20110093515A1 (en) * | 2009-10-15 | 2011-04-21 | Mary Elizabeth Albanese | Mobile local search platform |
US9092783B2 (en) * | 2009-10-16 | 2015-07-28 | Microsoft Technology Licensing, Llc | Viral distribution and tracking of electronic coupons |
US20110106599A1 (en) | 2009-10-29 | 2011-05-05 | Mccann Monica Theresa | Providing Digital Coupons for Third Party Network Sites |
US20110125581A1 (en) * | 2009-11-23 | 2011-05-26 | Reza Jalili | System and method for improving e-commerce with on-demand advertising |
US8458765B2 (en) | 2009-12-07 | 2013-06-04 | Samsung Electronics Co., Ltd. | Browser security standards via access control |
AU2010100229B4 (en) | 2009-12-17 | 2010-07-01 | Internet Brands, Inc. | Tool, method and system for testing of a redemption-value activator |
US8521758B2 (en) * | 2010-01-15 | 2013-08-27 | Salesforce.Com, Inc. | System and method of matching and merging records |
US20110191160A1 (en) | 2010-01-29 | 2011-08-04 | Bank Of America Corporation | Mobile payment device for conducting transactions associated with a merchant offer program |
KR20130009754A (en) | 2010-02-01 | 2013-01-23 | 점프탭, 인크. | Integrated advertising system |
US20110010235A1 (en) | 2010-02-04 | 2011-01-13 | CouponCabin, Inc. | Method and System for Setting an Online Coupon Cookie |
AU2011213606B2 (en) * | 2010-02-08 | 2014-04-17 | Facebook, Inc. | Communicating information in a social network system about activities from another domain |
US8775245B2 (en) | 2010-02-11 | 2014-07-08 | News America Marketing Properties, Llc | Secure coupon distribution |
US20110208797A1 (en) * | 2010-02-22 | 2011-08-25 | Full Armor Corporation | Geolocation-Based Management of Virtual Applications |
US20110208575A1 (en) * | 2010-02-23 | 2011-08-25 | Yahoo! Inc. | System and method for generating interactive advertisements |
EP2369546A1 (en) | 2010-03-01 | 2011-09-28 | Coupies GmbH | System and method for providing electronic coupons |
US20110225495A1 (en) * | 2010-03-12 | 2011-09-15 | Salesforce.Com, Inc. | Service Cloud Console |
US9681359B2 (en) | 2010-03-23 | 2017-06-13 | Amazon Technologies, Inc. | Transaction completion based on geolocation arrival |
WO2011123577A2 (en) | 2010-03-31 | 2011-10-06 | Phunware Inc. | Methods and systems for interactive user interface objects |
US8332517B2 (en) | 2010-03-31 | 2012-12-11 | Incnetworks, Inc. | Method, computer program, and algorithm for computing network service value pricing based on communication service experiences delivered to consumers and merchants over a smart multi-services (SMS) communication network |
US20110251897A1 (en) | 2010-04-12 | 2011-10-13 | The Associated Press | Online Shopping Circulars |
US20110270690A1 (en) | 2010-04-30 | 2011-11-03 | Research In Motion Limited | Remote Management of Mobile Advertising Application |
US20110270667A1 (en) | 2010-04-30 | 2011-11-03 | CouponCabin, Inc. | Method and System for Customer Registration and Discount Distribution in an Affiliate Network |
US20110288917A1 (en) | 2010-05-21 | 2011-11-24 | James Wanek | Systems and methods for providing mobile targeted advertisements |
US8364959B2 (en) * | 2010-05-26 | 2013-01-29 | Google Inc. | Systems and methods for using a domain-specific security sandbox to facilitate secure transactions |
CA2745536A1 (en) | 2010-07-06 | 2012-01-06 | Omar M. Sheikh | Improving the relevancy of advertising material through user-defined preference filters, location and permission information |
US20120010938A1 (en) | 2010-07-10 | 2012-01-12 | Bazomb, Inc. | Geographically defined electronic coupon or voucher dissemination |
US20120029998A1 (en) * | 2010-07-30 | 2012-02-02 | News America Marketing Properties, Llc | Promotional content and coupon delivery |
US9225510B1 (en) | 2010-08-17 | 2015-12-29 | Go Daddy Operating Company, LLC | Website secure certificate status determination via partner browser plugin |
US9443257B2 (en) * | 2010-10-21 | 2016-09-13 | Yahoo! Inc. | Securing expandable display advertisements in a display advertising environment |
US9558502B2 (en) | 2010-11-04 | 2017-01-31 | Visa International Service Association | Systems and methods to reward user interactions |
US20120116859A1 (en) | 2010-11-05 | 2012-05-10 | CouponCabin, Inc. | Method and System for Point of Sale Online Coupon Management |
US8396485B2 (en) | 2010-11-09 | 2013-03-12 | Apple Inc. | Beacon-based geofencing |
US9117226B2 (en) | 2010-12-02 | 2015-08-25 | Oncard Marketing, Inc. | System and method for delivering an authorized in-store promotion to a consumer |
US9147196B2 (en) | 2010-12-02 | 2015-09-29 | Oncard Marketing, Inc. | System and method for delivering a restricted use in-store promotion to a consumer |
US20120143720A1 (en) | 2010-12-07 | 2012-06-07 | Martin Moser | Location based mobile shopping |
US20120166268A1 (en) | 2010-12-23 | 2012-06-28 | Exclusive Concepts | Time to buy |
US10235688B2 (en) * | 2010-12-24 | 2019-03-19 | First Data Corporation | Web and mobile device advertising |
WO2012109628A2 (en) | 2011-02-10 | 2012-08-16 | Visa International Service Assocation | Electronic coupon issuance and redemption apparatuses, methods and systems |
US9002727B2 (en) | 2011-02-14 | 2015-04-07 | Coupons.Com Incorporated | Identifier-based coupon distribution |
US20120220277A1 (en) | 2011-02-27 | 2012-08-30 | David Gonynor | Promotion management system and smartphone application |
US8978106B2 (en) | 2011-03-21 | 2015-03-10 | Microsoft Technology Licensing, Llc | Programming, verifying, visualizing, and deploying browser extensions with fine-grained security policies |
US20130006727A1 (en) | 2011-03-25 | 2013-01-03 | Black Drumm, Inc. | Systems and methods for social filtering of geobookmarks |
US20170148046A1 (en) | 2011-03-31 | 2017-05-25 | Mavatar Technologies, Inc. | System and method for consumer management purchasing and account information |
US20120266079A1 (en) | 2011-04-18 | 2012-10-18 | Mark Lee | Usability of cross-device user interfaces |
US9037963B1 (en) | 2011-04-22 | 2015-05-19 | Amazon Technologies, Inc. | Secure cross-domain web browser communications |
US20120284107A1 (en) | 2011-05-03 | 2012-11-08 | Russell Gernaat | Digital coupon clearinghouse |
WO2012154440A2 (en) * | 2011-05-06 | 2012-11-15 | Evans Michael Shepherd | System and method for including advertisements in electronic communications |
US20120290383A1 (en) * | 2011-05-15 | 2012-11-15 | James David Busch | Systems and Methods to Advertise a Physical Business Location with Digital Location-Based Coupons |
US9723459B2 (en) | 2011-05-18 | 2017-08-01 | Microsoft Technology Licensing, Llc | Delayed and time-space bound notifications |
US9965768B1 (en) * | 2011-05-19 | 2018-05-08 | Amazon Technologies, Inc. | Location-based mobile advertising |
US9747646B2 (en) | 2011-05-26 | 2017-08-29 | Facebook, Inc. | Social data inputs |
CN103797500A (en) | 2011-06-03 | 2014-05-14 | 维萨国际服务协会 | Virtual wallet card selection apparatuses, methods and systems |
US20130024262A1 (en) * | 2011-06-23 | 2013-01-24 | Savingstar | Systems and methods for electronic coupon targeting |
US20130041737A1 (en) | 2011-08-11 | 2013-02-14 | Rajeev Mishra | Electronic coupon system and method |
US10559000B2 (en) * | 2011-08-19 | 2020-02-11 | Google Llc | Advertiser campaign script execution management |
WO2013043867A2 (en) * | 2011-09-21 | 2013-03-28 | Jeff Thramann | Electric vehicle charging station with connectivity to mobile devices to provide local information |
US20130085861A1 (en) * | 2011-09-30 | 2013-04-04 | Scott Dunlap | Persistent location tracking on mobile devices and location profiling |
US20130117646A1 (en) | 2011-11-08 | 2013-05-09 | RevTrax | System and method for delivering and activating a virtual gift card |
US9002395B2 (en) * | 2011-11-21 | 2015-04-07 | Richard Krukar | Message subscription, generation, and delivery with dynamic zones |
US9679296B2 (en) | 2011-11-30 | 2017-06-13 | Retailmenot, Inc. | Promotion code validation apparatus and method |
US20130188217A1 (en) | 2012-01-20 | 2013-07-25 | Couponcabin Llc | System and method for online coupon printing |
US8799988B2 (en) | 2012-01-25 | 2014-08-05 | Microsoft Corporation | Document communication runtime interfaces |
US10157388B2 (en) * | 2012-02-22 | 2018-12-18 | Oracle International Corporation | Generating promotions to a targeted audience |
CA2868192A1 (en) | 2012-03-23 | 2013-09-26 | Digital Retail Apps., Inc. | System and method for facilitating secure self payment transactions of retail goods |
US20130262203A1 (en) | 2012-03-27 | 2013-10-03 | Sirqul, Inc. | Location-based task and game functionality |
US20130282533A1 (en) * | 2012-04-18 | 2013-10-24 | Elizabeth Foran-Owens | Providing an online consumer shopping experience in-store |
US9116818B2 (en) * | 2012-05-31 | 2015-08-25 | Qualcomm Incorporated | Methods and systems for retrieving and caching geofence data |
US20130332283A1 (en) | 2012-06-11 | 2013-12-12 | Retailmenot, Inc. | Devices, methods, and computer-readable media for redemption of merchant offers |
US9727891B2 (en) | 2012-10-22 | 2017-08-08 | Marc Alan Mezzacca | System and method of automated delivery of relevance-checked benefit-conveying codes during online transaction |
US9922327B2 (en) | 2012-11-01 | 2018-03-20 | Ebates Inc. | System, method, and computer program for providing a multi-merchant electronic shopping cart for a shopping service |
US9549286B2 (en) * | 2013-02-22 | 2017-01-17 | Intel Corporation | Geo-fence notification management |
WO2017061558A1 (en) * | 2015-10-07 | 2017-04-13 | Wacom Co., Ltd. | Multi-user, cross-browser signature platform |
US10956961B2 (en) * | 2016-03-02 | 2021-03-23 | International Business Machines Corporation | Mobile application for managing offer records |
US20180060911A1 (en) * | 2016-08-25 | 2018-03-01 | International Business Machines Corporation | Dwell time incremental promotional offers |
US10304147B2 (en) * | 2016-10-31 | 2019-05-28 | Kevin Kelly | Drive-thru / point-of-sale automated transaction technologies and apparatus |
-
2013
- 2013-03-15 US US13/840,237 patent/US20130332283A1/en not_active Abandoned
- 2013-03-15 US US13/836,808 patent/US10346867B2/en active Active
- 2013-03-15 US US13/837,790 patent/US9639853B2/en active Active
- 2013-03-15 US US13/839,066 patent/US9881315B2/en active Active
- 2013-03-15 US US13/836,110 patent/US20130332284A1/en not_active Abandoned
- 2013-06-11 EP EP13731580.0A patent/EP2859514A1/en not_active Withdrawn
- 2013-06-11 WO PCT/US2013/045139 patent/WO2013188373A1/en active Application Filing
- 2013-06-11 WO PCT/US2013/045132 patent/WO2013188370A1/en active Application Filing
- 2013-06-11 CA CA2876174A patent/CA2876174A1/en not_active Abandoned
- 2013-06-11 CA CA2876004A patent/CA2876004A1/en active Pending
- 2013-06-11 CA CA3129998A patent/CA3129998A1/en active Pending
- 2013-06-11 AU AU2013274454A patent/AU2013274454A1/en not_active Abandoned
- 2013-06-27 US US13/928,833 patent/US10664857B2/en active Active
-
2017
- 2017-03-28 US US15/471,682 patent/US9953335B2/en active Active
- 2017-12-20 US US15/849,050 patent/US11068922B2/en active Active
- 2017-12-22 US US15/853,016 patent/US9965769B1/en active Active
-
2018
- 2018-04-03 US US15/944,469 patent/US10586243B2/en active Active
- 2018-12-13 US US16/219,649 patent/US10304074B2/en active Active
-
2019
- 2019-04-30 US US16/399,970 patent/US11321728B2/en active Active
- 2019-06-03 US US16/430,373 patent/US11151593B2/en active Active
- 2019-08-28 US US16/554,457 patent/US10586244B2/en active Active
- 2019-10-07 US US16/595,283 patent/US10915916B2/en active Active
- 2019-11-27 US US16/698,132 patent/US11386446B2/en active Active
-
2020
- 2020-04-13 US US16/847,470 patent/US11244337B2/en active Active
-
2021
- 2021-01-04 US US17/141,020 patent/US20210125213A1/en not_active Abandoned
- 2021-12-29 US US17/565,103 patent/US20220122112A1/en active Pending
Cited By (31)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9138081B1 (en) | 2009-06-24 | 2015-09-22 | Starlite Medite, LLC | Shopping cart corral for displaying one or more advertisements and method of providing same |
US9301628B1 (en) | 2009-06-24 | 2016-04-05 | Starlite Media, Llc | Shopping cart corral for displaying one or more advertisements and method of providing same |
US9675188B1 (en) | 2010-03-16 | 2017-06-13 | Starlite Media, Llc | Shopping cart corrals with at least two advertisement panels arranged in a staggered fashion and method of providing same |
USD756461S1 (en) | 2010-03-16 | 2016-05-17 | Starlite Media, Llc | Pair of advertising panels affixed to the entry portion of a shopping cart corral |
US9367859B2 (en) | 2010-03-16 | 2016-06-14 | Starlite Media, Llc | Systems and methods for near field communication enabled shopping cart corrals |
US8984782B1 (en) | 2010-03-16 | 2015-03-24 | Starlite Media, Llc | Shopping cart corrals with at least two advertisement panels arranged in a staggered fashion and method of providing same |
US9301627B1 (en) | 2010-03-16 | 2016-04-05 | Starlite Media, Llc | Shopping cart corrals with at least two advertisement panels arranged in a staggered fashion and method of providing same |
US20140222561A1 (en) * | 2013-02-04 | 2014-08-07 | Facebook, Inc. | Cross-Platform Advertisement Targeting |
US20140282620A1 (en) * | 2013-03-15 | 2014-09-18 | Frank Settemo NUOVO | System and method for triggering an event in response to receiving a device identifier |
US10592915B2 (en) * | 2013-03-15 | 2020-03-17 | Retailmenot, Inc. | Matching a coupon to a specific product |
US20150066654A1 (en) * | 2013-08-30 | 2015-03-05 | Linkedin Corporation | Techniques for facilitating content retargeting |
US10600087B2 (en) * | 2013-08-30 | 2020-03-24 | Microsoft Technology Licensing, Llc | Techniques for facilitating content retargeting |
US9946689B2 (en) * | 2013-11-08 | 2018-04-17 | Sony Interactive Entertainment Inc. | Generating a moving display image having a native image plane and a web image plane appearing continuously on a same plane |
US20150135044A1 (en) * | 2013-11-08 | 2015-05-14 | Sony Computer Entertainment Inc. | Information processing apparatus, information processing method, computer program, and recording medium |
US20160247182A1 (en) * | 2015-02-19 | 2016-08-25 | Target Brands, Inc. | On-line coupon use |
US10762519B2 (en) * | 2015-02-19 | 2020-09-01 | Target Brands, Inc. | On-line coupon use |
USD786974S1 (en) | 2015-02-27 | 2017-05-16 | Starlite Media, Llc | Pair of advertising panels with rounded marker for shopping cart corral |
USD788226S1 (en) | 2015-02-27 | 2017-05-30 | Starlite Media, Llc | Pair of advertising panels with rectangular marker for shopping cart corral |
USD786975S1 (en) | 2015-02-27 | 2017-05-16 | Starlite Media, Llc | Pair of advertising panels with triangular marker for shopping cart corral |
WO2017106051A1 (en) * | 2015-12-16 | 2017-06-22 | Alibaba Group Holding Limited | Method, system, and device for providing item information |
US11120465B1 (en) * | 2017-01-20 | 2021-09-14 | Walgreen Co. | Omni-channel digital coupon clipping and redemption |
US11861651B1 (en) | 2017-01-20 | 2024-01-02 | Walgreen Co. | Omni-channel digital coupon clipping and redemption |
US11842366B1 (en) | 2017-05-08 | 2023-12-12 | Walgreen Co. | Systems and methods for activating electronic coupons via third-party servers |
US11176567B1 (en) * | 2017-05-08 | 2021-11-16 | Walgreen Co. | Systems and methods for activating electronic coupons via third-party servers |
US10475081B1 (en) * | 2017-09-22 | 2019-11-12 | Inmar Clearing, Inc. | Coupon processing system including instant redeemable coupon redemption based upon short message service short code and related methods |
US10706462B1 (en) * | 2017-09-22 | 2020-07-07 | Inmar Clearing, Inc. | Coupon processing system communicating digital coupon offer based upon user bid request and related methods |
US10467648B1 (en) * | 2017-09-22 | 2019-11-05 | Inmar Clearing, Inc. | Coupon processing system including post-purchase coupon value assignment based upon physical coupon redemption and related methods |
US11509607B2 (en) * | 2017-12-13 | 2022-11-22 | Sage Global Services Limited | Chatbot system |
US20190199657A1 (en) * | 2017-12-13 | 2019-06-27 | Sage Global Services Limited | Chatbot system |
US11216865B2 (en) | 2018-03-29 | 2022-01-04 | Christos Parisis | Systems and methods for consumer-oriented behavior predictions and notifications |
US11663655B2 (en) * | 2019-07-03 | 2023-05-30 | Capital One Services, Llc | Augmenting online transaction statements using e-commerce receipts |
Also Published As
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10915916B2 (en) | Devices, methods and computer-readable media for redemption of merchant offers | |
US20150235268A1 (en) | Event-based offers for a geofenced geographic area | |
AU2013274398A1 (en) | Determining offers for a geofenced geographic area | |
CA2876007C (en) | Systems, methods, and computer-readable media for a customizable redemption header for merchant offers across browser instances |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: RETAILMENOT, INC., TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:FAITH, JOHN NEWMAN;BATH, JAGJIT SINGH;ZILKHA, EITHAN;AND OTHERS;REEL/FRAME:030544/0794 Effective date: 20130523 |
|
AS | Assignment |
Owner name: RETAILMENOT, INC., TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:TRIM, JAMES DAMON;REEL/FRAME:031680/0881 Effective date: 20131111 |
|
STCV | Information on status: appeal procedure |
Free format text: ON APPEAL -- AWAITING DECISION BY THE BOARD OF APPEALS |
|
AS | Assignment |
Owner name: CITIBANK, N.A., NEW YORK Free format text: SECURITY INTEREST;ASSIGNORS:RETAILMENOT, INC.;GIFTCARDZEN INC;YSL VENTURES, INC.;AND OTHERS;REEL/FRAME:042494/0822 Effective date: 20170523 |
|
AS | Assignment |
Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS AGENT, NEW YORK Free format text: SECURITY INTEREST;ASSIGNOR:RETAILMENOT, INC.;REEL/FRAME:042562/0481 Effective date: 20170523 Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS AGENT, Free format text: SECURITY INTEREST;ASSIGNOR:RETAILMENOT, INC.;REEL/FRAME:042562/0481 Effective date: 20170523 |
|
AS | Assignment |
Owner name: WELLS FARGO BANK, NATIONAL ASSOCIATION, SOUTH DAKOTA Free format text: SECURITY INTEREST;ASSIGNORS:RETAILMENOT, INC.;GIFTCARDZEN INC.;YSL VENTURES, INC.;AND OTHERS;REEL/FRAME:042684/0863 Effective date: 20170523 Owner name: WELLS FARGO BANK, NATIONAL ASSOCIATION, SOUTH DAKO Free format text: SECURITY INTEREST;ASSIGNORS:RETAILMENOT, INC.;GIFTCARDZEN INC.;YSL VENTURES, INC.;AND OTHERS;REEL/FRAME:042684/0863 Effective date: 20170523 |
|
STCV | Information on status: appeal procedure |
Free format text: BOARD OF APPEALS DECISION RENDERED |
|
STCV | Information on status: appeal procedure |
Free format text: REQUEST RECONSIDERATION AFTER BOARD OF APPEALS DECISION |
|
STCV | Information on status: appeal procedure |
Free format text: BOARD OF APPEALS DECISION RENDERED AFTER REQUEST FOR RECONSIDERATION |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |
|
AS | Assignment |
Owner name: RETAILMENOT, INC., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS AGENT;REEL/FRAME:054195/0983 Effective date: 20201028 Owner name: CSB ACQUISITION CO., LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 42494/0822;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:054241/0662 Effective date: 20201028 Owner name: DEALS.COM, LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 42494/0822;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:054241/0662 Effective date: 20201028 Owner name: YSL VENTURES, INC., TEXAS Free format text: RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 42494/0822;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:054241/0662 Effective date: 20201028 Owner name: RETAILMENOT, INC., TEXAS Free format text: RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 42494/0822;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:054241/0662 Effective date: 20201028 Owner name: CLTD ACQUISITION CO., LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 42494/0822;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:054241/0662 Effective date: 20201028 Owner name: SPECTRAWIDE ACQUISITION CO., LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 42494/0822;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:054241/0662 Effective date: 20201028 Owner name: GIFTCARDZEN INC., TEXAS Free format text: RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 42494/0822;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:054241/0662 Effective date: 20201028 Owner name: RNOT, LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 42494/0822;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:054241/0662 Effective date: 20201028 Owner name: SMALLPONDS, LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 42494/0822;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:054241/0662 Effective date: 20201028 Owner name: YSL VENTURES, INC., TEXAS Free format text: RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 42684/0863;ASSIGNOR:WELLS FARGO BANK, NATIONAL ASSOCIATION;REEL/FRAME:054243/0530 Effective date: 20201028 Owner name: RETAILMENOT, INC., TEXAS Free format text: RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 42684/0863;ASSIGNOR:WELLS FARGO BANK, NATIONAL ASSOCIATION;REEL/FRAME:054243/0530 Effective date: 20201028 Owner name: CLTD ACQUISITION CO., LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 42684/0863;ASSIGNOR:WELLS FARGO BANK, NATIONAL ASSOCIATION;REEL/FRAME:054243/0530 Effective date: 20201028 Owner name: SPECTRAWIDE ACQUISITION CO., LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 42684/0863;ASSIGNOR:WELLS FARGO BANK, NATIONAL ASSOCIATION;REEL/FRAME:054243/0530 Effective date: 20201028 Owner name: DEALS.COM, LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 42684/0863;ASSIGNOR:WELLS FARGO BANK, NATIONAL ASSOCIATION;REEL/FRAME:054243/0530 Effective date: 20201028 Owner name: CSB ACQUISITION CO., LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 42684/0863;ASSIGNOR:WELLS FARGO BANK, NATIONAL ASSOCIATION;REEL/FRAME:054243/0530 Effective date: 20201028 Owner name: RNOT, LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 42684/0863;ASSIGNOR:WELLS FARGO BANK, NATIONAL ASSOCIATION;REEL/FRAME:054243/0530 Effective date: 20201028 Owner name: SMALLPONDS, LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 42684/0863;ASSIGNOR:WELLS FARGO BANK, NATIONAL ASSOCIATION;REEL/FRAME:054243/0530 Effective date: 20201028 Owner name: GIFTCARDZEN INC., TEXAS Free format text: RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 42684/0863;ASSIGNOR:WELLS FARGO BANK, NATIONAL ASSOCIATION;REEL/FRAME:054243/0530 Effective date: 20201028 |