Understand email-open tracking limitations
Avoid treating a tracking-pixel request as conclusive proof that the intended recipient read the correspondence.
Exact navigationLetter Manager read-receipt evidence review
Before you begin
- Use an authorised account and confirm the customer, external recipient, template, letter or configuration is the intended one.
- Follow the exact route shown above and verify the stored record, generated file and delivery evidence instead of relying on an alert alone.
What this guide covers
Avoid treating a tracking-pixel request as conclusive proof that the intended recipient read the correspondence. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Exact step-by-step process
- Confirm the email was sent to the intended address.
- Review open count, time, IP source, user agent and proxy note together.
- Consider remote-image blocking, prefetching, privacy proxies and security scanners.
- Use stronger acknowledgement or e-signature evidence when legally required.
Fields, choices and supported possibilities
Action scopeAvoid treating a tracking-pixel request as conclusive proof that the intended recipient read the correspondence.
Module version1.0.0
Exact routeLetter Manager read-receipt evidence review
EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.
Code-backed validations and workflow rules
- A recipient can read an email without loading images.
- A proxy or scanner can load the pixel without a human reading it.
- The module does not establish unique-reader identity from the open event.
Expected result and verification
- The requested letter, template, setting, file or tracking detail is created or updated through the supported route.
- The history row, generated PDF, email/send metadata, public verification, signature evidence, client view or postal display agrees with the action.
- Any warning, missing file or failed send is investigated rather than bypassed.
Security, privacy and operational checks
- Apply least privilege and verify recipient identity before sending or exposing public links.
- Protect PDFs, enclosures, signatures, verification URLs, email-open metadata, IP addresses and customer data under organisational policy.
- Test configuration and deployment changes with controlled records before production-wide use.
- Interpret email opens and e-signatures according to their documented technical limitations.
Important code-backed limitationRead-receipt evidence is indicative, not definitive proof of human receipt or comprehension.