Skip to main content

Ideas

Filter by idea status

10000+ Ideas

K_DonkersLevel 3

Custom Form Management and OwnershipNew

Description and what we would like to see: The system doesn't provide a good way to manage the hundreds of forms in our system. We would like to see additional features added to allow a clearer definition about who owns the form. We currently get around this by sharing the form with a group and then grouping by that field. It isn't always accurate, nor does it allow for system level management to be clearly defined.  Ability to assign a form to a group who owns/manages it so ownership is apparent, and it can be viewed at the group level without needing to access the full list of forms which is daunting in a large instance Some forms are shared across groups, but we don't want group admins to think they can edit them. Instead, we would like the forms assigned to their groups to appear in their group area for management purposes. For system admins, the large number or forms are difficult to dig through to find specific forms. Assigning to a group would help in locating ones for a specific group.  Ability to assign a form used at the system level to the “system” so it can only be managed by dedicated system admins and displays that ownership is at the system level but can be used by group admins that need it (or as defined by the system admin) Add more descriptive fields suggestion which allows for more detail to be added to the who, how, what the form is used for instead of just a description field. (Related idea: Allow assigning custom form ownership to Groups - Adobe Experience League Community - 518377) Why is this feature important to you - We have a large number of forms managed by many people across nearly 60 groups. It is challenging to maintain a good record of who owns the form and know what it is used for in the system.       

mikaela_sLevel 2

Add option to have an "enter/exit segment node" in a Journey.New

Description - I would like the option to have one step in a journey where customers are entering into a segment or exiting from a segment from this step. Why is this feature important to you - This would help with orchestrating the journey so customers could at some point (depending on previous steps) enter into segment as part of the journey and that segment could then be used to trigger another journey or offer. I've used this feature in other tools and I find it very handy to connect journeys to each other at different points in time. They could also enter into a segment which excludes them from all email communication for X time for example, and then exit that segment whenever the journey says so. How would you like the feature to work -  1. I would like to have a node/step in a journey that only adds customer to a segment. The segment in itself is only set to accept customers coming from a journey and doesn't have any further requirements when being built.  2. I would like to have a node/step in a journey that only exits customers from a segment. If needed this could also only apply to segments specifically built to be orchestrated from actions in journeys.   Current Behaviour - We need to create a complex segment based on actions on commincation within a journey and those don't work as well as we would like them either. The counts differ from the reporting of how many clicked in an email to how many enter the segment based on the same requirement. We can't create segments that are "empty" so of course this would have to be an option as well.