Email Studio sends an email in five conceptual steps: pick the audience (Data Extension), pick the content (Content Builder), pick the send settings (subject, from address, schedule), validate, send. The first send takes a few hours to set up; subsequent sends are minutes.
- Prepare the audience
In Marketing Cloud, navigate to Data Extensions. Either select an existing Data Extension or create a new one with your subscriber list. The Subscriber Key must match across all Data Extensions for unified tracking.
- Build or pick the email content
Open Content Builder. Pick an existing email template or build a new one from a starter template. Design with the Drag-and-Drop editor, the HTML editor, or both. Save the email as a draft.
- Open Email Studio and create a Send
Email Studio, then Interactions, then Send. Pick the email from Content Builder. Set the From Address, Subject, Pre-header, and any AMPscript variables. Pick the Data Extension as the audience.
- Schedule or send immediately
Test send first to a small internal test list. Confirm rendering across major email clients (Gmail, Outlook, Apple Mail, iOS). When ready, schedule or send immediately.
- Monitor delivery and engagement
Email Studio, then Tracking, shows delivery, opens, clicks, bounces in near-real-time. Watch the first 10-30 minutes for delivery anomalies. Drill into individual subscribers if something looks off.
- Iterate based on performance
Use Email Studio''s A/B test feature for the next send: two subject lines, two creatives, two send times. Send to 10 percent of the audience, pick the winner, send to the remaining 90 percent. This is how Marketing Cloud campaigns get better over time.
Single sends and scheduled campaigns. The core Marketing Cloud email tool.
Multi-step customer journeys with Email Studio as one action among many.
Asset library for emails, images, templates, AMPscript blocks. Used by Email Studio.
Subscriber tables. The audience source for every Email Studio send.
- Subscriber Key is the primary key across Marketing Cloud. Mismatches between Data Extensions cause subscribers to be treated as different people, breaking suppression and segmentation.
- Email Studio sends count against your Marketing Cloud sending volume. Test sends to your internal list still count; account for them in volume planning.
- AMPscript bugs are invisible until send time. A typo in personalization syntax may render as %%FirstName%% in production. Always send test emails to multiple subscribers, not just one.
- Unsubscribe is global by default. A subscriber who unsubscribes from one publication is unsubscribed from all unless you set up subscription management explicitly. Document the unsubscribe model for your org.