User Counting
eyeo's Browser Ad-Filtering Solution collects user data to understand cross-platform usage and versioning while maintaining strict privacy standards by excluding personally identifiable information.
Why eyeo Counts Users
eyeo tracks users with ad-filtering enabled and those with both ad-filtering and Acceptable Ads enabled for several purposes:
-
Version Management: Distribution data helps determine which product versions warrant ongoing support versus deprecation
-
Platform Prioritization: OS and platform analytics guide quality assurance and automation resource allocation
-
User Experience: Opt-out rates inform understanding of user perception regarding Acceptable Ads
-
Partner Compensation: Data establishes the foundation for partner payouts based on Acceptable Ads monetization
How User Counting Works
The Solution automatically sends ping requests to eyeo's service at minimum twice daily when the browser is active and ad-filtering is enabled. These requests contain no personally identifiable information.
Ping Request Payload
The system combines ping timestamps with randomly-generated tags and truncates dates for enhanced privacy protection.
|
Parameter |
Type |
Description |
|---|---|---|
|
|
string |
UUID4-generated identifier distinguishing multiple ping requests with identical parameter values |
|
|
string |
Solution identifier (e.g., |
|
|
string |
Solution version matching addon_name (e.g., |
|
|
string |
Application name for product attribution (e.g., |
|
|
string |
Current application version, often reflecting Chromium version (e.g., |
|
|
string |
Initial server-acknowledged ping timestamp (e.g., |
|
|
string |
Most recent server-acknowledged ping timestamp |
|
|
string |
UUID4-generated client identifier for distinguishing requests with identical last_ping values |
|
|
string |
Penultimate ping timestamp copied from previous request |
|
|
bool |
User's Acceptable Ads opt-in status |
|
|
string |
Client operating system (e.g., |
|
|
string |
OS version (e.g., |