Adobe Marketo Engage

One of the question I get the most often when training Marketo customers is how can create fields that are attached to leads only in the context of a program. An example of this is sending invites for an event and ask for preferences in a field on the form, such as which track they will want to follow, what timeframe they would want to come, etc...For a few quarters now, SFDC has offered the possibility to add custom campaign member fields. This idea would be to enable programs in Marketo to support similar custom member fields, but also some standard campaign member fields that are not currently mapped, such as the member status date.Creation of the program member fieldsThe program member fields would be created automatically from the synchronization of salesforce campaign member standard and custom fields, as for any other field we sync. As with other SFDC fields, the "self healing" schema capability would be required.It should also be possible to create such fields directly in the M

I was so excited when PMCFs were launched, but it doesn't seem they've been shown much love since launch. I know its been mentioned to allow PMCFs to be used within smart lists, and to used to create reports. It would also be great if the individual PMCFs were visible outside of just the Program Members tab - in particular, as a field visible in smart list subscriptions that can be downloaded with reports. Currently its very manual to review what's captured in the PMCF and update it on external reporting. 

At present, the user-defined campaign execution priority is only visible at the campaign level in the schedule tab, it'd be great if we could see the list of campaigns that have their execution priority overridden by the Marketo user along with the default/original and the overridden priority at one place, probably the best place to add this could be the campaign inspector within the Marketing Activities.  

For the SFDC integration, there is multi-batch queuing (MBQ) support to help mitigate the occurrence of sync backlog. This would also be very useful for the native MSD integration, potentially solving a lot of the backlog issues that Marketo clients with larger databases currently experience.   Could this be added to the roadmap please (if it's not already on it)?

Currently, the only way I know of to access reCAPTCHA info from form submissions is to use trigger/filter constraints. It'd be helpful, however, to allow reCAPTCHA info to be passed through as tokens so that they can be used in internal email notifications for new form submissions. Since we just recently implemented the reCAPTCHA on forms, we'd like to monitor the reCAPTCHA info before automatically blocking bot-like traffic to make sure it'll work as intended if we do.   I'm aware we can set up separate smart campaigns with their own triggers/constraints based on the reCAPTCHA info, but that'd result in duplicate smart campaigns to accomplish the same goal

One of Marketo’s most innovative ideas in the early days of the company was Revenue Cycle Explorer (RCE), now named Advanced BI Analytics. — Marketo data extracted and transformed to a cloud repository/BI tool dedicated to advanced analytics. It was a good idea ahead of its time, but the product struggled largely because it lacked the right kind of documentation, and a really well-thought out library of example reports and dashboards. Today RCE may be Adobe/Marketo’s biggest missed opportunity. The idea remains sound, but it needs a rethink that allows for 1) flexibility to house the data in any cloud data store, 2) ability to use Marketo data with other data sets, 3) better and more attribution models users can tinker with, 3) better query optimization and faster data processing, 4) support for any of the modern BI tools in use today, and 5) a robust set of standard dashboards and reports. The world changed radically since RCE was released, now the world needs a better, mode

Marketo's primary metrics for programs are number of successes and new names.  We collect those data points in programs we build, and report on how programs and tactics performed on those measures.  It would be very useful for marketing planning and optimization to provide slots on the program object for forecasted new names and number of successes.     Marketers would be able to employ a simple, and relevant method to plan their marketing and measure outcomes against the plan.

We recently were trying to sync additional fields to Revenue Explorer and kept receiving an error. After opening up a support ticket, we were told that "this is now expected behavior to improve functionality and behavior results within the UI.  Standard fields can no longer be synced as Dimensions and we ask that you should create custom fields to store this data, as this is now the intended design".  So basically the only way to sync these fields is to create a new proxy field for every field we want to sync. How does that make any sense at all?!  Please bring this functionality back.

The current MKTO integration with LinkedIn matched audiences only leverages the email address.  We would like to see company name and other data points on a person record leveraged here to increase match rates and effectiveness of the tool.    Presently, we receive a better match rate through direct list upload as the MKTO integration is lacking functionality.  

Can you please make query string as an available  field for reporting  and smart lists. 

