Skip to main content

Filter by idea status

10000+ Ideas

emiliog
emiliogLevel 2

Data Warehouse new UINew

Description: While the new Data Warehouse UI is a much-welcomed step, I think it is missing some features that would make it more user friendly and efficient.These would be: 1. Add calculated metrics.2. Add custom date ranges.3. Add segments to individual dimensions. This is a Workspace staple, it is so necessary.4. Ability to edit/delete created accounts and locations. People make mistakes.5. Requesting an account name, description and hostname seems unnecessary.6. Ability to save notification emails.7. The "Save request" button unshaded seems weird and is unhelpful as you navigate the tabs. A Next button until the last tab (Notification email) would be more helpful. Why is this feature important to you1. Calculated metrics is an integral part of Adobe Analytics, and the success of content/campaigns cannot be fully measured without it.2. Custom date ranges. In addition to previous point, several campaigns and timeframes don't align with a standard calendar measurement (for example, since product launch).3. Segments to individual dimensions. While we can do an overall segment, adding segments to individual dimensions within DW would save an enormous amount of time during data analysis. It is a staple of Workspace already.4. Edit/Delete created accounts and locations. People make mistakes but also server information and credentials becomes outdated. Leaving the incorrect information there may lead to mistakes and isn't efficient.5. account name, description and hostname seems unnecessary. This is just repetitive and counter-intuitive. It should be a name and server information. The name can be the description.6. Save notification emails. Every other repetitive task has been eliminated but this one has been left on.7. A Next button until the last tab (Notification email) would be more helpful. Given how counter-intuitive the Save button currently is (and the fact that there needs to be information in each of the tabs) a next button until the last tab follows standard web UI more closely.How would you like the feature to work1. Calculated metrics. Make it available the same way it is now in Analysis Workspace.2. Custom date ranges. Make it available the same way it is now in Analysis Workspace.3. Segments to individual dimensions. Drag and drop from the segments bucket. Make it available the same way it is now in Analysis Workspace.4. Edit/Delete created accounts and locations. Add a delete and an edit button.5. account name, description and hostname seems unnecessary. Remove description6. Save notification emails. Add a plus sign (same UI as create accounts and locations)7. A Next button until the last tab. Remove Save and add next instead. Add save to the last tab (Notification emails) Thanks to @jennifer_dungan I wasn't able to reply to your comment in the questions part.

brentradLevel 5

Allowing segment updates to be reflected in other segments that use it as a referenceNew

Description -One feature of the Segment Builder is the ability to use existing segments when building out a new segment. I'll refer to this as a "reference segment".Once the reference segment is dragged into the Segment Builder it becomes "disconnected", and is more like a snapshot of what the reference segment looked like at the time. If an update is made to the reference segment this will not be reflected in any other segments that use it. It would be nice to have an option to "anchor" the reference segment so that any updates made to it are also reflected in other segments. This would preclude the Adobe Analytics user from having to find and update every segment that used the reference segment, and would ensure that changes to the reference segment are immediately reflected across all reports. This feature can be limited to only public segments. There are several risks associated with this idea.Uers may not be aware of how many segments use a particular reference segment as an "anchor", and thus may not truly understand the ripple effect caused by an update. Users would have to be provided with some sort of notification in the Segment Builder that shows both that a segment is being used as an "anchor" (think of a little icon next to the segment name) and which segments are using it as anchor. This option should require permission rights from an adminA change to the reference segment may break the segment logic of other segments, making them no longer work. This could happen if the container types in the reference segment were adjusted. One way to alleviate this would be to disallow the use of anchor segments in some cases, such as in sequential segments. Another option would be to not allow the anchor segment to update in a segment if the segment logic will be broken. The user would then have to be notified of the segments where this occurred so that he or she can make necessary adjustmentsWhy is this feature important to you -My organization often uses several core segments for KPIs, and then creates more nuanced segments based off of these core segments. The number of segments that use the core segments are substantial, meaning that a small change made to a core segment requires updating a large multiple of other segments with the same small change. How would you like the feature to work -When a reference segment is dragged into a new segment in the Segment Builder, a user can click on the gear option and select "Anchor Segment". Any updates made to this reference segment will automatically update this segment as wellThe Segment Builder page for the reference segment should indicate whether the segment is being used as an "Anchor Segments". This can be done using an icon or some similar call outThe Segment Builder page for the reference segment should contain some sort of interface for showing which segments use this segment as an "Anchor Segment"A warning should appear when someone tries to update an "Anchor Segment", telling the user that updates to this segment will impact other segmentsCurrent Behaviour -Dragging an existing segment ("reference segment") into the Segment Builder creates a copy of the existing segment. The reference segment component of the new segment will not update if the reference segment is updated.

amznJWLevel 2

FUSION: Stop Button Outside of the ScenarioNew

Description - Need a way to stop a running scenario from outside of the scenario itself.   Why is this feature important to you - If a scenario is running on a schedule and I need it to stop, I have no way of doing so.  If I open the scenario while it is already running, it is hit or miss as to whether or not it will even display a Stop button.  Even if it does display the Stop button, it never works.  I have literally a 0% success rate of that button ever having stopped a scenario under these conditions.   Additionally, if I have started a Scenario by clicking the Run Once button and the scenario decides to freeze up in my browser (this happens a lot and is becoming more and more frequent), then there is no way to stop it.  I have to wait the full 45 mins for it to time out before I can continue working on it because the stop button won't work after the freeze up and if I refresh the page, I just get a view of the diagram, not the progress of the current cycle and I run into the same situation where it is hit or miss as to whether or not the Stop button will appear and even if it does, it won't actually work.   How would you like the feature to work - When viewing the list of scenarios in Fusion, there should be a Stop button for each scenario that is accessible without actually opening the scenario.  Similar to the toggle switch that controls whether it runs on a schedule or not.  If/when it changes to a Force Stop button, that button should truly function as a force stop, literally killing the process running that scenario immediately without regard to anything it is doing at the time.     Current Behaviour - there is no button like I am describing.