Marketo

This documentation for the Marketo integration describes the technical capabilities of this integration, including authorization, scopes/permissions, and utilized endpoints. For more information on how to integrate Marketo, visit our connection instructions.

Version

This integration utilizes the Marketo REST API v1.

Base URL

The base URL used for all Marketo API endpoints contains the Subdomain:

https://subdomain.mktorest.com/rest/v1

---

Authentication & Authorization

The DataGrail Marketo integration connects using OAuth 2.0 with the following credentials: Client ID and Client Secret.

Sensitive Credentials

Publicly exposing your API credentials can allow unauthorized access to Marketo API endpoints by a third party. DataGrail stores your API credentials encrypted and protected.

Scopes

The Marketo integration requires specific scopes that must be granted in order to function for a given capability.

Scope	Base	Access	Deletion	Data Discovery	Opt Out	System Detection
Activity		✅		✅		✅
Activity Metadata				✅
Activity Assets				✅
Company				✅
Named Account				✅
Opportunity				✅
Person	✅	✅	✅	✅	✅	✅
Sales Person				✅
Schema Standard Field				✅
Schema Custom Field				✅	✅

Base Scopes

All base scopes must be granted in order to connect the integration with DataGrail. The remaining scopes are only required if enabling those capabilities

Endpoints Utilized

DataGrail uses the following endpoints to authorize and test the connection:

Method	Endpoint	Purpose	Docs
GET	/leads/describe.json	Returns metadata about lead objects in the target instance

---

Limits

Limits in Marketo are calculated using the leaky bucket algorithm. All requests that are made after rate limits have been exceeded are throttled and an HTTP 429 Too Many Requests error is returned. Requests succeed again after enough requests have emptied out of the bucket.

• DataGrail supports requests throttling to stay within 70-80% of specified service rate limits.
• DataGrail processes API responses with HTTP 429 status to interrupt requests, waiting and retrying (using an exponential backoff strategy).

---

Capabilities

Access

DataGrail's Marketo integration provides Synchronous Access capabilities for the following supported identifier category: Email.

Data Interactions

For Access requests, DataGrail will take the following actions:

1. Search Persons (aka Leads), who are people external to your company.
2. If found, collect Activities by the persons IDs

When reviewing data returned by Marketo please note the following:

• Only fields with values are returned
• Custom fields unique to the organization may also be returned if they may potentially contain PII.
• Other Custom Objects may also be returned if they are linked to a Lead, that may contain PII in one or more fields.

Endpoints Utilized

Method	Endpoint	Purpose	Docs
GET	/activities.json	Returns a list of activities
GET	/activities/pagingtoken.json	Returns a paging token for use in retrieving activities and data value changes
GET	/activities/types.json	Returns a list of available activity types in the target instance, along with associated metadata of each type
GET	/leads.json	Search leads by email
GET	/leads/describe.json	Fetch list of the lead object fields

---

Deletion

DataGrail's Marketo integration provides Synchronous Deletion capabilities for the following supported identifier category: Email.

For Deletion requests, DataGrail will take the following actions:

1. Search for Leads, who are people external to your company.
2. Depending on your custom Deletion Settings do the following:

• If "Add Leads object custom field name" is disabled:
  • Delete collected Leads by ID.
• If "Add Leads object custom field name" is enabled:
  • If "Update custom field only" selected:
    • Update the custom attribute for each of the collected Leads by ID.
  • If "Update custom field and delete user data" selected:
    • Update the custom attribute for each of the collected Leads by ID.
    • Delete collected Leads by ID.

Endpoints Utilized

Method	Endpoint	Purpose	Docs
GET	/leads.json	Search leads by email
POST	/leads.json	Update lead's attributes.
POST	/leads/delete.json	Delete a lead
GET	/leads/describe.json	Fetch list of the lead object fields

---

Opt Out

DataGrail's Marketo integration provides Opt Out capabilities for the following supported identifier category: Email.

Data Interactions

For Opt Out requests, DataGrail will take the following actions:

1. Find leads using configured identifiers.
2. Update the unsubscribed or/and configured custom attribute with the opted_out value for all detected leads by specifying a Marketo user identifier.

Endpoints Utilized

Method	Endpoint	Purpose	Docs
GET	/leads.json	Search leads by email
POST	/leads.json	Update lead's attributes.
POST	/leads/schema/fields/dg_opt_out_field_name.json	Create custom lead field in the target instance.
GET	/leads/schema/fields/%dg_opt_out_field_name5.json	Get lead field by name

---

System Detection

DataGrail provides continuous system detection, delivering a real-time inventory of your data assets.

Data Interactions

DataGrail's System Detection process runs once daily to detect new systems added in Marketo:

For System Detection requests, DataGrail will take the following actions:

1. Fetch metadata about lead objects in the target instance.
2. Fetch list of the users from the calls consumed in the past 7 days.

Endpoints Utilized

Method	Endpoint	Purpose	Docs
GET	/leads/describe.json	Returns metadata about lead objects in the target instance
GET	/stats/usage/last7days.json	Fetch number of calls consumed in the past 7 days

---

Data Discovery

DataGrail's Marketo integration provides data discovery capabilities based on the principle of finding any and all personal data that's stored in a data system.

Data Interactions

For discovery requests, DataGrail will take the following actions:

1. Count number of all records for each of supported objects.
2. Fetch example records for each of the supported objects.

Supported Objects

• Schema Standard Field
• Schema Custom Field
• Activity
• Activity Metadata
• Activity Assets
• Company
• Account
• Opportunity
• Person
• Sales Person

3. Sample data for the next analysis and classification.

Endpoints Utilized

Method	Endpoint	Purpose	Docs
GET	/activities.json	Returns a list of activities
GET	/activities/pagingtoken.json	Returns a paging token for use in retrieving activities and data value changes
GET	/activities/types.json	Returns a list of available activity types in the target instance, along with associated metadata of each type
GET	/asset/v1/programs.json	Retrieves the list of accessible programs from the target instance
GET	/companies.json	Retrieves company records from the destination instance based on the submitted filter
GET	/companies/schema/fields.json	Retrieves metadata for all company fields in the target instance
GET	/leads.json	Returns a list of up to 300 leads based on a list of values in a particular field
GET	/leads/schema/fields.json	Retrieves metadata for all lead fields in the target instance
GET	/namedaccounts.json	Retrieves a list of named account list records based on the filter type and values given
GET	/namedaccounts/schema/fields.json	Retrieves metadata for single named account field
GET	/opportunities.json	Returns a list of opportunities based on a filter and set of values
GET	/opportunities/roles.json	Returns a list of opportunity roles based on a filter and set of values
GET	/opportunities/roles/describe.json	Returns a list of opportunity roles based on a filter and set of values
GET	/opportunities/schema/fields.json	Retrieves metadata for all opportunity fields in the target instance
GET	/programs/program_id/members.json	Returns a list of up to 300 program members on a list of values in a particular field
GET	/programs/members/schema/fields.json	Retrieves metadata for all program member fields in the target instance
GET	/salespersons.json	Retrieves salesperson records from the destination instance based on the submitted filter
GET	/salespersons/describe.json	Returns metadata about salespersons and the fields available for interaction via the API