Ideas

As an integration developer, I would like to extend full-fledged support of Workfront and Marketo Engage to help customers who use both platforms. Today, the integration between the two platforms relies on using My Tokens in order to dynamically push and populate content. Because of this token pushing, knowing what tokens are actually in use by a program and which ones are extraneous or unused is important, especially at scale.   Would it be possible to pass a result key-value pair on tokens.json noting whether or not the token is in active use by an asset? This ensures that any token handling is only done to tokens which need it. ... View more

Straightforward request: today, when Marketo Engage exposes email activities via API, it tries to run some pre-calculated values on things such as Device. However, it's unrealistic to expect Marketo Engage to have calculated values for every single user agent, especially as more devices, operating systems, and bot patterns continuously come to market. Rather than take that work in-house, would it be possible to just expose the recorded user agent value to relevant activities? This is already being recorded and shown in the UI, and this change would give integration developers a chance to write more holistic information with the results. ... View more

As an integration developer, I would like to use calls to the "Browse" endpoints of Marketo's assets more effectively. For example, the following API calls have two optional parameters, earliestUpdatedAt and latestUpdatedAt:   /rest/asset/v1/emails.json /rest/asset/v1/programs.json /rest/asset/v1/smartCampaigns.json /rest/asset/v1/staticLists.json This is incredibly useful when trying to manage large-volume instances, as you can constrain to ongoing behavior. However, this ability to filter is missing from several other asset calls, despite them being similar in nature and reporting updatedAt details when called:   /rest/asset/v1/channels.json /rest/asset/v1/folders.json /rest/asset/v1/forms.json Would it be possible to get these two parameters added for these three specific calls? There's likely merit in adding them elsewhere (e.g., snippets.json) but I'm only looking specifically for these three. ... View more

Today, while Marketo has the ability to group a Revenue Model's stages into phases, there is no way to access this data outside of the Marketo UI itself. As a Marketo integration developer, I would like to see the phase a Revenue Stage is grouped into via the API in some way, shape, or form.   The most straightforward way to handle this would be to add additional response parameters to Change Revenue Stage activities to include "Old Stage Phase" and "New Stage Phase", but a metadata call to show how the Model is set up would work equally well. ... View more

When setting up software to interface with Marketo's REST API, especially the bulk API, users are limited to understanding what API manipulation they have within their control—the calls and jobs they themselves have made and can poll. However, this view completely misses any other action other accounts may be using. What I'd like to see is a set of additional features around stats and usage, including:   1. The ability to see how many bulk jobs are queued: right now, you can only manage the amount of bulk jobs your process has created, but there's no way to see what other bulk jobs are running in parallel. I'm thinking of something as straightforward as an API call that lists the current number of bulk jobs being processed. Major bonus points if the call can also give an expected ETA when the next job that will complete first will end. This way, bulk jobs can be scheduled more effectively rather than checking existing jobs continuously.    2. The ability to see how much bulk data has been passed: while subscriptions can have varying bulk data limits for the day, knowing if your API process or if others took up the entire import/export daily limits is difficult. If there was some way to check against the same mechanism that limits data, this would help developers make smarter decisions on how much data to import/export and when it makes the most sense to do so. Alternatively, this can help ensure there's a buffer of bulk data available for other processes.    3.  When using any bulk job status API endpoint, having a (very rough!) estimate of when the job is anticipated to complete returned would be great. Queuing multiple jobs means the estimate you'd have for one job completing may not be accurate, and even knowing within a five-minute window when a job is anticipated to complete helps with properly queuing subsequent jobs.  ... View more

When using the variables.json endpoint today, the returned data does not include the type of variable used (e.g., boolean, string, img, color).  As a result, filtering through complex email variables is more onerous than necessary. Could the variable type be added to the data that's returned, and ideally a parameterized filter when calling the endpoint? ... View more

As of today, using /rest/v1/program/members/describe.json will return default Program Member fields in addition to whatever custom fields have been defined. Although items like Acquired By and Success are present, the field for Success Date is not. Could this be added to the list of extractable fields, both when describing and exporting? ... View more

Today, when using the Bulk Lead Import endpoint with the REST API, users are given the option to declare a lookupField for deduplication matching. This allows for closer control over what versions of a record are updated--particularly if secondary forms of identification, like Marketo ID or Salesforce Lead ID, are used in lieu of email.   However, this same functionality isn't available for the Bulk Import Program Member endpoint; you are instead reliant on email for matching. Would it be possible to get lookupField support added to this call? I'm particularly interested in Marketo ID but would appreciate any other non-email matching available. This is also particularly strange in light of the one-off call for syncing program member data actually requiring the Marketo ID instead. ... View more

