CTR-WEB-ANALYTICS · version 1
Digital Analytics — Session events
The highest-volume feed on the estate and the least reviewed. That combination is the point of showing it.
What the contract says
These are the terms the connector is generated against. A source that stops matching them is a drift finding, not a silent data change.
Review state
Neither review is performed by the team that wrote the contract.
Validation and drift
Drift is only detectable on a contract that has been read against a sample.
The field list
4 fields · 1 key · 1 personal. The validation rule on each row is what admits or rejects a record at the staging boundary.
| Field | Source | Target | Type | Flags | Drift | Validation |
|---|---|---|---|---|---|---|
| Event id | event.id | sessionEvent.ref | string(36) | keyinternal | Never checked | Unique. |
| Session id | session.id | sessionEvent.sessionRef | string(36) | internal | Never checked | Stitched upstream. |
| Event type | event.name | sessionEvent.kind | string(60) | internal | Never checked | Mapped against a 38-value table. |
| Visitor id | visitor.id | sessionEvent.visitorHash | string(64) | personalrestricted | Never checked | Pseudonymized. Under the draft contract this field is the reason privacy review has not started. |
What has passed the staging boundary against this contract
1 batch · 18,200 arrived · 0 admitted · 18,200 quarantined · 0 rejected
| Batch | Arrived | In | Admitted | Quarantined | Rejected | Result | Gate |
|---|---|---|---|---|---|---|---|
| STG-0026 | Aug 17, 22:00 | 18,200 | 0 | 18,200 | 0 | Nothing admitted | No record cleared the gate. 18,200 are in quarantine and 0 were rejected outright. |
Rejects raised against these batches
1 reason covering 18,200 records. Each one names a field, what was observed and what the contract expected.
Replay windows
1 window recorded against this contract.
Write-back routes into this system
No write-back route is designed into this system.
A contract, a validation rule, a freshness commitment and a replay path are real mechanisms and they are what this wave builds. What they are not is a connection. No connector on this estate is attached to a customer instance, so every batch, every replay and every write-back attempt recorded here ran against a modeled extract or a sandbox, and the registry keeps saying modeled.
This contract has never been validated against a sample. Every type, every cardinality statement and every validation rule on this page is a declaration taken from documentation, not an observation. Its drift state is unknown rather than clean.