Relationships
See how a data model connects to destinations, clients, API keys, and Analytics APIs.
The data model detail page brings related resources together. Use these relationships to understand the impact of a change.
Destination relationship
A destination decides where records for the model are delivered. A model without an active destination may accept configuration work but cannot complete the intended storage path.
Write access
Ingest clients and ingest-capable API keys list the models they may write. The runtime checks this allowlist for every request.
Removing a model from a client's allowed set blocks future requests from that identity. It does not delete previously stored data.
Read access
Analytics APIs reference model fields through their saved definitions. Query clients and query-capable API keys then control access to those Analytics APIs.
The Data Model detail view shows API-key context in the relevant Ingest Client or Query Client area rather than maintaining a separate API Keys tab.
Why relationship checks matter
Before editing or archiving a model, answer:
- Which senders still write it?
- Which destination stores it?
- Which analytics definitions depend on its fields?
- Which consumers call those analytics?
- Will a field change remain compatible with stored records?