Adobe Marketo Engage

This could be me coming from Drift before Dynamic Chat, but the one item that I really miss and would love to have is their path that shows where people are dropping off in conversations. We would review this quarterly, at least, to see where our content needs to be adjusted to help push more people through the chat. It also helped us to see how many people would click on each option throughout the chat as well so we could get a rough idea of how many said support, billing or sales to go through those paths. 

Summary of Request The current Adobe Marketo Engage REST API is severely limited regarding the programmatic construction of marketing assets. While we can "Clone" or "Trigger" assets, we completely lack the ability to Create, Read, Update, and Delete (CRUD) the internal logic of Smart Campaigns (Flow Steps & Triggers) and Smart Lists (Filters & Rules) via API.As marketing operations move toward hyper-automation and dynamic campaign generation, the inability to define campaign logic via code is rendering the Marketo API obsolete compared to modern, developer-friendly platforms. We urgently request new endpoints to manipulate these assets' definitions directly.Current Limitations & Pain Points Smart Campaigns are "Black Boxes" to the API: The Problem: We can create a shell campaign or clone an existing one, but we cannot add, edit, or order Flow Steps (e.g., "Send Email," "Change Data Value," "Wait") or Smart List Triggers via API. The Impact: We cannot dynamically gen

It would be extremely useful to be able to utilize $TriggerObject in Email Script Tokens for the "<Custom Object Name> is Updated" trigger, in addition to the "Added to Opportunity", "Opportunity is Updated", and "Added to <Custom Object Name>"  triggers. This would provide the following benefits: Increased flexibility in Email sends using VTL tokens Increased efficiency in API use Increased scope of Custom Object use

Having a form performance report where completions could be viewed by day, week or month would be of great benefit to users that embed forms on their web pages vs. using Marketo landing pages. This would allow allow users to analyze form completions week-over-week, month-over-month or year-over-year without having to build smart lists for each time frame. It could also be used to see number of form completions over the course of the year by month.Furthermore, smart lists only report unique people that filled out the form within the defined time period, making it incredibly challenging to account for multiple submissions by the same person within that given time period. This report could have two option 1) to report by unique people that completed the form and attribute the most recent completion to its time frame or 2) to report total form completions.

Today in MSI our sales team can create modified list views for Best Bets using basic "AND" statement logic . In many cases the team would like to be able to configure this list using more advanced logic such as "OR" statements and logic groupings. A AND (B OR C)  

When simulating an email in Marketo and trying to add people as recipients, the list of available people is empty. Users can only add recipients if they already know the exact email address and search for it explicitly.This behavior is extremely cumbersome and inefficient, especially for testing purposes. It would be much more user-friendly if existing people records were displayed in the list, allowing users to simply select recipients instead of having to manually search by email address.Additionally, if an audience (e.g. a Smart List or static list) is already defined within the program, it would be very helpful if those audience members could be shown and selected directly during email simulation.Displaying available people and/or program audiences would significantly improve usability, save time, and reduce friction when testing emails. 

