Ideas

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 fields The 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 Marketo admin section, either when one does not use SFDC as a CRM or when Marketo admins would want to benefit from the capability without going through the burden of modifying SFDC schema. It is important to note than, as with lead fields, both Marketo only and CRM sync'ed fields should co-exist Some program member fields would also exist by default in Marketo to host information such as Program Member Status and date, success and acquire by information. These fields would be synchronized by corresponding ones in SFDC if the program is syncrhonized. This means that Sync'ed member fields and unsync'ed member fields would be able to co-exist in the instance, as for lead fields. Obviously the program member fields meta model would be the same for all the programs in the instance, and all the workspaces Some campaign member fields in SFDC would also be created as part of the MLM package, such as "acquired by" checkbox field and "acquisition date". The Acquired by would also be used in a rollup field in the campaign. [EDIT] as the MLM package does not exist any more, it should be possible to create these fields in SFDC, with a specific syntax, and they would automatically be recognized and mapped by Marketo (as it's now done for the lead score for instance). Population of the fields The program member fields values could be used in forms and filled out from there. The values entered in the form would be stored in the program containing the landing page hosting the form, provided that the LP is hosted in a program. The program member fields would be eligible to the hidden field feature in form so that they could be populated from referrer, URL or cookie values. In case a form is embedded in a non Marketo LP, if the form belongs to a program, the values would also be stored in the program. In case of neither the form nor the LP belong to a program, a hidden standard field or a form parameter could be provided (or added to the form code for an embedded form) that could host the name (or any other ID) of the program supposed to contain the data It should be possible to update the value of the program member fields with simple "Change Data Value" flow steps, in smart campaigns, only if these smart campaigns are located in the context of the program. It should be possible to populate the program member fields through import of members in a program or import into a list located in the program. In case of import into a list not located in a program (a Lead Database list), the import would prompt the name of the program to import these values in ("None" would be a possible answer, in which case the imported program member field values would be lost ). These fields values would also sync with SFDC, so the fields value could also be populated from SFDC. Sometimes, these fields might be formulas in SFDC, in which case they would be read-only in Marketo. Materialization and usage of the program member fields The field values would obviously be available only within a program context, somewhat similarly to program "my." tokens, but with the difference that each lead being a member of the program could have different values. These fields would be available as "program." tokens (to differentiate them from the "my." tokens) and usable in all assets within the program. These program tokens would even be available for webhook payloads. These fields would sync with SFDC campaign member fields, in a 2-way sync, if the fields are mapped with SFDC fields. These fields would also be available to filter leads through constraints for the "member of program" filter and the "Program Status is changed" trigger The program member fields would also be eligible to the "data value changes" trigger and the "data value changed" filter. Alternatively, a separate set of filter & trigger could be created. The program into which the filter applies would be set through a constraint (which value could be set to "is any") The Marketo event mobile app should also be able to leverage these fields to display them or to allow update. The program member fields should also be accessible in read and write modes through the API. A new "campaign member" API will obviously be needed for this. When added to a view in a smart list or a list, these program member fields would display a value only if the smart list belongs to a program Reporting: These program level fields would be used as additional filters in the program performance reports. It should also be possible to add the program member custom fields to generate custom columns in the program performance report. In this case, each possible value of the chosen field would create a column and the rows would provide counts. They could also appear as filter, breakdown or grouping field in the program analyzer. It should be possible to add these fields to the revenue Explorer, as additional dimensions. Especially key to all program oriented report types Example of use cases Storing program membership source tracking, in a much simpler way, without to have to create a complex structure of multiple programs by source. That would make the creation of an offer-channel attribution model so much simpler! Storing visitor food preferences for an event Soring registration date/time to and event or subscription date time on an opt-in and being able to report on it easily Capturing visit hours choices on a tradeshow booth Store a membership date that would be different from the date/time the program member record has been technically created Last but not least, create a very significant differentiation against Marketo competition, with regards to the way SFDC campaigns are integrated and supported (and hopefully one day for MS Dynamics as well). Store the date at which a form fill out was performed for each lead Greg ... View more

Dear Marketo Community, Sometimes we like to check our fields and see how often and where they are being used. Doing so, I miss the functionality of simply export all values. We only get to export a list of the actual fields, but not of the assets and programs. ... View more

Would love to see the same "Sync error" tab for the SFDC connector as the one that will be released soon on MS Dynamics in Spring '16: -Greg ... View more

The new guided landing page templates are great as it enable significant improvement in template dynamics through variables and also reduce errors with the use of elements. Would you please add the same functionality to email (text, snippet and image elements would be needed, as well as variables) ? It would be also cool to add the same kind of functionality that I collected for the landing page enhancement idea ( ) : Add toggle variables that can really remove sections from the template, not just hide them Add drop lists to text variables done with the editor 2.0 Add drop lists to color variables. We could even use a color palette for color variables, being set by the admin. 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. 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. Again, toggles have to remove the code, not just hide it 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 for text variables Have the "Replace HTML" function to be controlled as a right in roles. Have variable to display (in the email editor) 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. Have dependent variable, similar to the visibility rules in the Forms 2.0 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...) Repeating regions. See Guided Landing Page Enhancement: Repeating Region Plain text regions. See Guided Landing Page Enhancement: Plain Text. Make variables "segmentable" (so that we could change color, change a title or make a region visible or not, based on segment). Authorize 2 elements to have the share the same content. In which case they would exactly have the same content and Marketo would control that they are of the same type. 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 a different placement. I would have to enter it once only and the system would make sure that both zones remain identical. Make templates being developed at 2 levels, the template itself, that include the overall frameworks and styles, and also template sub elements, that can be added, placed and reordered freely by the user. See Building modular email templates with snippets ​(Thx Benjamin Arndt​ ). This could also be achieved with reorderable regions, that together with repeating and removables with toggles would provide the same level of functionality. Preprocess emails and inline all styles before sending. See   Thx Brice Dunwoodie​ My 2 cents, Greg ... View more

Large organisation usually have centralized Provisioning / Deprovisioning solutions. But these cannot be integrated to Marketo because there is no API to do this. We would need at least to have the following operations : Create user Reset passord Change / add / remove role Get role list Get User list, filtered by active, inactive or role Delete user -Greg ... View more

Marketo support has access to SFDC sync logs to help diagnose when the sync is lagging behind and what seems like information on the type/number of changes queued to process. Giving us Marketo admins some level of access to those sync log details would help us monitor the sync more closely and be able to provide quicker feedback to users why changes are not updating in a normal time frame. ... View more