Understand recipient deduplication
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Prevent duplicate delivery where the same email address is represented by more than one selected CRM record.
Where to goAdmin Area → Letter Manager → Email Marketing / Newsletter → Review selection
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 this guide helps you do
Prevent duplicate delivery where the same email address is represented by more than one selected CRM record. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Follow these steps
- Select the required contacts, leads or groups.
- Check the Selected estimate.
- Start the campaign.
- Go to campaign Details and confirm one recipient row per unique email.
Fields and options
Action scopePrevent duplicate delivery where the same email address is represented by more than one selected CRM record.
Module version1.0.0
NavigationAdmin Area → Letter Manager → Email Marketing / Newsletter → Review selection
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.
Rules and limits
- The directory may contain separate source records, but campaign creation indexes validated recipients by normalised email address.
- The last validated selected entry for a duplicate email becomes the stored recipient identity; only one message is queued for that email.
Check 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.
Related guides
Was this guide useful?Your response is stored only in this browser.