Skip to main content
GitAscii Pro’s v2 traffic signal comes from the separate analytics badge, not the profile SVG hosted on GitHub. Labels inherited from older dashboard versions can say “views”; interpret those numbers as badge requests observed by GitAscii. One badge fetch can represent multiple README visits because GitHub caches images. Direct badge fetches and automated clients can also appear. Do not use the request count as exact profile views. The v2 system does not provide trustworthy unique-visitor, geography, browser, device, operating-system, or viewer-theme measurements for GitHub-hosted SVGs. The badge response itself is cached, so even badge fetch counts are subject to cache behavior. Comparing adjacent periods can show changes in observed request volume, but not a reliable change in unique people. For how the signals are collected, see Telemetry & Privacy. To inspect refresh failures, see Health Monitoring.