What this template is for
Write the register before building or rebuilding a welcome series, before an email audit, and whenever a list diagnosis needs results by source and nobody can say which sources exist. Then keep it current: a new form, a new pop-up, a changed sentence beside a box, a new event or an import is a new or changed row before it goes live, not after. The register answers, once per source rather than once per address, the question the list building and consent guide asks of every subscriber: how they arrived and what they were told.
The register sits among documents that each own a part of the list, and it links them rather than repeating them. The list building guide's placements table says which offer suits each placement, and the tutorial on in-person sign-ups sets out each counter and phone capture point; the register records which of those the business actually runs. The consent map for the marketing stack has one row for email marketing across every tool; the register breaks that row down by source. A new sign-up form or changed opt-in wording reopens the email row of the consent mapOne table with a row per purpose the stack uses personal data for: where permission is captured, which system holds it and how a withdrawal reaches each tool. as well, because the capture point for that purpose has changed. The welcome series tutorial builds the flow the register's branches feed, the email marketing calendar template plans the sends that follow, and the nurture sequence plan template handles leads moving towards sales. The email list hygiene SOP processes bounces, complaints and unsubscribes after every send and checks inactive contacts and consent records once a month; the register's quality column reads the bounces, complaints and unsubscribes by source.
If one source has started losing subscribers fast, start from the unsubscribe spike diagnosis; if opens fell as the list grew, from the open rate diagnosis; if mail has moved to spam, from the diagnosis of emails going to spam. Each reads results by source as one of its checks, which is quicker with the register to hand.
The template
Copy the table into a spreadsheet, one row per source, with the field names as columns. Fill the first six columns when a source is added, before it goes live, and the rest as results come in. Keep a retired source as a row marked retired rather than deleting it, because the addresses it brought are still on the list.
| Field | What to write |
|---|---|
| Source and placement | Each form, checkout box, pop-up, download, counter, event or import that adds addresses, where it sits and who owns it |
| Wording and promise | The exact wording shown at sign-up, what the person was promised about content and frequency, and any offer given for signing up |
| Consent basis and record | The basis relied on for the source as agreed with whoever owns data protection, and the system that holds each address's consent record |
| Opt-in method | Single or double opt-in for the source and the reason, with the confirmation message and the expiry of unconfirmed addresses where double opt-in is used |
| Source value and fields captured | The source value and date written to the contact at capture, and any interest or preference fields the form collects |
| Offline and imported capture | For counters, events, phone and paper, how the address is captured and confirmed; for imports, where the list came from and what its people agreed to |
| Welcome branch | The welcome series branch the source enters, what its first email delivers and the exit checks that apply |
| Quality by source | Bounces, complaints, unsubscribes and engagement read by source and join month, and the signal that sends a source to review |
| Value by source | Contribution per subscriber by source from cohorts and, where a holdout exists, the incremental part |
| Status, owner and review | Live, paused or retired, the owner of the form or capture point, when the wording was last checked against the record, and the decision at review |
Above the table, write who keeps the register, usually whoever runs the email programme, and the date of the last change. Keep a dated screenshot of each source's form, sign or script beside its row, since the words a person saw belong to the record.
How to fill each section
Source and placement
List every place an address can join the list, one row per source rather than per channel: two pop-ups with different offers are two sources. The list building and consent guide gives the usual placements, from checkout and account creation to inline forms, exit overlays, the footer, post-purchase moments, events and gated resources, and the welcome series tutorial's own list adds lead magnet downloads, event registration and imported partner lists. Look for the sources nobody thinks of as sources: a checkout box, an integration with a booking tool, a partner promotion, a file from an old platform. Write where each sits, on which pages, devices or counters, and the person who can change it, because a source with no owner is the one whose wording drifts.
Wording and promise
Copy the exact wording shown at sign-up, the promise about content and frequency, and any offer. The list building guide puts most list churn down to a mismatch between the line beside the sign-up box and the mail that followed; a loose promise like "get our newsletter" commits to nothing, while a sentence that says what is sent and how often can be kept or broken. It also treats a download and ongoing marketing mail as two separate choices, and asks that the offer be the thing the newsletter actually delivers. Write the sentence word for word, the date it came into use and the offer, so a later reader can compare what was promised with what the list received. The in-person tutorial keeps each version of spoken lines and signs with its date for the same reason.
Consent basis and record
Write the basis relied on for the source, as agreed with whoever owns data protection, and the system that holds each address's record. The tutorial on mapping consent across the marketing stack records the data protection owner's decision for each purpose rather than making it, names the system that holds the record and traces how an unsubscribe reaches every tool that reads it; the register copies its email marketing row's system here. The list building guide sums up the GDPR's test for consent (given freely, specific, informed, unambiguous, provable, and no harder to withdraw than to give) and points to the direct marketing guidance from the UK regulator on when consent is required, when existing customers may be mailed about similar products without asking again (the soft opt-in) and the need for an opt-out in every message. The in-person tutorial adds, from that guidance, that the soft opt-in needs a chance to refuse when the customer bought. Record the basis per source as the owner decides it. Nothing here is legal advice; it is general direction.
Opt-in method
Write single or double opt-in for the source and the reason. The comparison of single and double opt-in chooses source by source: single opt-in suits a source where the address was verified moments before, such as checkout, and Double Opt-InA sign-up process in which the subscriber confirms through a link sent to the address given. suits open web forms, giveaways and referral rewards, sign-ups keyed in from paper or events, and any form exposed to bots. For double opt-in, write the confirmation message, which should go out at once, say what it is for and ask for a single action, and the period after which unconfirmed addresses expire. For single opt-in, write the protection the form carries instead: address validation, a prompt for misspelt domains and bot protection. Where the risk of a source is unclear, the double opt-in test splits its submissions between the two and reads email revenue per submission; record the result here.
Source value and fields captured
Write the value written to the contact at capture and any interest or preference fields the form collects. The segmentation guide lists sign-up source and date among the data worth keeping, for lifecycle stage, cohort comparison and re-permission by origin, and warns that they must be recorded at capture because they cannot be reconstructed later. Use a fixed list of values set automatically by each form, as the in-person tutorial does for counters, so the same source is named the same way every time. For interest fields, the guide's rule is to ask only for what will be used and keep the options few, and its preference segments come from the same fields as the Preference CentreA page where a subscriber chooses which messages, topics and channels they receive and updates their own details, instead of an all-or-nothing unsubscribe.. Write which field maps to which segment, and drop any field that maps to nothing.
Offline and imported capture
For counters, events, phone and paper, write how the address is captured and confirmed; for imports, where the list came from and what its people agreed to. The tutorial on collecting email sign-ups in person puts the address straight into the email platform, ideally typed by the customer themselves, records the location and how it was captured, and sends a confirmation before any marketing to any address staff typed, heard or copied. Trade stands and badge scanning follow the in-person event readiness checklist. For imports, the list building guide asks whether these people agreed to this sort of mail from this business, and whether that agreement can be shown: purchased lists almost never pass, exports from an old platform usually do when their consent records travel with them, and every import is staged in a holding segment and mailed in small batches before it merges. The tutorial on importing contact lists into the CRM sets the source value, checks suppression and keeps an import from overwriting existing records.
Welcome branch
Write the branch of the Welcome SeriesThe automated sequence of emails sent to a new subscriber in the days after sign-up. the source enters, what its first email delivers and the exit checks. The welcome series tutorial captures the source as a property at entry and builds branches on it rather than separate flows: a download leads with the download, a checkout opt-in skips the sell, an offer arrives in the first email and an event sign-up gets a reminder of what the person saw, with a default path for any source without its own branch. Entry waits for the confirmation click where double opt-in is used. Exits are checked before every send, with a purchase, an unsubscribe, a hard bounce or a complaint taking the person out. Write the first email's job in terms of the row's promise, so the welcome confirms that promise rather than making a new one.
Quality by source
Write bounces, complaints, unsubscribes and engagement by source and join month, and the signal that sends a source to review. The unsubscribe spike diagnosis pulls exits with the source recorded at joining and asks whether one source accounts for far more than its share; its fix moves that source into a holding segment with one re-permission message, and its prevention is to report unsubscribes per source every month. The open rate diagnosis compares clicks and opens across sign-up sources and join months, and the spam diagnosis compares the Spam Complaint RateShare of delivered emails that recipients marked as spam. by list source. Report List Growth RateNet change in an email list over a period as a share of its size at the start. by source too, as the in-person tutorial does, so a source whose many sign-ups mostly drop away cannot inflate the overall figure. Set the review signal from the business's own history, such as a source well above the rest, not from a benchmark.
Value by source
Write the contribution per subscriber for each source from cohorts and, where a holdout exists, the incremental part. The guide to valuing an email subscriber tracks cohorts grouped by join month and source, valued on contribution margin, measures what the programme adds by keeping a randomly chosen slice of new subscribers off marketing mail, and repeats both by source where volume allows. Where a source is too small for its own holdout, it applies the programme-wide ratio to the source's cohort value and records that as an assumption, and it counts the cost of subscribers who complain or leave within weeks, which can give a source with cheap sign-ups a negative value. Beside the value, write the sign-up rate the list building guide measures each placement by first; the conversion rate calculator turns impressions and sign-ups into that rate.
Status, owner and review
Write live, paused or retired, the owner, when the wording was last checked against the record, and the decision at the last review. The email programme audit collects every source with the wording it shows, and scores consent records as a gate that is passed only when the source, date and agreement behind every subscriber can be produced. Since the in-person tutorial treats the wording as part of the record, the check compares the live form with the stored wording and the record's source value. Review every row on a routine the team sets, and at once when a form, offer or platform changes. Record each decision with its reason: keep, rewrite the offer or wording, move to double opt-in, re-permission, pause or retire.
Filled example
Below, the register is completed for an invented business. It is shown with the fields as rows so that it fits the page; in the spreadsheet each source is a row. The sources, figures and dates are illustrative.
Zolirn Honey: email sign-up source register
Zolirn Honey is an invented honey producer selling online and from a weekend market stall, with a list of 9,600 subscribers and a twice-monthly letter of new harvests and recipes. The marketing lead keeps the register; the operations partner owns data protection. Results below are for January to June 2026, by join month, with 10% of new subscribers from every source held out of marketing email since January.
| Field | Checkout box | Footer form | Recipe booklet download |
|---|---|---|---|
| Source and placement | Unticked box at online checkout; owner: shop manager | Footer of every page; owner: marketing lead | Recipe pages; owner: marketing lead |
| Wording and promise | "Send me the honey letter: new harvests and recipes, twice a month." No offer | Same sentence; no offer | "Get the recipe booklet." Separate unticked box: "Also send me the twice-monthly honey letter" |
| Consent basis and record | Consent, as agreed with the operations partner; record in the email platform | As left | Consent for the letter only; the booklet is sent either way |
| Opt-in method | Single: the order confirmation has already verified the address | Double; unconfirmed addresses expire after 14 days | Double; same expiry |
| Source value and fields captured | checkout, with date | footer, with date; interest: recipes or harvests | booklet, with date |
| Offline and imported capture | Not applicable | Not applicable | Not applicable |
| Welcome branch | Customer branch: story and proof, no sell | Default branch | Booklet branch: booklet first, recipes next, products after |
| Quality by source | Complaints 0.02% per send; unsubscribes 0.3% | Complaints 0.03%; unsubscribes 0.5% | Complaints 0.04%; unsubscribes 0.6%; opens lowest of the three |
| Value by source | Highest per subscriber over 6 months; holdout shows most of it incremental | About half the checkout figure | About a third of the checkout figure, still positive |
| Status, owner and review | Live; wording checked 2 June; keep | Live; checked 2 June; keep | Live; checked 2 June; add the letter's frequency to the download page |
| Field | Market stall tablet | Summer giveaway | Old shop platform import |
|---|---|---|---|
| Source and placement | Tablet form on the stall; owner: stall manager | Hamper giveaway on the shop's social page; owner: marketing lead | 2,140 subscribers moved in March 2026; owner: marketing lead |
| Wording and promise | Sign on the stall: who sends, what, twice a month, unsubscribe in every email, privacy notice link | "Enter to win a hamper." Separate box: "Also send me the honey letter" | Old forms' wording, exported with each record |
| Consent basis and record | Consent; record in the email platform with location | Consent; email platform | Records carried over from the old platform, checked by the operations partner |
| Opt-in method | Double; confirmation names the stall and the date | Single at launch; double from 1 July | Not applicable; staged instead |
| Source value and fields captured | stall, with date and how captured | giveaway, with date | import-oldshop, with original sign-up date |
| Offline and imported capture | Customer types own address; staff never type | Not applicable | Holding segment, 4 batches over 2 weeks, merged after bounces and complaints matched the list |
| Welcome branch | Stall branch: thanks for the visit, stall dates | Offer-free default branch | None; joined the regular letter after staging |
| Quality by source | Complaints 0.03%; unsubscribes 0.4% | Hard bounces 4.8% on first send against 0.4% for the list; complaints 0.31%; unsubscribes 2.9% | In line with the footer form after staging |
| Value by source | Close to the checkout figure | Negative in its first weeks after complaint and hygiene costs | About half the checkout figure |
| Status, owner and review | Live; sign checked 7 June; keep | Paused 18 June, moved to double opt-in; past entrants sent one re-permission message | Closed source; keep as a row |
The giveaway brought 1,350 addresses in 3 weeks, more in those weeks than any other source, and the sign-up rate from the conversion rate calculator looked like its best result. By its first send it had the most bounces and complaints of any source. The marketing lead paused it, moved its past entrants into a holding segment and sent one re-permission message; 38% confirmed and the rest were suppressed. The next giveaway ran with double opt-in and a confirmation that named the prize and the letter, and its complaints matched the footer form's.
Common mistakes
- Sources nobody listed. A checkout box, an integration or an old import adds addresses like any form. List every route, not only the visible forms.
- Wording that changed without the record. A form edited later no longer matches what earlier sign-ups saw. Date every version and check the live form at each review.
- A download treated as a subscription. Keep the resource and the letter as separate choices.
- One opt-in method for every source. Choose by the risk each source carries and write the reason.
- Source values typed by hand. Free text drifts. Set a fixed value from each form.
- Imports merged straight into the list. Hold each import in a separate segment first and note where it came from.
- Every source in one welcome branch. The source says what the person wanted; branch on it.
- Judging sources by sign-ups alone. Read quality and value by source before a source is grown.
- The register deciding the basis. Whoever owns data protection decides; the register records the decision.
The email marketing calendar, the nurture sequence plan and the other programme documents are in the templates library.
