# Read event analytics without turning views into attendance

Original constructed teaching cases, not real accounts, participants or customers.

## Case 1

A1 — Constructed report: 120 unique event visits and 30 native registrations during the same declared window. Arithmetic gives 30/120 = 25%, but no matched visit-to-registration path was supplied. Decision: report both counts; label the quotient only as an unmatched descriptive ratio if retained. Result: no verified visitor conversion or physical attendance rate.

## Case 2

A2 — Constructed video: 240 qualifying views, 150 lifetime viewers and a peak of 40 concurrent viewers. Decision: preserve three units and the video source; do not add them or describe 240 distinct attendees. Result: a bounded video summary with completion, live/replay membership and registration linkage still unknown.

## Case 3

A3 — Constructed missing audience panel: an event report has no usable demographic breakdown. Decision: retain “not available” and the actual help/account context, rather than inserting zero or inferring the audience from speaker identities. Result: no fabricated demographic statement, and no collection of private attendee data to fill the gap.