/ Docs

Marketo

Last updated November 4, 2025 · View as Markdown

Image 1 of 1 Marketo is a data-driven Software-as-a-Service (SaaS) platform designed to help businesses assess and automate marketing tasks. It helps organizations automate and measure marketing engagement, tasks and workflows.

In order to integrate Marketo with Relyance AI you will need a Marketo Instance Munchkin ID, Client ID, and Client Secret.

Permissions Relyance needs

Marketo authorises through an API-only user whose role carries these permissions:

Permission Needed for
Read-Only Person discovering and classifying person records
Read-Only Opportunity opportunity records
Read-Only Custom Object custom objects
Read-Write Person DSR only — deleting or updating a person to fulfil a request

Grant Read-Write Person only if you run DSRs through Marketo; with the three read-only permissions the integration cannot modify anything.

The connection is Two Legged Oauth2 — client credentials, no browser step and no refresh token, so it keeps working until the API user or its client secret is removed. Maximum Concurrent API Calls is optional; lower it if Marketo's API limits are tight in your instance.

In Marketo:

  1. Login to your Marketo account.
  2. Click on the Admin tab at the top of the page.
  3. Navigate to the Users and Roles page.
  4. Select the Roles tab and click New role.

marketo-1.png

  1. Enter a name for the Relyance API access role.
  2. Expand the properties list next to Access API, scroll down, and select the following attributes:

marketo-2.png

  1. If connecting Marketo for processing DSRs, the following additional permissions need to be selected:
    1. Read-Write Custom Object
    2. Read-Write Person
    3. Read-Write Opportunity
    4. Read-Only Assets
    5. Read-Only Activity
  2. Click Create.
  3. Navigate to the Users tab, and select Invite New User.
  4. Enter user information and click Next.

Email: A service account email at your organization First Name: Any descriptive name (ie: Service) Last Name: Any descriptive name (ie: Account)

Marketo-8a.png

The email doesn’t need to be verified since it’s for API access only. 11. Select the role created in step 4, and check the API access box, and click Next.

marketo-3.png

  1. Click Send to finalize user creation.
  2. Navigate to the LaunchPoint page listed under the admin panel’s integration menu.
  3. Select New Service and enter the information for the previously created user.

marketo-4.png

Marekto-5a.png

  1. Click Create.
  2. Click the View Details button for the newly created service.
  3. Copy the Client Id and Client Secret for later use.

marketo-6.png

  1. Navigate to the Munchkin page from the integrations section of the Admin home page.

marketo-7.png

  1. Select it and copy the Munchkin Account ID for later use.

In the Relyance AI application:

  1. Login to your Relyance account.
  2. Navigate to the Settings (bottom-left corner).
  3. Select Integrations.
  4. Search and locate the Marketo integration card and click on it.
  5. Click on the Add Connection button on the top right
  6. Provide a meaningful name for the integration and click on the Add button
  7. In the Overview section, select the integration features you wish to enable for the integration, review the Scope and Permission, and Endpoint details and click on Continue. For more details, see Integration Features
  8. In the Connection section, provide the appropriate values and click on Continue,

Screenshot Screenshot

Screenshot

  1. In the Authentication section, fill in the Marketo Instance Munchkin ID, Client ID, and Client Secret into their respective fields.
  2. If the Data Inspection check box is checked from step 7, In the Data Inspection section, provide the appropriate values and click on Continue Minimum Confidence Level: This property adjusts the sensitivity of the Data Inspection feature. Lower likelihoods (e.g., unlikely) offer more coverage but may produce false positives, while higher sensitivity (e.g., very likely) provides greater accuracy but less coverage.

Screenshot

  1. Review the configuration summary from the Completion section and click on Finish.
  2. Confirm the integration Status reflects Connected

Screenshot

Manage this integration with Terraform

Connections for this integration can be managed as code with the Relyance Terraform provider. Non-secret fields go in auth.params; secret fields go in auth.secrets_wo, which is write-only — never stored in Terraform state. Rotate secrets by bumping auth.secrets_wo_version.

resource "relyance_integration_connection" "marketo" {
  vendor = "marketo"
  name   = "<your connection name>"

  auth = {
    method = "oauth-client-credentials"
    params = {
      munchkin_id = "<munchkin_id>"
      client_id = "<client_id>"
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      client_secret = var.marketo_client_secret
    }
    secrets_wo_version = 1
  }

  scans = { "data-inspection" = { enabled = true } }
}