What This Registry Is
Reference registry of vendor event, user-data, normalization, hashing, and transport contracts for tracking integrations.
Source Policy
- Verified rows require official vendor-owned developer-grade documentation with explicit technical contract content (API/schema/parameter/reference/command docs).
- RudderStack (
rudder-transformer) is used only for discovery and cross-check, never as source of truth.
- Source classification is content-based, not hostname-based. Vendor-owned help/support hosts can qualify only when pages are explicit developer/API references.
Verification Methodology
| Level | Definition |
|---|
Verified | Directly supported by Tier A canonical developer docs. |
Needs manual review | Partial or secondary evidence exists; not strong enough for verified publication. |
Excluded | Investigated and intentionally left out of verified contracts. |
| Confidence | Meaning |
|---|
High | Explicit and clear contract in canonical docs. |
Medium | Supported but fragmented across canonical docs. |
Low | Ambiguous evidence; requires manual verification. |
Registry Schema
Each row includes object/event, field, applies-to surface, data type, requirement level, exact format, normalization, hashing, caveat, primary source, status, confidence, and review date.
Registry Snapshot
- Platforms:
59
- Rows total:
357
- Verified rows:
306
- Needs manual review rows:
40
- Excluded rows:
11
Changelog / Last Reviewed
- Registry generated:
2026-03-31
- Generator:
tools/publish_verified_only_registry.py