p202 click-filter

See and change why clicks are filtered: the built-in checks, your address list, and an address test

New in 1.9.79
All commands

p202 CLI reference

Back to the docs

01How it works

A filtered click is recorded and redirected, and left out of Real clicks. Three built-in checks filter one, all on by default: an address a user of this install last signed in from (sign_in_addresses), the built-in search engine crawler ranges (crawler_ranges), and a repeat click from the same address within the repeat window (repeat_visits, repeat_window). The address list beats them: an entry is always counted (count, which beats every check) or always filtered (filter). Bot detection, which reads the browser, always applies. p202 click get says which rule filtered a click (filter_reason). Every command acts on your own account; --user-id names another you may manage.

02Commands

4 under p202 click-filter.

p202 click-filter getShow the click filter's checks, repeat window and address listp202 click-filter listShow the address list: addresses and blocks always counted or always filteredp202 click-filter setSwitch the built-in checks on or off, and choose the repeat windowp202 click-filter testTest whether a click from an address would be filtered, and by which rule

03For agents

Running this from an agent

  • Read the same facts as JSON: p202 commands click-filter --json.
  • With AI_AGENT, CLAUDECODE or another agent variable set, output is compact JSON and errors arrive on stderr as a JSON envelope with a hint.
  • Exit codes: 0 ok, 1 bad input, 2 auth, 3 network, 4 server error, 5 partial failure, 6 no Pro licence on the install.
p202 commands click-filter --json
{
  "path": "p202 click-filter",
  "use": "click-filter",
  "short": "See and change why clicks are filtered: the built-in checks, your address list, and an address test",
  "long": "A filtered click is recorded and redirected, and left out of Real clicks. Three built-in checks\nfilter one, all on by default: an address a user of this install last signed in from\n(sign_in_addresses), the built-in search engine crawler ranges (crawler_ranges), and a repeat\nclick from the same address within the repeat window (repeat_visits, repeat_window). The address\nlist beats them: an entry is always counted (count, which beats every check) or always filtered\n(filter). Bot detection, which reads the browser, always applies. `p202 click get` says which rule\nfiltered a click (filter_reason). Every command acts on your own account; --user-id names another\nyou may manage.",
  "runnable": false
}