Items: content IDs, content type, title, slug, summary, body, status, visibility, priority, categories, tags, calls to action, related record references, publication timestamps, author and workflow identifiers
Purpose: content publishing, editorial governance, placements, customer experience
Retention: Workspace-scoped records persist with content lifecycle and maintenance operations.
Items: campaign IDs, names, types, objectives, goals, channels, assets, stages, runs, statuses, schedule timestamps, audience bindings
Purpose: campaign planning, execution, coordination, measurement
Retention: Campaign records persist with workspace campaign history and related operational records.
Items: event content IDs, occurrence IDs, registration records, guest counts, waitlist state, attendance state, reminder state, feedback
Purpose: event registration, capacity management, attendance, reminders, feedback, analytics
Retention: Event operational records persist with the workspace event and reporting history.
Items: promotion IDs, promotion codes, claim IDs, claimant identifiers, claim status, claim event history
Purpose: promotion claims, claim tracking, conversion measurement
Retention: Promotion and claim records persist with promotion lifecycle and reporting history.
Items: provider application ID, provider connection ID, audience catalogue metadata, category metadata, selected audience identifiers, provider configuration
Purpose: provider discovery, audience selection, provider access
Retention: Provider configuration persists while the workspace integration remains configured.
Items: snapshot IDs, selection IDs, provider identifiers, member identifiers, normalized names, eligible channel addresses, deduplication fields, snapshot counts, status and timestamps
Purpose: frozen targeting, visibility, campaign execution, audit
Retention: Snapshots persist as workspace-scoped engagement records until removed by workspace operations.
Items: secure-file provider IDs, file IDs, media type, purpose, caption, alt text, content bindings, delivery metadata
Purpose: content presentation, attachments, secure file delivery
Retention: EngagementHub retains file references while related content and bindings exist.
Items: session IDs, analytics events, views, clicks, conversions, registrations, attendance, claims, channel totals, daily totals, attribution events
Purpose: engagement analytics, campaign measurement, reporting
Retention: Raw and aggregate analytics remain workspace-scoped and are subject to maintenance operations.
Items: application grants, integration connections, Bridge profiles, replay and rate state, event inbox and outbox records, communication queues, delivery outcomes, webhook deliveries, activity logs, job attempts, dead letters
Purpose: authorization, reliability, integration, audit, operations
Retention: Operational records persist according to queue completion, retry, audit and maintenance behavior.
