Product ideas | Community
Skip to main content

Filter by idea status

10000 Ideas

Alok_biswas
Alok_biswasNew Participant

Dedupe rule and Marketo trackingNew

As an automation platform, tracking leads in a holistic manner is crucial.    Currently, if your Marketo platform has an additional dedupe rule set other than just an email address, it won't differentiate between leads if the same browser has been used to fill out the form.   Let's take an example:   Let's say your Marketo platform has a customized dedupe rule of Email + Last name. Ideally when a lead 'A' fills out the form entering both of the parameters exactly the same as per an old lead that exists in the database then it should update the corresponding lead in Marketo else it should create a new lead.   Old lead present in Marketo database: email: alokbiswas1@gmail.com, Last name: Biswas New lead fills the form with details: email: alokbiswas1@gmail.com, Last name: Biswas   Then the same old lead should get updated.    New lead fills another form with details: email: alokbiswas1@gmail.com, Last name: Alok   Ideally, a new lead should get created as the 'Last name' is different.   Current Issue1:   So, when the lead fills multiple forms or even the same form in the same browser, then the old lead is getting updated even if the lead enters a different 'Last name' every time.   As per Marketo, it's happening due to the cookies in the browser. Ideally, this concept contradicts the concept of the de-dupe rule   Current Issue2:   Let's say your Marketo platform has a customized dedupe rule of Email + workspace. Ideally when a lead 'A' fills out the form of workspace 'A' and the same lead fills the form of workspace 'B',  then it should create duplicate leads instead of updating the existing one.   For now, it will update the existing lead in case the second form fill happens in the same browser due to cookies.   Suggestion:   So, Marketo should enhance its tracking in the upcoming releases. As we have workspace-level Munchkins as well. Basically, if a lead opens the LP of workspace 'A', its respective munchkin should be linked with the lead record. When the same lead opens another LP of workspace 'B', then it should not link with the munchkin of workspace 'A' and should treat it differently.

dleblanc01New Participant

Nested segment two-way inheritanceNew

Description - I thought I was being smart when I set up segments to contain learning assets for each product, then collected those inside segments for the business units that "own" the product, and then nested the BU version into larger org structures. I figured that this way, I could update, say, the product segment and that would populate to the BU and larger org segments. Or that if I updated a smaller segment inside one of the larger ones, the update would cascade down to the product segment. The result has been that if a new asset was created, the changes are only applied to whatever I directly edit. I have to go add the new item everywhere that the related segments are nested into other segments. It is frustrating and time consuming and ultimately can lead to errors where not everything was properly updated. I can see why it might not be desirable for this to be automatic for some use cases, but a toggle to turn on change inheritance would be great. Why is this feature important to you - It would automate manually intensive labor to avoid errors and free up time to focus on bigger work. How would you like the feature to work - Say that I create 26 segments, each for files starting with a letter of the alphabet. Then I create a nested segment including segments a-c, d-f, etc. And then finally, I used the nested segments (a-c, etc.) to  create a larger nested segment containing all of the alphabet segments.Then I get 3 new assets, each a different letter of the alphabet. When adding these, I want to make the change once for each. Whether that's in the exact letter segment (a, b, etc), in the nested segments a-c, d-f, etc, or in the larger nested segment of all of the alphabet, I want that change to be automatically applied to all of these in the right places so I don't have to do it individually for each of the 3 new assets.

Jennifer_Dungan
Jennifer_DunganNew Participant

Make the Workspace Text Colour Pallet more readable between Light/Dark Mode displays (provide preview sample for each mode in the selector)New

