Costs
Part of What an Email Marketing Template Actually Needs
Email marketing templates sections: the permission record
Email marketing templates sections for permission: the record that shows why each person received a message, tied to the exact send and to suppression.
What to take away
- The permission section answers one question for any recipient: why did this person receive this message?
- Store the audience source, basis, notice, action, date, topics, sending entity, market, preferences, and suppression in one controlled record.
- Link that record to the audience query and the exact send, so the basis can be shown for the version that went out.
- Use role-based views for occasional reviewers, but keep one traceable record.
Why this person received this message
A permission record exists to answer a single question about a single recipient: why did this person receive this message? If the answer needs a search through inboxes and spreadsheets, the template does not hold the section it needs.
Permission record fields
- Template ID and message class
- Purpose and audience need
- Sender entity and recipient market
- Consent or permitted basis
- Source, proof, notice version
- Preference, suppression, frequency
- Reviewer and review scope
Here, "email marketing templates sections" means connected records, not only the visible content modules. The permission section sits beside the audience, content, and approval records, and each of them points back to it.
The fields of a permission record
Each field below answers a question that a reviewer, a complaint, or a regulator can ask later. Keep the fields in the template, as required entries, so a blank one is visible before the send and not after it.
| Field | What it holds | Question it answers |
|---|---|---|
| Source | Where the address came from | How did we get it? |
| Basis | Consent or another permitted basis | What lets us send? |
| Notice | The version shown at collection | What was the person told? |
| Action and date | The sign up or purchase and when | What did they do, and when? |
| Topics | What the person agreed to receive | Is this message in scope? |
| Entity and market | Who sends, and where the person is | Which rules apply? |
| Preferences | Choices the person has made | What did they ask for? |
| Suppression | Addresses that must not be mailed | Who is excluded? |
Required fields work best when they enforce a decision, which is the point of marketing plan templates. A send should not be schedulable while the basis field is blank.
Which rules apply
The rules differ by market, so the record names the market for every address. Use the current guidance for the market you send to and never treat one country's rule as a global permission rule.
The UK Information Commissioner's Office, in its electronic mail marketing guidance, says you must not send marketing emails or texts to individuals without specific consent, with a limited exception for your own previous customers, often called the soft opt-in. The record must therefore show which of the two applies.
For U.S. commercial email, review the CAN-SPAM Act and the Federal Trade Commission's compliance guidance. The record should capture recipient type, message purpose, identity, and opt-out handling, which are the contextual questions the guidance raises.
Preferences and suppression
An opt-out is a record change with a deadline. The FTC's CAN-SPAM compliance guide says you must honor a recipient's opt-out request within 10 business days, so the suppression list has to reach every sending path in time.
Synchronize suppression across the provider, the automation tool, and any export used for another channel. Record the date each change was made and who made it. A suppression held in only one tool is a suppression the others will ignore.
Tie the record to the exact send
Permission is judged at the moment of the send, so the record must be tied to that moment. Preserve the audience query, the basis it relied on, the sender, the content version, the rule version, and the variant that went out.
The audience query is where planning meets permission. How a plan defines its audience fields is covered in marketing plan template sections, and the campaign's intended audience starts in the campaign brief template sections. The permission record then shows which of those people could be mailed.
Borrowed templates and their fields
A borrowed email template arrives with another sender's permission fields, or with none at all. Map every field to your own record before reuse, and delete any field you cannot fill truthfully. Vetting a free file is covered in free marketing plan templates, and the same tests apply here.
Give each required field an owner, an allowed value, and a review rule, as the marketing plan template checklist does for plan fields. A field with no owner is a field nobody will correct when the audience source changes.
Views for occasional reviewers
Not every reviewer needs every field. Give the requester, reviewers, and publisher role-based views, so occasional reviewers are not faced with a wall of technical fields, while the complete governed record stays in one place with its source evidence, approvals, and change history.
After the send, store the counts and the evidence in a form the reporting side can reuse, as laid out in marketing report template sections. Keep corrections and incidents with the same record.
Common questions
Where should permission evidence live?
In a controlled record linked to the audience query and the exact send, with source, notice, action, date, topics, entity, market, preferences, and suppression.
Does consent from one market cover another?
No. The record names the market for each address, and the rule that applies is the one for that market, checked against current guidance and local review.
What should remain after the email is sent?
The audience definition, the basis relied on, the sender settings, the approvals, the responses, the suppressions, and any correction. Remove nothing that a later question about that send would need.
