Abstract: The subject matter of this specification generally relates to detecting events that occur within mobile applications without modifying code of the mobile application. In some implementations, a front-end server receives, from a mobile application management application installed on a client device, interaction data specifying (i) a user interaction identifier for a user interaction with an interactive item that presents, at a first mobile application, content for a second mobile application and (ii) an interactive item identifier. The front-end server receives event data specifying an occurrence of a specified user action within the second mobile application and the interactive identifier for the interactive item. A back-end server determines that the specified user action resulted from the user interaction based on a match between the interactive item identifier specified by the event data and the interactive item identifier that links to the user interaction identifier for the user interaction.

Abstract: Systems and methods herein allow for automatic monitoring of conversions associated with uniform resource identifiers (URIs) accessed via client applications but actuated on web browsers. Upon actuation of a URI on a browser of a client device, a data processing system can assign a click ID to the actuation event and send it to the client device. The client device can open the URI in a client application and send the click ID and a client ID associated with the client device to the client device. The data processing system can map the click ID to the client ID. Upon occurrence of a URI related conversion, on the client application, the data processing system can receive a conversion message indicative of the conversion and including the client ID, and link the URI related conversion to the click ID based on the stored mapping.

Abstract: Systems and methods herein allow for automatic monitoring of conversions associated with uniform resource identifiers (URIs) accessed via client applications but actuated on web browsers. Upon actuation of a URI on a browser of a client device, a data processing system can assign a click ID to the actuation event and send it to the client device. The client device can open the URI in a client application and send the click ID and a client ID associated with the client device to the client device. The data processing system can map the click ID to the client ID. Upon occurrence of a URI related conversion, on the client application, the data processing system can receive a conversion message indicative of the conversion and including the client ID, and link the URI related conversion to the click ID based on the stored mapping.

Abstract: Systems and methods herein allow for automatic monitoring of conversions associated with uniform resource identifiers (URIs) accessed via client applications but actuated on web browsers. Upon actuation of a URI on a browser of a client device, a data processing system can assign a click ID to the actuation event and send it to the client device. The client device can open the URI in a client application and send the click ID and a client ID associated with the client device to the client device. The data processing system can map the click ID to the client ID. Upon occurrence of a URI related conversion, on the client application, the data processing system can receive a conversion message indicative of the conversion and including the client ID, and link the URI related conversion to the click ID based on the stored mapping.

Abstract: Systems and methods herein allow for automatic monitoring of conversions associated with uniform resource identifiers (URIs) accessed via client applications but actuated on web browsers. Upon actuation of a URI on a browser of a client device, a data processing system can assign a click ID to the actuation event and send it to the client device. The client device can open the URI in a client application and send the click ID and a client ID associated with the client device to the client device. The data processing system can map the click ID to the client ID. Upon occurrence of a URI related conversion, on the client application, the data processing system can receive a conversion message indicative of the conversion and including the client ID, and link the URI related conversion to the click ID based on the stored mapping.

Abstract: The subject matter of this specification generally relates to detecting events that occur within mobile applications without modifying code of the mobile application. In some implementations, a front-end server receives, from a mobile application management application installed on a client device, interaction data specifying (i) a user interaction identifier for a user interaction with an interactive item that presents, at a first mobile application, content for a second mobile application and (ii) an interactive item identifier. The front-end server receives event data specifying an occurrence of a specified user action within the second mobile application and the interactive identifier for the interactive item. A back-end server determines that the specified user action resulted from the user interaction based on a match between the interactive item identifier specified by the event data and the interactive item identifier that links to the user interaction identifier for the user interaction.

Abstract: The subject matter of this specification generally relates to detecting events that occur within mobile applications without modifying code of the mobile application. In some implementations, a front-end server receives, from a mobile application management application installed on a client device, interaction data specifying (i) a user interaction identifier for a user interaction with an interactive item that presents, at a first mobile application, content for a second mobile application and (ii) an interactive item identifier. The front-end server receives event data specifying an occurrence of a specified user action within the second mobile application and the interactive identifier for the interactive item. A back-end server determines that the specified user action resulted from the user interaction based on a match between the interactive item identifier specified by the event data and the interactive item identifier that links to the user interaction identifier for the user interaction.

Abstract: The subject matter of this specification generally relates to detecting events that occur within mobile applications without modifying code of the mobile application. In some implementations, a front-end server receives, from a mobile application management application installed on a client device, interaction data specifying (i) a user interaction identifier for a user interaction with an interactive item that presents, at a first mobile application, content for a second mobile application and (ii) an interactive item identifier. The front-end server receives event data specifying an occurrence of a specified user action within the second mobile application and the interactive identifier for the interactive item. A back-end server determines that the specified user action resulted from the user interaction based on a match between the interactive item identifier specified by the event data and the interactive item identifier that links to the user interaction identifier for the user interaction.

Abstract: Systems and methods herein allow for automatic monitoring of conversions associated with uniform resource identifiers (URIs) accessed via client applications but actuated on web browsers. Upon actuation of a URI on a browser of a client device, a data processing system can assign a click ID to the actuation event and send it to the client device. The client device can open the URI in a client application and send the click ID and a client ID associated with the client device to the client device. The data processing system can map the click ID to the client ID. Upon occurrence of a URI related conversion, on the client application, the data processing system can receive a conversion message indicative of the conversion and including the client ID, and link the URI related conversion to the click ID based on the stored mapping.

Abstract: Systems and methods herein allow for automatic monitoring of conversions associated with uniform resource identifiers (URIs) accessed via client applications but actuated on web browsers. Upon actuation of a URI on a browser of a client device, a data processing system can assign a click ID to the actuation event and send it to the client device. The client device can open the URI in a client application and send the click ID and a client ID associated with the client device to the client device. The data processing system can map the click ID to the client ID. Upon occurrence of a URI related conversion, on the client application, the data processing system can receive a conversion message indicative of the conversion and including the client ID, and link the URI related conversion to the click ID based on the stored mapping.

Abstract: Systems and methods herein allow for automatic monitoring of conversions associated with uniform resource identifiers (URIs) accessed via client applications but actuated on web browsers. Upon actuation of a URI on a browser of a client device, a data processing system can assign a click ID to the actuation event and send it to the client device. The client device can open the URI in a client application and send the click ID and a client ID associated with the client device to the client device. The data processing system can map the click ID to the client ID. Upon occurrence of a URI related conversion, on the client application, the data processing system can receive a conversion message indicative of the conversion and including the client ID, and link the URI related conversion to the click ID based on the stored mapping.

Abstract: Systems and methods include receiving an indication of a hardware or software configuration of a client device. Content associated with a downloadable application is identified by matching installation requirements for the application to the hardware or software configuration of the device.

Abstract: Systems and methods include receiving an indication of a hardware or software configuration of a client device. Content associated with a downloadable application is identified by matching installation requirements for the application to the hardware or software configuration of the device.