Description -As pointed out in https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-questions/multiple-black-colours-when-using-colour-palette-in-text/td-p/590810 Some of the colour options available in the colour pallet work well for Light Mode and not for Dark Mode... since Light/Dark mode is left to each user to choose, it can be hard to ensure that descriptions and notes are properly visible.   While the colour pallet does oscillate between shades, the readability of those shades isn't exactly equal. Perhaps WCAG's colour contrast checker could be used to ensure that shades meet the accessibility standards in each mode, but providing options with similar contrast balance. In addition, to help report creators see what the colours might look like, I am suggesting that the pallets for light/dark be shown with a sample so that the creator doesn't need to switch their modes constantly to see the result.  Why is this feature important to you -Notes, descriptions, text blocks, etc are important to provide context to the reports... if these can't be read, they are no longer doing their job.  How would you like the feature to work -I am suggesting to display the colour pallet showing both variations (the selection box with a diagonal slash showing the Light Mode variant on the top left and the Dark Mode variant on the bottom right) and providing a Light/Dark Mode Preview sample.The preview should change with hovering over a colour, and when not hovering, show the current selection (The text could just be coded to "Sample", it doesn't need to reflect the actual text in the description)  In addition, the colour option in the top right (position 5) the colour contrast in Light Mode is quite different from the contrast in Dark Mode... I would suggest reviewing the colours against WCAG Contrast Checkers to find colours that site within a similar contrast range The Light Mode Variant (Cyan on White) has a contrast ratio of 1.66:1The Dark Mode Variant (Dark Blue on Grey) has a contrast ratio of 1.85:1(Both technically fail WCAG at default font sizes, but the Cyan is more readable)  Current Behaviour -There is no way to preview the colour options without switching between Light and Dark mode.. this takes extra time that a lot of report curators wouldn't normally take. The colour options aren't completely one to one between Light and Dark Mode when it comes to readability.. making some information significantly harder to read when in certain modes.

jeff_bloomer
jeff_bloomerNew Participant

AA Workspace - Dynamic Elements for Text FieldsNew

Currently in Adobe Analytics, I have text field elements for recurring, monthly reports that I must manually change before I can send them out.Description:I would like the ability to drag certain components (date ranges, eVars, segments, etc.) into my Text field and choose to display the title or value represented within that component.For example, if I dragged in a date range, it would display the beginning and end date, or if it was Last Month, then Month-YYYY.Why is this feature important to you:I have a number of reports where these are the ONLY updates I need to make, whereas the rolling date ranges inside the reports automatically update themselves.  If I can then have these dynamic elements, I would only need to make a periodic QA check of the contents and focus my energies elsewhere.  This would be a much-appreciated productivity enhancement for me.How would you like the feature to work:Similar to the diagram above, I would like to either drag and drop a component (easiest) or type in a variable that represents the value I would like to display when the text field is not in EDIT mode (i.e., when the checkmark and 'x' are displayed).If I drag a component into the text area containing more than one value, I would like the option to choose or search for the value I would like to display from a list of existing values, OR, I can choose a value from the List of Items within a component to drag into my text area.A bonus for this feature would allow me, AFTER a component with multiple values is dragged into  my text area, I can select it in-line and choose a different value to display, if/when needed. 

CarolMajewskiNew Participant

Option to Field Format a date field as Date/Time on the Header within a Layout TemplateNew

Description - We would like the option to format a date field to show Date and Time on the Header within a Layout Template Why is this feature important to you - Working in an agency environment, our tasks are due in hours not days. Our users work out of their Work List to see work items assigned to them. They use the time due to help prioritize their tasks. We have added the Planned Completion Date to the Task header page to show at the top of the Task page and the Task Summary Panel on the Home page, but it only shows the Date due not the time due. When assignees click on the Planned Completion Date field in the Header to view the time due in the Calendar popup window, it changes the task constraint to MUST FINISH ON (even if they just view the calendar popup and don't modify the date or time). How would you like the feature to work - I would like to be able to Field Format a date field to show Date and Time not just Date in the Header within a Layout Template. I would like the functionality to be the same as in Reports where under Advanced Options you can select Field Format. Current Behaviour - When adding Planned Completion Date to the Header in a layout template it only shows the Date. If an assignee who has task editing access clicks on the Planned Completion Date field in the Header, even to just view the time from the calendar popup window, it changes the task constraint to MUST FINISH ON and breaks the waterfall timeline.