Knak, Stensul, Jeto and Campaign Launchpad compared

What goes into a campaign

In Oracle Eloqua or Adobe Marketo, the email is one piece of a campaign. Before it sends, someone has to:

1. Take the request: what is going out, to whom, and when.
2. Build the email, and the landing page if there is one.
3. Clone the campaign or program it goes out in, and fill in its settings.
4. Choose the audience, or import the list.
5. Get it approved.
6. Schedule it and launch it.

In most enterprise teams, marketers write the request and Marketing Ops does everything after it, one ticket at a time. Every tool in this guide takes work out of that queue. They differ in how much of it they take.

Email builders: Knak and Stensul

Knak and Stensul are built around step 2. Marketers design emails and landing pages in a visual editor, inside templates that hold the brand and layout rules, and reviewers comment and approve in the same place. Both offer AI drafting, and both push finished emails into Eloqua, Marketo and dozens of other platforms.

Neither replaces the platform it pushes to. Stensul’s FAQ says so plainly: it is “not an ESP or MAP,” and teams push emails “into their existing ESP or Marketing Cloud to deploy as usual.”

How much of the campaign they take on depends on the platform.

• In Eloqua, both hand over the finished asset. Knak pushes emails and landing pages, and Stensul pushes emails into Eloqua folders. The campaign canvas, the segment and the schedule are then built in Eloqua, by someone who knows Eloqua.
• In Marketo, both go further. Knak and Stensul can clone a program from a template, place the email in it and schedule the send without anyone opening Marketo. Choosing the audience isn’t part of either workflow as documented, so it comes with the program template or is set in Marketo.

A builder is the right tool when the email is the bottleneck: too few people who can design one, too many rounds of review, a brand that drifts from region to region. It takes step 2 off the Ops queue. In Marketo it can take some of the later steps too, as long as the program template fits the campaign. In Eloqua, steps 3 to 6 stay with Ops.

Campaign platforms: Jeto and Campaign Launchpad

Campaign platforms start at step 1. The marketer’s request is the input. Instead of writing a brief for Ops, the marketer fills in a form or a wizard, and the platform builds the campaign from a template Ops set up in advance: the program, the email, the audience, the approval and the schedule. Ops configures each type of campaign once, then reviews campaigns instead of building them.

Jeto

Jeto is built for Adobe Marketo Engage and works only with Marketo. A marketer fills in an intake form, and Jeto clones a Marketo program template and passes the form’s values into the new program’s tokens. The marketer edits the emails and landing pages inside that program, and Jeto launches it once it is approved. Jeto names each new program from the form’s fields using a naming convention Ops sets, and the audience is one existing Marketo smart list.

Campaign Launchpad

Campaign Launchpad does the same job in both Oracle Eloqua and Adobe Marketo, and its wizards can do more than clone a template. Marketing Ops builds each wizard from the steps a campaign needs:

• Clone a campaign or program.
• Create, update or clone emails.
• Create or update landing pages.
• Import contacts or custom object records, with the data validated before anything is imported.

Ops decides what each wizard allows: the parts of an email or landing page a marketer can change, the audiences they can reach, and who approves the campaign. Marketers choose from lists Ops sets up, such as regions, business units and products, and Launchpad uses those choices to name every asset in the campaign by your naming convention. The marketer writes the content, or asks AI to draft it within rules Ops sets. Launchpad builds the campaign inside your own instance, routes it to whoever has to approve it, and launches it.

Any number of Eloqua and Marketo instances can connect to one Launchpad account, so an organization with several instances, on one platform or both, runs its campaigns from one place.

Side by side

What Knak, Stensul, Jeto and Campaign Launchpad each do in Oracle Eloqua and Adobe Marketo

Capability	Knak	Stensul	Jeto	Campaign Launchpad
Kind of tool	Email and landing page builder	Email and landing page builder	Campaign platform	Campaign platform
Platforms	40+, including Eloqua and Marketo	100+, including Eloqua and Marketo	Marketo only	Eloqua and Marketo, any number of instances
Emails and landing pages	Yes	Yes	Yes	Yes
Review and approval	Yes	Yes	Yes	Yes
Sets up the campaign in Eloqua	No, pushes emails and landing pages	No, pushes emails	Doesn’t support Eloqua	Yes
Sets up the program in Marketo	Clones a program template	Clones a program template	Clones a program template, with tokens	Yes
Chooses the audience	No, set in Eloqua or Marketo	No, set in Eloqua or Marketo	Yes, one existing smart list	Yes, from audiences Ops allows
Imports contacts or custom objects	No	No	No	Yes, with the data validated first
Schedules the send	Marketo only	Marketo only	Yes	Yes, in Eloqua and Marketo

Jeto and Campaign Launchpad on Marketo

For a team that runs only Marketo, these two are the likeliest shortlist. Both clone programs from templates Ops controls, and both launch campaigns without anyone opening Marketo. They differ in what a campaign can do beyond that.

Jeto and Campaign Launchpad compared for Adobe Marketo

