Product ideas | Community
Skip to main content

10000 Ideas

brentradNew Participant

Add Number of Users column to Workspace managerNew

DescriptionIt is difficult to determine how frequently Workspace projects are accessed. Adding a feature to the Workspace homepage that shows the number of unique users who have viewed the project will make it easy for admins to quickly find this information. Why is this feature important to youAllows users, especially admins, to see which Workspace projects are used frequently without having to parse Usage Log data. This may also make it easier for admins to determine if a Workspace project can potentially be removed, as projects that have not been engaged with in, say, 180 days may not be useful anymore. Adobe has made a "Used In" column available in the Filter/Segment and Calculated Metric manager pages, which has made it easy for us to see how a component is used in other components.  How would you like the feature to workAdd "Number of Users" as a table option in the Workspace manager. This would show the total number of unique users who have engaged with a Workspace project (viewed, created, modified, shared, etc.) over a set time period (e.g. last 90/180 days).  Current BehaviourThe number of users who have accessed a Workspace project is not currently available in the Workspace manager for Adobe Analytics or Customer Journey Analytics. To find which projects are used, admins must parse through Audit Logs (CJA) or Usage Logs (AA). This is time consuming.

lizanneNew Participant

Integrate Target APIs as Power Platform ConnectorInvestigating

Description -Integrate Target Admin APIs (and potentially all Target APIs) into Microsoft's Power Platform as a Connector: Integrate your service with Microsoft products and services | Microsoft LearnWhy is this feature important to you -Low/No Code solution to assist with automating workflow and reporting of Target- consistent with Target's approach to simplify experimentation access via a low/no code platform. How would you like the feature to work -Target Admin APIs (and potentially all Target APIs) are available as Certified Connectors published by Adobe into PowerPlatform- this is consistent with other Adobe Product integrations available today as connectors: Microsoft Power Platform and Adobe integrations | Microsoft Learn - List of available Adobe Connectors in Power Platform (Updated 2023); Adobe Experience Manager - Connectors | Microsoft Learn - AEM Connector (Not mentioned in above link)Current Behavior -Any automation or even basic reporting needs that have to happen outside of the Adobe Target Web UI require a developer to build a postman connection & run an API. Extensibility of the Target platform is limited to those with developer resources & time- something as simple as sending a notification when an activity has been live for more than 90 days has to be done manually or through extensive development & custom integration. 

Adilos-Cantuerk
Adilos-CantuerkNew Participant

FPO - essential function - JPG can not display transparency - additional slider for PNGalpha can fix the feature.Investigating

Request for Feature Enhancement (RFE) Summary: I suggest to have a PNG option for the FPO setting slider to enable a seamless working with assets that do rely on transparency. Use-case: FPO Renditions for InDesign Asset Link are OOTB only available as JPGs.This file format does not meet the needs of modern print media production workflows, since images rely more heavily on transparency settings instead of cutting paths. This change is not very new and i have seen companies made that switch from cutting paths to transparency back in 2010. This makes JPG a suboptimal choice for FPO renditions since this format is not capable of containing transparent pixels. The picture would be flattened on a white background. Current/Experienced Behavior: FPO is simply not an option on every asset that has a transparent background. This goes for pretty much every single product picture within our AEM.Since the setting is applied via Folder setting, we have to manualy delete the FPO renditions on assets that need its inbuilt transparency to be able to layout correctly in InDesign (since JPG does not hold any transparency) and to make things worse - this increases the loading time significantly for bigger print media cataloges, since InDesign will load the orignal files into the cache every time the user checks out the cataloge. We are talking 10Gig every single checkout.To make the FPO a good thing - it needs to have more options than just JPG. Improved/Expected Behavior: Give users more than just JPG as a FPO format. I suggest PNGalpha since it would meet the transparency criteria, yet there might be some additional things i don't have on my radar.  Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS 2023.12.14697.20231215T125030Z Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

FrederikWerner
FrederikWernerNew Participant

Easily accessible date granularity toggles for line charts in Analysis WorkspaceNew

Description - Everybody loves a good line chart. With line charts, you can easily see numbers, but on a line! It's amazing! But I think it could be even more amazing. In many Analysis Workspace projects, I see some sort of line chart for top-level metrics and trends, like this one: Now, depending on how our stakeholders would use this project, they might want to change the granularity of the chart to reflect longer-running campaigns, sudden traffic increases, and many more use cases. To do that, they currently have two options: Find the connected Freeform table, drag and drop a new granularity in there, and hope it doesn't go wrong OR do it directly on the chart by (finding and) clicking the little gear icon: Now, while those methods work well enough once you a) know where to find the option and b) remember where it is hidden, we might have an opportunity here to make it just a bit easier for people to play with granularities, especially if they only use Workspace every now and then. To achieve that, I proudly propose to you: The same, but slightly different: Now, we have a quickly accessible, not-scary, simple-to-understand way to change granularities without having to find the gear icon or any drag and drop. Amazing! All it needs is this little group of buttons (or, for the cool kids, a Coral.ButtonGroup) that might only show up when hovering over the chart and possibly can be hidden entirely from the gear box. And, as we all know: Fewer clicks always mean higher adoption, so this might be an easy win! Why is this feature important to you - Because I want my stakeholders to work with the data on their own instead of asking me time and time again how to change granularities, so I can spend more time doing what I love: Fixing GenAI errors (or whatever the much cooler analysts do these days) How would you like the feature to work - Like above Current Behaviour - Many clicks for few changes, therefore fewer changes, and more "quick 5-minute calls" with stakeholders

Casey_Grimes2
Casey_Grimes2New Participant

Align Opportunity Identification Across API BehaviorsNew

As a technical solution provider, I would like to provide enhanced opportunity information across Marketo behaviors--and ideally, without the use of a separate CRM. However, when a CRM is attached to Marketo, there are several issues with translating Marketo opportunity activity: Activities such as Add to Opportunity/Remove from Opportunity/Update Opportunity (Activity IDs 34-36) use an integer as the identifying value for an opportunity. For example, a recent "Add to Opportunity" activity returns the following:{"id":98506929,"marketoGUID":"98506929","leadId":2054980,"activityDate":"2024-05-01T09:40:00Z","activityTypeId":34,"primaryAttributeValueId":72984,"primaryAttributeValue":"Opportunity Name - 2024","attributes":[{"name":"Is Primary","value":true},{"name":"Role","value":"Relevant Executive"}]}, This results in an Opportunity ID value of "72984." While I can work backward using the primaryAttributeValue to match via the opportunity name, this is less than ideal. There is also no reference to any externalOpportunityId, which would be used in this case (the instance is synced to an SFDC instance).Querying Marketo's own recording of opportunities independent of the CRM results in displaying a UUIDv4 value, but there is no reference to either the integer value on the Opportunity-related Activities value that could be used to cross-reference between systems:{"requestId":"11802#18fdeddf644","result":[{"seq":0,"marketoGUID":"be320968-423a-48e2-9730-e2e08df61fae","externalOpportunityId":"0061R00000m3kRLQAY","updatedAt":"2023-09-06T01:27:58Z","createdAt":"2018-12-17T15:43:08Z"}],"success":true}The marketoGUID is written activity-style rather than reading from the integers recorded in the opportunity-related activity. This leaves no way to resolve Marketo's own ID systems to tie the data together.Could you provide either the GUID in the activity or the integer in the main Opportunity query? Likewise, since something is translating the integral Opportunity ID to the Salesforce Opportunity Name, could the externalOpportunityId be exposed as a value on Opportunity-related activities? Otherwise, this data is disjointed and can only be poorly unioned together.