Ideas

derelict_wombat · ‎10-14-2025

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

Grégoire_Miche2 · ‎03-01-2018

As part of the GDPR, we need to get consent from people in order to be able to keep their data. If someone registers to download a white paper but does not opt-in, we are supposed to delete any reference to the person. This means deleting it or anonymize it. One very big issue with this is that when we delete the person, it is automatically deleted from all reporting. The work around this is to anonymize the person, since it is accepted that we keep anonymous information in our systems. We can easily replace the first name, last name or email address in the database with "John Doe" or "Anonymous Person". But there are some information that cannot be manipulated from a smart campaign: Cookie IDs attached to the person Inferred and system data such as the IP address Data value changes in the activity logs Fills out form in the activity logs Furthermore, relying on users to run data value changes is error prone. It would be very helpful if a new "anonymize Person" flow step was created. In the field management, we would be able to define which fields should be anonymized, and what would be the anonymous value for each of them (for instance, we would define that the anonymous value for first name would be "Anonymous" and for last name it would be "Person", and NULL for the email address). Then, when running the "Anonymize person" flow step, Marketo would automatically replace all the fields set in the admin with their anonymous value, cleanse the system fields that could be considered as personal Ids and also cleanse all the DVC activities (either deleting them or replacing all values with their anonymous counterpart). -Greg

asd · ‎07-22-2025

新規メールデザイナーでは、旧来のサンプルメール送信の方法が「コンテンツをシミュレート」に変わっており、テキスト版のサンプルメール送信ができなくなっているため、対応させて欲しい。

NagaprabhuK · ‎10-08-2025

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 Activities (form submission alone) your document clearly states 300 records will be pulled in one single call. Whereas in reality just for 26 records, 10+ calls were used by Marketo API moreResults is set to true but the response will not have any result. What kind of logic is this and the worst part is when we raised a support request they simply said "it's a usual behavior" - I don't understand what kind of behavior is this. - API users are counted under users limit - with that of all these limitations I'm not sure why they are counted. It is atleast considerable to a certain extent for counting the license for users with UI access. Why API users? I'm a developer and I have noticed such things, when I speak with Marketing team they are giving even more such list. Very Strange tool.

Shinya_Fujimoto · ‎11-05-2025

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.

anne_sample_f5 · ‎05-05-2025

There's been previous conversations about how "before" date filters include blank values, and whether or not that is ideal behavior. I think the best solution to this would actually be to add another constraint to date/datetime fields called "include blanks: true/false." That way you could make determinations definitively whether blank dates should be included in each filter.

Casey_Grimes · ‎10-31-2019

Upcoming changes to Chromium are enforcing better policies around using Secure and SameSite flags in cookies. Unfortunately, this conflicts with the way Marketo writes cookies today and could potentially cause major issues for Marketo customers once this is rolled out—Microsoft and Mozilla are also planning to treat cookie flags differently around the same time. Could cookie writing please be updated at a minimum to have the Secure flag set (and preferably explicitly declare SameSite=None when appropriate on third-party values and Lax on first-party)? Otherwise, this could lead to headaches. Getting it prioritized now will ensure the transition is seamless for Marketo customers.

Vinay_Kumar · ‎08-19-2025

I was developing a campaign to track records created by Web API users and assign a specific person source accordingly. Although the campaign was set up, it currently qualifies all records created via the API because there’s no way to specify or filter by the individual API user. To improve this, I suggest Marketo to introduce a "User" constraint in the trigger “Person is Created” and the filter "Person was created" to identify which user created the record. This capability would streamline tracking and attribution, making campaign management more precise and efficient.

Michael_Florin · ‎10-04-2025

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.

Grégoire_Miche2 · ‎11-20-2015

