Understand Email Marketing & Newsletter limitations
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Follow this guide to use only the functions present in module v1.0.0.
Where to goAdmin Area → Letter Manager → Email Marketing / Newsletter
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
Use only the functions present in module v1.0.0. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Follow these steps
- Use the module for bulk email, queue processing, history and open-pixel evidence.
- Use Letter Manager separately for letters/PDFs.
- Use the normal CRM for consent, suppression, templates and SMTP administration.
Fields and options
Action scopeUse only the functions present in module v1.0.0.
Module version1.0.0
NavigationAdmin Area → Letter Manager → Email Marketing / Newsletter
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.
Rules and limits
- No campaign cancel, pause, resend-failed, export, attachment upload, unsubscribe processor, bounce mailbox, API, webhook or dedicated staff capability is implemented in the supplied code.
- No Letter Manager PDF or Letter History record is created.
- Open tracking depends on remote-image loading and may be blocked or proxied.
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.
Important code-backed limitationDo not describe a missing control as available. Use only the code-backed functions documented in this section.
Related guides
Was this guide useful?Your response is stored only in this browser.