Analytics Export Privacy and Count Definitions

Document what counts mean and prevent identity or precision claims the data cannot 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.

Reference

1. Read definitions. Viewer/session/view/event/retention/geo/device/referrer/network.
2. Record bot handling. Included/excluded/flagged.
3. Record uniqueness. Signals are not guaranteed people.
4. Record time rules. Zone/boundary/late data/retention.
5. Minimize raw fields. Remove unnecessary identifiers.
6. Aggregate small groups. Reduce re-identification.
7. Confirm recipients/purpose. Approved use.
8. Attach methodology. Definitions/caveats.

Use this reference to confirm: The deliverable or analysis is correct for the intended scope, reviewed, reproducible, and protected according to policy.

Validation checks

• Scope/uncertainty stated.
• Small groups protected.
• Recipients understand limits.

Compatibility notes

Exact people requested

Explain limits.

Exports differ

Compare time/filters/freshness/schema.

Small group identifiable

Aggregate/suppress.

Limits and cautions

• Do not re-identify.
• Network/location is sensitive/approximate.
• Use lawful purpose.

Related guides

• Export Analytics as CSV or JSON
• Security and Privacy
• Detect Bots, Suspicious Traffic, and Viewer Anomalies

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