Product ideas | Community
Skip to main content

10000 Ideas

Marti_ANew Participant

AA/CJA - Enhance component & segment governance and traceabilityNew

Hi there, I'd like to raise a feature request on AA/CJA segments & components. DescriptionI’d like to suggest a few improvements related to traceability and governance of key components in AA and CJA, specifically for segments, derived fields, and Data Views. Why is this feature important to youThese features would greatly enhance collaboration across teams, improve auditability, and enable safer and more transparent management of assets within Analytics. In environments with multiple users and frequent changes, it's essential to track who made what changes and when, and to be able to recover previous versions if needed. How would you like the feature to workSegment change history: Ability to view a log of changes for each segment, with the option to restore previous versions. Ideally, this could be enabled selectively for specific segments to avoid unnecessary data load.Author and last modifier for derived fields: Each derived field should display who created it and who last modified it, along with timestamps.Timestamp and user tracking in Data Views: Every component added to a Data View (dimensions, metrics, filters, etc.) should record the user who added it and the time it was added.Current Behaviour Currently, there is no version history for segments, nor clear traceability of who created or modified derived fields or Data View components. This makes collaborative management and troubleshooting more difficult in complex environments.

Pradeep-Jaiswal
Pradeep-JaiswalNew Participant

Reading licence numbers in long zero formats is mentally taxingNew

Description : When large values are shown as long strings of digits it slows comprehension and increases the chance of misreading. Replacing long zeros with readable units like 𝗺𝗶𝗹𝗹𝗶𝗼𝗻𝘀 and 𝗯𝗶𝗹𝗹𝗶𝗼𝗻𝘀 for counts and 𝗠𝗕 𝗚𝗕 𝗧𝗕 for data size will make licence pages clearer and faster to use. Why is this feature important to you :𝗖𝗹𝗲𝗮𝗻𝗲𝗿 𝗱𝗶𝘀𝗽𝗹𝗮𝘆𝘀 𝗽𝗿𝗲𝘃𝗲𝗻𝘁 𝗰𝗼𝘀𝘁𝗹𝘆 𝗺𝗶𝘀𝘁𝗮𝗸𝗲𝘀 ✅Teams must validate entitlements at a glance during renewals audits and governance checks. Human eyes scan better with semantic units like 𝗺𝗶𝗹𝗹𝗶𝗼𝗻 𝗯𝗶𝗹𝗹𝗶𝗼𝗻 and 𝗚𝗕 𝗧𝗕 rather than counting zeros. This reduces review time supports accurate decisions and improves confidence across stakeholders 📊 How would you like the feature to work :Display large counts using compact units 𝗸 𝗺𝗶𝗹𝗹𝗶𝗼𝗻 𝗯𝗶𝗹𝗹𝗶𝗼𝗻 with hover or tap to reveal the exact numberShow data size using 𝗠𝗕 𝗚𝗕 𝗧𝗕 and allow switching to bytes when neededProvide a small toggle on the page to choose 𝗿𝗮𝘄 𝗱𝗶𝗴𝗶𝘁𝘀 or 𝗿𝗲𝗮𝗱𝗮𝗯𝗹𝗲 𝘂𝗻𝗶𝘁𝘀Maintain consistent formatting across tables cards and summaries for a cohesive experience Current Behaviour :Today many licence fields show values like 1000000000 or 1048576 which are hard to parse quickly and prone to misread especially under time pressure. The absence of unit formatting and toggles creates friction and slows audits and planning.

Mel-4New Participant

Single Select Only drop down option (Filter)New

Description:Introduce an option in Adobe Analytics Workspace filters (e.g., dropdown segments, panel filters) to enforce single selection only so users cannot apply more than one filter value at the same time. Why is this feature important to you:When users multi‑select from a dropdown filter or segment, some reports produce incorrect or misleading values. As an example, we use segments to isolate our Web and App experiences. However if a user selects both of these from a dropdown, they will get inaccurate values in the data set. Similarly, during gradual rollouts, mixing two experiences into one selection can lead the stakeholder to make decisions based on inaccurate values. A single‑selection restriction would ensure data integrity, especially in decision‑critical scenarios such as product rollouts. How would you like the feature to workAdd a setting to the filter/dropdown component in Workspace (e.g., a checkbox “Limit selection to one value”). When enabled, the filter behaves like a radio button list so selecting a new value automatically deselects the previous one. This should work for dimensions, segments, and metrics where dropdowns are used.Current BehaviourWorkspace filters and dropdown segments allow multiple selections by default. The “Require selection” option only forces one or more selections, not exactly one. There is no native way to prevent multi‑select, forcing workarounds like separate panels or project links.

TonyWa3New Participant

mTLS or OAuth authN between AEP mobile SDK and edge network for data collectionNew

Description - Datastreams are required to set access type to Mixed Authentication to allow unauthenticated requests from AEP web or mobile SDK https://experienceleague.adobe.com/en/docs/experience-platform/datastreams/configure. My understanding is edge network validates ECID, environment id, org id and other non-cryptographic-secrets to ensure request is not bogus, but does not care where the request is coming from. Can we have the option for authenticated access type to protect our datastream from spoofing attacks?  Why is this feature important to you -Our organization has security requirement for this. Data passed from mobile SDK to datastream contains sensitive customer data, that if unprotected can expose notifications intended for our customers to unauthorized third parties, and possibly fraud activities. In my country, there are federal cybersecurity guidelines and laws that govern how we handle customer data. How would you like the feature to work -Have the option to configure authenticated communication between AEP mobile SDK and edge network for data collection. Either mTLS or OAuth 2.0 Client Credentials flow works for us. Current Behaviour -To use AEP mobile SDK, datastreams are required to set access type to Mixed Authentication to allow unauthenticated requests https://experienceleague.adobe.com/en/docs/experience-platform/datastreams/configure

Casey_Grimes2
Casey_Grimes2New Participant

Allow Custom Fields on Program Period CostsNew

While being able to list out individual Program cost line items is a useful feature, it's limited by a few things: namely, the ability to only parse certain types of budget information based on information in the note. I would like to build a more robust approach for budget measurement and compliance in Marketo by providing a standardized set of custom fields that could provide more detail in budget analysis. While I would expect to have some of these as fully custom, I think others are widely applicable and may make sense to be in the core product. Some examples of these would include: - Spend Type: Categorizes the primary expense of the campaign (e.g., 'Media Spend', 'Agency Fees', 'Content Creation', 'Sponsorship'). This allows for a more granular analysis of where the budget is going and the ROI on different types of spend.- Budget Source / Team: Tracks which team's budget is funding the campaign (e.g., 'Corporate Marketing', 'Product Marketing', 'Field Marketing'). This is essential for leaders to see how different teams are performing with their allocated spend. - Vendor / Payee: A field to specify the vendor who will receive the payment (e.g., 'Google', 'LinkedIn', 'Gartner', 'Acme Agency'). This allows you to run reports on your total spend by vendor across all campaigns, which is invaluable for negotiating contracts. - Invoice / PO Number: A text field to record the associated invoice or Purchase Order number for the expense. This creates a direct link between your marketing plan and the financial transaction records, making audits and expense verification straightforward. Implementing these sorts of additional fields would turn Program Costs from a legacy piece of information to one that's more central to Marketo setup and ROI; please consider expanding out the feature in this way or with similar functionality.