Interpret Audience and Technical Analytics

Use geography, devices, referrers, ISP/ASN, time zones, currency, and recent activity for support.

Best for: Authorized producers, analysts, accessibility leads, organization owners, and support staff.

Before you start

Availability depends on role, event access, plan entitlements, retained source data, export/AI/statistics features, and privacy policy.

• Confirm exact organization, event, language, and reporting period.
• Verify requester, recipient, and retention/privacy authorization.
• Preserve raw source data before cleanup, editing, or deletion.

Review workflow

1. Set scope. Organization/event/date/freshness.
2. Review geo/time zone. Approximate network location.
3. Review devices. User-agent limits.
4. Review referrers. Distribution, not identity.
5. Review ISP/ASN. Network clusters/proxies/VPNs.
6. Review recent activity. Operationally, not surveillance.
7. Review commercial fields. Exact definition.
8. Correlate incidents. Drops/audit/support.
9. Export minimally. Only needed fields.

What success looks like: The deliverable or analysis is correct for the intended scope, reviewed, reproducible, and protected according to policy.

Check your setup

• Conclusions cite uncertainty.
• No unsupported identity claim.
• Correlates with event evidence.

Troubleshooting

Location wrong

VPN/mobile/ISP approximation.

Device unknown

Privacy/embed limits.

Referrer absent

Direct/privacy-suppressed.

Security and operational notes

• Do not re-identify.
• Protect network/activity data.
• Communicate uncertainty.

Related guides

• Detect Bots, Suspicious Traffic, and Viewer Anomalies
• Use Statistics Filters and KPIs
• Security and Privacy

Documentation status: Draft for operational, privacy, and analytics review before publishing.