History, delivery and read evidence

Understand email image-proxy opens

Interpret Gmail/Google and Outlook/Microsoft proxy evidence correctly. 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.

Audience: CRM staffPermission: Staff loginModule v1.0.0
Jump to steps
Where to goAdmin Area → Letter Manager → Email Marketing / Newsletter → History → Details
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

Interpret Gmail/Google and Outlook/Microsoft proxy evidence correctly. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Follow these steps

  1. Go to the recipient detail.
  2. Check Detected source and proxy note.
  3. Treat proxy IP and user agent as provider infrastructure rather than definitive recipient location when IMAGE_PROXY is shown.

Fields and options to review

Action scopeInterpret Gmail/Google and Outlook/Microsoft proxy evidence correctly.
Module version1.0.0
NavigationAdmin Area → Letter Manager → Email Marketing / Newsletter → History → Details
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.

Rules the system enforces

  • Google/Gmail or Microsoft/Outlook user-agent patterns are labelled IMAGE_PROXY.

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.