LogoLogo
About GitLabAcceptable Ads
  • Getting Started
  • Browser Ad-Filtering Solution
    • Features
    • Getting Started
      • Quickstart
      • Integrate the Solution
      • Set up user counting
    • Guides
      • User counting
      • Configure Solution settings
      • Run separate instances of the filtering engine
      • Update the Solution
      • Understand the snippets library
      • Create a filter list
      • Testing
    • Advanced
      • Services and classes
      • Sitekey
      • ADRs
      • Frame hierarchy
  • Snippets
    • Snippets Overview
    • Behavioral Snippets
      • abort-current-inline-script
      • abort-on-property-read
      • abort-on-property-write
      • abort-on-iframe-property-read
      • abort-on-iframe-property-write
      • array-override
      • cookie-remover
      • freeze-element
      • json-override
      • json-prune
      • override-property-read
      • prevent-listener
      • replace-fetch-response
      • replace-xhr-response
      • simulate-mouse-event
      • skip-video
      • strip-fetch-query-parameter
    • Conditional Hiding Snippets
      • hide-if-canvas-contains
      • hide-if-contains
      • hide-if-contains-image
      • hide-if-contains-similar-text
      • hide-if-contains-visible-text
      • hide-if-contains-and-matches-style
      • hide-if-has-and-matches-style
      • hide-if-labelled-by
      • hide-if-matches-computed-xpath
      • hide-if-matches-xpath
      • hide-if-matches-xpath3
      • hide-if-shadow-contains
    • Debugging Snippets
      • debug
      • log
      • profile
      • trace
    • Performance Snippets
      • race
    • Snippets Support by Platform
    • Node Highlighting
    • Accessing shadow DOM elements
  • Working with filters
  • DATA AND PRIVACY
    • Data collection at eyeo
Powered by GitBook
On this page
  • Obligatory arguments
  • Optional arguments

Was this helpful?

Edit on GitLab
Export as PDF
  1. Browser Ad-Filtering Solution
  2. Getting Started

Set up user counting

How to set-up eyeometry.

Last updated 1 year ago

Was this helpful?

No requests sent to data collection services contain any personally identifiable information. To learn about eyeometry, view .

Obligatory arguments

You must provide special gn arguments before building your product in order to enable user counting.

  • eyeo_telemetry_client_id

  • eyeo_telemetry_activeping_auth_token

eyeo will provide the argument values upon contact.

To set the arguments, generate project build files like the following:

gn gen --args='eyeo_telemetry_client_id="mycompany" eyeo_telemetry_activeping_auth_token="peyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9" ...' ...

If you don't set these arguments, eyeo will not correctly attribute users to your product, although your application will still build and run.

Keep your auth token secure. Never embed it in open-source repositories or documents. If your auth token is revealed, reach out to eyeo as soon as possible to receive a new token.

User counting doesn't transfer any PII or other identifiable data to eyeo, nor does it allow tracking or profiling of users by eyeo.

Optional arguments

You may additionally provide values for application and application_version by setting the following gn arguments:

  • eyeo_application_name

  • eyeo_application_version

For example:

gn gen --args='eyeo_telemetry_client_id="mycompany" eyeo_telemetry_activeping_auth_token="peyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9" eyeo_application_name="My great browser" eyeo_application_version="111.24.0.1" ...' ...

In absence of these values, the eyeo Browser Ad-Filtering Solution will fall back to version_info::GetProductName() and version_info::GetVersionNumber() from

User Counting
version_info.h