On Marketo	Jeto	Campaign Launchpad
Clones a program from a template	Yes	Yes
Emails	Edited in the program it clones	Created, updated or cloned
Landing pages	Edited in the program it clones	Created or updated
Images	Uploads new images only	Browses Marketo’s library or uploads to it
Audience	One existing smart list	Existing smart list or imported
Imports contacts and custom objects	No	Yes, with the file validated first
Naming convention	Names the campaign and program	Names every asset in the campaign
AI copy drafting	Shown as a prototype	Yes, within rules Ops sets
Approval	Any one user with approval rights	Workflows that route to the right approver
Steps done by Ops	Done in Marketo, outside Jeto	Handed to Ops in Launchpad, with a deadline
Reporting after launch	No, results are read in Marketo	Opens, clicks, visits and form submissions
Instances in one account	Several Marketo instances, as a paid add-on	Any number, Eloqua and Marketo mixed
What each plan includes	Events, webinars, SMS, SSO and the API need the Enterprise plan	No plans: every feature at every tier, priced by email volume
Oracle Eloqua	Not supported	Supported

Jeto starts every campaign by cloning a new program, so changes to emails or landing pages already in Marketo are made in Marketo. Its audience is one existing smart list, so a campaign that goes to an uploaded list, or needs custom object records loaded first, goes back to Ops.

Images work the same way. Jeto uploads new images into Marketo’s Design Studio but can’t browse the ones already there. A request to reuse existing images, raised because Jeto was filling Design Studio with duplicate logos, has been open since 2020. Launchpad users can browse the image library in Marketo or Eloqua and pick what is already there, or upload a new image for the platform to host.

Campaign Launchpad also lets marketers draft copy with AI, under rules Ops writes once: the brand’s tone, length limits, words that must never appear, and standing instructions added to every prompt. Requests go to Anthropic or OpenAI on your organization’s own API key. Jeto has shown a prototype of AI-written campaign copy and describes AI drafting inside Jeto as the first phase of its roadmap.

Both can run several Marketo instances from one account. Jeto added this in October 2025 as a paid add-on; Launchpad can hold Eloqua instances alongside them.

The two are also sold differently. Jeto has two plans: Essential covers email programs, while event, webinar and SMS programs, the landing page layout editor, SSO, the API and automated governance rules need Enterprise. Campaign Launchpad has no plans. Every feature is included at every tier, and the price is set by email volume.

The fairest test is still to build one of your own campaigns in each.

When a campaign needs Ops

Not every campaign fits a template. A list needs cleaning before it is imported, a region wants an extra step, or the campaign is a kind nobody has run before. What a self-service tool does with those campaigns decides whether Ops still keeps a second, informal queue on the side.

Jeto is built for campaigns that run start to finish on their own. The marketer fills in the form, Jeto builds the program, and any one user with approval rights signs it off. Its help center describes approvals and comments on assets, but no way to hand a step to Ops. When a campaign needs something the launcher can’t do, an admin does it in Marketo, and Jeto’s own documentation recommends exactly that for cases such as interactive webinars.

Campaign Launchpad is built for both. A wizard can run start to finish with nobody from Ops involved, or include steps someone on the Ops team does by hand. When a campaign reaches one of those steps, Launchpad notifies the right person, gives the request a deadline, and keeps their conversation with the marketer on the campaign. Every campaign in flight sits in one queue that marketers and Ops can both see, and whether a marketer finishes a campaign alone or Ops steps in partway, it passes through the same templates, the same checks and the same audit trail.

That also changes how teams roll it out. Ops doesn’t have to automate every step of a campaign before marketers can use it. A new kind of campaign can start with Ops doing the hard steps, then hand more of them to marketers as the template settles.

Reporting after launch

Taking the build off the Ops queue doesn’t end the requests. The next one often comes a day after launch: how did it do? If the results live only in Eloqua or Marketo, a marketer without a login has to ask Ops to pull them.

Jeto doesn’t report on campaigns once they launch. Opens, clicks and conversions are read in Marketo. A reporting dashboard has been on Jeto’s ideas portal since 2019, and in April 2024 Jeto said it was “still planned but not currently on our immediate roadmap,” with customer success managers providing some campaign reporting in the meantime.

Campaign Launchpad reports every campaign’s opens, clicks, visits and form submissions inside Launchpad, and breaks performance out by campaign, template and sender. The marketer who launched a campaign sees how it did without asking anyone, and Ops can compare templates and senders across every campaign in the account.

Which kind of tool you need

Start from where requests wait today.

• If they wait on the email (design, copy, rounds of brand review) and Ops is happy to finish the campaign, an email builder fixes the slow part.
• If they wait on the campaign (Ops cloning programs, setting up audiences and scheduling sends for other people), a builder moves the wait rather than removing it. The email reaches Eloqua or Marketo sooner, then sits in the same queue. A campaign platform takes the whole request off the queue.
• If you run Eloqua, or both platforms, Campaign Launchpad is the only one of the four that builds campaigns in Eloqua, and one account can hold any number of Eloqua and Marketo instances.
• If some campaigns will always need Ops (a list to clean, a step no template covers), look at how each tool hands work over. Launchpad routes those steps to Ops with a deadline; with Jeto, they happen in Marketo.
• If marketers need to see results, check where they will read them. Launchpad reports each campaign back to the marketer who sent it; with Jeto, results stay in Marketo.

To put a number on what building other people’s campaigns costs your team, try the Campaign Launchpad calculator.