Figure 5 — Tri-Source Engagement Tracking and Correlation System

Source 1: Email Delivery Log
When email is sent to party
event_type: string
sent_at: datetime
recipients[ ]
— email: string
— role: string
— success: boolean
Populated by: sendOfferNotifications, sendCounterNotifications, etc.
Source 2: Tracking Pixel Events
When party opens email
viewer_email: string
event_type: string
fired_at: datetime
source: "email"
document_type: string
Populated by: trackEmailView function when pixel is loaded in email client
Source 3: Authenticated Portal View
When party logs in and views document
viewer_email: string
viewer_role: enum
viewed_at: datetime
source: "portal"
document_type: string
Populated by: front-end when party authenticates and opens document in portal
↓
↓
↓
Engagement Correlation Engine — Tri-Source Synthesis Per Party
1.Join email_delivery_log + pixel events + portal views by viewer_email
2.Match document_type to offer, counter_offer, amendment, or reinstatement array
3.Generate unified per-party engagement timeline with source attribution
4.Resolve gaps: if pixel fired → email was opened; if portal view exists → party authenticated and viewed
↓
Output: Unified Per-Party Engagement Timeline
Example timeline for one party (buyer_agent):
2025-03-15 10:15 AMEmail delivered [source: email_delivery_log]
2025-03-15 10:22 AMEmail opened [source: tracking_pixel]
2025-03-15 10:45 AMPortal view — document: offer [source: portal]
2025-03-16 09:30 AMPortal view — document: counter_offer [source: portal]
Single source of truth per party — supports litigation discovery, audit review, and engagement analytics.
Why This Matters (Patent Claim)
Prior systems track only email delivery, or pixel fires, or portal views in isolation. This system synthesizes all three sources into a single verified engagement timeline per party per document type. This enables: (1) unambiguous proof of document receipt, (2) detection of delivery gaps — email sent but not opened, or opened but not viewed in portal, (3) automated reminders triggered by detected gaps, and (4) a litigation-grade audit trail combining three independent verification methods.
Fig. 5 — Tri-Source Engagement Tracking and Correlation System. Three independent data sources are synthesized in real time: email delivery logs confirm transmission, tracking pixels confirm email opens, and authenticated portal views confirm document access. The Engagement Correlation Engine matches these events to document types and generates a unified timeline per party.