Methods and apparatus for mobile device messaging-based communications using custom-generated deeplinks and based on the hyper text transfer protocol (http)

Abstract

In some embodiments, a method includes in response to an integration tag included in a webpage at a first user interface being executed at a mobile device, receiving a mobile device identifier and a request to retrieve a purchase identifier. The method includes sending a first signal causing a frame to be provided within the webpage at the first user interface. The method includes in response to a first user input, receiving a Hyper Text Transfer Protocol (HTTP) POST request and determining a uniform resource identifier (URI). The method includes retrieving purchase information and sending a HTTP response message including the URI of the second user interface and the purchase information to deeplink to the second user interface and to cause the second user interface to be rendered at the mobile device with the purchase information pre-populated in an input field of a text message.

What is claimed is: 
     
         1 . At least one non-transitory processor-readable medium storing code configured to be executed by at least one processor of at least one server, the code comprising instructions configured to cause the at least one server to:
 define an integration tag configured to be embedded with content displayable via a first application of a mobile device, the integration tag defined to cause: 
 (1) the mobile device to display a promotional message via the first application when a predefined condition is met; 
 (2) the at least one server to receive user data in response to a user of the mobile device interacting with the promotional message via the first application, the user data including at least two of: an operating system identifier associated with an operating system of the mobile device, a mobile device identifier, a user device identifier, user viewing history, user location, user click/tap history, or impression data; 
   define, based on the at least two parameters from the user data, a uniform resource identifier (URI) that deeplinks to a messaging application of the mobile device to cause the mobile device to populate a custom message with a message body that is associated with at least one parameter from the user data such that the custom message can be sent to the at least one server via the messaging application in response to the user of the mobile device interacting with a send button of the messaging application; and   cause a promotion to be delivered based on receiving the custom message.   
     
     
         2 . The non-transitory processor-readable medium of  claim 1 , wherein the predefined condition is that the mobile device is not a desktop or laptop computer. 
     
     
         3 . The non-transitory processor-readable medium of  claim 1 , wherein the predefined condition is that the mobile device and/or a user of the mobile device (1) is on a whitelist or (2) is not on a blacklist. 
     
     
         4 . The non-transitory processor-readable medium of  claim 1 , wherein the predefined condition is that the user and/or the mobile device are within a country from a predefined list of countries. 
     
     
         5 . The non-transitory processor-readable medium of  claim 1 , wherein the URI is defined such that the URI can be sent to the mobile device in response to receiving an indication that the user of the mobile device interacted with the promotional message. 
     
     
         6 . The non-transitory processor-readable medium of  claim 1 , the code further including instructions configured to cause the at least one processor to:
 send the URI to the mobile device from the at least one server in response to receiving an indication that the user of the mobile device interacted with the promotional message.   
     
     
         7 . The non-transitory processor-readable medium of  claim 1 , wherein the promotion is a subscription sent to the mobile device without an entity that controls the at least one server charging a fee. 
     
     
         8 . The non-transitory processor-readable medium of  claim 1 , wherein the message body is associated with at least two parameters from the user data. 
     
     
         9 . The non-transitory processor-readable medium of  claim 1 , the code further comprising code to cause the processor to receive, from a client device, an indication of the predefined condition. 
     
     
         10 . The non-transitory processor-readable medium of  claim 1 , wherein the first application is at least one of a website browser, an email application, a book reader application, or a mobile application. 
     
     
         11 . The non-transitory processor-readable medium of  claim 1 , wherein the URI is configured to cause the mobile device to automatically transition from the first application to the messaging application when initiated. 
     
     
         12 . The non-transitory processor-readable medium of  claim 1 , wherein the URI is defined to deeplink to the messaging application to cause the mobile device to automatically transition to an interface of the messaging application having the send button, allowing a user of the mobile device to send the message with a single interaction with the send button after the URI is initiated. 
     
     
         13 . The non-transitory processor-readable medium of  claim 1 , the code further comprising code to cause the at least one server to send a confirmation message to the messaging application in response to receiving the message. 
     
     
         14 . The non-transitory processor-readable medium of  claim 1 , wherein the predefined condition is based on at least one of a referrer whitelist or a referrer blacklist. 
     
     
         15 . The non-transitory processor-readable medium of  claim 1 , wherein the mobile device identifier includes at least one of a user agent field or a user phone number. 
     
     
         16 . At least one non-transitory processor-readable medium storing code configured to be executed by at least one processor of at least one server, the code comprising instructions configured to cause the at least one server to:
 define a promotional message;   define a destination phone number associated with the promotional message and a message body associated with the promotional message;   define an integration tag configured to be embedded with content displayable via a first application of a mobile device, the integration tag defined such that:
 (1) the mobile device displays the promotional message via the first application when a predefined condition is met, and 
 (2) the at least one server receives user data in response to a user of the mobile device interacting with the promotional message via the first application, the user data including at least two of: an operating system identifier associated with an operating system of the mobile device, a mobile device identifier, a user device identifier, user viewing history, user location, user click/tap history, or impression data; 
   define, based on at least two parameters from the user data, a uniform resource identifier (URI), the URI configured to:
 (1) deeplink to a messaging application of the mobile device to cause the mobile device to automatically populate a custom message that includes the destination phone number associated with the promotional message and the message body associated with the promotional message, and 
 (2) enable the custom message to be received at the at least one server in response to a user of the mobile device interacting with a send button of the messaging application after the custom message is automatically populated; and 
   define a response for the mobile device containing the URI in response to the user of the mobile device interacting with the promotional message.   
     
     
         17 . The non-transitory processor-readable medium of  claim 16 , wherein:
 the messaging application is a default messaging application pre-installed with the operating system of the mobile device;   the user data includes the operating system identifier; and   the URI is customized for the operating system based on the operating system identifier deeplinks to the default messaging application of the mobile device such that the URI, when initiated causes the custom message to be automatically populated with the message body without having a custom application associated with the promotion installed at the mobile device.   
     
     
         18 . The non-transitory processor-readable medium of  claim 16 , wherein:
 the user data includes at least one of the mobile device identifier or the user identifier; and   the message body is associated with the at least one of the mobile device identifier and the user identifier,   the code further comprising instructions configured to cause the at least one server to identify the mobile device after receiving the message based on the message body and the at least one of the mobile device identifier or the user identifier.   
     
     
         19 . The non-transitory processor-readable medium of  claim 16 , the code further comprising code to cause the processor to:
 authenticate the user of the mobile device based on associating the message body with the user data; and   deliver a promotion associated with the promotional message in response to authenticating the user.   
     
     
         20 . The non-transitory processor-readable medium of  claim 16 , wherein the URI is defined to cause the mobile device to automatically transition from the first application to the messaging application when the URI is initiated. 
     
     
         21 . The non-transitory processor-readable medium of  claim 16 , wherein the mobile device identifier includes at least one of a user agent or a user phone number. 
     
     
         22 . At least one non-transitory processor-readable medium storing code configured to be executed by at least one processor of at least one server, the code comprising instructions configured to cause the at least one server to:
 receive, from at least one client device, an indication of a custom message body associated with a promotional message and a business rule associated with that promotional message, the business rule describing a predefined condition for display of the promotional message;   define an integration tag configured to:
 (1) be embedded with content displayable via a first application of a mobile device, 
 (2) cause the mobile device to display the promotional message via the first application when a predefined condition is met, and 
 (3) cause the mobile device to send, to the at least one server, user data in response to a user of the mobile device interacting with the promotional message via the first application, the user data including at least two of: an operating system identifier associated with an operating system of the mobile device, a user device identifier, user viewing history, user location, user click/tap history, or impression data; 
   define, based on the at least two parameters from the user data, a uniform resource identifier (URI) that deeplinks to a messaging application to cause the mobile device to populate a message with the custom message body such that the message, including the custom message body, is received at the at least one server in response to the user of the mobile device interacting with a send button of the messaging application; and   cause a promotion to be delivered to the mobile device based on receiving the message including the custom message body.   
     
     
         23 . The non-transitory processor-readable medium of  claim 22 , the code further comprising code to cause the at least one server to send the URI to the mobile device in response to the user interacting with the promotional message. 
     
     
         24 . The non-transitory processor-readable medium of  claim 22 , the code further comprising code to cause the at least one server to send the integration tag to the at least one client device, the integration tag being embeddable with the content. 
     
     
         25 . The non-transitory processor-readable medium of  claim 22 , wherein the URI is configured to cause the mobile device to automatically transition from the first application to the messaging application when the URI is initiated. 
     
     
         26 . The non-transitory processor-readable medium of  claim 22 , wherein:
 the messaging application is a default messaging application pre-installed with the operating system of the mobile device;   the user data includes the operating system identifier; and   the URI is customized for the operating system based on the operating system identifier and deeplinks to the default messaging application of the mobile device such that the URI, when executed causes the custom message to be automatically populated with the custom message body without having a custom application associated with the promotion installed.   
     
     
         27 . The non-transitory processor-readable medium of  claim 22 , wherein the URI is defined to deeplink to the messaging application to cause the mobile device to automatically transition to an interface of the messaging application having the send button, allowing the user of the mobile device to send the message with a single interaction after the URI is executed.