Product Communities

Hi,Idea:The alert builder should provide the option to set the number of maximum alerts to be sent. thanks.

Currently, anyone looking to build marketing links in the Mobile Marketing Link Builder must have admin access to Mobile Services. In practice, that means that either someone on the analytics team has to build the links (which can lead to bottlenecks), or the marketers must have admin access to Mobile Services, which brings some risk as there's additional access.Can we add a level of access to build mobile marketing links without requiring Mobile Services access?

When you drag a component into a segment definition there is no reference to the variable (i.e. eVar1) it refers to.  So for classification folders, if they do not contain the variable reference in the friendly name (i.e. page url (v1)) you do not know.  Can this be added?  I believe it was just added for components in analysis workspace tables.

Whenever we want to share a component from the Workspace, we click-right in the concerned component and then click "Share". This will display a small pop-up where we have to select the users we want the component to be shared with.However, if we want to see with whom the component has already been shared, the only way right now is to scroll the whole user list and see one by one if the checkbox is checked or not.It would be great to order by default the list by putting the already selected users on top so that we can see them directly.

HiThe recent release has seen a change to the components in workspace.You now no longer see icons next to all dimensions, metrics and time segments (calculated metrics still have the calculator).We have some users that are colour blind, and now this makes things difficult for them, are there are dimensions and time segments with the same name (out of the box adobe ones) such as Day.People who are colour blind can now not easily see which is the dimension and which is the time segment

Hi,Idea:The alert builder should provide the option to specify how many times the alert condition needs to be true before sending an alert. Example: the alert condition needs to be fulfilled 1, 2, 3, ...100 times before sending the alert.

I've created a time period column from the context menu for "These 6 weeks last year" - p.s. thanks for this feature! So useful.When I try to create a metric based on my selection, and ask for percent change, what I really want is for each day to be compared against each other e.g. Feb 4th 2018 vs Feb 5th 2017 (current day vs current day -364).What I actually get, are visits for Feb 4th 2018 vs the entire 6 week date range, and it breaks my workspace by forcing the date range to start at Feb 5th 2017:This create metric from selection can be a lot smarter by contextually comparing the data based on the granularity selected e.g. day vs same day last year, week vs same week last year, so on.Being able to visualise a trended year on year line like that by simply creating a percent change metric like this would be awesome.p.s. has the feature to "compare time range", which appeared under the "add time range", and automatically created a percent change column, been removed?

Hi,Scheduled reports from the workspace of Adobe Analytics don't have the ability to embed the report in the email body, in addition to the attachment. Can we add this functionnality. This is very practical when we need to read it on the smartphone.Best,

hi,Idea:The alert builder should provide the option to select a custom reference period for the anomaly detection.Example: rolling last 2 hours, last 12 hours, from date x to date z rolling

Currently, with the new Admin Console, there is NO INTUITIVE TOOL to send a user another e-mail when they say they have not received the first e-mail that Adobe supposedly sent.  Ever since we moved to the new Admin Console on the experience cloud, it seems a lot of your e-mails are captured and sent to a user's Junk/Spam folders, which makes it a lot harder to manage new users to the system.  I don't have an interface where I can say, "send this person another e-mail" like we did specifically within Adobe Analytics.Something you should have at least considered was maintaining parity when migrating to your new system.  Honestly, we really don't need anything more to undermine our organization's trust in Adobe Analytics.Thanks in advance!

For example, on rubular.com using the regular expression /TestString/i matches teststring and TestString and TeSTstriNG Would also like to have \L lowercase regex replacements in an Adobe Classification Rule Builder rule.  For example, match $1 and lowercase it.http://www.regular-expressions.info/replacecase.html

