A connected course guide
35,320 words of teaching, with 37 glossary terms and 42 sources in the complete guide.
Open the course wikiOnline · Self-paced · By Bow Tie Kreative
Email marketing course
Send email people understand and expect.
Design an email relationship around a clear promise. Learn to segment for a useful reason, plan a welcome sequence, understand authentication, and give automations sensible entry and exit rules.
Included in both lifetime memberships. Already a member? Open this course.
136 visual lessonsWiki + PDF + workbook
- Lessons
- 136
- Course guide
- 166 pages
- Workbook
- 187 pages
- Glossary
- 37 terms
The idea, made clear
What is email marketing?
Email marketing uses messages to continue a relationship with people who expect that communication. Effective planning connects permission, relevant content, reliable delivery, and a useful next step. Measurement must account for the limits of delivery and engagement signals.
What you’ll learn to do
Write a specific signup promise and choose meaningful segments.
Build a welcome sequence around the reader’s next task.
Explain the purpose of sender authentication and review delivery signals.
Define entry, exit, and stop rules before running an automation.
Your learning path
Inside the 136 lessons
Each lesson connects a focused idea to practice and an explanation. Chapter links open the matching course wiki section. Sign in with course access to read the complete guide.
- Wiki chapter
Set the expectation
Make the purpose and frequency of an email relationship understandable.
- Wiki chapter
Keep the relationship useful
Make messages understandable and recipient control easy to find.
- Wiki chapter
Make the signup promise specific
Explain what subscribers will receive and how they can change their choice.
- Wiki chapter
Segment by a useful, supported difference
Choose groups that change the message without inventing personal traits.
- Wiki chapter
Build a welcome sequence that keeps the promise
Deliver the requested value before asking for additional actions.
- Wiki chapter
Write one message around one reader task
Align subject, body, action, and destination.
- Wiki chapter
Understand sender authentication
Explain the different jobs of SPF, DKIM, and DMARC at a practical level.
- Wiki chapter
Give automations entry, exit, and stop rules
Design a message workflow that reacts correctly when a person’s state changes.
- Wiki chapter
Interpret engagement and delivery signals carefully
Separate opens, clicks, delivery issues, and business outcomes.
- Wiki chapter
Run a pre-send and post-send review
Check audience, content, links, controls, and evidence before scaling.
- Wiki chapter
Start with the promise made at signup
A useful marketing message fits what the recipient was told to expect, and a stored address alone does not establish permission for every use.
- Wiki chapter
Plan what happens after the form
Acquiring a subscriber and serving that subscriber after signup are different jobs that need connected plans.
- Wiki chapter
Keep the service message true to its job
A service email's actual content and primary purpose matter; adding promotion can change how the message must be treated.
- Wiki chapter
Make stopping persist
When a program stops marketing to a contact or receives an opt-out, that state must remain effective across later campaigns and launches.
- Wiki chapter
Say exactly what will stop
Ending marketing messages and closing a product account are different actions and require accurate, separate explanations.
- Wiki chapter
Review the tracking purpose separately
Permission or another basis to send an email does not automatically settle the separate requirements for tracking pixels or website behavior.
- Wiki chapter
Carry the offline promise into the record
Offline interactions can inform relevant follow-up only when the contact information, promise and applicable permission are accurately recorded.
- Wiki chapter
An address is not an invitation
Buying, scraping or discovering an email address does not by itself establish permission for the intended marketing relationship, and can conflict with provider policy and recipient expectations.
- Wiki chapter
Make a referral worth receiving
An incentive can encourage sharing, but a referral program still needs relevant participants and an appropriate basis for contacting each invited person.
- Wiki chapter
Describe the person and the moment separately
A persona summarizes a group's needs, while a journey describes changes in context or readiness; one does not substitute for the other.
- Wiki chapter
Read the request, not just the referral
An acquisition channel does not by itself establish a subscriber's intent or readiness for an offer.
- Wiki chapter
Decide what the email should deliver
The resource being offered and the channel delivering its invitation are separate design decisions.
- Wiki chapter
Make the next action earn its place
An email's main requested action should follow logically from the reader's current task and the message's promise.
- Wiki chapter
Choose the moment from the reader's side
A useful sending time follows the recipient's task, urgency and time context rather than the sender's convenience or a universal best hour.
- Wiki chapter
Move the relationship, not just the address
Contact exports can support provider portability only when subscription status and relevant permission records remain attached to the data.
- Wiki chapter
Separate the standard from inbox access
Email uses interoperable transport standards, but successful sending still depends on providers, mailbox policies and operational configuration.
- Wiki chapter
Test the provider against the job
An email service provider should be selected against the program's actual requirements, constraints and operator skills rather than a universal ranking.
- Wiki chapter
Make a migration case before moving
A provider migration should solve a demonstrated limitation whose expected benefit justifies the transition cost and risk.
- Wiki chapter
Give every integration a reason
Connecting an email provider to another system should transfer the data needed for a defined task, with appropriate permission and tested meaning.
- Wiki chapter
Verify the connection you actually need
An intermediary connector can bridge some systems without a direct integration, but supported events, actions and limits must be verified.
- Wiki chapter
Create a segment only when it changes the work
A useful segment groups contacts whose relevant evidence calls for a different message or treatment; more segments are not automatically better.
- Wiki chapter
Keep a guess separate from a stated choice
A preference explicitly provided by a person and an interest inferred from behavior have different evidential strength and should be stored and used accordingly.
- Wiki chapter
Know which record wins
Coordinated communication needs clear ownership of customer facts and status, even when records are distributed across several systems.
- Wiki chapter
Give a tag one clear meaning
A tag can represent membership in a defined category or a recorded yes-or-no state, but its absence is meaningful only if tagging is reliable.
- Wiki chapter
Store the value in a form you can use
Values such as dates, amounts and selected preferences should be stored in suitable structured fields when the program needs to compare, sort or update them.
- Wiki chapter
Make labels understandable six months later
A shared naming convention and a bounded set of categories make tags and fields easier to maintain than ad hoc or extremely granular labels.
- Wiki chapter
Make each question earn its place on the form
Each form field should justify the effort it asks of the user through a defined need or benefit; more fields can reduce completion without improving the program.
- Wiki chapter
Remember what was requested without overreading it
The resource requested and page where a form is submitted can provide useful context, but they do not conclusively establish skill, identity or lasting preferences.
- Wiki chapter
Offer a reason to answer the questions
A survey or quiz can gather declared preferences when its purpose, effort and benefit are clear to the participant.
- Wiki chapter
Follow the answer into the record
A form or survey integration should be tested from a submitted response through the final contact record before it controls communication.
- Wiki chapter
Make the preference choice visible
A link used to collect a preference should clearly explain the choice and lead to a relevant, understandable result.
- Wiki chapter
Choose one favorite or several interests
A preference model must specify whether a new selection replaces an earlier value or adds another interest.
- Wiki chapter
Know which visits can be connected
Associating website activity with a subscriber requires supported tracking and a reliable way to identify that contact; an email address in a database does not reveal every visit.
- Wiki chapter
Label the event you actually observed
A recorded page view can show that a page was requested, but it does not prove that its content was read or understood.
- Wiki chapter
Read the segment as a sentence
Combining segment conditions with AND requires all conditions to match, while OR includes contacts matching any listed condition.
- Wiki chapter
Know when the audience is evaluated
A rule-based segment can change as contact data changes, while an exported or fixed audience snapshot represents a particular point in time.
- Wiki chapter
Inspect who the rule actually selects
A segment should be checked with known included and excluded records before it is used for sending.
- Wiki chapter
Plan for the person who matches no branch
A personalization workflow needs an intentional fallback for missing, unrecognized or conflicting preferences.
- Wiki chapter
Localize what actually changes for the reader
Location and language can improve relevance when they are accurate, appropriate to use and connected to a real difference in the message.
- Wiki chapter
Do not let an imported guess become a fact
Third-party enrichment is another data source to evaluate for purpose, accuracy and lawful use, not automatic proof of a subscriber's attributes or permission.
- Wiki chapter
Label the creative, not the person
Campaign tracking parameters should use nonpersonal identifiers rather than subscriber details or personalized subject text that could expose personal information.
- Wiki chapter
Write the event and response separately
An automation begins from a defined event or condition and performs explicit actions; the event and the action are different parts of the rule.
- Wiki chapter
Automate the record when no message is needed
An automation action can update data or coordinate another workflow without sending an email.
- Wiki chapter
Decide what a second trigger should do
Several valid events can enter one workflow, but overlapping events require an explicit rule for duplicate entry and re-entry.
- Wiki chapter
Specify both the wait and the clock
An elapsed waiting period and a permitted sending window impose different timing conditions on an automation.
- Wiki chapter
Make every branch answer a precise question
A workflow decision routes contacts according to a defined condition evaluated at a particular point in the flow.
- Wiki chapter
Let completed work stop the reminder
A delayed follow-up should be skipped or redirected when the recipient has already completed its purpose or is no longer eligible.
- Wiki chapter
Test the behavior behind the diagram
Different automation designs can implement the same intended behavior, so correctness should be tested against outcomes rather than a copied diagram.
- Wiki chapter
Check whether actions really can run together
Parallel workflow actions should be used only when their independence and combined effects are understood.
- Wiki chapter
Give automation a working pause button
Automated content needs an operational way to pause or change when external events make the planned message inappropriate or inaccurate.
- Wiki chapter
Make access true before saying it is ready
An access email should follow confirmed provisioning, because sending a message does not itself enroll a user or change product access.
- Wiki chapter
Test the event across the boundary
A webhook integration works only when the receiving endpoint can interpret the event data and reliably perform the intended downstream action.
- Wiki chapter
Find the right account before acting
An automation must resolve the correct account identifier before making an account-specific change, and ambiguous matches need a safe exception path.
- Wiki chapter
Decide what completed actually means
A completion marker must be set by evidence that satisfies the defined requirement; submitting a form is not necessarily passing an assessment.
- Wiki chapter
Count the inbox from the reader's side
Frequency decisions must consider the recipient's total messages across workflows, because several individually reasonable sequences can create an overwhelming combined schedule.
- Wiki chapter
Decide which message wins
When campaigns compete for the same recipient, explicit eligibility and priority rules make the next message more predictable than independent sequences competing without coordination.
- Wiki chapter
Give a temporary pause a reliable ending
A temporary campaign block needs defined ownership and cleanup on every exit, so it neither persists forever nor gets removed while another valid block remains.
- Wiki chapter
Choose the purpose before the send mechanism
A campaign's purpose and its delivery mechanism are separate decisions; a related series may use scheduled broadcasts, event-driven messages or both.
- Wiki chapter
Meet the moment of the request
A welcome or access response should arrive when it is useful after the initiating request, rather than inherit an unrelated promotional schedule.
- Wiki chapter
Help the newcomer do one useful thing
Onboarding should help a new user complete a meaningful first action, chosen for the value the product or service is meant to provide.
- Wiki chapter
Give every message a separate job
A longer onboarding or educational series is justified only when its additional messages serve distinct needs and produce useful incremental value.
- Wiki chapter
Decide what participation means here
Engagement should be defined as behavior meaningful to the particular service, rather than assumed from email opens or a fixed purchase frequency.
- Wiki chapter
Define inactivity before reacting to it
An inactivity threshold should reflect the product's normal use cycle and reliable signals, rather than a universal number of days or missing opens alone.
- Wiki chapter
Make returning useful to the recipient
A re-engagement message should offer a relevant reason to return and a clear action, with a finite plan if the person does not respond.
- Wiki chapter
Choose the audience before the broadcast
A scheduled broadcast can be appropriate when a shared message is relevant to an eligible audience; scheduling alone does not make it spam or justify sending to everyone.
- Wiki chapter
Ask a question someone will answer
Inviting replies can produce useful customer feedback when the sender has a monitored inbox and a plan to handle the responses.
- Wiki chapter
Check whether the message can age safely
Reusable newsletter sequences need durable content and periodic review, while time-sensitive news should use a schedule that matches its actual relevance window.
- Wiki chapter
Give the newsletter a reason to exist
A newsletter earns coherence by selecting content for a defined reader need rather than including everything the organization has recently produced.
- Wiki chapter
Offer a smaller subscription and a complete exit
A preference center can let recipients choose topics or frequency, but it should not obstruct a clear option to stop all applicable marketing.
- Wiki chapter
Remind at the likely point of need
A replenishment reminder should use a plausible consumption cycle and current purchase context rather than a universal delay after purchase.
- Wiki chapter
Help the customer make a renewal decision
A renewal or upcoming-charge message should clearly communicate the relevant terms, timing and available account actions.
- Wiki chapter
Explain what the feature helps someone do
Product features become persuasive information when the message explains how they help the particular reader's task, without promising unsupported results.
- Wiki chapter
Add preparation only when it helps the decision
A preparatory message can help an audience understand an upcoming offer when it supplies genuinely needed context, but extra preliminary emails are not always necessary.
- Wiki chapter
Pay off the question you raise
A teaser or continuing story should set an honest expectation and deliver the promised resolution without withholding information needed for a current decision.
- Wiki chapter
Use a deadline only when it is real
A deadline should describe a real, clearly defined limit whose terms and expiry behavior match the message.
- Wiki chapter
Let evidence support the decision
Testimonials, results and customer examples should be authentic, relevant to the reader's decision and presented without unsupported implications about typical outcomes.
- Wiki chapter
Make the trial understandable before it starts
A time-limited trial should explain access, duration, completion requirements and what happens afterward before a person relies on it.
- Wiki chapter
Test the person on the boundary
A qualification rule should match the service's actual fit criteria and define its boundary and alternative path clearly.
- Wiki chapter
Name the kind of additional offer
A cross-sell offers a complementary item, while an upsell offers a higher-value version or tier; neither inherently requires a short deadline.
- Wiki chapter
Offer the next item only when it fits
A recent purchase is a relevance signal for an additional offer, not proof that every buyer wants or can use another product immediately.
- Wiki chapter
Count what remains after the discount
A discount can increase response while reducing contribution per order, so an incentive should be evaluated against costs and the intended customer outcome.
- Wiki chapter
Let a paused checkout be a paused checkout
A cart event alone does not establish abandonment; define meaningful inactivity and check a permitted contact path before sending a reminder.
- Wiki chapter
Help the person continue where they stopped
A useful reminder gives recipients enough accurate context and a working route to resume the unfinished task without recreating unnecessary effort.
- Wiki chapter
Finish what the email sends people to
A campaign is not ready when the email alone is finished; its promised resources, offer terms and destinations must also be ready and consistent.
- Wiki chapter
Continue the relevant conversation on the page
A known, appropriate subscriber preference can guide website copy after an email click, provided the page has a useful fallback when that preference is unavailable.
- Wiki chapter
Test the task with your thumb
A mobile-friendly email must let readers understand and complete the intended task on a small screen, including the linked destination.
- Wiki chapter
Check the message where it will be read
Email clients can render the same message differently, so important layouts need testing in representative receiving environments.
- Wiki chapter
Let the message survive missing pictures
The essential message and action should remain understandable when images are unavailable.
- Wiki chapter
Review the message without the layout
When an email has a plain-text alternative, that version should preserve the essential information and usable destinations rather than be an unchecked byproduct.
- Wiki chapter
Make the subject a promise you keep
A subject line should accurately signal the message's useful content or action, with curiosity and urgency limited by what the email actually delivers.
- Wiki chapter
Use the second inbox line deliberately
Preview text can complement a subject line with useful context, while leaving it unset can expose unhelpful text from the message.
- Wiki chapter
Make the important meaning findable
Clear hierarchy, short coherent paragraphs and descriptive action labels help readers find the message's meaning without reading every word.
- Wiki chapter
Review the suggestion before accepting the edit
An editing aid can flag language problems, but its suggestions still require human review for meaning, factual accuracy and necessary conditions.
- Wiki chapter
Let the situation guide the voice
An email's tone should fit the audience and situation while remaining recognizable and clear across the service experience.
- Wiki chapter
Give scanners a useful final line
A postscript can restate the main point for scanning readers, but important terms must remain clear in the main message.
- Wiki chapter
Check what a recipient will receive
Before sending, a campaign needs a check of its actual text, destinations, offer details and audience-specific values rather than approval of the draft alone.
- Wiki chapter
Let the button explain the next step
A call-to-action label should tell the reader what action or destination to expect, using language consistent with the message and the next screen.
- Wiki chapter
Repeat a useful action when the reading path needs it
Repeating the same main action can help readers at different points in a longer message, while adding unrelated actions can fragment the decision.
- Wiki chapter
Make responsibility and terms easy to find
A message should make the responsible sender and essential contact or offer information easy to find; a footer does not make concealed material terms adequately clear.
- Wiki chapter
Look beyond the contact total
Subscriber count alone cannot establish the value of an email program; relevance, permission and useful outcomes also matter.
- Wiki chapter
Choose a measure that can change a decision
Email measurement should connect a small, decision-useful set of metrics to the specific task being supported.
- Wiki chapter
Compare the next useful customer relationship
Repeat-customer offers may avoid some acquisition work, but their economic value still depends on incremental response, service costs and incentive costs.
- Wiki chapter
Name the satisfaction signal precisely
A standardized recommendation score, a star review and an actual referral measure different things and should not be treated as interchangeable.
- Wiki chapter
Follow the task beyond the click
Improving email outcomes can require changes to the offer, message, destination or service experience, not only the button or subject line.
- Wiki chapter
Find out whether the real-world task happened
When the desired action occurs outside observable systems, an email program needs a proportionate feedback method before claiming that the action happened.
- Wiki chapter
Name what the customer-value number measures
Historical spend is a useful commercial measure, but it is not identical to customer profit, future lifetime value or loyalty.
- Wiki chapter
An open event is not a reading certificate
Tracked opens are technical signals affected by image loading and privacy features, so they cannot establish that a person read or ignored a message.
- Wiki chapter
Check who may have followed the link
Recorded email clicks can include security scanning and other automated activity, so a click alone is not conclusive evidence of human intent.
- Wiki chapter
Read both numbers in the fraction
A count measures the number of events or people, while a rate divides a specified numerator by a specified population; increasing list size alone does not raise the rate.
- Wiki chapter
Know what the click percentage is divided by
Click rate and click-to-open rate use different denominators, and a click-to-open ratio inherits the uncertainty of the tracked-open denominator.
- Wiki chapter
Write down what counts as success
A conversion metric needs a defined completed action, measurement window, eligible population and attribution rule to be interpretable.
- Wiki chapter
Credit is not the same as cause
Revenue attributed to email is not automatically revenue caused by email, and neither attributed revenue nor sales count alone establishes profit or return on investment.
- Wiki chapter
Learn from the exit without fighting it
Unsubscribes and complaints are useful negative signals, but their meaning should be investigated by campaign and audience rather than reduced to a universal quality score.
- Wiki chapter
Give campaign visits consistent labels
Consistent campaign parameters help attribute website visits to email activity, provided the destination preserves the labels and the analytics system is configured to collect them.
- Wiki chapter
Make a test answer one useful question
A campaign experiment is easier to interpret when it compares equivalent eligible groups, changes a defined factor and uses a preselected outcome and observation window.
- Wiki chapter
Read the failure before retrying
Hard bounces indicate permanent delivery failures and soft bounces typically indicate temporary failures, but the actual reason and provider policy determine the appropriate handling.
- Wiki chapter
Delivered is one checkpoint
A successful delivery report generally indicates acceptance without a reported bounce, not proof of inbox placement or human reading.
- Wiki chapter
Verify the identity behind the From line
A recognizable From address does not replace technical sender authentication; the sending domain and provider must satisfy applicable SPF, DKIM and DMARC requirements.
- Wiki chapter
Treat a spam score as a clue
Email filtering reflects multiple receiver-specific signals, so a keyword checklist or a single test score cannot guarantee that a message reaches the inbox.
- Wiki chapter
Repair the process behind the trap signal
Spamtrap evidence calls for examining acquisition and list-maintenance practices, because traps have multiple origins and removing a guessed address does not fix the underlying process.
- Wiki chapter
Start with the rules that apply to this send
Email compliance depends on applicable jurisdiction, message purpose and recipient context; US CAN-SPAM and Canadian CASL are different regimes, and provider rules may add requirements.
- Wiki chapter
Test the exit all the way through
An unsubscribe mechanism must be easy to use and must reliably stop the applicable future marketing across connected sending paths.
- Wiki chapter
Check the technical unsubscribe mechanism
For senders subject to Gmail's bulk requirements, eligible marketing messages need the specified one-click unsubscribe mechanism as well as a visible body link; an ordinary footer link alone does not meet that technical requirement.
- Wiki chapter
Let delivery evidence set the pace
Sending volume should change gradually in response to delivery and recipient feedback, rather than following an arbitrary identical weekly count or a sudden large burst.
- Wiki chapter
Use the evidence your tools can actually show
Delivery monitoring should match the program's risks and available evidence rather than an arbitrary subscriber-count threshold, and missing dashboard data is not proof of healthy delivery.
- Wiki chapter
Know what an address check cannot tell you
An address-validation result is a limited technical signal; it does not prove ownership, interest, consent or guaranteed future delivery.
A small decision. A useful connection.
Try the thinking for yourself.
Read the situation and pause before opening the explanation. You don’t need an account for this example.
Fictional teaching example. Your response is not recorded.
Give an automation a stopping rule
A fictional welcome sequence invites people to book a consultation. Someone books after the first message but continues receiving reminders to book. What is missing?
Show the explanation
The automation needs an exit rule tied to the completed action. Review how that action is recorded and what should happen next. More messages are not automatically a better customer experience.
Put the course to work
A welcome-sequence map and a pre-send review with entry and exit rules.
Keep the idea within reach
Read it. Check it. Apply it.
Your course resources are digital and included with membership. Move from a question to the wiki chapter, or take the PDF and workbook with you.
A guide you can keep nearby
A 166-page PDF brings the course together in one document, with linked sources to follow when you want more context.
Find the course PDFSpace to make it your own
A 187-page workbook helps you turn ideas into written decisions, check your assumptions, and plan what to try next.
Find the workbookSources to explore
Selected references from the course guide. Research supports particular ideas in context; it does not guarantee a marketing result or a learning outcome for every person.
- Personalization in Email Marketing: The Role of Noninformative Advertising Content
- Getting too personal: Reactance to highly personalized email solicitations
- Enough Is Enough! The Fine Line in Executing Multichannel Relational Communication
- CASL frequently asked questions
Find the complete reference list in the course wiki sources.
Does this cover email deliverability?
It introduces authentication and the interpretation of delivery and engagement signals. It helps you ask useful operational questions, but it does not guarantee inbox placement.
Is this specific to one email platform?
No. The planning concepts apply across providers. Platform setup instructions and legal requirements should be checked for your actual use case.
What happens if I answer a practice question incorrectly?
You receive a teaching explanation and a worked example, with another opportunity to practice. Correct answers also lead to an explanation so you can understand the reason behind your choice.
Does access include every Program Reset course?
Yes. Both lifetime options include all 13 courses in this library, their wiki guides, PDFs, and workbooks. Community and the separate 200+ course vault are included in the Community & Vault bundle. Access lasts while the platform operates. See the access terms.
One membership. A connected library.
Learn this. Then connect the dots.
Email marketing course is included in both Program Reset lifetime access options. Move between visual lessons, the linked wiki, PDF guides, and workbooks as your questions change.
Keep building your understanding.
10 lessons · Self-paced
Sales funnel course
Make the next step clear, useful, and believable.
Explore the course
10 lessons · Self-paced
Content marketing course
Make every piece of content earn its place.
Explore the course
10 lessons · Self-paced
Web analytics course
Turn reports into decisions you can explain.
Explore the coursePublished by Bow Tie Kreative · Calgary, Alberta, Canada · Course page reviewed .