Visitor export & erasure

Verify the request#

Use your established privacy-request process to verify the requester and identify the correct site and available visitor identifier. A cookieless estimate may not supply a reliable cross-device identity. Do not guess a subject from a public IP or another person's timeline.

Export records#

An administrator can export the specified visitor's analytics and legacy identity mappings. The tool is throttled and fails explicitly when the export is too large. Store and deliver the result securely; it may contain personal data and is not a public share report.

Queue erasure#

The erasure tool requires visitorId and an exact matching confirmVisitorId. Queuing pauses tracking for the site and schedules deletion work. queued=true is not proof that every backing store is already cleaned up.

Track completion#

Inspect privacy request status and completion times, then review before re-enabling collection. Operators must run cleanup/deletion processing successfully. Record the outcome according to your privacy-request procedure without publishing subject identifiers.

API equivalents#

export_visitor_data, erase_visitor_data, list_privacy_requests. Administrator access is required; erasure additionally requires write consent and exact confirmation.