# Email marketing system > The operating system behind campaigns: consent, list, ESP, CRM, and analytics, and what fails when one piece is missing. - HTML: https://omentir.com/email-marketing-system - Markdown: https://omentir.com/email-marketing-system.md ## A system is the path a person takes through your tools An email marketing system is not a logo. It is the chain: someone consents, the consent is stored, a sender is allowed to use it, the CRM (if you have one) does not fight that fact, and you can see whether the mail did anything. Campaigns are what you publish on top. When the chain is broken, campaigns still go out. They just go to the wrong people or to nobody who can still receive them. [Salesforce](https://www.salesforce.com) often holds the CRM box. The ESP is a separate box even when one vendor sells both. Draw it on a whiteboard with five boxes: capture, consent record, ESP, CRM, analytics. Draw the arrows for subscribe, unsubscribe, bounce, and purchase. If an arrow is 'someone downloads a CSV on Thursdays,' that is the system. It will fail on a holiday. *Capture, consent, ESP, CRM, analytics. A Thursday CSV is not a system.* ## List and consent The list is every address you might send to, plus the fields that justify the send. Consent is a timestamp, a source, and a scope (newsletter versus SMS versus partner mail). Without scope, a checkout address becomes a weekly blast. Store consent in a place that both marketing and sales can see. A note in a Slack thread is not a record. Hygiene sits here too: hard bounces leave, role accounts (info@) get treated with care, and people who complain are suppressed everywhere, not only in the campaign they replied to. A system that only unsubscribes inside one ESP while the CRM keeps 'subscribed = true' will re-permission people by accident. ## ESP and CRM The ESP sends and holds templates, throttling, and mailbox-facing headers. The CRM holds ownership, deals, and the human follow-up. They should share an ID. They should share suppression. They should not both believe they are the only place a marketer may send from. Pick a system of record for marketing permission. The other tool reads it. If you have no CRM, the ESP is the record. That is fine for a publisher. It is cramped for a sales team. If you have no ESP, the CRM send button is a mailbox. That is fine for ten personal notes. It is not a system for a newsletter. Name which case you are in so you stop buying software for the other case. ## Analytics and the loop Analytics is tagged links, revenue or leads that can be tied to a send, and provider signals (complaints, Postmaster). The loop is using those to change the next audience or the next offer, not to decorate a slide. If UTM tags are optional, the system has a hole. If nobody looks at complaints except when Gmail blocks you, the system has no immune system. People are part of the diagram. A system without an owner for DNS, an owner for the calendar, and an owner for replies will look complete in software and still stall. Assign names. Software does not attend the post-send hour. ## Failure modes worth designing for A form that writes to the ESP but not the CRM. A purchase that writes to the CRM but not the ESP, so buyers keep getting abandon mail. An agency user who exports the list. A domain renewal that drops SPF. A second 'backup' ESP that still has last year's audience. Each of these is cheaper to prevent with a checklist than to discover from customers. When you add a new tool, update the diagram first. If you cannot say where unsubscribe goes, do not connect the tool. That rule alone keeps most systems from rotting. ## Related - [Small business email marketing](https://omentir.com/small-business-email-marketing.md) - [Ecommerce email marketing](https://omentir.com/ecommerce-email-marketing.md) - [Best email marketing software](https://omentir.com/best-email-marketing-software.md) ## Common questions **Is a customer data platform required?** Not for a small program. A CDP helps when many sources must agree on one profile. It becomes another box that can desync consent if you are not careful. Fix ESP and CRM sync before you add a third brain. **Where should the preference center live?** On a domain you control, fed by the system of record for permission, and honored by every sender. A preference center that only updates one ESP is decoration. [Create an Omentir account](https://omentir.com/signup). Pro is $49/month.