Campaign Studio makes Wave the marketing automation platform for teams leaving Marketo.
Campaign Studio is described here in full. Each part carries its status: Early access is built today and opens to founding customers first; At launch arrives when Campaign Studio launches.
A campaign is one Goal plus many Promotions. The Goal is what the campaign is for: an asset, a webinar, a virtual or in-person event, a demo or trial, or something else.
Each Promotion has its own channel, tool, planned and actual cost, dates, tracking code and status, from Targeted to Queued, Pushed, Delivered, Interacted and Drove engagement. A built-in Marketo crosswalk turns a Marketo program into one Goal plus its Promotions.
Run a campaign as traditional, hybrid or buying-group. Whichever mode you choose, one contact policy governs every send and every push to an outside tool, and every hold records why.
Saved, versioned audiences with an exact live count and a breakdown of who was excluded and why.
At launch Describe an audience in plain English and get the definition back to review.
A brand kit and locked templates, so every email looks like you and nobody breaks the layout.
At launch Modules, tokens, dynamic content, preview as any person, and test sends.
Send a batch now, at a set time, or in each person's local time. Seed lists show you the inbox before your audience sees it. Every batch is armed by a person.
Every email carries a compliance footer and one-click unsubscribe, and bounces and complaints suppress the person automatically.
Early access A single email from your own domain, armed by a person.
Forms and landing pages on your own domain, with UTM capture, a bot check, progressive profiling and returning-visitor prefill.
Triggers and steps live inside the campaign they serve. When a step fails, the person is parked with a reason instead of silently dropped.
A consent ledger per channel records what each person agreed to, and it can only narrow who may be contacted.
At launch Suppression causes you can read, email topics, and a preference center.
Folders, multi-step approval with four-eyes review, a naming policy, a version diff, and a campaign history you can read yourself.
At launch Launch checks that block what is definitely wrong before it goes out.
Tell your paid ads, sales engagement, ABM and direct-mail tools exactly who needs a promotion, then pull back the touches and the spend.
A campaign calendar, and a comparison of every promotion across campaigns on cost, reach and engagement.
At launch Lifecycle reports and named attribution models, always labelled descriptive. Causal claims come only from the control group.
Plan a campaign, turn a brief into a campaign, or describe an audience. The assistant drafts; a person approves everything.
A weekly recap, scheduled reports, observations on each campaign, and one decision inbox for everything waiting on you.
A REST and bulk API for your own integrations and for loading your history.
Wave holds the marketing record of each person. Your CRM stays the sales system of record: HubSpot now.
At launch Salesforce.
No big-bang cutover. You move one webinar program or one nurture, and you decide when the next one moves. At launch
Today, Wave's Marketo read and writeback are built and awaiting their first live customer. Marketo writes are audited like every other write; one-click rollback is HubSpot-only today.
Campaign Studio is launching soon. Until it launches, Wave does not send bulk, sequenced or scheduled email: the one send that exists today is a single email from your own domain, armed by a person and off by default. Unless you opt in to Campaign Studio, your marketing platform stays sender of record.
Straight answers about Campaign Studio, Marketo and sending.
Campaign Studio launches soon. Parts of it are built today and in early access, opening to founding customers first; join the founding list to be first.
Yes, for teams that choose it. Campaign Studio makes Wave the marketing automation platform for teams leaving Marketo: campaigns, audiences, email, sending, forms, flows, consent and governance in the same place that knows each buyer. It is opt-in per customer; if you don't opt in, nothing changes and Wave keeps running beside your marketing platform.
Yes, and that is the only way we migrate. You move one workload at a time, such as one webinar program or one nurture. Each runs side by side for at most four weeks, one goal never has two senders, and suppression syncs both ways during the switch.
No. Until Campaign Studio launches, Wave does not send bulk, sequenced or scheduled email. The one send that exists today is a single email from your own domain, armed by a person, and it is off by default. At launch, Campaign Studio adds batch and scheduled sending for customers who opt in, with every batch armed by a person.
Your CRM stays the sales system of record. Wave holds the marketing record of each person, and new leads reach your CRM through Wave's audited write path: HubSpot now, Salesforce at launch. Wave does not replace your CRM.
Campaign Studio keeps a consent ledger per channel, and it can only narrow who may be contacted, never widen it. One contact policy governs every send and every push to an outside tool. Suppression is always enforced, and every hold records why.
The assistant plans a campaign, turns a brief into a campaign, and describes an audience in plain English. It only drafts: a person reviews and approves everything before it runs.
Founding customers get founding-customer terms. Join the founding list and we'll talk them through with you.
Tell us the workload you want to move first, and we'll keep you posted as Campaign Studio opens.