Ideas

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

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. ... View more

Please add the ability to export/download email samples as PDFs. It's helpful for internal sharing of campaigns. Downloading HTMLs are difficult to save somewhere others can access/remains a link and there's no way to convert it. ... View more

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. ... View more

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 ... View more

Hello Adobe community, For those of us using Advanced BI Analytics for the enterprise, I think it's a great idea to introduce access level permissions such that we can assign specific view only, read/write, create permissions for different users of the platform. It would also be useful to have permissions for different dashboards or reports, for example, certain teams could have access to a high level dashboard but not an operational one. Such arrangement would also make it easy to find reports & dashboards.  Is it a bad idea to split the dashboard platform across workspaces ? it may be for a small or mid-size business but for a company like mine, which has many business units and lots of persons with access to marketo, I don't think so. I think it's primordial if we want to avoid the chaos of having multiple users from different departments using the platform.  ... View more

Currently, Marketo’s report subscription feature only allows users to select the day for report delivery, without the ability to specify a time. I’d like to propose an enhancement to include a time selector within the subscription settings. This would allow users to schedule reports not just by day, but also at a specific time, enabling more precise report delivery aligned with business hours, stakeholder availability, or operational workflows. Adding this flexibility would improve usability and scheduling control, especially for teams working across different time zones or requiring reports before key meetings or decision-making windows. Thanks ... View more

Hi, I wanted to suggest adding a new filter option in the dropdown for time frames.   Currently Marketo has the below:   1. "is" (Specific date) 2. "is not" (specific date) 3. "between" (b/w specific dates) 4. in past (one filter - such as past 30 days) 5.  in time frame (today, yesterday....) 6. after (specific date) 7.before (specific date) 8. on or after (specific date) 9. on or before (specific date)   I’d like to recommend a new filter that allows users to select a range within relative time frames.  For example, filter data between "past 3 months" and "past 1 month", effectively capturing a 2-month window. Currently, this can be achieved by combining two separate filters. A dedicated option would simplify this process.   Let me know what you think 😄  ... View more

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    ... View more

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. ... View more

There is no option to accommodate a long string within the Program Member Custom Field object. A text area field would allow us to store URLs with long query parameters, lengthy content for personalization, and open-ended form responses within the program context. ... View more

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. ... View more

Can we add an option in the admin section where we can define the default fields of a forms, when a new form is created within that particular instance. Ex: Currently whenever we create a new form, we always get First Name, Last Name and Email. There should be an option in admin section where we can define some custom fields like UTM etc. as a default field available in the form whenever anyone creates a new form. ... View more

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 ... View more

Can you please add the ability to rearrange the fields on the layout when viewing custom object records? The fields are perhaps arranged according to the order in which they were created, but there are logical groupings that we want to create to make it easier when viewing the records. As it stands, we have date fields that are all over the place, in an order that is not helpful.   ... View more

As we continue to use forms within the tool and require access to view submission data, we've identified a need for the creation of multiple people views that can be shared with our users. This enhancement would eliminate the necessity for each user to individually set up their own views, promoting greater standardization and consistency across our instance.   We kindly ask you to consider adding this shared view feature as a potential enhancement in upcoming updates. Thank you! ... View more

We are currently unable to capture url parameters when a user engages with a dialogue in Dynamic Chat. This is a big miss IMHO because it means we're unable to align dynamic chat engagement with campaign activities, or campaign costs. Many people user UTM parameters, and we currently use GCLID and CMPID as parameters to align user engagement to marketing activity, and marketing investment.   Capturing these parameters is critical to showing DC value. ... View more

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. ... View more