Build better products with our product team
Could we please introduce additional preset date range selectors in Data Warehouse? Currently, we don't have any options between 7 and 30 days (14 & 21 days would be great). And the custom date range doesn't include a rolling data range feature. This causes problems for regularly scheduled reports.
There is a need to have a view only of all the variables and processing/channel rules in analytics. Currently, unless you are an admin, you cannot see which variables are activated for your report suites, when they expire or any of the processing rules that assign values to variables. This can be limiting if you are trying to decipher some of the reporting (especially if things are not quite adding up).Don't want admin rights to change things – but would like the right to view things.
Currently Admin Console gives the perception that granting permissions by product profile is a scalable way to grant permissions, with AND logic, and reinforced here: Enterprise Help | Manage product permissions in the Admin Console. After talking with Adobe client care, this is false. Not only can product profile permissions conflict with each other, in an OR logic fashion, but there is no way to know how product profiles will interact with each other except through trial and error (per Adobe Client Care Incident: 190204-000614). For example, in trying to combine a product profile with a single report suite in it with a product profile granting access to an array of data feeds utilities, the user does not get access to the single report suite such that it can be used in combination with the data feeds permissions. This was confirmed by ACC.Solution proposed:- Create product wide AND or OR logic for product permissions and document it, ideally AND logic
We are heavy Alert Users.The challenge: We want *relevant alerts*. Adobe's Anomaly detection system is ok, but 95% of the *Hourly Alerts* it spits out are completely irrelevant as traffic simply oscillates too much from one hour to the next, AND because Adobe seems to take only the last 24 hours into account when looking for Anomalies. So we had to deactivate all our Hourly Alerts.1. However, Daily Alerts are too late for something really critical, so Adobe needs to either improve the Hourly Alert logic, or offer something in between, like _3-hour-periods or 6-hour-periods_ which don't jump up and down all the time like hourly data.2. Alerts should be configurable to fire only "only if a value is _HIGHER/LOWER_ than expected" (and a certain Significance Level. We don't care so much if the Conversion Rate of Google Shopping is greater than expected, we want to be ALERTED when it goes DOWN because then we have to take immediate action.
Hello, When using A4T integration in Target for my activities, I can see in Target reports AND in Analytics reports which experience is the control experience for any given activity. But after speaking with Analytics support, it is not possible to retreive that information from Report Builder. So, make possible to get information about which experience for any given Target activity (with A4T integration) is the Control experience. That would greatly help on subsequential calculations based on that output.
The Analytics Data Feed is only available over SFTP to port 22. It would be more convenient if the user could specify other ports.
It would be incredibly helpful to add a few columns to the Request Manager display. I would most like to see Report Suite ID or Name. And Date Range would also be very helpful.
The link generated from "Get Project Link" in Workspace directs you to the legacy analytics login. This should direct you through Marketing Cloud login instead.
Data Warehouse had a dedicated DataWarehouse API v1.3 but has been deprecated and my understanding is due to be shelved completely sometime this year. Though, it was lacking in the features I desired anyway (read on)The current standard is to use Report.Queue to request a Data Warehouse report. 1) DOCUMENTATION UPDATE - The reportDescription listing documentation does not show how to specify ftp info for ftp delivery. I was able to piece this together together because the example Object output by the API Explorer includes it, and it's relatively straight forward - mostly. Specific values I was also able to piece together from the v1.3 DataWarehouse.Request listing (not the same property names but still). Also, the v1.4 Data Warehouse Reports documentation just gives a quick comment about referencing the Report.ReportQueue method - which doesn't even exist anymore (it points to a 404 page, and the method itself was deprecated from v1.4). So.. this should point to the Report.Queue method, but now we've come full circle with no info detailing Data Warehouse API usage for v1.4 Report API. Can someone please update the v1.4 documentation to include Data Warehouse report pull usage?2) FEATURE REQUEST - Report.Queue only lets you make a one time report request to Data Warehouse. It does not let you include/configure anything for scheduling a repeated/ongoing report export like you can in the interface. Well, it's not documented, anyways. Not even in the v1.3 version. This is a very big pain point for several of my clients and it would be super nice if it could be added.3) FEATURE REQUEST - Also, there is no way to retrieve information about Data Warehouse reports currently in the Data Warehouse queue. I would like to be able to make an API request to get a listing of all Data Warehouse reports in the Data Warehouse queue, whether it be one time jobs still in the queue, history of completed jobs, and - most importantly (to me, anyways) - list of Reports on an ongoing / repeating schedule. Maybe a method to pull a list of all id/names and then another method to pull config data based on id? That would be super nice and helpful.4) FEATURE REQUEST - And following that train of thought, it would also be nice to have API methods that allow me to update configuration or cancel/delete report jobs.5) BUG FIX (?) - In the Data Warehouse interface, I am able to choose Marketing Channel Last Touch Instances as a metric. It is there. I can select it, and it shows up in the exported FTP. I can provide screenshot evidence. But it is not available via an API pull. I have tried generic "instances" - says this metric is not available for data warehouse pulls (what??). One trick I have found over time to get around lack of documentation is to inspect html elements on pages within the Adobe Analytics interface. I can do this in the Data Warehouse interface screen and in the html code "@marketingchannellasttouchinstances" - does not work (with and without the leading @ sign). I've tried many variations of that. I've tried a Report.GetMetrics API call and nothing relevant is listed, though I saw a lot of other "instance" type metrics for other elements listed with their "instance" prefix, followed by their element id, so I tried "instanceslasttouchchanneldetail" - no joy. I tried all kinds of combinations of these words. Reordered, added. Removed. No joy all around. But clearly this is available as a metric within the DW interface, so it MUST be a metric available on the back-end, and the API just isn't aware of it. Or more accurately, the Report.Queue API's data validator isn't aware of it so maybe any one those things does in fact work but is getting blocked by the API's validator because the whitelist is not comprehensive. Whatever the case may be, can someone please add this, and while you're at it, do an audit to sync up what is available within the DW interface vs. the API!6) BUG FIX (?) - I created a segment in segment manager. In the Data Warehouse interface the segment is available. I can schedule a DW report within the interface using the segment. I receive the exported report and the data accurately reflects what I expect. I have verified this thoroughly. I attempt to throw the same segment into the Report.Queue API call for Data Warehouse, and I am sent a blank file with nothing but the column header row. The DW API request sends me all the data in the world without the segment thrown into the mix, but returns me nothing when I add it. Scheduling the same exact thing within the DW interface sends me data. Yes, I have triple checked that the segment id is correct. I even used that inspect html element trick I mentioned earlier to verify it both within the segment manager AND within the DW interface. All shiny. So this seems to me that there is some kind of bug with applying segments to Report.Queue API calls for data warehouse. Sidenote : segments applied to regular Adobe Analytics reports work just fine for me; I do those all day long for other projects. So whatever is wrong with segments via API call, I think it is Data Warehouse specific ("source":"warehouse"). Can someone please look into and fix this?
As an analytics admin, I only want to maintain a single set of user permissions and user groups. Currently we have to maintain our user groups and permissions and a seperate list for emailing. Publishing Lists & Email Users options should include as default lists the ability to select groups defined in the user management area. You could then send a report or an email to all the users defined in this group instead of having to build a seperate publishing list that replicates these admin groups.
In the old billing section, were we could see server call usage, there was a breakdown of your server call usage based on the call/function type, s.t function vs s.tl function.This breakdown was useful in knowing why server call usage grew over a specific period. The new Server Call Usage area doesn't have this breakdown (not to mention not having a monthly breakdown, but that idea has already been raised I'd like to be able to trend server call usage reports by month )Please bring this functionality back.Thanks
Currently only users will full admin rights to a suite can create and share a workspace custom template (https://marketing.adobe.com/resources/help/en_US/analytics/analysis-workspace/starter_projects.htmlI am told that there is no way to give anyone the ability to create templates without giving them full admin rights.Please add the ability for product managers to give ability to create templates on a account-by-account basis without requiring the user to be full-admin.Thanks
With the push to remove complexity out of tagging, reporting and analysis I would like to see eVar support inside of the real time reports and API.For those of us that want to use the realtime reports we are forced to leverage props. But we do not want to use both props and evars for the same data (too confusing for end users!).I propose that the support for evars works exactly how the prop support works. Whatever data is on the hit should be available in real-time and we leave persistence of data to reporting and analysis workspace.
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.
We have a few marketing partners requests this integration: https://support.google.com/searchads/answer/7669521?hl=en&ref_topic=7670432Would love to see this built out in Data Connectors for easier setup and management.
I have an abandonment fallout path I need to create where visitors start Checkout Start>go to any page(s) BUT Thank You>start Checkout Start again>then Thank You page. The trick is that I can't just put the Checkout start twice because there needs to be at least one page in between them (rather than a reload).Rather than create a sequential segment and drop into the checkpoint, it would be great to be able to have a condition of NOT as a stand alone in addition to Eventual Path and Next Hit. That way we could create Checkout Start>NOT-Thank You>Checkout Start>Thank YouAlso it would be great to have a Next Visit condition as well. It would have to be available only if the Visitor option is selected. An example would be Checkout Start>NOT-Thank You>Next Visit-Checkout Start>Thank YouIt's certainly different than the NOT condition, but would be useful for helping to understand multi-visit situations.
It would be helpful if delimiters for the various operators with list capabilities were standardized to one character. Using spaces doesn't allow you to search on items with spaces in them (perhaps using single quotes?).Also it's a total guess as to what delimiters should be used with which operators currently. For instance "contains any of" is a space delimiter while "equals any of" is a comma. The only reason I know is because Jen Lasser told me (and even she wasn't sure if "contains" could take commas).There should be an indication of which delimiter is required when an operator is selected. It's a simple text addition and would avoid a good deal of trial and error.
You can create a set date range from the left hand panel (purple tiles). It would be great if we could create this set date range from the date selector in the top right hand corner by right clicking. (We can right click on so many elements except the date selector) I find exploring data around date ranges happens by using the top right hand date selector. But exploring gets tedious when having to re-create a set date range (that you have already selected) in the bottom left hand corner.
Nowadays, we can breakdown by position and this is great. However, I just can’t understand why this setting is turned off by default? Aren’t we always try to breakdown by position = give me TOP something. If there are special cases, we can always manually choose to filter SEO traffic if for some reason we want to always breakdown by SEO in last touch channels, or we could manually filter certain products if we want to week by week just to follow certain products. To me these are special situations and manual work would be just fine, but for my common sense it doesn’t make any sense that breakdowns aren’t ordered by position as default. I’ll give one example with screenshots.(Edit: Seems I can add only one screenshot, so I added combination of 5 and 6) 1) Added entries as metric and week as dimension. Time range is last 2 full weeks. Breakdown by position disabled by default.2) Added last touch channel as breakdown for weeks. Breakdown by position still disabled by default.3) Ok, I’ll check breakdown by position. I tested this separately and noticed you need to check this option if you want to see last touchchannels as breakdowns for new weeks when time moves on. This is alone good reason why this option should be enabled by default. Hard to understand why you wouldn’t want those breakdowns to continue. 4) Just to double-check, every dimension has its own ”breakdown by position” option, so these aren’t enabled for last touch channels, I just enabled these for week dimension.5) Week just moved on to another Monday morning and we have new week starting from 27th of February. There is a breakdown for last touch channel, I guess this due the fact I enabled breakdown by position for the week dimension. However, now it shows Natural Search as number 1 and that is not true, I mean that is not my best traffic sources for that week.6) Just to double-check I modified the filtering options and now I can see that direct traffic is the best traffic sources for that week. I could have done my analysis totally wrong if I didn’t realize to put that setting on for every single dimension = Time-consuming. Not sure did I do everything correctly, I tried… but please comment If I did or understood something wrong. If I’m correct, then I just can’t understand why Adobe (or any other user) would want this to work like this? You should always want to see your TOP breakdowns, and if there are moments you want to see something else then you can do manual filtering or something. Ps. Again, we would like the option (as admins at least) to choose our own default settings, and there is idea request for that one too. But even if we could do that, I still would want this breakdown by position feature to be by position as default.
I noticed a request for preventing alerts from firing on certain days of the week, but what I would like to see is the ability to prevent alerts from firing on certain days. One of my clients is a financial company that sees extremely low traffic on days the stock market is closed, so I would like to not only prevent alerts from firing on Saturdays and Sundays, but also during holidays on which the stock market is closed -- Martin Luther King Day, Labor Day, Christmas, etc. Otherwise, if I want to use daily alerts, I have to choose between alerts firing every weekend and on holidays and setting a much lower bar than I would prefer for the alert to fire. Thanks for your consideration.
Hello,It would be nice to be able to include data labels on Workspace visualizations and tables that will display either the absolute value, the percentage of total, or even an abbreviated value. This would best function as a toggled feature. The lack of this feature today prohibits our organization from utilizing Adobe Analytics Workspace at an enterprise level because the visualizations don't provide a clear delineation between similar values. If I schedule a Workspace as a PDF to my organization, we may get questions from the visualization as per the values each bar, or pie section represents.
Segments are useful for data pull of specific requirements, esp. customized pathing. However, sometimes segments are created for one-time use and don't need to be saved in the segments manager. I'm hoping we can bring back the function to create a segment without saving. (I believe Ad Hoc has this function in segment builder). Another idea is to create folder or tags for segments so it's easier to group things together and search. Raising this idea because a lot of us are facing the struggle of a long list of segments on the left panel, which is hard to navigate or find the commonly used segments.
I'd like to have the ability to export the existing set of processing rules we have in place for a particular reporting suite. We currently leverage context variables for both our sites and native apps traffic tags. The list of processing rules is easily over 70 and becoming harder to document on our internal systems. An export of any kind of all the rules currently active would allow for improved documentation for other organizations within the company.
Add the ability to put two dimensions next to each other in a workspace freeform table instead of only allowing to pivot dimensions.Example:DayWeekday/Weekend Marketing ChannelOrders7/11/2019WeekdayOrganic Search47/11/2019WeekdayPaid Search67/10/2019WeekdayOrganic Search27/10/2019WeekdayPaid Search1
Within the attachment you can see that we can apply a filtering possibility on the blank panel element. This is very useful for our complex deepdives on page or section level. However this isn’t possible yet for freeform tables. We could really use this functionality so that we can make a breakdown per specific freeform analysis on a page level that we want to drag in. I would assume that this innovation could easily be built for the freeform tables as well?This would make it possible to make complex analyses and easily filter between pages/sections. This will prevent making very long workspaces where you have to do a lot of manual work.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
