trace.
Log in
Start for free No card required

Advanced ingestion and compliance reference

Updated 30 September 2026

Audience

Technical operators and compliance stakeholders who need deeper behavior notes beyond standard setup docs.

Key concepts

  • Consent precedence: ingestion decisions can depend on explicit consent context.
  • Quarantine and aggregation: some events can be buffered/aggregated under policy.
  • Restricted aggregates: certain aggregate outputs are not eligible for unrestricted export/commercial use.
  • Retention windows: data lifecycle differs by plan/policy state.

Practical guidance

  1. Define your consent and legal basis strategy first.
  2. Document which event classes are critical for reporting.
  3. Review retention expectations with legal/compliance stakeholders.
  4. Validate downstream uses of aggregate data against policy restrictions.

Troubleshooting

  • Unexpected attribution gaps: inspect consent state propagation and ingestion policy decisions.
  • Data unavailable for export: check if dataset is marked restricted by policy.
  • Retention surprises: confirm plan-level retention and purge timing assumptions.
Was this useful?