Flow B

Event → Receipt (Turning Actions into Proof)

Campaign activity generates events across channels:

• impressions
• clicks
• conversions
• on-chain actions

Each event is:

• signed locally
• timestamped
• streamed into a unified event layer

For every event, two receipts are generated:

• Usage Receipt records what data was used, under which policy, and at what privacy cost
• Result Receipt records anonymized outcomes such as reach and conversions

Only cryptographic commitments are stored on-chain. Detailed records remain in their original domains for audit.

Output: → verifiable, tamper-proof event records (VUR)