Understand newsletter database records
This guide explains that which campaign, recipient, delivery and open metadata is retained. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goCode-backed reference → Email Marketing & Newsletter installation schema
Before you start
- Use an authorised account and confirm the source CRM record or setting is correct.
- Follow the exact route shown above; do not force database values to imitate a completed action.
What you’ll accomplish
Know which campaign, recipient, delivery and open metadata is retained. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Follow these steps
- Check a campaign in Newsletter History.
- Go to Details to inspect recipient records.
- Use database access only for authorised diagnostics or retention work.
Fields and options to review
Campaign recordSubject, HTML body, total/sent/failed counts, status, creator and timestamps.
Recipient recordSource key/type/ID, recipient name/email, pending/processing/sent/failed state, error and sent time.
Tracking evidenceUnique tracking token, open count, first/last open, IP, source and user agent.
Rules the system enforces
- Campaign and recipient rows are related by campaign ID.
- Open evidence is updated by the public pixel endpoint.
How to confirm it worked
- The requested record, output or setting is created or updated through the supported module flow.
- Any related status, count, email, audit/event, PDF/file or queue evidence agrees with the source action.
- An error message is investigated rather than bypassed.
Security, privacy and operational checks
- Apply least privilege and verify the correct customer, lead, sales document or recipient before processing.
- Protect public tokens, recipient data, IP/browser evidence, templates and exported files according to organisational policy.
- Test configuration changes with controlled records before production-wide use.
- Retain or delete evidence only under an authorised retention process.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.