Once your instance of Jeto is created, you can begin connecting it to your Marketo instance.
Steps to follow in Marketo
1- Create a new dedicated API Only User. The API Only User must have permission to view all the workspaces in which program templates or cloned programs will live. The user must also have the following roles:
Activate Campaign, Deactivate Campaign, Execute Campaign, Read/Write Campaigns and Read/Write and Approve Assets
If you are unsure how to do so, you can view the Marketo Documentation
NOTE: You may need to create a new role for this. If you are unsure how to do so, you can view the Marketo Documentation
2 - Create a LaunchPoint Service
Once your API Only User is created with the appropriate permissions, you will need to create a dedicated LaunchPoint Service in Marketo. The service type will be Custom and the API Only User will be the newly created dedicated user for Jeto.
If you are unsure how to do so, you can refer to the Marketo documentation
3 - Now that your API Only User and LaunchPoint Service are created, note down the following information, located in Marketo:
Endpoint URL - located under the Web Services menu in the Admin panel, you will find the URL in the REST API box, at the very bottom. Note down the Endpoint URL.
Client ID - Located under the LaunchPoint menu in the Admin panel, click "view details" next to your newly created Jeto LaunchPoint Service. From this pop up, note down the Client ID.
Client Secret Key - In the same pop up, under the Client ID, you will find the Client Secret. Note the key down.
Steps to follow in Jeto
Once you have noted the REST API Endpoint, Client ID and Client Secret Key, click Review. If you do not see the Review button, click on the red exclamation point.
1- Enter your Rest API Endpoint URL, Client ID and Client Secret Key in the form and click Save
Make sure there are no spaces in the values if you copy/paste from Marketo
Your Jeto instance will beginning syncing with your Marketo instance. Depending on the number of programs and folders in Marketo, this step may take up to an hour. Once the sync is complete, you will see a green check mark. You can click on the ‘x’ at the top of the window to return to the main admin console.
Connect multiple Marketo instances
Many companies (and Jeto clients) still use more than one Marketo instance, which brings significant challenges in environments, including brand and process inconsistency and fragmented workflows which result in inefficiency and delays.
While it was previously possible to connect only one Jeto instance for each Marketo Instance, this model showed it's limits, including the lack of compatibility with Jeto SSO, and the additional complexity (and confusion) from handling campaigns in 2 different Jeto accounts.
With the new "Platform Integrations"(PI) feature, we're allowing Administrators to connect multiple Platform integrations (PI) / Marketo instances to a single Jeto account. This allows Marketing Operations to:
Centralize Campaign Requests: All campaign requests, regardless of the target Marketo instance, are routed through a single portal, ensuring consistency and a predictable workflow.
Increase Efficiency: By consolidating the intake process, MOPs teams can eliminate manual chaos and focus on higher-value, strategic work.
Improve Governance: Centralizing the process gives MOPs greater control over brand consistency across all campaigns, and ensures all campaigns follow established best practices.
Managing Platform Integrations
The new Platform Integrations page is accessible from the same "settings" top menu. where admins can view and add new Integrations.
Launcher X Integration Mapping
Now that multiple Platform Integrations can 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 the corresponding Integration\Instance. You can still manage access and permissions for users to specific Launchers, and therefore, specific PIs given each Launcher can only be configured with a single PI.
New Launcher Modal
