Ideas

Marketo was built from the ground up on the idea that all fields should be on the person record.  Yes, you can pursue a one-to-many design using Custom Objects but they are difficult to use because they are implemented by way of API calls.   Features that could solve this:   Add new "List Field" Fields Type that can hold multiple values.   Support one-to-many with Flow Steps to Add/Remove/Filter items in "List Field" or Custom Objects ... View more

The trigger tokens for Custom Objects work perfectly when the trigger is "Added to Custom Object" but the "Custom Object is Updated" trigger does not allow you to use these. In most cases, you need both of these triggers to work for a marketing process to function correctly.  ... View more

Hi all,   it would be great to enhance the Delete Custom Object API endpoint by the possibility to delete multiple records with one call* by e.g. allowing createdAt, UpdatedAt and individual dedupe fields as criteria.   Examples: Delete all custom object records created on 1/1/2020 Delete all custom object records where dedupe field "ABC" = "XYZ"   Kind regards, Thorsten   * other than IDs or _all_ dedupe fields...  ... View more

As outlined on Merging Person Records Disconnects Marketo Custom Object Record   Marketo custom object records can be disconnected when person records are merged. This is annoying as the custom object records then need to be re-connected.   It would be good if when person records were merged that the remaining person record automatically had all Marketo custom object records associated with the merged records associated with the remaining person record. ... View more