Currently our optout.html page (https://smetrics.solarwinds.com/optout.html​) has mixed content on it (http and https).  example: the <img src="http://assets.omniture.com/en/images/skins/default/transformation/002251.global.logo.oms-mark.152x63.png" width="152" height="63" border="0"> is http and not https.  In an effort to become GDPR compliant we need to ensure our visitors have the option to opt-out from being tracked by Adobe Analytics.  The resulting optout.html page needs to be https as the rest of our site is https.  We would like the optout.http page to be 100% https if possible, or for an option to go either way.  Thanks,Damon

Median and percentile functions are available as built-in functions for calculated metrics within Adobe Analytcs, but they are Table based,From Adobe Documentation:Table Functions versus Row Functions A table function is one where the output is the same for every row of the table. A row function is one where the output is different for every row of the table. See below example of table using the this functionality with one Median and one 90th Percentile metric.The base metric that is calculated as median and 90th percentile is a Numeric metric. With Row capability for median and percentile, instead of having the median/percentile for  all line items in total it would be possible to see the median for each individual row. Ie, what was the median/percentile for Feb 4, Feb 11, Feb18.This functionality would be fantastic and help to calculate medians/percentiles directly in the Adobe interface without having to resort to large data exports and manual calculation. Useful for any Numeri

Adobe Analytics User A is leaving their position. User A has created some segments and workspaces. Some of these workspaces are scheduled to be delivered to multiple people on the first of each month. Today we are able to transfer User A's workspaces and segments to User B, but not the Scheduled Projects (aka the scheduled delivery of the pdf/csv of the workspace).If a new person wants to also receive one of User A's projects on the first of the month, User B can schedule the delivery of the project. If a current recipient wants to be removed from the list, or if the report delivery date needs to change, User B cannot do so. Only the Adobe Analytics Admin can make these changes.It would be great if we could transfer Scheduled Projects from one user to another, just like workspaces, segments and reports.

I've been doing a series of Workspace workshops with groups of people who are not familiar with Analytics at all. In my workshops, I cover basic concepts, implementation and, of course, how to create projects in WS. However, the biggest difficulty I see from these folks is to be able to tell what are the page names they need to use to create flows, fallouts and page reports. Although they have internal documentation with these details, they are not available to everyone and not so easily accessible.My suggestion would be to allow the customer to upload screenshots for their pages to Analytics and these screenshots show up when you hover over the dimension details in WS. So when a business user is not sure if that's the page they're looking for, then can do a quick check looking at the image and they don't have to go through a bunch of excel or powerpoint files to make sure they're picking the right one.The images could be pulled from AEM Assets as well.

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.

Many times business team is concerned about data of last bucket because there is no visibility on chart about time of last update. I strongly suggest you to add this detail in the note of any chart, in the same way we have now other details:I ask that for standard reports in Adobe Analytics, but please figure out how to have it in Workspace as well.Jarno Rossijarno.rossi@luxottica.com

We have many report suites, and many users, each of which can see only 1 or 2 report suites. I have access to all the report suites. I need to make a dashboard that I can share with all the users. When each user views the dashboard, it needs to show the data for the report suite that the user has access to. So the dashboard will be a template that is filled in with different data, depending on who is using it. This could be done by each user having a default report suite that will be used automatically in the dashboard, or by letting me assign a report suite for each user that will be used in the dashboard.The current situation requires me to re-create the dashboard, along with all reportlets, for every single user, using a different report suite each time. Since we could have over 100 report suites and users, this is time consuming and impractical. Thanks,Christopher Stanwood

If you have a Workspace project that uses the same segment/dimension in multiple dropdown areas or within visualizations itself (i.e. Columns in a Freeform table), it would be cool if you could choose to manually "link" them such that if you change one, any "linked" versions of that would also change.For example, let's say that you have many visualizations in a project and you have chosen to filter based upon Page = Home via a dimension. Now you want to change the focus page from Home Page to Cart Page. Today, unless you are able to use the dropdown area at the top for all items (which is not always possible), you have to manually change all of the individual cases where you have segmented/filtered by Page = Home.It would be great if when building the tables, you could check a box to link the segment/filter to a master one such that changing that one changes all linked ones. This is similar to setting a cell equal to another cell in MS Excel to make the two dynamic.

We have 38 actively used report suites.  Classifications require back end div IDs to be aligned across all 38 in order to create a classification on a variable. When one report suite is misaligned, there is no way to easily identify which report suite is misaligned or to update all report suites with new classification or div values at the same time. You would need to manually click through all report suites to identify the delta, delete, and realign. ALL manually.Occasionally as well, you may have a report suite with the same friendly named classifications, but the back end div IDs could be out of sync depending on how they were created in the past.  There is no way to see the div IDs in the client facing UI to know which one is misaligned. Again, the only way to correct this is to delete all classifications in all report suites and start over. I would LOVE to see new functionality in this area of the admin UI.  Something similar to processing rules where you can work in one report su

As an admin, I would like to push specific calendar events only to specific distribution lists as long as we have a multi brand account.This way it would be quicker to share the calendar event, instead of selecting (and potentially forgetting) all the users interested in the event. Thanks

This used to be available in the previous "Billing" tool but the new Server Call Usage report doesn't seem to let you trend over time.  I don't don't see where to change the date range unless I go back to Reports.

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.

Hi,This idea is related to a question I posted : Incorrect attribution of conversions to Target activities in Analytics(?)It would be great to be able to choose the attribution period. Currently there is no expiration, which means that conversions are attributed to a past activity even long after this activity was live. So, doing your Target activity evaluation one week after your test or one month after your test or 2 months after your test might result in ending up with a wrong conclusion related to that test (because of being impacted by many other external factors, campaigns & tests).Some people might now think "but you can do this in the Segment builder by creating a segment on visit level and selecting Activity (Analytics for Target) exists THEN conversion exists" (cfr next screenshot). But no.. the result will still be that conversions are attributed to activities that were active even long ago. Reason: the IF condition 'Activity (Analytics for Target) exists' does not expir

I would like the ability to set up simple year over year daily alerts. Our industry is very cyclical and/or seasonal on a daily, weekly and monthly basis. Trying to set up day over day, week over week or month over month alerts is not feasible. I have done the analysis on basic metrics; visits, transactions, etc. and I see the variance for the highs and lows for those comparisons as follows; Day over Day: -47% to +148%Week over Week:  -51% to +150%Month Over Month: -71% to +142%When I do a Year over Year (i.e. -364 days, same day of week) I get the ranges -15% to +21%,So for us having alerts for a Year over Year day are a much more accurate measure of change and allow for setting tighter thresholds