Jeto Ideas

User Story

As an… Administrator
I need to… support multiple Marketo instances and allow my users to create campaigns from a single Jeto account.
User could potentially save API connections to multiple marketo instances and assign launchers (and dependent campaigns) to one of the pre-configured instances connections.

Solution Overview:

Administrators will have the ability to add multiple Platform Integrations (PI) \ Marketo Instances to their Jeto Account.
When multiple PI exist, it will be required to specify the PI for each Launcher.
When a campaign is created or updated from that Launcher, the programs paired with the related campaigns will be created in that instance.
It will still be possible for Admins to segregate the access for collaborators for specific Launchers, and therefore, specific PI (each Launcher can only be configured with a single PI). This feature will be a paid add-on with a free access to try it. Pricing will match the current model/replace the need for multiple instances.

Terminology

Platform Integration: this represents an instance of our client’s Marketing Automation Platform (Marketo or eventually other MAP like SFMC) that is integrated to Jeto.

Connection: API Access that is established between Jeto and the Platforms using the API Credentials (Typically required by a valid Authentication token)

Overview

• Allow to store multiple “Platform Integrations (PI)” at the account level

• Among the multiple PI, user must select a default Instance

• PI is added as a New Launcher Property. Each launcher and can be associated with any one of the Account level PI.

Program and Folders Sync

• In addition to Account ID, the programs and folders must now include an additional “PI” parameter that will store the associated instance API credentials and allow to distinguish from folders and programs that belong the the same Jeto account but that are tied to a different Instance.

Parallel\Simultaneous PI API Connections

• On any given Jeto account, users must be able to perform actions on multiple PI instances - therefore Jeto needs to manage token issue and refresh in parallel. (ex: User A can update a campaign in PI A, while user b creates a campaign in PI B at the same time)

Top Nav

• Gear Icon now leads to new “Account Settings” Page (below) instead of Modal.

• Top nav Sync status widget (giving update on sync status from top menu) will be removed. Platform Integration will host display the sync status status for each PI instead.

New “Account Settings” Page.

See Mockups Sections 01-02-03-04 ** DISREGARD ALL “FUTURE STATE” Screens.

• New page under https://app-staging.jeto.io/account/settings to manage account settings (no sub navigation for now but will be in the future

• User can view existing PI (Vendor Icon, PI Name, Connection Status)

• On click “PI Section expands with list of PI

• User can click “+” to create a new PI. Opens PI Credentials Modal.

  • Select Vendor (Marketo only for now)

  • Add PI Name

  • Add Credentials

  • Save PI

• User can click edit on any PI to change the Access Credentials

Entitlement:

Additional Integrations will be a paid feature. Therefore we need to enforce entitlement as follow:

• A new parameter stored in DB to store “Plan” object in “Platform Integrations Limit” (in the future it should also allow to host other limits (ex: n of users) - we should fill with value being 1 for all clients initially.

• As user creates a new integration we count the number of existing rows in the existing integrations. If the limit is already reached

We intercept with confirmation message in modal:

• Title: Unlock new marketing possibilities!
  Body: We've granted you a free trial access to a new Jeto feature: integrating with a additional Marketo instances. To permanently add more integration(s) to your subscription, simply connect with your account manager.
  Buttons: Cancel Proceed

Launchers

See Mockups ** DISREGARD ALL “FUTURE STATE” Screens.

• Updated Launcher Modal

  • A new single select input field is added before the existing ones for user to select the right PI.

  • When a specific PI is selected, only the folders and programs associated to that instance will be selectable in subsequent fields (destination folder, Program)

  • Images and files destination folder also populates only with the PI folder. Backward compatible: The Default “Images and Files Folder”is selected (and if it’s saved with the “Jeto” default values, verify later created and set in the selected instance) - this function targets the PI instance.

• All API calls to Marketo from this Launcher and the associate campaigns are made to the API from the selected PI.

• Updated Launcher Settings Page

  • Display PI in Launcher Settings - Once the PI between an instance and a Launcher is established it cannot be edited

  • Backward Compatibility: Create Launcher action is Disabled if ANY of the connections is in “Syncing” status”

Campaigns:

• No change on campaign level.

IP Permissions, Authentication & SSP SSO

• All Admins will have the ability to Create, View, Edit all PIs.

• There will be no impact on SSO. Users that are added to the instance will have access to all connected Marketo Instances and the segregation of access will be controlled by granting access to specific Launchers.

Notification Emails

• Only if more than 1 platform is configured, Add Platform Integration Name in parenthesis after the Account Name for all Notification Emails. Example for campaign notifications.
  
  Title: You have a new Jeto Campaign!

  Body:
  Account: [ACCOUNT NAME ] ([PLATFORM INTEGRATION NAME])
  Launcher:

  Campaign name:

  Submitted on:

  Submitted by: ( )

  Marketo program:
  
  **Apply to all Notification Emails where Account is specified.

Known Limitations

Limitation: Marketo does not allow to clone program across instances, therefore, The indexing of source Marketo Program Template template folders and programs will still be clustered “per instance”.

Documents and References

Auth0 SSO Dashboard Applications: https://auth0.com/docs/customize/extensions/single-sign-on-dashboard-extension/create-sso-dashboard-application

Future State Considerations

• Consider: There will eventually be a sub navigation under the /account/settings page, but for now there is only “Integrations” so no need to have it for now.

• Out of scope for MVP: User can Delete a PI if no “non deleted” launcher is using it. Else we block deletion of PI. in MVP user cannot delete any PI.

• Out of Scope for MVP: Allow user to change PI on a launcher - in MVP - once a PI is defined at Laucher Level it is not editable.

• Out of Scope for MVP: PI Sharaing is excluded - All admins will be able view-edit any of the PI.

• Out of Scope for MVP: Add filtering of campaigns and\or Launchers by Platform Integration.

• Out of Scope for MVP: Some Admins may want to clone launchers across PI. That would required that we clone only the form and ask the admin to select PI and Template Program in an intercept action/workflow during clone Launcher action.

• Out of scope - restore sync status to handle multiple PI in top menu:

  • Sync Action, Status + Error

    Change logic for Sync Status:

    • if ALL PI connections are “Sync Completed” (no error, no Sync in Progress), then we show green check (logic previously considering only 1 connection, now need to consider multiple)

      
      

      If ANY of the PI connections are in Error, then show the error icon

      • When Jeto is in Sync Error State, clicking this link currently opens the new “account settings” page in the “Platform integrations” section. (in replacement of opening the App Integrations modal)

      • If any PI is “Syncing Data…” then we show spinner.