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 Cyera 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. Cyera 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	Opt Out
Activity		✅
Activity Assets
Activity Metadata
Company
Named Account
Opportunity
Person	✅	✅	✅	✅
Sales Person
Schema Custom Field				✅
Schema Standard Field

Base Scopes

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

Endpoints Utilized

Cyera 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.

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

---

Capabilities

Access

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

Data Interactions

For Access requests, Cyera 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

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

For Deletion requests, Cyera will take the following actions:

1. Search for Leads, who are people external to your company.
2. If Add Leads object custom field name is disabled:
   • Delete collected Leads by ID.
3. If Add Leads object custom field name is enabled:
   • If Update custom field only is selected:
     • Update the custom attribute for each of the collected Leads by ID.
   • If Update custom field and delete user data is selected:
     • Update the custom attribute for each of the collected Leads by ID.
     • Delete collected Leads by ID.
4. Set dg_deletion to TRUE on the Leads object.

Custom Field Requirements

Custom field must exist on the Leads object and use the API Name in Marketo. The field can be any type (e.g. boolean, string, or text).

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

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

Data Interactions

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

1. Find leads using configured identifiers.
2. Update the unsubscribed field with the opted_out value.
3. If Add Leads object custom field name is enabled, update the custom attribute for each of the collected Leads by ID.
4. Set dg_opt_out to TRUE on the Leads object.

Custom Field Requirements

Custom field must exist on the Leads object and use the API Name in Marketo. The field can be any type (e.g. boolean, string, or text).

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

---