The purpose of this idea is to gather all requirements for the next level of program token management. Here they are : New types of tokens required : URL token types () so that managing URLs for CTAs no longer requires a 1 page how-to guide Image / File token types, so that updating a image in a email or LP can be done easily without error () Form tokens types to enable changing the form in an LP without editing the LP. See List and smart list tokens () Formula tokens () All tokens providing program information, tags etc... () Multi line text tokens (not rich text, but just multi-line) List of values tokens ( Thx Andrew Sielen) Select field tokens, so that the standard user cloning programs has the possibility to choose values within a limited list (in conjunction with limited rights, see below). See , thx Robb Barrett Color picker tokens (), which settings could be restricted to a limited set of values. Program level or campaign level UTM tokens that would be automatically appended to emails links PURL tokens (see ) Asset (email, Landing page) tokens, that would provide the asset name, the asset ID, the asset template (see ) Tokens that could store value lists to be used in forms 2.0 select field values (see ) User/sender tokens should also be available for MSI emails: (Thx Josh Hampleman ), (Thx Aqeel Akbar) and Change the Date Token to a DateTime. When used for a webinar it'd be nice to be able to put in the time of the webinar, not just the date, so that we could use the token on reg page. Have a Time Token that automatically parsed it into local timezones. If I set the token for 12:00 CST it'd be nice if it showed up as 1:00 EST on the landing page, based on their locale. Tokens to set CRM users that could be used in lead assignment flow steps. See Furthermore, we should be able to access campaign/program member values as tokens, including SFDC custom fields on the campaign member object (see ) We should also be able to access all SFDC campaign fields as tokens in Marketo programs. See , , , and this one and this one: . Of course, all these would be used in flow steps (such as change data values, interesting moments, SFDC task creation, etc...) and in assets Token management also needs some significant improvement : We should be able to know easily where a token is used (see , thx 54930 and , thx Jordan Lund Token name change should be propagated to where they are used (see , thx Boris Kiperas) We should be able to nest tokens (, thx 77896c23b3a73646ac738677aabf9c4454ddc324 and , thx 3f4b511b1ff3aa191ec9a659bd8f25e857df9b7e) Token definition should be separated from token value entry. We should be able to control who can create / delete tokens or edit token names or settings (see ) and it should also be possible to control who has the right to edit token values. Cloning tokens should be easy (see , thx Cecile Maindron) and moving them should be done without having to recreate them (see ) It should be possible to override token values down to each asset (see , thx @Alan Brown) We also would need to have the token inheritance to be brought to full power with root folder tokens (see ) It would be welcome if the tokens could be ordered in programs or folders to make them easier to manage. See Ability to create validation rules on token, to ensure correct entries (Thx Robb Barrett) Token input should be submitted to some validation. See It should be possible to append some help text to tokens. See Finally, token usage should also be strengthened : "My tokens" could be used as default values for field tokens (see ) My Tokens to be used to be default values for forms 2.0 fields, including hidden ones (Thx 14675) see here More token drop lists everywhere tokens can be used. Using local tokens in forms 2.0 (Thx Dan Stevens). Great one It should be possible to use tokens in filter and trigger parameters and constraints. See (Thx Jeff Shearer) and more globally in all smart lists in smart campaigns. See (Thx Dan Stevens) UTM tokens should automatically be appended to all email links. see It should be possible to update {{my.token}} values from within a smart campaign. See Use of tokens to populate form field list of values () Program, lead and company tokens should render in MSI. See (Thx Alex Stanton) All these improvements, combined, would lead Program + tokens technology to a unmatched productivity tools for marketers in small to very large teams. -Greg

Jose_Tarzian14 · ‎09-20-2024

New possible duplicate records could be found by adding new fields or combination of fields in the "Duplicate Fields" filter. Besides the existing ones, we believe the following ones would help detect duplicates: 1- Mobile Phone Number 2- LinkedIn Profile URL 3- Combination of First Name, Last Name and Company Name And we understand the level of complexity of doing so should be relatively low.

fabiomcruz · ‎09-24-2025

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.

Sant_Singh_Rath · ‎09-23-2025

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.

Yanick · ‎09-16-2025

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.

Anonymous · ‎09-19-2013

It would be great if there was a recycling bin or trash can that would hold data for a set amount of time before it's permanently delete. Similar to the SFDC recycle bin where we can go in and see what's been deleted the last 21 days, and also as an admin I'm able to go in and see what other users have deleted out of the system and if need be retrive the files.

Zoe_Forman · ‎03-26-2025

Due to a Salesforce input error, we need to find emails from outside the United States ending with a local email domain in our database. Can we add a filter into the Email Address for "ends with" ? such as .co.uk .fr . de . see .it etc to identify Country. As often, only two letters using the "contains" filter brings in too many additional addresses where the letters are part of a name or company. This will also help with reporting, personalisation and target audiences. Thanks, Zoe

Matthew_Smith · ‎06-21-2017

As customers utilize newer features within GTW, the use case for this feature will grow and it would ideal for the integration with Marketo to support this.

Anonymous · ‎05-13-2013

We have clients who have requested pdf versions of the newsletter emails we've sent out - and there's no way to currently do this in Marketo. Right now, I'm having to send the email to myself, save as HTML, then export to pdf from there, and then crop the pages in Acrobat. This is the only way I've found to preserve both the look of the email and the active links. It would be great to have a feature directly in Marketo to export to pdf and keep the integrity of images/links.

Grégoire_Miche2 · ‎02-09-2016

One of the recurring issue in the Community is to exclude some lead population from some content type. e.g. Exclusion List and also automating management of subscription center. It's a cumbersome and very error prone process as it entirely relies on user discipline to exclude people who chose to receive only certain type of content. The Community readings on subscription centers is comprehensive, but at the end of the day, no matter how well designed is the subscription center, enforcing visitors choices in smart campaigns is always the weakest part of the process. This idea is to enable admins or some users with specific roles to link an exclusion smart list or some segments from receiving content with this tag. This would work only for mandatory tags, so all content would be submitted to these exclusion leads. For instance, when creating a subscription center, we would create smart lists for : people who do not wish to receive newsletters, called "No Newsletter" people who do not wish to receive event invites, called "No Invite" ... We would then create a program tag with the following values: Newsletter -> Exclusion list = "No Newsletter" Event Invite -> Exclusion list = "No Invite" Content promotion -> Exclusion list = "No Gated Content" ... When preparing and sending email in a program, which tag value = newsletter, Marketo would automatically filter out all leads belonging to the "No Newsletter" smart list, exactly as if the lead was suspended. These tag exclusion lists would apply to program tags and channels. Additionally, if this idea: is implemented, the Tag Exclusion Lists would also apply to asset tags, so that we could filter not a whole program but a specific email. The interest of this approach is that it would be very systematic and even if a user forgets to exclude, Marketo would automatically manage it. [EDIT] When implemented together with workspaces, it should be possible to set the tag-level exclusion lists per workspace. This is because is a multi-BU organization, each BU may have a different approach of the subscription center. [EDIT] asset level exclusions would enable to mimic the behavior of operational emails : some emails would be filtered based on their tag, and some would not. If the asset has no tag, the program tag exclusion list would apply. Another possibility would be that operational emails would not be impacted nor filtered by tag exclusion lists. -Greg

Grégoire_Miche2 · ‎06-18-2015

The purpose of this idea is to start collecting ideas to enhance the fresh new and awesome Guided landing pages. Being able to choose the templates with a picker (as the email picker) would be really a plus for the users. See Make the LP templates really modular, as emails are. See , and , as well as . {display:none} still leaves the code in the LP, which might have various drawbacks, starting with the fact that hidden sections still have to be loaded, which slows down the LP display Enable select / drop list in text variables, in order to limit data entry errors. Enable date and datetime variables. See enable select / drop lists in color variables, to make it easier, reduce errors and limit usable values. See Michael Roper comment below. We could even use a color palette for color variables, being set by the admin. see Have variable to display (in the landing page edit) in the order they are created and not in a Marketo arbitrary order. Usually, the designer will create them in an order that makes sense for the future user. Marketo show them in a order than apparently depends on the type of the variable. See Have dependent variables, similar to the visibility rules in the Forms 2.0 See Enable minimum scripting to leverage boolean or text variable. for instance, I would have a text variable with 3 possible values and 3 zones. depending on the value in the text variable, only 1 of the 3 zones would appear. enable HTML boxes (see Thx Courtney Grimes enable to set min and max sizes for images (in pixels), to avoid users to set images either too big (and therefore too heavy to download) or too small. It is important that one can set min / max width, but leave height free, though. See Enable to set max length to text variables. (See ) Enable to set Alt values for mktoImg elements See (Again) enable to switch to external path for images and in this case prompt for image URL (Let's say I want to reuse an image from my web site...) See again Plain text regions. See Make all type of elements "segmentable" (apparently only text elements are) so that one could have a different image or form, depending on the segment. (Thx JD Nelson ). EDIT: in fact this is already available, but you cannot segment an element until you have first populated it. It would better if it one could segment it event when empty. Make variables "segmentable" (so that we could change color, change a tiltle or make a region visible or not, based on segment). (Thx JD Nelson). See Create a "Script" variable type. When in the template, it would enable the user pick an "application/javascript" type file or switch to a external URL and provide the script URL Create a "Script enabling" toggle variable. The template designer would add this variable and design it to point to a script file stored in Marketo or externally or even enter the script in an editor. The User would be able to activate or deactivate the script just pushing the toggle. Better than the script variable as it leaves less initiative to the user, and therefore, less risk for errors. Example of toggles would be "Add a GA event on form post". Add a "Hide from MSI web activity" in a "Landing Page Properties" -> "page properties" dialog. (See comments below and here ) Authorize 2 elements to have the same ID. In which case they would exactly have the same value. The use case of this is that I may have 2 images, one appearing on certain devices and the other appearing on other devices, with different placement. I would have to enter it once only and the system would make sure that both zones remain identical. See Have token picklist for variables, so that when one want to use a token in a variable, he/she can pick and existing token, instead of having to type it or paste it from somewhere else Have background image variables that would enable to pick an image in variable and would render the image URL, so that it could be used in CSS and/or html background without coding Add more documentation about customizing sections, the edit bar and toggles (Thx Nichole Trobare) Allow for reorderable sections. Together with repeatable and removable ones, this would make for a very flexible template. Make it impossible to approve an LP if meta data is missing. See Enable to use tokens in Page Meta tags. See Use tokens in variable definition. See Token Error Message in Guided Landing Page Template The possibility to set a default form for mktoForm elements in a Landing page template. See How do I set a default form on guided LP template? , Thx Olivia Piper and also The possibility to leave some variables without a default and make them mandatory. See The possibility to manage <A> links with images. See Make it easy to add JS code or tags to a page. See , Thx Courtney Grimes Improving the code editor would also be a real plus. See , thx Joe Schaeffer Please contribute in below and let's make this a collective work to make the new Guided LP the best ones on the market. Greg

Ideas

Add a dark mode to Marketo Designer

Update TinyMCE to no longer strip <picture>, <sour...

Custom Activity Triggers: Enable {{trigger.}} tok...

Archiving a program will unsync program from SFDC campaign

GDPR and Privacy: "anonymize person" flow step

新規メールデザイナーの「コンテンツをシミュレート」でテキストメールを対応させて欲しい

REST API Enhancements

I want to add Adobe ID users from SSO-configured domains

"Include blank" constraint for date filters

Update Marketo cookie setting to not break in Chrome 80

User-Specific Filtering for Web API Created Records in Marketo

Dynamic Chat: Meeting Confirmation Email doesn't list skipped values

Tokens on Steroïds

Add Mobile Phone and LinkedIn URL to Duplicate Fields filter

Marketo unsubscribing users from multiple emails

Native multi step form within Marketo

Share campaign email with internal employees

Recycling Bin / Trash Can

Ability to filter on email address “ends with”

"Simulated Live" Integration with Marketo

Have the ability to create a pdf version of an email within Marketo

Tag-level exclusion lists

Guided LP enhancements