Product ideas | Community
Skip to main content

Filter by idea status

10000 Ideas

Gigazelle
GigazelleEmployee

Include currency conversion in calculated metricsNew

There is currently no form of currency conversion in Analysis Workspace. There is a rudimentary version in Reports & Analytics, but is woefully inaccurate and report numbers change depending on the day that you look at a report. Why this feature is important - Organizations that operate internationally need to view revenue in various currencies throughout the world. Current implementations for multiple currencies involve highly customized and complex implementations to accommodate them, when Workspace could fairly easily enable it for everyone out of the box. How I anticipate this feature could work - When dragging a metric into the calculated metric canvas, add an option inside the gear icon. In addition to 'Metric type' and 'Attribution', add a 'Currency conversion' section that allows you to select: The currency that the metric is currently in The currency that you want to convert the metric to Adobe already partners with XE (see currencyCode) for converting currency from the currencyCode variable to a report suite's currency; it seems pretty reasonable to use XE's API to retrieve daily currency conversion for a reporting date range. Having this feature in Workspace would allow you to perform advanced analysis on many different currency types, and allow an organization to view any metric in any currency. It is also valuable in both traditional Analytics and Customer Journey Analytics, as both products can benefit from having flexible currencies at report time.  

emarganneNew Participant

Time consumed by customersNew

Description - Let’s imagine you have many customers with many contracts. On some of them you let them the opportunity to consume 15 F.T.E. a month. When doing your planning you can see the total availability of the team and also where their time is planned (resource planner report). Now if you want to see in a simple dashboard, as the resource planner, the remaining F.T.E. that customer has and where time is planned so that it does not go over the 15 total… How would you do that ?   I will even add a more complex point. You may have several customers sharing the same infrastructure (servers, network, …) all of that infrastructure has to be maintained. You are logging operational time in Workfront. Customers pay their share to the common infrastructure acording a defined ratio, so you want to reflect these ratios in their 15 F.T.E.. That would give you the remaining F.T.E. for the month at any time regardless of it got spent on operational or project time.   Why is this feature important to you - We like to keep track of where time got spent in Workfront. We want to automate reporting for our customers through Workfront.    How would you like the feature to work - A sort report comparable to the "resource planner" in which you would select a customer and it would show if time got spent on operational time or projects.   Current Behaviour -  We have to extract the resource planner view with a filter on the customer to determine the time passed on project. We then add the percentage of time passed on operational time to determine how much FTE is left for the month for that customer.Each time we need to plan a project we have to repeat the operation.  

Grégoire_Miche2
Grégoire_Miche2New Participant

Have extended Marketo Program member fields and use them to full power (with or without SFDC campaign member field sync)Delivered

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 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-existSome 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 workspacesSome 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 fieldsThe 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 dataIt 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 fieldsThe 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" triggerThe 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 programReporting: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 typesExample of use casesStoring 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 eventSoring registration date/time to and event or subscription date time on an opt-in and being able to report on it easilyCapturing visit hours choices on a tradeshow boothStore a membership date that would be different from the date/time the program member record has been technically createdLast 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 leadGreg

edersantosNew Participant

Show the correct time of the time posting (Timesheet)New

Description - We have the following Issues:I raised this ticket here (Case #00337225) and was told that there is no solution at the moment, so I am putting this on record. This is an important issue because without this we don't know if the user logged into the system today and put in hours on past dates.1 - In the user updates it does not show on which date I posted the timesheet, it only shows me the update from when I attributed the hours.See, for example, I log into the Timesheet and fill in information from previous days, still in the example, Let's suppose I logged in today (October 21) and filled in hours from October 10.What happens today is that I don't have a clear view of when the user added those hours. Because the system shows me that the user logged into the timesheet on today's date, but does not tell me which dates he actually filled in. Is that clear to you? (attached screenshot of what I am saying)2 - The second issue is that when we post hours in the "General Hour" topics, which are: sick, vacation and etc... The system, besides not returning to me the real date that I filled that field, does not return to me the Hour Type name.   Why is this feature important to you - is important, because then we will know the right time that the user posted his or her hours.  How would you like the feature to work -That it is possible to check by user updates and have this field available in the report Current Behaviour - Currently, we do not have this information and we are unable to verify which moment (date/time) the user posted the time.