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...
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 ...
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 ...
This is so minor it may as well be trivial, but would also be (presumably) a small fix: could the MIME type Marketo serves for icon files (.ico) be updated so it uses image/x-icon?...
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 quer...
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 Acqu...
Straightforward request: I am a big advocate of using Marketo's description fields when using any sort of asset that's in a Marketo tree—a local asset, program, campaign, folder, t...
Beth, if I could like your comment five times over, I would—this solves several pain points I have. Still would like to see that in the UI (or at least explained somehow that this ...
There are times when a user may send a record a sales email from Marketo Sales Insight, only for the recipient to be uninterested in the email and unsubscribe if the option is avai...
It looks like there's been some recent improvements to Marketo Engage's form accessibility around validating fields. This is great! However, there are some small tweaks that need t...