# US 2026/0086911 A1 · Systems and Methods of Delegated Analytic Collection

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0086911 A1
- Document ID: US20260086911A1
- Status: Published application
- Kind: A1
- Application number: 19/397,504
- Filed: 2025-11-21
- Published: 2026-03-26
- Earliest claimed: 2025-11-21
- Assignees: Google Inc.
- Applicants: Google LLC
- Inventors: Charbel Zaarour
- Web page: https://patentgrep.com/patent/US20260086911A1

## CPC

- G06F 11/3438: {monitoring of user actions (tracking the activity of the user H04L67/535)}
- G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications}
- G06F 21/552: {involving long-term monitoring or reporting}
- G06F 21/6254: {by anonymising data, e.g. decorrelating personal data from the owner's identification}
- G06Q 30/0244: {Optimization}
- G06Q 30/0251: Targeted advertisements
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

A method including tagging a feature of a mobile application as an event generator, in response to a user interacting with the feature of the mobile application on a mobile device, generating an event having an event type, requesting, by an interaction measurement software development kit (SDK) from the mobile application, interaction data associated with the user interaction with the mobile application based on the event type, and securely transmitting, by the interaction measurement SDK, the interaction data to a first computing device indicated by the interaction measurement SDK.

## Claims

### Claim 1

A method comprising:
detecting, by a software development kit, SDK, an event and generating, by the SDK, event data in response to user interactions with a mobile application on a mobile device, wherein the event data includes an event type;
collecting, by the SDK, event data for each detected event
bundling, by the SDK, the event data;
determining, by the SDK, that a connection to a first data processing system is unavailable;
preparing, by the SDK, the bundled event data for transmission to a second data processing system by removing identifiers from the bundled event data; and
securely transmitting, by the SDK, the thus prepared bundled event data to the second data processing system.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
tagging a feature of the mobile application as an event generator;
requesting, by the SDK from the mobile application, interaction data associated with the user interaction with the mobile application based on the event type; and
securely transmitting, by the SDK, the interaction data to the first data processing system.

### Claim 3 (depends on 2)

The method of claim 2, wherein the SDK bundles interaction data from a number of events and transmits the bundled interaction data in response to a threshold.

### Claim 4 (depends on 3)

The method of claim 3, wherein the threshold is a threshold period of time or a threshold number of events.

### Claim 5 (depends on 2)

The method of claim 2, wherein the SDK generates a signature of the interaction data using a hashing algorithm, and wherein the first data processing system validates an authenticity of the interaction data using the signature.

### Claim 6 (depends on 2)

The method of claim 2, further comprising securely transmitting the interaction data to the second data processing system associated with the mobile application, and wherein the SDK removes personal identifiers from the interaction data prior to securely transmitting the interaction data to the first data processing system.

### Claim 7 (depends on 6)

The method of claim 6, wherein the interaction data includes an intermediary identifier, and wherein method further comprises:
identifying, by the second data processing system, supplemental data using the intermediary identifier;
transmitting, by the second data processing system to the first data processing system, the supplemental data; and
correlating, by the first data processing system, the interaction data with the supplemental data.

### Claim 8 (depends on 7)

The method of claim 7, wherein the first data processing system does not have access to personally identifying information.

### Claim 9

A system for correlating data from different entities, comprising:
a client device including a processing circuit having one or more processors and memory, the memory having instructions stored thereon that, when executed by the one or more processors, cause the processing circuit to:
detect an event and generate event data in response to user interactions with a mobile application, wherein the event data includes an event type;
collect event data for each detected event
bundle the event data;
determine that a connection to a first data processing system is unavailable;
prepare the bundled event data for transmission to a second data processing system by removing identifiers from the bundled event data; and
securely transmit the thus prepared bundled event data to the second data processing system.

### Claim 10 (depends on 9)

The system of claim 9, wherein the instructions cause the one or more processors to:
tag a feature in the mobile application as an event generator;
request interaction data associated with the user interaction with the mobile application based on the event type; and
securely transmit the interaction data to the first data processing system.

### Claim 11 (depends on 10)

The system of claim 10, wherein the instructions cause the one or more processors to bundle interaction data from a number of events and transmit the bundled interaction data in response to a threshold.

### Claim 12 (depends on 11)

The system of claim 11, wherein the threshold is a threshold period of time or a threshold number of events.

### Claim 13 (depends on 10)

The system of claim 10, further comprising the first data processing system, wherein the instructions cause the one or more processors to generate a signature of the interaction data using a hashing algorithm, and wherein the first data processing system validates an authenticity of the interaction data using the signature.

### Claim 14 (depends on 10)

The system of claim 10, wherein the instructions further cause the one or more processors to securely transmit the interaction data to the second data processing system and remove personal identifiers from the interaction data prior to securely transmitting the interaction data to the first data processing system.

### Claim 15 (depends on 14)

The system of claim 14, further comprising the first data processing system and the second data processing system, wherein the interaction data includes an intermediary identifier, wherein the second data processing system identifies supplemental data using the intermediary identifier;
wherein the second data processing system transmits the supplemental data to the first data processing system; and
wherein the first data processing system correlates the interaction data with the supplemental data.

### Claim 16 (depends on 15)

The system of claim 15, wherein the first data processing system does not have access to personally identifying information.

### Claim 17

A computer-readable medium having instructions constituting a software development kit, SDK, for a mobile device stored thereon that, when executed by one or more processors, cause the one or more processors to:
detect an event and generate event data in response to user interactions with a mobile application on the mobile device, wherein the event data includes an event type;
collect event data for each detected event
bundle the event data;
determine that a connection to a first data processing system is unavailable;
prepare the bundled event data for transmission to a second data processing system by removing identifiers from the bundled event data; and
securely transmit the thus prepared bundled event data to the second data processing system.

### Claim 18 (depends on 17)

The computer-readable medium of claim 17, wherein the instructions cause the one or more processors to:
tag a feature of a mobile application as an event generator;
request interaction data from the mobile device associated with the user interaction with the mobile application based on the event type; and
securely transmit the interaction data to the first data processing system.

### Claim 19 (depends on 18)

The computer-readable medium of claim 18, wherein the SDK bundles interaction data from a number of events and transmits the bundled interaction data in response to a threshold, wherein the threshold is a threshold period of time or a threshold number of events, wherein the SDK generates a signature of the interaction data using a hashing algorithm.

### Claim 20 (depends on 18)

The computer-readable medium of claim 18, wherein the instructions further cause the one or more processors to securely transmit the interaction data to the second data processing system and remove personal identifiers from the interaction data prior to securely transmitting the interaction data to the first data processing system.