As of today, there is no programmatic way to send one-off program member custom field data via requested campaigns; the only alternatives are to run a one-off bulk import job or to run a separate form submission call. However, for existing organizations that already have set up REST campaign requests, there is no straightforward way to append this data.   Ideally, passing PMCF data could be done by including something similar to the way token names and values are passed. At this time, this could only support passing records one at a time through the request, but that's a reasonable compromise for most uses. ... View more

While /rest/v1/stats/usage.json can return API usage from different API users over the course of the day, there's no way today to see a subscription's daily request limit (enforced or purchased). As a result, if you wanted to scale a program to use a certain ratio of calls relative to the subscription, you must first retrieve the number in the UI.   Having API access and exposure to the request limit in addition to daily calls would be a major win for Marketo integration developers, as proper scales and checks could be dynamically built into applications. ... View more

Today, if you wanted to see what Smart Campaigns are idle or inactive via API, you would need to query activities for the Smart Campaign being referenced and work backwards. This makes ongoing performance maintenance for the good of the platform onerous.   By comparison, if one could pull something like the last timestamp someone ran through a trigger campaign or the last time a batch campaign processed more than 0 records, finding what Smart Campaigns need to be deactivated/flagged for review/etc. becomes more straightforward. Often the 6 months inactivity notification is insufficient for larger instances, and more proactive checking via API would alleviate problems for those more complex instances. ... View more

Today, there is no automatic way to set a Salesforce campaign that should be linked with a Program using only the REST API. However, when querying program information, both the linked sfdcId and its associated name are displayed. Would it be possible to update createProgramRequest/updateProgramRequest  so an SFDC Campaign ID value can be passed? Ideally, there'd be an option a la the UI to auto-create an SFDC campaign in addition to setting a predefined value, but even having the ability to link pre-existing campaigns would be tremendously helpful.  ... View more

Imagine a scenario where lead IDs 4 and 5 are merged together in a Marketo instance. 5 is the "winning" ID, so querying the lead via the REST API returns data. However, if you query for data on lead ID 4, a successful API query is returned with no data in it. This means reconciling that 4 was merged into 5 difficult, and leaves a stray ID. Would it be possible to update results on merged records so that they pass something like "mergedInto" : 4 when this occurs?   Bonus points if the winning record also got a note like "mergedWith": 3,4,7 -- something that concatenates all records which have been merged into this winning record; this would be nice to help verify on both ends that a merge was successful. ... View more

Currently, the REST API only facilitates running a batch campaign immediately or once at some time in the future: https://developers.marketo.com/rest-api/assets/smart-campaigns/#batch   This idea proposes that the schedule request be modified to allow setting of a recurring schedule for the batch campaign, as can currently be done with the GUI as shown in the attached image. Setting the recurring schedule for a batch campaign via the Marketo GUI ... View more

As an integration developer, I would like to include Marketo data in various large-scale big data projects. However, there is no reliable way to pull a list of all lead records in Marketo. Marketo's own response to the question historically has been to determine the oldest part of an instance and run rolling 30-day exports of records. This is resource-intensive from both Marketo and the end-user side.   The more reliable option in such cases is to make a Smart LIst that contains all records, then reference that Smart List ID in the bulk export. That requires that marketers set up a Smart List ahead of time—but it makes little sense when there is already a Smart List that does this (consistently ID 1014 across instances).  However, the system-generated Smart Lists cannot be referenced with this export.   Would it be possible to update behavior so either System Smart Lists are compatible with Bulk Lead Extracts or supplemental additions solve the problem of pulling all records from all time? ... View more

Straightforward idea: with folders.json effectively acting as an "all assets" query at this point, could please get the ability to segregate out what assets are retrieved by having the folderType value available for parameterization?  ... View more

Straightforward request:   I would like to have an API endpoint that allows for automated import of programs from trusted instances into a given instance. Currently, only UI controls allow you to import between trusted instances, which causes considerable slowdown and does not allow you to  change conflict rules in bulk(Allow custom conflict rules when importing programs ). Having API access both to set import conflict rules AND the ability to queue imports would be a big win for technology partners looking to deploy standardized programs as well as handle enterprise sandbox->production migration in a smooth way. ... View more