Skip to main content

Filter by idea status

10000+ Ideas

Andrew_Wathen_
Andrew_Wathen_New Participant

All our niggles from the first month of using Adobe LaunchNew

We've recently moved over to using Adobe Launch which was on the whole a very positive experience. However, there is always room for improvement and I've kept a list of all the little niggles that we came across in the first month which I've provided (in no particular order) here below... Adobe Analytics Set Variable action - Add conditionality to individual variablesThis form/interface seems a little clunky and unsophisticated.  I'm guessing this is because it was done this way for DTM backwards compatibility?  It would be good if this was re-thought.  In particular, I'd like the ability to add conditionality to the setting of individual variables to stop us having to fall back to custom code. Add ability to enable/disable actions within a ruleIt would be useful for trouble shooting to be able to quickly knock out actions to see what affect it has.  Also in the same way as disabling rules, it would be good to be able to remove something from the current build without completely deleting it from the interface. (possibly access by right clicking on the action?)  Add ability to move/copy actions between rulesIn the same way it is useful to be able to copy between properties, it would be useful to be able to move/copy actions between rules within a property. (possibly access by right clicking on the action?) Add 'save and continue' to unsaved changes warningWhen you navigate away from something without saving first you get a warning but it doesn't give you the option to save! Add 'go to property' option when copying to another propertyWhen copying to a property, it is logical that you would want to go to the property you have copied stuff to.  At the moment there is no shortcut to get there. Compare revision from within Edit Library (under publishing)When reviewing a library (e.g. before publishing) you typically what to compare revisions.  It would be good to be able to do this within the library screen rather that have to navigate out to Data element/rules. Auto associate library with environment when rejectingWhen a library is rejected back to a previous stage there is no environment automatically associated with the library.   If there is only one environment at that stage and no other library is using the environment it would be a time saver if it auto associated the environment. Retrieve library back to previous stage once submittedIf you submit a library to across to a stage that you do not have permissions for, you cannot get it back.   e.g. accidental approval ready for publishing by a tester cannot be retrieved by the tester, you have to find someone with publishing permissions to reject the library.  It would make sense to me that if you have permission to push a library to a particular state you should be able to retrieve the library from that particular state. Remove comments during minificationAlthough custom code seems to get minified, comments do not appear to be removed from the code which seems odd. Can't search within long sections of custom code Where a JS library has to be put in by cuting and pasting custom code you can end up with large blocks of custom code.  It is not possible to search this custom code due to the way Adobe incrementally loads this code as you scroll to view it.  This can make it difficult to manage. Default to more items on the rules list and elements listThe default is 10, I'm regularly selecting 100.  Could you default to a larger number or remember the users selection? Add ability to alert when a library is published (e.g. via email, SMS/Text)From a security point of view we would like to be able to have alerts sent out whenever a library is published.  The publisher should not be able to block the alert or amend the distribution list.

Set Global Delay on Program Member/Campaign SyncNew

Idea: My proposed idea is to implement a global setting in the Salesforce section within Admin that allows you to delay the sync of campaign member for a designated number of minutes.  Why: I've often found myself at odds with the practicality of leaving on the Salesforce Campaign Sync feature in Marketo. It's super helpful in that it ensure proper alignment between our Marketo Programs & Salesforce Campaign. We can also easily sync period costs to total cost, saving time, effort, and improving data accuracy across systems. My main issue with leaving the program sync on, is that the sync operates too quickly and sends leads to Salesforce before they're considered "ready" from the operations perspective. I'm sure every business has their own standard of "ready" but in our case, we stamp the Lead Source, populate Lifecycle Stage, fill in some datastamp, and run some data append processes via webhook in market. Ideally we want all of these values populated before the lead ever hits salesforce to ensure accurate lead routing to sales, and leaving the salesforce sync on causes leads to be sent over to salesforce before marketo has had a chance to do its thing.We've gotten around this by implementing wait steps before "change SFDC campaign status" flow steps in every marketo program we run. This works for us in theory, but doesn't work 100% at scale. Sync campaign flow steps can fail at times for various reason (either marketo or salesforce related), and we cannot create reports or receive alerts about those failures within Marketo. Also, the flow step failures never attempt to resync automatically, leaving us in the dark to research for errors in the activities log for all of our marketo programs manually, or pulling logs from the batch API.This solution also doesn't scale particularly well if we ever want to adjust that wait step. Since wait step values can't be populated by global token, we need to go into every single active program to change the wait time. Not fun. Curious what the community's thoughts are on this matter.If you leave the campaign sync on, how do you get around imcomplete records from entering salesforce before they're "ready"Do other people leave the sync off like we do? Have you seen problems flow steps failing? How do you scale managing your wait steps?

Urs_Boller
Urs_BollerNew Participant

Web Extension "Adobe Analytics" - Action "Set Variables" - Improve "additional settings"New

With the new v1.8.4 there is a change which I really don't like. To understand  the change, first have a look at how it looks in the old v1.8.3: As you can see there are all the default variables easy to access. I understand that in most cases all the fields remain empty and it is a lot of place ... that might be the reason why the change was made in v1.8.4, see here:All the default variables are now hidden behind a simple checkbox - check it and see the additional fields as above. What's bad?There are 2 points that I don't like about thatIf you have the settings closed, you have no indication that you maybe have filled in some of the fields - so easy to forget about a single field that has a value. just had sort of nightmare while debugging an issue...the action remembers the setting of the view in the UI - good. but this setting is written in the final launch library code! it adds an additional string to the action with a boolean value for "showAdditionalSettings".Idea to improveI suggest to change it from a checkbox-feature to an "accordeon", so basically hiding the additional fields until the user clicks on the header (or on an icon to open), closed by default.in case there is at least 1 field with a value the accordeon could either be open at view or the accordeon title could have a badge indicating that there are hidden settings. please change this as soon as possible!