Abstract:
A server generates a unique URL corresponding to a data payload, provides that unique URL for exposure to mobile devices of different types, and when the server receives a request for the unique URL from a mobile device, the server uses a payload-type to mobile-device-type mapping to generate a device-type-specific URI that includes the data payload, formatted for the device type. The server delivers the device-type-specific URI to the mobile device to invoke an application for handling the data payload.
Abstract:
When a server receives a request for an information payload from a remote device, the server may determine the device's type and identify an optionally-installable application that can be used to access the information payload on devices of that type. When the optionally-installable application is not installed on the remote device, the server may store a identifier for the remote device and send the device a redirection message via which the device can obtain and install the application. Subsequently, when the server receives an installation indication from the application executing on a remote device, the server may identify the device as having recently been redirected to install the application and store or update a record indicating that an application-installation event occurred.
Abstract:
When a server receives a request for an information payload from a remote device, the server may determine the device's type and identify an optionally-installable application that can be used to access the information payload on devices of that type. When the optionally-installable application is not installed on the remote device, the server may store a identifier for the remote device and send the device a redirection message via which the device can obtain and install the application. Subsequently, when the server receives an installation indication from the application executing on a remote device, the server may identify the device as having recently been redirected to install the application and store or update a record indicating that an application-installation event occurred.
Abstract:
Multiple applications may be targeted via key/value data associated with a resource identified by a primary Uniform Resource Locator (“URL”). By parsing the key/value data, an alternative application for accessing the resource may be identified. When the alternative application is installed on a device, the alternative application may be invoked to access the resource.
Abstract:
Disclosed are systems and methods for improving interactions with and between computers supported by or configured with application servers or platforms. The systems interact to identify and retrieve data across platforms, which data can be used to improve the quality of tracking data used in processing interactions between or among processors in such systems. The disclosed systems and methods provide for conversion tracking. That is, the disclosed systems and methods enable the tracking of user information, associated with the user and/or the user's device, upon a user performing a conversion action including, but not limited to, downloading an application, visiting a website or downloading other types of online content.