Understand newsletter open tracking
Know how the appended one-pixel image records email-client image requests.
Exact navigationPublic email-client request → email_marketing_newsletter/open/{recipient_id}/{tracking_token}
Before you begin
- 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 this guide covers
Know how the appended one-pixel image records email-client image requests. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Exact step-by-step process
- Send a campaign with the normal queue.
- Allow the recipient email client to load remote images.
- Open campaign Details.
- Review Open count, First open and Last open.
Fields, choices and supported possibilities
Action scopeKnow how the appended one-pixel image records email-client image requests.
Module version1.0.0
NavigationPublic email-client request → email_marketing_newsletter/open/{recipient_id}/{tracking_token}
EvidenceConfirm the stored record, status, output, email, event or log produced by the code path.
Code-backed validations and workflow rules
- A valid recipient ID and tracking token are both required.
- Every valid image request increments open_count and updates last_opened_at.
- First-open metadata is retained when the first valid request arrives.
- An open record proves the tracking image was requested; it does not prove that a human read or understood the entire message.
Expected result and verification
- 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.