Interpret read count and timestamps
Follow this guide to review first open, last open and total detected image requests. 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 goAdmin Area → Letter Manager → Internal Full View; or customer profile → Letter History
Before you start
- 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 you’ll accomplish
Review first open, last open and total detected image requests. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Follow these steps
- Go to the letter’s Internal Full View.
- Check Email Open Count.
- Check First Opened At and Last Opened At.
- Compare repeated opens with the detailed email-open table when authorised.
- Do not equate open count with unique human readers.
Fields and options to review
Action scopeCheck first open, last open and total detected image requests.
Module version1.0.0
Exact routeAdmin Area → Letter Manager → Internal Full View; or customer profile → Letter History
EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.
Rules the system enforces
- Every valid pixel request increments email_open_count.
- The first timestamp is set only when previously empty.
- The opens table retains one event row per detected request.
How to confirm it worked
- 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.