Description - Allow calculated field values to populate list of same field that can be used for drop down. Why is this feature important to you - I want to create separate IDs associated with certain projects and I want to be able to tie like projects to another project (it is our workaround for no real campaign object). How would you like the feature to work - A calculated field creates a value upon project creation when project type = campaign. The value generated will be "campaign-1234"; the field name will be "campaign custom ID" it is a calculated field. I want to then create a custom form for a non-campaign project object and on this form i want to have a drop down of the existing values in the "campaign custom ID" field. That way, I can tie projects to one or many other campaign like projects. Current Behaviour - I don't believe there is currently an option to do this.
Today, users have the ability to use the "New --> New Person" menu option inside the Database section of Marketo to directly add a record if necessary. However, the New Person flow does not account for pre-existing records with the same primary key—even if both versions of the record are Marketo-only and not synced to a distinct CRM record. Would it be possible to update this behavior to either explicitly prevent creating a duplicate in the Marketo database or notify the user that a user with that record's email address is already associated with a record? Again, I'm not sure if this is an "intentional" workaround for creating duplicates, but it's unexpected behavior.
It would be nice to hide the task condition update independently from just turning on or off system updates on task updates. Currently when someone clicks "Work on It" for a task an update is posted saying the task condition is "Going Smoothly". Our users don't agree that just because they start work on a task instantly means that everything is fine for the task. Showing this in the task updates causes a lot of confusion, but we don't want to turn off system updates since other system updates are important
Adobe,The Admin Console is still HIGHLY labor intensive when you want to control permissions for Adobe Analytics. Not only that, it's a BAD user experience.First of all, I should not have to go to the Help documentation just to understand the sub-groupings of permissions you previously had in the group and user access management in the Adobe Analytics tool.Even worse: On any of the Permissions edit screens - EVERY time you add or remove an item from either the Available Permission Items or Included Permission Items, the list jumps back to the top and also wipes out your search criteria. You also can't select more than one permissions option at a time (REALLY?!?). The Metrics and Dimensions permissions contain ~2,000 options alone, and you want me to either add/remove everything, or tediously scroll (or search) for every single change I need to make?I was honestly hoping when we went through the user migration that this would be fixed shortly afterward, but I'm thinking Continuous Improvement has really missed the boat on this interface. PLEASE, PLEASE, PLEASE, make this easier for us to administer. I should NOT have to lose half a day of productivity just trying to create an Adobe Analytics Product Profile.
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
Analysis in Flow looks like:Often, I find that I want to see all 140+ values in the left column, or 76+ values in the right column. To do this takes click after click, where each click shows 5 items at a time. Would love to be able to right-click to expand the full dimension and see all values.
Analytics is so integral to our business that losing any portion of it for an hour is an issue. I want to be kept abreast of when an issue is resolved. I want the ability to select tools that I'm interested in automatically receiving maintenance / issue alerts for. For example, when there are issues with Analytics, I can currently subscribe to an issue to see the ongoing status of the issue. I want to get these automatically without having to manually subscribe. I would even like to have a set of email addresses that would receive these.
I love the customize calendar feature for a report suite but it doesn't work correctly with our fiscal calendar. We use a modified gregorian calendar but the end of our calendar year is a year forward. Can you please add the ability to select what the year should be for starting. Example:Our fiscal year starts in March. So calendar March 2019 is month 1 of fiscal year 2020. If I use the modified gregorian calendar option today and select first month of year as March. The reports are one year behind. (Example: calendar February 2019 is fiscal year 2018 (correct should be: fiscal 2019) and calendar March 2019 is fiscal 2019 (correct should be: fiscal 2020). Solution:If you add a drown down option to select, year forward or year backward that would allow people to adjust based on their specific calendar. I would be surprised if people haven't had issues with this in the past.
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
Currently, date ranges builder under components does not allow users to select non-sequential dates/months/years to create a date range. It would be great to have the ability to select the non-sequential date ranges to create the desired date range for a specific purpose. some examples.Ability to select random days in a month. eg. 1, 7, 21 & 30 day of the month. (Movies releases schedule)Ability to select random weeks. eg. 1st & 3rd week of the month. (Broadway weekly discounts) Ability to select random months. eg. January, April, July, October (First month of each quarter) Ability to select random years. eg. 2015, 2017, 2019 (Year of textbook adoption in the selected state)Ability to select calendar by columns. eg. all Mondays in a month.Ability to select week vs weekend in a month or selected time range. (Have another idea based on this ability)Thanks!
We have third-parties that need to ingest Analytics data with specific column names. It would be ideal if we could overwrite column names in the exports. Example:- Need to send transaction IDs, Orders, Revenue to an FTP- However, the vendor has strict requirements that these be called ordr_id, ordr_cnt, rv_amt
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.
Hello Adobe Community,I want to submit an idea about new Time ranges that could be calculated from a selected date.For exemple, If I select a week on the date selection ( let's say week 52 of 2016) , my custom time range should be calculated from date selection - and wouldbe week 51 - in order to make a week to week analysis on week 52. Time ranges can already be calculated from rolling dates, but cannot change whenever the date selection changes.These new time ranges could facilitate the analysis of past weeks or past months - since it would'nt be necessary to change all the time ranges from existing reports on rolling dates.Kind regards,and Cheers to the Adobe Community !Mario
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
New feature is nice, but here's an improvement.If you select more than 2 metrics and does the "create metric from selection", make the options just to Add or open in Metric Builder (could maybe make a case for multiply -- divide and subtract don't seem to make sense). Right now, it just takes the first 2 metrics you have highlighted and ignores the rest.
In case bugs happen on the web page events and variables in Adobe can be affected, especially with "wrong" data. As an example: you are measuring error events for a webpage component and due to a bug all events are fired 10x instead of once. In all reports this massive spike is now messing up averages, etc You could deal with that by using filters, but the more users have acces to the raw data the harder this is as you can't enforce segments or filters to all users. You could also set calendar events, but those only show up in charts, not in tabular analysis. Therefore we need the capability of deleting data from individual evars and props for selected time frames.
I understand that there was once a time when the cost to supply and maintain Adobe Analytics was based directly on the number (and size) of server calls being processed and stored. I would guess that this is no longer one of the main operating costs in providing and supporting Adobe Analytics client companies. I'm not saying that bigger companies with higher volume shouldn't pay more than smaller ones with lower volume. But, the strict 1:1 relationship between server calls and dollars presents a perverse economic incentive that twists implementation design and methodology in ways that don't best serve the goal of providing good information for analytics. The primary example of this can be seen in the implementation of a product detail page on an e-commerce website. We have a few things that we might want to track on this page: The load of the page itself (for AA traffic reporting, Pathing, etc). The product view for the primary product (or products on the page). Impressions of cross-selling products served from a 3rd party service (e.g. Rich Relevance, Certona, Adobe Target). Product Rating and review information served from a 3rd party server (e.g. Bazaarvoice, or PowerReviews)Any other latent 3rd party tag info relative to the product or customer which may be loaded asynchronously. If cost were no object, I would argue that it is a better design to send an s.t() (page view) tag to AA for #1 above and send s.tl() (custom events) for #2-#5 above. Since cost is a factor (driven directly by server call volume), as an implementer I am forced to suppress the page load (#1 above) and write code to wait for events #2-#5 hoping to consolidate all the information into a single server call. This leads to less accurate reporting since the delayed page view tag is recorded less often. It also leads to more complicated implementations which are harder to maintain. It is a mindset based in the past, based on synchronous, monolithic, server-managed websites. It does not translate well to Single Page Apps, or microservice/component-based design patterns.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.