Product Communities

It would be superduper if we could select the delimiters for our reports in Data Warehouse. We are automatically importing that data into a database here, and have run into a problem with the comma delimiter because some of our data has come across with commas in it. Would be nice to be able to change the delimiter to a pipe rather than have to go back and recode the data going into our variable.

Hello All,I was hoping you could get two things on the roadmap.1.  Better documentation around your APIs (Though what you have is a great start) 2. Better responses from your APIs when the WSSE Header is wrong (which, though I'm no expert, I feel was stupid hard  "unable to validate" is not helpful).Here's some things that aren't mentioned (Keep in mind, I'm not a network/IT guy, just trying to help):1. Nonce / Digest should be ASCII format when created (not sure if this is 100% correct, but it worked for me)2. Base 64 encoded Digest and Nonce must be DEcoded before sending (this may be common knowledge for some, but wasn't listed)3. When decoding, you have to remove the leading whites pace from the values that are decoded4. The POSTMAN example is a good start, but it would be great if you could explain in more detail what is occurring at each step.5. You don't need a SHA1, you can use any hashing algorithm as long as its sent in the header6. Each parameter value of the header should b

As an Admin on the Microsoft Store account of Adobe, one of the most popularly requested features we encounter is the ability for users (non-Admins) to selectively grant "write-access" to other's Workspace projects so that teams may collaboratively edit one another's work. Within the same feature request, it would be great to have a view of the "recent edit history" so this way teams can track any changes made.Current Issue:Right now, users (non-Admins) are limited to only having "read-access" to others workspace projects and components (segments, metrics, etc.). This prevents teams from being able to effectively collaborate on projects. For example, let's say team member A creates a workspace project, and wants team member B to edit and update it.  Team member A may share it with team member B, but team member B cannot make any edits to the original version. Instead, team member B only has "read" access to the original copy. Team member B must "save as" a copy of the original project,

Hi,we want to give Adobe Analytics access to an external partner - with limited access to only a few metrics and dimensions. For this we created a virtual report suite, where we limited the access to one specific segment, created a product profile and a user profile. For those profiles we also specified only a few metrics that should be visible for the external partner. Unfortunately, while testing we discovered that the partner can also view all calculated metrics that are shared with "All users". This is currently a blocker for us - we do not want that the external partner can see all shared calculated metrics and can use them in Workspace. So the solution would be to only show the metrics and dimensions that have been specified for the virtual report suite and product profile.Thank you and best regardsPatrick

In Workspace, we can select all results from the first dimension and break them all out at once by a second dimension. While everything is still all selected, it would be helpful to be able to change the number of Rows in the first breakout item and have that apply to all the breakouts.

Hi,It would be a time if "create segment" or create calculated metric options is provided on right click of dimensions/metrics/segments and when a specific dimension item is opened.Thanks

Hi,Currently it is not possible to resize the legend width in order to have the label visible on one row and not be truncated over multiple rowsCfr next screenshot.It would be great that we could resize this by pulling/dragging the scrollbar line (cfr yellow marked) to the right.Thanks,Sarah

In most cases, folks create new Bot Rules specifically because they've uncovered a bot that has been messing with their data... unfortunately, by the time you've identified the problem and created the rule, it's too late: the bot has already done damage.The workarounds are pretty drastic- applying a segment to every report, or moving entirely into a Virtual Report Suite that doesn't include the bot traffic retroactively.Bot rules working on historical data would be a huge help.

Telecom Customer would like to update a number of Adobe Reports and Analytics segments at one time. Example: Identify segments that use a specific prop like prop 22 and replace it with prop 25. But the segments would not have the same definition.Currently searching for segments and editing one by one is not ideal and very time consuming.

When we delete any segment, it shows the notification that it could have been used in dashboards but it doesn't show the name of dashboards using this segment. Ideally, it should display all the dashboards which are currently using a particular segment so we can easily do segments cleanup whenever required.

A Flow visualization can get a little difficult to handle after the user switches from one dimension to another.One dimension:Very clean and aligned with what I clicked. Page Type = Product Details is expanded into all the next Page Types.But as soon as I switch dimensions in the right-most column to Product (to analyze what products were being accessed), I get into trouble:Each value that was shown in the Page Type column is now expanded into the Product dimension column: Product Details, Department, Search Results, Shopping Cart, and Home. To continue my analysis, I have to click everything but Product Details.I'd love to be able to right-click on one of the values in Page Type to focus on paths that go through that Product Details item only:

Example: In AA,  I am only able to see the variable name, but not if it is a prop or evar.AA: Adhoc, which clearly states if thi is an evar or a prop.Asking since AA will be sunset eventually.

In a previous post (http://ideas.omniture.com/t5/Idea-Exchange-for-Adobe/Segment-Toggle-quot-Normal-Exclude-qu ot-Feature/idi-p/14612) I mentioned it would be great to basically have a quick negative segment creation. It appears as if Adobe figured this logic out with the "Everyone Else" feature with Segment Comparison. While, Segment Comparison is nice, it really seems to give limited results outside of "next steps to investigate". For instance, it will give me a weight of say 0.20 for Mobile visitors and tell me, "hey this metric is important" but then I have to go investigate that and then to truly understand that metric, i have to create an "Everything else Metric" to continue this investigation. Where I think this becomes truly applicable is going to my own freeform table and being able to drop the segment of I am investigating and then be able to have the ability to select the segment, right clicking it, and have an option to negate the segment, which would be the same as "Everyo

Currently the only way to rank dimensions by metric is to sort them (example: page URL's by Visits). But what about when you want rankings for a certain metric to persist, even after you've sorted by a different metric? (Similar to the Rank function in Excel). This is particularly important in web analysis from a page performance and path optimization perspective as it's possible to create participation/contribution metrics but extremely difficult to track changes in rank leaders over time. The fix for this would be to add a simple rank function in the metric container.

Hello Adobe Community !I noticed that Summary Numbers don't support conditional formating, nor polarity on the number ( negative numbers are the same font color than positive numbers ).It would be nice to support this, spetially polarity !Thanks again!And cheers for the great work of the Adobe community !

Would love to see an improved variable change log incorporated within the Report Suites area of Admin Console (Conversion Variables, Success Events, Processing Rule, Traffic Variables, etc).   I could see this as an additional expanded menu that shows changes for that specific variable and the date.  This would help with quickly debugging issues and keeping a record of changing that can have a large impact on your data.  The Admin Tools Log is not exactly what I want to be sifting through when I am double checking a change seen in a particlar variable and need to get a better understanding of potential changes on this variable's settings. 

It would be helpful to have a "last used" type of timestamp or something similar on segments in order to be able to determine if a segment or set of segments is in use or has ever been used to assist with making decisions surrounding segment cleanup initiatives.

Currently within Analysis Workspace, there is the ability to use the "cumulative" function to get a running total of a metric, such as unique visitors, over a period of time and divide within that period of time, such as by month. However, this does not take into account that several of those visitors are the same visitors, returning from one month to the next.Request is to have an option to deduplicate the grouped results over time so that it would be possible to have a running total of values that takes into account de-duplicated data, so that rather than adding up to the individual totals from each month, the total across the time period with this metric would potentially be less than the total by month.Example:MonthUnique Visitors (Base Metric)Unique Visitors (Cumulative function as it exists today)Unique Visitors (Cumulative Distinct proposed metric across entire time period)Jan 2019100100100Feb 2019150250230 (20 of these visitors overlap with ones we've already recognized from th

if i send a workspace project by PDF (or CSV) without schedule (just immediate sending), it will produce an entry in the list of "scheduled reports". this way, the more projects you send by email, the longer get's the list. an moreover, you can not filter which "scheduled reports" are really schedules or not ...even i think this is a bug in implementation, i raise an idea to improve the "scheduled reports" list and ask for an additional filter:- "active" schedules: would show only scheduled reports which are still active, will be sent in future- "scheduled": will show all scheduled reports which have a real scheduling option- "expired": will show scheduled reports where the expiry date is in the pastfeel free to add more filter ideas in the commentskind regardsurs

In the old admin system, you could easily en masse transfer all segments, calculated metrics dashboards etc from one your to another. This was particularly helpful when deleting a user from the system (for example if a person left the company and they were a heavy AA user, i'd transfer their segments, calculated metrics dashboards etc to my account so they wouldn't be deleted).I raised this with customer support and they said it is no longer possible, so my idea is to bring this feature back.Thanks.

IssueDeleting data is incredibly problematic (and expensive!) in Adobe analytics. One of the impacts is on our agility - we have several dimensions that are tied up as they contain historic data that is no longer relevant and we are waiting for that data to disappear through the standard data retention deletion process before we reuse - This is something we really struggle with. RequirementsThe requirement is to be able to quickly re-purpose variables/dimensions, thus increasing the flexibility/agility of the Adobe Analytics tool. For this scenario the requirement is to prevent end users seeing the historical data (rather than deleting the data).  Therefore I was wondering if there was an alternative approach which would allow us to free up dimensions quickly for new purposes.   Possible solution?The problem with deleting data seems to be unpicking all the processing that has happened.  My thinking is this unpicking could be avoided by having virtual variables (much like a "virtual tra

Hi,there have been several report builder outages for us recently. Can you please provide some suggestions of how we can firefight situations like this?I.e. delete lower-prio scheduled reports or is there a quick way to convert ad-hoc format to reportbuilder format.... ? Issue: London Data Center was flooded with the huge report api requests.ReportBuilder is an important tool for us, but is not even mentioned on the status website? http://status.adobe.com/marketing_cloudRegardsStefanie

It would be great to make the following updates to the processing rules interface: 1. have an expand / collapse all button.  (i have to expand all to make the rules searchable (CNTRL F)2. make the rules searchable/filterable.  i typically look for specific variables.3. allow rules to be tagged/assigned to categories.4. in history, all revisions to be tied to users.

There are two use cases for VRS component customization:1: Specifying a smaller set of core components to be available in a VRS (auto-exclude anything new)2: Removing specific components that might not be applicable to a VRS (but wanting everything else included)By default, any new component created in the parent report suite is placed in the Exclude bucket, this works great for use case #1, but for use case is #2, we constantly have to be going into the VRS settings to move new components from "Exclude" to "Include".It would be awesome if there were a toggle in the VRS settings to auto include, or auto exclude newly created components.

Currently Conditional Formatting in Analysis Workspace evaluates the values within a single column. Please add a feature that would allow to switch the logic to the entire freeform table so that the cell colour would reflect the value against all other cells in the viewable area of the table (within the page).