Product ideas | Community
Skip to main content

Filter by idea status

10000 Ideas

adamj74598025New Participant

Export Analysis Workspaces into Report Builder Formatted DeliverablesNew

The workflow of discovery in Analysis workspace, and curation is fantastic! Thank you for the years of work and great experience. Building on that workflow, ideally we could make complex queries (workspace) that could be "designed" by the teams (personas) and then graduate into standing Report Builder enabled reporting.This is great for two reasons in true multi-national environments where multiple brands and geographies are required to be accounted for in thinking and process.     1. The "common elements" (Usually 80% repeated by market) are then accessible in an area where we can further reduce the audience as needed by simply      adapting filtering capabilities or by many other segmentation abilities in RB downstream.     2. For companies that have vendor, owner and franchise models, in RB the end user (quarterback from marketing to end user) can then "lock down" the data by      rendering the view for a single property, brand, product, owner, franchise etc to further reflect the complexities of the legal relationships companies have with their      own ownership and business models. (Travel is heavily skewed with this consideration in mind)*The hidden value is that in RB, the analyst can then continue to slice and dice the data at the end user level, change formats or communicate in a standard and repeatable medium both in a SaaS Multi-tennant environment (Workspace) but also in a static environment where considerations held in banking, finance, law and other sensitive areas can be respected.Please and thanks!~El Barto

jeremyl59043873New Participant

Processing Rules: Add Events to the line item conditionsNew

With the release of Processing Rules where all Admins have the ability to leverage processing rules to increase their data accuracy and completeness, it would extremely helpful if we added Events to the line item conditions.Use Case - We currently have a DTM Javascript heavy based implementation of Adobe Analytics and have been working with our IT department to reduce the size of both the JS files (DTM's satelliteLib and AA's s_code) as well as reduce the size of the client side beacon calls / hits to the Adobe servers.we are looking for ways to achieve these size reduces without sacrificing our tracking / metrics capabilities.  so we thought processing Rules would be a great place to start, as we can set our metrics and define our props/evars based on the end user's URL and the Defined Page Name.Since this is a migration strategy and not a new install, we have to use conditions like set prop14 = name when prop14 is not set.  which means processing rules are simply filling in the gaps when the information is missing.but when it comes to setting events there is no 'when' option.  So we can't say set event100 when event100 is not set.  the 'when' statement seems to be limited to just props and evars.  Currently when you use this set event options it will set the event regardless of what events are already there so if you have it both in the javascript and the processing rule the event gets counted twice, obviously that is not accurate.because of this limitation we are limited in our ability to reduce our dependency on the client side javascript and a large percentage of the data we send to Adobe, especially since Adobe has given everyone 1000 events to set within their properties, are individual events for each page and user action.so it would super helpful if we could add events to the 'when x is not set' conditions in the processing rule line items.  this would enable customers to set events or to fill in events gaps when the javascript happens to miss them.