Jeto Ideas

Today Jeto operates only on programs it creates — it can't attach to or manage a program that already exists in Marketo. This idea proposes letting Jeto inventory existing Marketo programs and make them editable through Jeto, so collaborators can work on a program in place instead of always starting from a clone.

The problem it solves

There are several situations where cloning isn't the right move and users need to work on a program that already exists:

• A program was built directly in Marketo (for example, Interactive Webinars, which can't be created through Jeto — see JETO-I-271) and teams still want a controlled, Jeto-based way for collaborators to edit its assets.

• A live or in-flight program needs edits, and cloning would fragment reporting, membership, or attribution.

• Marketing ops wants non-Marketo users to safely edit specific existing programs without granting them full Marketo access.

Proposed concept

• Jeto inventories the programs in a connected Marketo instance.

• Based on specific program properties (Ex: Tags, Jeto determines which programs are editable and by whom mapping specific Jeto users or groups - or overwrites this in Jeto directly).

• Authorized collaborators can then open and edit that existing program's assets through Jeto's guided interface, with the same guardrails Jeto applies to programs it creates — without cloning, and without direct Marketo access.

Why it matters

This would extend Jeto's value from "create new campaigns" to "govern collaborative editing across the campaign lifecycle," give teams a controlled front door to programs Jeto can't create itself, and use Marketo's existing tag structure as the permission model rather than requiring new configuration.