Dynamically configurable client application activity

Patent metadata

Field	Value
Publication number	US-11539802-B2
Application number	US-202117459628-A
Country	US
Kind code	B2
Filing date	Aug 27, 2021
Priority date	Sep 9, 2019
Publication date	Dec 27, 2022
Grant date	Dec 27, 2022

Abstract

A method includes selecting, by one or more servers, a digital component to be presented in an application executed at a client device; obtaining, by the one or more servers, attributes of the digital component, including at least one or more of a destination network location to which the digital component redirects users in response to interaction with the digital component and a reporting network location to which the interaction with the digital component is reported; after selecting the digital component and obtaining the attributes of the digital component, selecting, by the one or more servers and based on the obtained attributes, a config file that specifies a set of operations to be performed by the client device that presents the digital component; and transmitting, to the client device, a payload that includes information specifying the digital component to be presented in the application and the config file that, upon execution by the client device, causes the client device to perform the set of operations specified by the config file.

First claim

What is claimed is:

1. A method comprising:
selecting, by one or more servers, a digital component to be presented in an application executed at a client device;
obtaining, by the one or more servers, attributes of the digital component, including at least one or more of a destination network location to which the digital component redirects users in response to interaction with the digital component and a reporting network location to which the interaction with the digital component is reported;
selecting, by the one or more servers and based on the obtained attributes, a config file that specifies a set of operations to be performed by the client device that presents the digital component, wherein selecting the config file comprises:
determining a particular format of the digital component based on the obtained attributes,
determining a version of the application that is being executed by the client device, and
selecting, from among multiple different config files, a particular config file that is defined for the combination of the particular format of the digital component and the version of the application; and

transmitting, to the client device, a payload that includes information specifying the digital component to be presented in the application and the config file that, upon execution by the client device, causes the client device to perform the set of operations specified by the config file.

2. The method of claim 1 , wherein the config file records statistics of impressions or clicks in an application.

3. The method of claim 2 , wherein the config file causes an entity to be charged for the impressions or clicks in the application.

4. The method of claim 1 , further comprising:
receiving a config reporting packet that (i) is generated by the client device in response to execution of the config file, and (ii) specifies the interaction with the digital component at the client device.

5. The method of claim 1 , further comprising:
after transmitting the payload to the client device, selecting the digital component to be presented in the application a second time;
selecting a different config file that specifies a different set of operations than the config file transmitted in the payload based on the different config file being mapped to the attributes of the digital component, instead of the config file, at the second time; and
transmitting, to the client device, a different payload that includes the information specifying the digital component and the different config file, instead of the config file, based on the selection of the digital component while the attributes of the digital component are mapped to the different configuration file.

6. The method of claim 5 , wherein the different set of operations includes an additional operation that causes the client device to perform an action that the config file did not cause the client device to perform.

7. The method of claim 6 , wherein the additional operation causes the client device to collect visual element interaction data that the set of operations of the config file did not cause the client device to collect, wherein the visual element interaction data is collected in response to user interaction with visual elements of the application that are not part of the digital component presented in the application.

8. The method of claim 1 , wherein the set of operations comprises:
a first operation that is performed by the client device in response to a first type of interaction with the digital component; and
a second operation that is performed by the client device in response to a second type of interaction with the digital component.

9. The method of claim 8 , wherein:
the first operation causes the client device to report a presentation of the digital component in response to a first interaction with a first view of the digital component that is presented before interaction with the digital component within the application; and
the second operation causes the client device to report a second interaction with a second view of the digital component that is presented after the first interaction with the first view of the digital component.

10. A system, comprising:
one or more memory devices storing instructions; and
one or more data processing apparatus that are configured to interact with the one or more memory devices, and upon execution of the instructions, perform operations including:
selecting a digital component to be presented in an application executed at a client device;
obtaining attributes of the digital component, including at least one or more of a destination network location to which the digital component redirects users in response to interaction with the digital component and a reporting network location to which the interaction with the digital component is reported;
selecting, by the one or more servers and based on the obtained attributes, a config file that specifies a set of operations to be performed by the client device that presents the digital component, wherein selecting the config file comprises:
determining a particular format of the digital component based on the obtained attributes,
determining a version of the application that is being executed by the client device, and
selecting, from among multiple different config files, a particular config file that is defined for the combination of the particular format of the digital component and the version of the application; and

transmitting, to the client device, a payload that includes information specifying the digital component to be presented in the application and the config file that, upon execution by the client device, causes the client device to perform the set of operations specified by the config file.

11. The system of claim 1 , wherein the config file records statistics of impressions or clicks in an application.

12. The system of claim 2 , wherein the config file causes an entity to be charged for the impressions or clicks in the application.

13. The system of claim 10 , wherein the one or more data processing apparatus that are configured to interact with the one or more memory devices, and upon execution of the instructions, perform operations, further comprising:
receiving at the reporting network location a config reporting packet that (i) is generated by the client device in response to execution of the config file, and (ii) specifies the interaction with the digital component at the client device.

14. The system of claim 10 , wherein the one or more data processing apparatus that are configured to interact with the one or more memory devices, and upon execution of the instructions, perform operations, further comprising:
after transmitting the payload to the client device, selecting the digital component to be presented in the application a second time;
selecting a different config file that specifies a different set of operations than the config file transmitted in the payload based on the different config file being mapped to the attributes of the digital component, instead of the config file, at the second time; and
transmitting, to the client device, a different payload that includes the information specifying the digital component and the different config file, instead of the config file, based on the selection of the digital component while the attributes of the digital component are mapped to the different configuration file.

15. The system of claim 14 , wherein the different set of operations includes an additional operation that causes the client device to perform an action that the config file did not cause the cli

Assignees

• Google Llc

Inventors

• Wu Xiao
• Wu Edward
• Klebanov Moshe Albert

Classifications

• G06F9/44505 Primary

  Configuring for program initiating, e.g. using registry, configuration files · CPC title

• H04L41/0806

  for initial configuration or provisioning, e.g. plug-and-play · CPC title

• G06F9/451

  Execution arrangements for user interfaces · CPC title

• G06F3/04817

  using icons (graphical or visual programming using iconic symbols G06F8/34) · CPC title

• H04L67/34 Primary

  involving the movement of software or configuration parameters  (network booting or remote initial program loading [RIPL] G06F9/4416) · CPC title