An event taxonomy that survives connector growth
How to name events and properties so a dozen new integrations do not create a dozen incompatible datasets.
Connector analytics often starts with events named after individual integrations. That feels quick, but it makes portfolio questions unnecessarily hard as coverage expands.
Use a consistent object-action pattern for shared journey events, such as connector_setup_started or connector_sync_completed. Store connector type, provider, direction and trigger as governed properties. Reserve provider-specific events for genuinely unique behaviour.
Every event needs an owner, firing rule, source, identity scope and example payload. Describe what must be true, not simply what interface element was clicked. Version breaking definition changes and record the release date.
A sound taxonomy makes analysis composable. Teams can compare activation and reliability across the portfolio while retaining enough detail to diagnose one connector. Governance then becomes a lightweight release habit, not a periodic rescue project.