Real User Monitoring counts unique visitors and leaves out your own IPs

Real User Monitoring now answers «how many people?» next to «how many page views?», and lets you keep your own traffic out.

• Unique visitors. The report, the API (visitors, prev_visitors, and per interval and breakdown row), ctl rum report and rum_report show the distinct visitors of the period. The edge derives a daily visitor id from the IP address, the User-Agent and the zone with a key that changes every UTC day and is deleted when the day ends. No cookie, nothing stored on the device, and the IP address and User-Agent are still never stored.
• Excluded IPs. rum.exclude_ips takes up to 100 IPv4 or IPv6 addresses or CIDR prefixes (your office, home connection, uptime monitors, test browsers). Their page views never get the script and their beacons are dropped; the report says how many page views were excluded by IP. Set it in Analytics › Real performance › Settings, with ctl zones set … rum.exclude_ips=…, the API or update_settings. See excluded IPs.
• Where RUM is on. A zone with RUM off at the zone level but on for some names used to be reported as off. The report now carries host_settings (the effective RUM of every name with its own settings), and the dashboard, ctl and rum_report say which names measure.

Visitor counts start with the measurements received after the change; earlier page views have no visitor id.