
Email has the highest ROI potential of any direct channel — and the highest technical responsibility.
Launching without preparation is an investment in problems you will be fixing for months.
A corporate domain is not about image — it is a technical requirement.
Only from your own domain can you configure digital signatures, build a reputation, and separate different communication types.
SPF, DKIM, and DMARC are the language of trust between mail servers.
Without them, your domain cannot prove its authenticity, and mailbox providers treat your emails with suspicion.
Domain warm-up is not bureaucracy — it is a technical reality.
Mailbox providers judge a new domain by what it does in the first few weeks. Yespo automates the process, but the strategy for your first sends is the marketer’s call.
List quality matters more than list size.
Double Opt-In, legitimate collection sources, and subscription categories ensure your list contains real, interested people — not random addresses.
Sender reputation is a long-term asset.
It takes years to build and can be lost in a week of uncontrolled sends. Postmaster Tools and Yespo’s built-in monitoring are a required part of the weekly routine.
Yespo handles the technical complexity so you can focus on strategy.
This is not about becoming an email engineer — it is about staying focused on what actually drives business results: content, segmentation, triggers.
The email editor is the marketer's operational interface, not a design tool. It's the final step where data collection, unification, and segmentation become a specific message delivered to a specific customer — everything built in earlier lectures converges here.
The drag-and-drop editor replaces the old engineering workflow, and the numbers explain why. A model where a brief goes through a developer, then a tester, then a designer takes 2–5 days per email. That doesn't scale past a handful of triggered workflows — Yespo clients running 70+ of them need emails built in 15 minutes to 2 hours instead.
Every template follows one hierarchy: Stripe → Structure → Container → Block. The stripe defines a horizontal region (header, content, footer, info area), the structure sets the column layout inside it, the container groups content, and the block is the actual text, image, or button the subscriber sees.
Confusing hierarchy levels has a direct technical cost. Wrapping every structure in its own stripe unnecessarily inflates the HTML file, and once it crosses roughly 102 KB, Gmail clips the email — the subscriber sees only the beginning and misses the CTA and footer entirely.
The editor is organized into six panels, each with a distinct job. Email management handles saves and testing, Structures and modules speeds up assembly, Content blocks fills the email, Email settings covers delivery parameters, Global styles keeps the brand consistent, and Comments replaces chat threads and screenshots for team review.
Global styles follow a cascade principle, just like CSS. Set fonts, colors, and button styles once and every email inherits them — but an element with its own individual settings will override the global style, which is the most common reason a "global" change doesn't seem to apply everywhere.
Blocks split into two fundamentally different categories. Content blocks (text, image, button, video, AMP carousel) hold whatever the marketer types in manually. Data-driven blocks (smart container, Products with AI recommendations, Price/Discount) are never filled in by hand — the marketer sets a rule, and the system populates them automatically from the site or the subscriber's profile.
Content blocks are what the marketer fills in manually — unlike the data-driven blocks covered later. Images, banners, video, buttons, tables, and navigation all show exactly what you type or upload; nothing here pulls from an external source.
The Image block is a small production tool in itself, and Rollover adds interactivity without AMP. Six gallery tabs, a built-in editor for filters and cropping, and alt text that matters in practice since Outlook on Windows blocks images by default. Rollover swaps one image for another on hover — useful for showing a discount or product angle — but both images need the same aspect ratio, or the layout shifts.
The Timer and Video blocks both convert attention into measurable lift. A timer keeps counting down even if the email is opened hours late, adding roughly 15–25% CTR in limited-time promos; a video preview reliably outperforms a text-and-image-only email, especially in welcome or post-purchase series.
The CTA button lives inside a container, not on its own — this isn't cosmetic. A structure holding only a button doesn't reflow correctly on mobile. Style is set once at the General styles level, and the default placeholder text should always be replaced with a real action verb.
AMP turns the email into a data collection point, not just an interactive one. Carousel, accordion, and form blocks let a subscriber browse, expand, or submit data without leaving their inbox — and a form response feeds straight into the CDP profile instead of routing through a landing page with a 30–40% drop-off. Google sender verification is required first, and approval takes a few weeks.
Gmail Promotions Annotations get an email noticed before it's even opened. Product carousel, deal, or single-image previews appear in the Promotions tab on mobile — but only after enabling the toggle in Email settings, and any promo code shown there must also appear in the email body.
Modules replace manual assembly with reusable building blocks. Any stripe, structure, or container — a header, a footer, a product card — can be saved once as a module and reused across every email, adapting automatically to the template's existing styles.
Synchronized modules solve the 70-email update problem. Change a synchronized footer once, and it propagates to every template using it, instead of requiring 70 separate manual edits. The tradeoff: a synchronized module can't be nested inside another one, since it can't be both parent and child at once.
Smart containers turn a product URL into a fully populated card. Paste the link, and the system pulls image, name, price, and button URL from the page's OG tags — no manual copying, and no developer needed even for non-standard fields like SKU or fabric composition, via CSS-selector variables.
The Products block picks products per subscriber, not per campaign. Backed by 200+ recommendation algorithms with up to 69% predicted accuracy, it requires web tracking, a CDP plan, and a configured data source — the marketer chooses the algorithm, and the system generates a unique selection for every recipient.
Price and Discount blocks keep pricing accurate without manual updates. Displayed as static text, a price goes stale the moment it changes on the site; these blocks sync in real time and only appear once the account has at least one recorded order.
Testing personalized content requires a real contact, not the standard test send. "Send test" shows an empty template or generic best sellers — to see what an actual subscriber would see, you preview against a specific contact or segment tied to the relevant workflow.
Responsive design is automatic, but not automatic enough on its own. Since 50–80% of opens happen on mobile depending on the category, the editor reflows layouts by default — but the marketer still needs to check the mobile view, set up inversion for reordered containers, hide unnecessary elements, and adjust mobile spacing separately.
Font choice is a tradeoff between brand and compatibility, not a single right answer. Safe fonts render everywhere but look generic; web fonts show your brand to about 80% of subscribers and fall back for the rest; custom fonts render reliably in most modern clients but should stay on banners and headings rather than body text, where a broken fallback quietly wrecks the design.
Built-in AI covers both routine fixes and the highest-leverage line in the email. Inside a text block, it fixes errors, adjusts tone, translates into 10 languages, and rewrites length — but the subject line and preheader get two extra options, including generating from the email's own content and rewriting through Cialdini's six principles of influence.
AI also optimizes product copy pulled in through smart containers. This matters specifically when the source description on the site is too technical or too long for an email format.
Collaboration is built into the editor instead of running through Slack screenshots and file versions. Simultaneous editing shows who's working on what in real time, change history lets you review or roll back any edit, and comment mode attaches feedback directly to specific elements.
Campaign setup is the activation point of the CDP model.
Every previous layer converges here: data, profile, segment, email. The quality of the launch depends on the quality of the work done at every layer below it.
The subject line and preheader are the cheapest optimization with the highest ROI.
Test your subject lines. Fill in the preheader. These are the two phrases the recipient sees first. Spending 10 minutes on them is the best investment you can make in opens.
The annoyance level protects the list from fatigue.
A single contact should never receive more messages than they are willing to absorb. This is not a restriction — it is an investment in the list’s long-term loyalty.
A/B testing has three levels.
Basic: multiple subject lines in one email. Intermediate: group splitting for full funnel analysis. Advanced: continuous testing through the “One from Many” block with machine learning.
Time zone and send speed are reputation-protecting parameters.
Contact time zone improves how the campaign is received. Send speed protects the domain from reputational risk at high volumes.
Re-engagement is a continuation of the campaign, not a repeat of it.
Switching channels for those who didn’t respond to the first message adds up to 30–40% more revenue on top of base campaigns. This isn’t “spam” — it’s responding to actual customer behavior.
Predictive segmentation saves campaign budget.
Instead of paying to send to everyone, you send to likely buyers. ROMI goes up, spam complaints go down, reputation strengthens.
A campaign doesn’t end when you click “Send.”
Post-launch analysis is part of the campaign. Without it, every future send repeats the same mistakes.
This course contains the use of artificial intelligence.
Email looks like the simplest channel to launch — until a poorly warmed-up domain lands every future send in spam, including the order confirmations your business depends on. This module treats email the way it deserves: as an infrastructure project first and a design project second.
You'll start with what most marketers skip — domain authentication (SPF, DKIM, DMARC), sender reputation, and the warm-up process that determines whether mailbox providers trust your domain at all. From there, you'll move into the Yespo editor itself: its stripe-structure-container-block hierarchy, the six panels that make up the workspace, and why an oversized HTML file gets your email clipped by Gmail before the reader even reaches your CTA.
You'll then build out full emails using content blocks (images, banners, timers, tables) and AMP interactivity, before moving into automation — modules that update across dozens of templates at once, smart containers that pull live product data from your site, and AI-recommended product blocks that generate a unique selection for every subscriber. You'll also cover responsive design, custom fonts, the built-in AI writing assistant, and real-time team collaboration inside the editor.
Finally, you'll get to the part where all of this converges: launching the campaign. You'll learn how to protect your list with the annoyance level, use contact time zones and send speed correctly, and run A/B tests — from a simple subject line split to continuous, machine-learning-driven testing with the One from Many block.
By the end of this module, you'll be able to take an email from a blank domain to a fully automated, tested, and protected send.