Skip to main content
Use the @bijection/connectors/marketo entrypoint to declare Adobe Marketo Engage resources.

​
Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

​
Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

​
Activities

​
pull: Paging-token activity occurrences from a carried activityDate

The following example matches configuration standard.

​
Configuration: standard

Case: marketo/activities/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: marketo. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: activities
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Leads

​
pull: Deleted-lead and lead-change streams with batched lead reads

The following example matches configuration standard.

​
Configuration: standard

Case: marketo/leads/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: marketo. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: leads
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. The connection’s munchkinId setup selects https://<munchkinId>.mktorest.com. The marketo credential is the instance’s client-credentials grant against /identity/oauth/token, written as a bearer header: Marketo removed access_token query parameters on 2026-08-31. Marketo documents the token request as GET or POST but shows only query parameters; whether it accepts a form body has not been checked. Marketo names no instance identity, so the connection is its own namespace. Marketo refuses with HTTP 200, success: false and a coded errors entry. Codes 601/602 (token), 603 (access), 606 (100 calls per 20 seconds), 607 (daily quota) and 615 (concurrency) are declared failures, so a refusal is never an empty page. The budget declares the daily quota (dailyQuota, default 50,000) as a fixed window from 06:00 UTC (Marketo’s “12:00AM CST”; its daylight-saving midnight is not modelled) and 100 calls in any 20 seconds. Every read walks a paging token minted for an instant. Token lifetime is undocumented, so a finished pass carries the latest activityDate it read and the next pass mints a new token overlapMinutes (default 15) below it; re-read rows deduplicate by version. activities.pull publishes one to ten activity types as occurrences keyed by marketoGUID (the numeric id may be absent and is not unique), versioned by activityDate, never withdrawn. since is where the first pass begins; most activities are purged after 25 months and high-volume types after 90 days. leads.pull keeps leads as refreshable records. Each pass first walks deleted-lead activities (type 37), each withdrawing its lead, then the lead change stream (New Lead and Change Data Value for the declared fields): every change page’s distinct lead ids are read in one leads.json?filterType=id request, the page that publishes, versioned by updatedAt. The first pass begins both streams in 2006, so New Lead activities, which Marketo keeps, name every lead. Delete Lead activities are reportedly kept 14 days, so a source unread for longer misses deletions; merges are not documented. Not built: Bulk Extract. Its job needs a create and a separate enqueue call, states its status in a 200 body at a route built from the job id, and returns CSV, none of which the provider-job contract admits. Nothing here has run against Marketo.

​
Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

​
Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.