There are some obvious small usability improvements that would go a long way to increase user efficiency in Marketo. These are probably posted already, but I am bundling them here in a single ask under the banner of improving usability.  Allow Custom Fields in use to be renamed Allow List import to update by Marketo ID Sort Person Records in views list by any Field Preview Email by User – Refresh Button Allow for renaming images and files  

We'd like to have the possibility to send our emails only on weekdays and to differenciate this feature for different countries, ex. in UAE Friday is not a working day but Sunday.

After cloning a Program, you often need to make many manual adjustments to Smart Lists and Flow steps to customize the cloned Program.  Supporting tokens in Smart Lists and all Flow Steps would allow for modular programs that could be configured with tokens reducing the manual configuration steps

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

Tokens are really helpful and powerful, but become very difficult to clean up when you’re managing them long term. What would help is a ”Used By” view that shows you all the assets actively referencing tokens, enabling user to identify where references need to be updated or removed.

It’s not currently possible to recover deleted or previously saved versions of programs and assets. To solve this, provide: A change history function on assets and programs that enables you to revert to a previous version, see who made changes/created new drafts, and when A recycle bin feature - a temporary holding zone for all deleted smart campaigns, programs, assets, where they can be retrieved from if needed.

Please remove the date format put in place by Marketo. It is an inconvenience for customers to interpret YYYY-MM-DD.Please update the date format to MM-DD-YYYY or let the user decide which date format they want to keep.

Currently, when trying to submit a form via REST, you receive a 1006 error code "Field '[X]' not found in form definition" if the field in the payload is not configured in the form. This behavior doesn't appear to be documented anywhere that I can tell other than the actual error message, but this seems like a huge missing feature in terms of establishing parity with other form submit methods such as the Forms 2.0 API which allows you to addHiddenFields with any valid field, regardless of if it is defined in the form or not. This front-end behavior is a huge advantage over other form libraries as it allows global form solutions to scale easily and would be a welcome addition to the REST behavior as well.

I'd love to have the ability to duplicate individual flow steps and smart list filters in a smart campaign. It would save time when building campaigns by eliminating the need to recreate repeat steps and filters. 

Hi all,    as everything in internet space move forward quite fast so we as well moved to Google Analytics 4 property.   However as I quickly noticed in RTP product documentation, there is nothing about integration with latest version of Google Analytics 4.   At this stage I'm not sure whether it is just lack of documentation or lack of functionality to integrate with latest version of GA4. If there won't be official announcement soon I will run test on my end but will be really nice to hear official answer on that.   Best, Konrad

Currently it is not possible to include List Import Aliases in any type of field export (UI nor API). Having the ability to include all field metadata in a UI export, or at least the API would be helpful when doing field audits, migrations, etc. 

Any reports that are set up within a program of course are meant to report on that program specifically. When cloning a program, reports that are set up directly under the program itself are updated automatically. However, when you apply some housekeeping on more complex programs and put reports into a subfolder, the updating of this reference to the cloned program no longer happens. It would save a lot of manual work if this would also be updated automatically.

It's great that so many people helped with the re-ordering of Progressive Profiling fields though Javascript. But why is not possible to just drag & drop the whole section on the form editor? Nobody wants their ProgPro fields underneath an opt in box.

To extend the idea provided at "Add additional usage data for bulk API queries", handling bulk API data should be adjusted to understand datacenter locales as well. As an example, if you were looking to set up API extractions after a daily API limit is passed, knowing where the datacenter is helps integration providers understand when, exactly, an API limit will reset. Would it be possible to get AB, SJ, E, NL, SN, etc. passed as a result to calls like usage.json, or could we get a generic instance metadata call to provide information like this?

Today, users have the ability to use the "New --> New Person" menu option inside the Database section of Marketo to directly add a record if necessary.   However, the New Person flow does not account for pre-existing records with the same primary key—even if both versions of the record are Marketo-only and not synced to a distinct CRM record. Would it be possible to update this behavior to either explicitly prevent creating a duplicate in the Marketo database or notify the user that a user with that record's email address is already associated with a record?   Again, I'm not sure if this is an "intentional" workaround for creating duplicates, but it's unexpected behavior.