Abstract: A technique that can be implemented by the digital asset repository, and includes the steps of (1) receiving, from a first application executing on the first computing device, a request to access information associated with a second application managed by the digital asset repository, wherein the request: (i) is transmitted in response to a selection of a user interface that is displayed by the first application and that relates to the second application, and (ii) includes a set of parameters that is provided by a remote server and that specifies at least one utilization requirement pertaining to the second application; (2) receiving, from the second application, an indication that activity associated with the second application has been performed; (3) determining, based on the indication, that the at least one utilization requirement is satisfied; and (4) providing the set of parameters to a metrics manager executing on a second computing device.

Abstract: The embodiments set forth techniques for managing advertisement attributions. A first technique can be implemented by an “app store” application, and include the steps of (1) receiving, from a first user application, a request to view a second user application, where the request includes a set of digitally-signed parameters that are specific to an advertising campaign (provided by an advertisement network) for the second user application that is presented by the first user application. In turn, and in response to identifying that the second user application satisfies at least one criterion, the app store application provides the set of digitally-signed parameters to an advertisement metrics manager that: (i) verifies the set of digitally-signed parameters, and (ii) indicates, to the advertisement network, that business logic should be carried out in association with the first user application and the second user application. A second technique for managing advertisement attributions is also disclosed.

Abstract: Systems, methods, and computer-readable media for personalizing program credentials are provided. For example, a program credential (e.g., loyalty pass) associated with a program provider (e.g., an issuer) subsystem may be customized using personal data. The personal data can be collected from an electronic device before provisioning the customized program credential on the electronic device for use in a suitable transaction. However, such personal data may not be collected unless an administration entity subsystem is first able to validate the program provider subsystem. The administration entity subsystem can generate tracking data that may be used during the validation and/or provisioning in order to track when program credentials are personalized.

Abstract: The embodiments set forth techniques for managing advertisement attributions. A first technique can be implemented by an “app store” application, and include the steps of (1) receiving, from a first user application, a request to view a second user application, where the request includes a set of digitally-signed parameters that are specific to an advertising campaign (provided by an advertisement network) for the second user application that is presented by the first user application. In turn, and in response to identifying that the second user application satisfies at least one criterion, the app store application provides the set of digitally-signed parameters to an advertisement metrics manager that: (i) verifies the set of digitally-signed parameters, and (ii) indicates, to the advertisement network, that business logic should be carried out in association with the first user application and the second user application. A second technique for managing advertisement attributions is also disclosed.

Abstract: Systems, methods, and computer-readable media for personalizing program credentials are provided. For example, a program credential (e.g., loyalty pass) associated with a program provider (e.g., an issuer) subsystem may be customized using personal data. The personal data can be collected from an electronic device before provisioning the customized program credential on the electronic device for use in a suitable transaction. However, such personal data may not be collected unless an administration entity subsystem is first able to validate the program provider subsystem. The administration entity subsystem can generate tracking data that may be used during the validation and/or provisioning in order to track when program credentials are personalized.