# Data provenance: connected, witnessed, uploaded

> Data provenance says where the data behind an audited result came from: read from the customer's own systems (connected), streamed by the vendor as it happened (witnessed), or a file (uploaded).

Published 2026-11-12 · Reviewed 2026-11-12. Canonical: https://attify.app/glossary/data-provenance

Data provenance says where the records behind a result came from, and so what the result can support. Attify labels every result with one of three: connected (read from the customer's own systems), witnessed (streamed by the vendor's agent as each interaction happened), or uploaded (a file someone chose).

| | Connected | Witnessed | Uploaded |
|---|---|---|---|
| What it is | Attify read every record of the period from the customer's help desk, CRM, calendar, booking system, or an agent platform account the customer owns, through the customer's own authorization | The vendor's agent sent each interaction as it happened, signed with its deployment's key and timestamped by Attify on arrival; or Attify read the vendor's own platform account as it happened | A file. Whoever supplied it chose what it includes and how its columns map |
| Who could leave records out | Nobody, within each connected system for the period | The vendor; the customer's monthly reconciliation checks the total and a random sample | Whoever made the file |
| Supports a vendor verification and badge | Yes | Only after the customer consents and [reconciles](https://attify.app/glossary/reconciliation) each month | Never |
| Label on the verdict | None needed | "On witnessed data not yet reconciled", until reconciled | "On self-reported data" |

In a vendor's verification program, the vendor chooses which customers to invite, whatever the provenance, so a score describes those customers.

## Whose account

For agent platforms (Vapi, Retell AI, ElevenLabs, Bland AI, Voiceflow) and observability tools (Langfuse, LangSmith), the owner of the account decides the provenance, and Attify records it when the account is connected. A buyer's own account is connected. A vendor's own account is witnessed. A customer offering an account Attify finds is the vendor's is refused, and the refusal is logged.

## Outcomes are read in the customer's systems

Whatever the provenance of the conversation, its outcome is checked in the customer's own systems where they exist: a repeat contact in the help desk, a meeting's attendance in the calendar, an appointment's status in the booking system. A vendor's stream says what the agent did; the customer's records say what happened next.

## Late data

A witnessed interaction with an event that arrived more than 5 minutes after it happened is stored and counted but never scored as witnessed. A conversation read from a vendor's platform account is late when first read more than 2 hours after it happened, so the first read, which reaches 90 days back, is late throughout.

For developers: the [Ingest API](https://attify.app/docs/ingest) describes signing, sequence numbers and what Attify checks on arrival.

## Questions

### Can a vendor's own data support an audited score?

Only witnessed data, sent as each interaction happened, and only after the customer consents in Attify and reconciles it each month against its own records. A file the vendor uploads never can.

### My agent runs on Vapi. Is that connected or witnessed?

It depends whose account it is. The buyer's own platform account, connected by the buyer, is connected data. The vendor's account, connected by the vendor, is witnessed. Attify decides and records this when the account is connected, and refuses a vendor's account offered as the customer's.

### Why are late events not scored as witnessed?

An interaction that arrives long after it happened could have been written after the fact. Events more than 5 minutes late (2 hours for a conversation read from a vendor's platform account) are stored and counted, never scored as witnessed.

## Sources

- Attify: [Attify Audited Resolution Standard v0.11: Data provenance](https://attify.app/standards/support-resolution#data-provenance), read 2026-11-09
- Attify: [Ingest API, schema proven.ingest/1](https://attify.app/docs/ingest), read 2026-11-08
