Describe the usable unit
Aggregated events, reporting definitions and funnel histories. Explain whether the archive preserves the connections between records and the process they represent. File count alone does not show coverage, quality or usefulness.
Ask this before preparing a sample
Ask whether aggregate reports are sufficient and who holds rights to the underlying event data.
Review sensitive and restricted elements
Tracking identifiers, consent obligations and platform contractual limits. Check the actual contents, including hidden fields, metadata, embedded files and related records. Data minimization and de-identification are separate from confirming the right to license the material.
Evidence to bring to a fit discussion
Prepare a schema or category-level description, date range, approximate volume, export format, known gaps and exclusion list. Clearly distinguish measurements from estimates. Do not upload the underlying archive simply to obtain a preliminary opinion.
Compare the proposed use
Ask whether the provider wants training examples, evaluation material, retrieval content or a simulated environment. These are different purposes and should not be bundled into vague unrestricted language. Confirm downstream recipients, duration and any right to sublicense.
Tests to agree before a sample
- Record the event definitions and changes to tracking configuration.
- Separate aggregate reports from user-level event streams.
- Explain sampling, filtering and bot exclusions so apparent trends are not treated as raw facts.