While being able to list out individual Program cost line items is a useful feature, it's limited by a few things: namely, the ability to only parse certain types of budget information based on information in the note. I would like to build a more robust approach for budget measurement and compliance in Marketo by providing a standardized set of custom fields that could provide more detail in budget analysis. While I would expect to have some of these as fully custom, I think others are widely applicable and may make sense to be in the core product. Some examples of these would include: - Spend Type: Categorizes the primary expense of the campaign (e.g., 'Media Spend', 'Agency Fees', 'Content Creation', 'Sponsorship'). This allows for a more granular analysis of where the budget is going and the ROI on different types of spend.- Budget Source / Team: Tracks which team's budget is funding the campaign (e.g., 'Corporate Marketing', 'Product Marketing', 'Fiel

Description:Having he ability to remove/delete/replace custom dimensions from those 10 in the system tab.

I want to add Adobe ID users from SSO-configured domains.The reason for this is that we use Marketo and AEM at multiple locations globally, and although we use a common domain, some locations do not support SSO.Users in SSO-configured domains cannot be added using Adobe ID, so new users cannot use Marketo and AEM.

One of my biggest issues when it comes to coding landing pages/ emails is the white screen that plagues the Marketo Designer. It would be really cool to add the option to switch on "dark mode" to make coding easier as the black screen helps with coloring and finding/fixing errors. I'm not entirely sure if this already is a feature - but I haven't been able to find it and I think it would be an awesome asset to add for people who tend to code a lot and don't have the resources outside of Marketo. What do you guys think?  

When developing email templates that work with both light and dark mode, using <picture> and <source> tags with a fallback <img> inside it is a clean way to set both light and dark mode images without having to assign the image a conditional media query show/hide via CSS. However, the TinyMCE editor today will strip this markup rather than allow it to be in editable areas. Can this please be updated to no longer have this behavior?

It would be great to be able automatically un-sync a program from a SFDC campaign when the program is archived. 

Hi Team, I’m currently working on a requirement related to interaction aging buckets. The idea is to categorize leads based on their most recent engagement in Marketo and assign them to corresponding buckets. I’ve created a text field for the interaction bucket, which I’ll start populating once the full solution is ready. To determine the appropriate bucket for each lead, I’m using the Marketo activity log to track opens and clicks. This helps us identify the least engaged leads and allows us to tailor specific campaigns or strategies for them. For context, we also have a custom rule that marks a lead as ineligible if they haven’t engaged for over 18 months. By implementing these buckets, we can be more mindful of engagement levels and run targeted re-engagement strategies. Below are the bucket ranges we’ve defined:My question here is :For example, in the 121–150 day bucket, I’m seeing leads who have interacted in the last 30 days, which is causing confusion.I’ve created

The following are the REST API Enhancements we as a user are expecting to see it in near future. - Asset creator details to be included in the API (Email, Files, Campaigns etc.,)- Flow ID is returned in campaign API, however there is no endpoint to utilize and get the flow details- SmartList Cloning option is there, however there is no SmartList Update option (PUT method for updating the rules/criteria/conditions) via API. Likewise for Files, images can be created via API but there isn't an API option to update (PUT method) it. How come your product team ended up with just providing endpoints for reading and updating the meta data? Why should a development team in a company should create lines of code just to update a file name. I completely don't understand. - Final member count in a smartlist is not able to be pulled via API, again I'm not sure why this not considered as a meta information.- Worst pagination technique followed for returning records. While trying to pull the

If you have a Conversational Flow with a Meeting Booking, and set info capture to "Skip if value is already in database", the meeting confirmation email does skip these fields as well. That's not a great experience. If the value is skipped, because it already exists in the database, the confirmation email should grab that value from the database. Otherwise the sales person that takes the meeting doesn't get that information. Here's the confirmation email for a new person that doesn't skip values: And here's the same confirmation for a person that is already known in Marketo:Sales Person wouldn't know First, Last, Country and Company Name.

I've had this request from our sales team. They would like to be able to view leads who have visited specific pages and/or content on our website. While I can set this up as an Interesting Moment its still only showing at the person or account level. They want a view where they can filter by using a URL on from our website and see a list of their leads have viewed that content.   

User field "reason" should be editable.Since Marketo migrated to Admin Console, this field is no longer available. It used to be available on creating a New user in Marketo, but it isn't available when creating a user in Admin Console.It was always annoying that it couldn't be edited after creation.With a large instance, and almost 100 users, this field is important for managing who is who in the zoo. 

When editing any email in the new email designer, Edit Email Content>AI assistant (option on the right bar)>Text settings>Language. The only language option in which the text can be generated is English.  There should be support for multiple languages like, German, Polish, French, Italian, Spanish, Dutch, Portuguese, etc. 

Experiencing an issue while creating new event channels in Marketo—specifically, the dropdown under System Mappings isn’t allowing us to input additional values.Need to link the defined Statuses under the Channel with the appropriate System Mappings.

Currently, Marketo forms are limited to single-page layouts. If we want to create a multi-step form (where users can complete one section, then click “Next” to proceed to another), it requires custom code or third-party tools.A native multi-step form feature would be really useful because:It improves user experience by reducing form fatigue. Instead of seeing a long list of fields at once, users can progress step by step.It often increases completion rates, since breaking questions into smaller chunks feels easier to complete.It makes it possible to collect more data without overwhelming prospects.It keeps the form design consistent and aligned with Marketo’s existing functionality, instead of relying on workarounds.I’d love to hear if others have faced the same challenge and whether this would be a valuable addition for you as well.

Field Mapping between CRM (Salesforce) and Marketo currently remains in perpetuity, disabling the Marketo Admin's ability to remove (or merge) a field if it has ever been mapped to a Salesforce field.  A client of mine was just informed on a support call that this field mapping cannot be deleted from Field Mapping, and once a Salesforce field has been mapped it must remain.   Salesforce admins consistently over-permission fields to the Marketo Sync User, which creates incredible amounts of technical debt and sync backlog issues for Admins.  Our current solution is to get our Salesforce admins to remove Field Level Security (FLS) permissions from within Salesforce, which addresses only part of the problem.  However, we have no means in Marketo of removing the field association within Marketo Admin so that we can remove the technical debt (the field that was errantly created) on our side.   Please allow Marketo Admins, either via Support or via a UI mechanism, to

Some time ago, Adobe recommended using the “share with a friend” option, but this feature is no longer available:https://nation.marketo.com/t5/product-blogs/deprecation-of-forward-to-a-friend/ba-p/358045#:~:text=As%20of%20September%2029%2C%202025%2C%20the%20Forward%20to,been%20or%20will%20be%20sent%20using%20the%20token. We need a way to share emails with internal personnel for review before sending them out. Since we are working with the new email designer, we must avoid adding employees as additional contacts in Marketo, as these would count against our license.

We’ve seen a sharp spike in unsubscribe rates in recent months. Unsubscribe logs show users being marked as unsubscribed across multiple emails (see image), with entries spaced just 5 minutes apart—this does not reflect actual user behavior. This issue began in June 2025, coinciding with the rollout of one-click unsubscribe by major email providers. It now inflates unsubscribe metrics, distorts performance data, and raises serious concerns about potential domain reputation impact. Other Marketo customers are reporting the same problem. This is more than noise in analytics—it’s a systemic issue that demands urgent investigation and resolution. 

Hi,   I think it would be great if we have a multi-select option to select more than one tag value for a specific tag in the system. ex: Lets say i have a tag named Vertical and I would like to select more than one picklist value during the program creation step. Currently, we either have to select one or come up with a specific tag value that could accommodate this specific need as we are unable to select more than one value from the picklist.   Thanks, vineela.  

オーディットレールの情報は、最大直近6か月分しか管理画面でエクスポートが出来ず、また手動作業でのみしかエクスポートが出来ない。Marketo上のデータは、個人情報（氏名、メールアドレスなど）を含む情報を取り扱っているため、その操作ログ（オーディットレールの情報）を6ヵ月以上保持（最低3年間は保管）を社内ルールとして求められている場合に、都度、手作業での個人情報を扱う作業はリスクが高い（漏洩事故につながりやすい）ため、Marketo内に蓄積されているオーディットレールの情報をシステム間連携で、保存できるよう仕組み化したく、オーディットレールの情報を取得するAPI機能の追加をお願いしたいです。