Adobe Target

Hi Adobe Team, https://experienceleague.adobe.com/en/support?support-tab=my-cases&case-id=E-002435848&org-id=231F22CE527850C40A490D4D%40AdobeOrg#homeWe're currently using the Adobe Target MCP tool (get_a4t_report) to pull A4T report data programmatically. The tool works well for retrieving activity-level metrics, but we'd like to request one enhancement:Request: Add a metric parameter to get_a4t_report so users can specify the counting method — e.g., visits, visitors, or entries — rather than having it hardcoded to entries.Current behavior: The tool always returns data based on metrics/entries with no option to change it.Desired behavior: Allow an optional metric parameter (e.g., metric: "visits") so we can retrieve visit-based or visitor-based reporting depending on the activity setup.This would make the tool significantly more flexible for teams who measure activity performance on a visit or visitor basis rather than entry-based.Please let me know if additional context or a u

Requested EnhancementsPlease consider expanding the Activity Revisions API to include more complete audit information, such as:What exactly changed in each revision Who made the change When the change occurred Previous value and new value for changed fields Change type or action performed, such as create, edit, approve, deactivate, archive, or schedule update Workspace, property, or environment context where applicableWhy This MattersMore comprehensive revision history would significantly improve:Audit readiness Troubleshooting and incident analysis Operational transparency Change tracking across teams Governance and compliance reviewToday, it is difficult to fully understand the history of an activity and determine the precise sequence of updates made over time. Expanded revision details would make the API much more useful for enterprise activity management.Request to AdobeWe would appreciate it if this enhancement request could be shared with the Adobe Target product team for conside

There are two toggles in the Target Activity QA Link UI:Match audience rules to see experiences → This is toggled OFF by default Show default content for all other activities → This is toggled ON by defaultWe share preview links with business partners of all technical levels, and users are constantly perplexed that after previewing a draft activity, they can no longer see any live activities.I’ve explained they can use the Target QA bookmarklet or manually clear the at_qa_mode cookie, but the better solution is for me to remember to toggle the second option off before sharing links.But it’s not sticky, so that’d be helpful: toggle it off once per activity and it should retain that state instead of defaulting back to ON. Better yet would be a global setting in the Admin panel, like there is for the VEC settings.   

Models API (https://experienceleague.adobe.com/en/docs/target-dev/developer/api/models-api/models-api) currently allows getting a list fi features that make up models for AP/AT activities. While it works for activity-level, would be beneficial to get the list of all features across an organisation so that we can block unwanted features globally.For mature organisations that use many AP/AT activities, its difficult to identify features as part of an activity and then block those globally. Getting list of all features in one single API response will help saving time.

Description –Currently, assets such as audiences and activities created via the Audience API or Activity API in Adobe Target cannot be edited in the Adobe Target UI. Why is this feature important to you –Our customers want to use AI to create audiences and activities automatically. However, there are cases where they need to review and manually edit these assets later in the Target UI. The inability to do so limits flexibility and usability for marketing teams. How would you like the feature to work –We want assets created via the Audience or Activity API to be editable directly in the Adobe Target UI, just like those created manually within the interface. This would ensure consistency and allow users to make adjustments without recreating assets. Current Behaviour –Assets created using the Audience API or Activity API are not editable through the Adobe Target UI. Any updates or modifications must be done programmatically through API calls.

We have received confirmation from Adobe Support that when importing customer attribute data from non-Adobe CDP sources using the Adobe Target Bulk Profile Update API (v2), although the data is transferred in array format, Adobe Target can only process it as ‘single-value strings’.If array format can be received, should it not then be possible to handle it as an array within Target?This would be significantly more convenient when creating audiences, so we would very much appreciate your consideration of this matter.

It would be nice to be able to programmatically access the QA URLs for a current running AB test.  We run a small subset of front end tests in our CI pipeline and we need the tests to be deterministic.  The way we do that now is manually retrieve the QA URL from the adobe target GUI.  We'd like to have the test determine the experience without having to retrieve the QA URL manually.   I have two suggestions:First:  Add it to the existing `Get AB Activity by ID` Second:  Create a new API to `Get AB Activity QA URLs by ID` Suggested response:    "experiences": [ { "experienceLocalId": 0, "name": "Experience A", "visitorPercentage": 34, "qaUrl": "at_preview_token=g5xKOs9QjAl3KN%2BwvyAAmnWEFq%2Br1NJA9GWwjZnLpb4%3D&at_preview_index=1_1&at_preview_listed_activities_only=true&at_preview_evaluate_as_true_audience_ids=1100025", "offerLocations": [

In a global company, the Adobe team recommends consolidating multiple countries in a single AEP Organization, with separate sandboxes. However, Adobe Target doesn't have the same hierarchy of "organization + sandboxes", so the Out of the box integrations are not available:* The Adobe SDK don't allow two deployments across digital channels, one for AEP Org and another for Adobe Target Org. Therefore, we have to manage a dependency by uninstalling the Target SDK and modifying the integration through the Server Side, which is not friendly for marketers.* Audience destination nether works. We have to share segments through Tag Manager or create a custom microservice to integrate Adobe CDP + Target. Some suggestions:* Allow the installation of two SDK, one per Organization, across digital channels* Align the Adobe Target and AEP hierarchies (Org + Sandbox)* Create a OOTB destination with Target in a different Org to avoid creating an in-house microservice 

Regulators and external stakeholders may impose requirements regarding the monitoring of functionality and data usage by internal employees. This includes tracking who accesses which data and what actions are performed with it. The objective is to enable the automatic detection of anomalies through monitoring tools.To achieve a form of automated monitoring and alerting, detailed logging must be implemented, and these logs must be accessible. Since this is currently not the case, I would like to propose implementing such logging. As an example, consider the level of detail captured in Adobe Analytics.

Description - While creating a new audience by combining existing audiences, we can only add upto 20 segments and add upto 2 containers one with in another.Why is this feature important to you - In some cases we want to add more than 20 segments and create complex audiences making use of profile scripts and add 3 or more containersHow would you like the feature to work - Just as the regular segment creation, with updated max limits. 

Description -Currently to target a triggerView() call, widely used in SPAs you have to use the VEC. This can be very cumbersome and the VEC is not always supported by user's website setups, making it difficult or impossible to build activities with triggerView. Ideally we would be able to select view names in the Location dropdown of a form based activity so that we can target views without having to manually reach them in the VEC. This would also be useful for tests which span multiple locations and cover both mboxes and views. Why is this feature important to you - A large part of my website is a React SPA, in order to build tests for some components I have to go through my entire SPA which can take upwards of ten minutes to trigger the view I want to target. I only use target as a code delivery tool rather than using the VEC, so form based activities are much more suitable, but can't be used at the moment with views. Also, the VEC is fairly unreliable and often breaks my site s

Description - We have Adobe Target on +30 websites, when selecting Analytics as a reporting source, the Report Suite's are listed in a random order. If they were listed alphabetically it would save time and reduce frustration. Why is this feature important to you - Would save time hunting for the correct report suite How would you like the feature to work - List report suites alphabetically  Current Behavior - Report suites are listed in a seemingly random order

DescriptionThe proposal is to integrate quantum computing capabilities into Adobe Target’s personalization and optimization workflows. Quantum computing enables processing of exponentially complex datasets and can solve optimization problems faster and more accurately than classical AI. By embedding quantum-inspired or quantum-hardware-accelerated models into Adobe Target, businesses can achieve ultra-precise personalization and superior optimization outcomes. Why is this feature important to youNext-level personalization: Today’s AI-driven personalization is powerful but constrained by classical computing limits. Quantum computing can unlock new levels of accuracy and context-awareness.Faster experimentation: Reduce time-to-confidence in A/B and multivariate testing, helping businesses act on insights faster.Competitive edge for Adobe: Adobe would become the first mover in merging marketing technology with quantum innovation, increasing adoption of Adobe Target.Revenue impact: Su

This request is for Adobe Target. Please add to the Target Admin API "List Activities" endpoint a param/value pair with "modifiedBy" that would correspond with the already-existing "modifiedAt" param/value pair. Doing this work manually takes 1 FTE an average of 7 hours/month. This costs us $21k/year and hundreds of thousands in Business Decisions made from this.

 Documentation shows that only a limited set of activities are compatible with the VEC:https://experienceleague.adobe.com/en/docs/target/using/experiences/spa-visual-experience-composer#s... Description - Automated Personalization, Auto Target, and Recommendations are not supported by the Visual Experience Composer. Why is this feature important to you - Requesting these activity types get support through the VEC in the future, to enable SPA sites to utilize Adobe Sensei activities (Automated Personalization + Auto Target) and Recommendations. How would you like the feature to work - Enable "Current View" to display and for ViewName to be recognized from Single Page Applications when in the VEC for Automated Personalization + Auto Target activities. Current Behaviour - The VEC does not recognize ViewName, and activities do not render based on the ViewName. Documentation shows that only a limited set of activities are compatible with the VEC:https://ex

Description -I'm creating A/B test using AT auto-allocate but unable to choose AA calculated metrics for my optimization goal, while I still can use AA calculated metrics for my Experience Targeting activities. Why is this feature important to you - AA calculated metrics allow us to flexibly targeting events which is not well define by AA events yet How would you like the feature to work -Current Behaviour -

Description - Have the ability to edit Shadow DOM elements using the HTML editor in the VEC, which is currently not supported.Why is this feature important to you -Many of our business users rely on the VEC, and adoption would significantly increase if this capability were available. It would reduce dependency on developers, save time and resources, and accelerate test launches.How would you like the feature to work - When you click on a Shadow DOM element in the VEC, have "Edit HTML" as an optionCurrent Behaviour - When you click on a Shadow DOM element in the VEC, "Edit HTML" does not appear

Description - At present my understanding is that we are only able to see collisions information in Target by opening each activity, this is very time consumingWhy is this feature important to you - We have many experiments running at the same time often using the same website pages.How would you like the feature to work - A collisions dashboard that would show all of the activities running on a specific page.Current Behaviour - Currently I can only see this information by seperately opening each activity.

Description:In Adobe Target, once changes are made to an experience (e.g., offer content, audience rules, design tweaks in VEC), there is no built-in versioning or rollback functionality for that specific experience. If a mistake is introduced or someone wants to revert to a previously working version, it often requires manually redoing the changes or referencing screenshots or documentation - if available. Why is this feature important to you:Teams working on multiple activities across A/B tests and personalization campaigns need the ability to iterate quickly and safely. Mistakes can happen, especially in large organizations or distributed teams. Having a version history would reduce risk, support better collaboration, and speed up debugging and approval workflows. It’s especially useful for regulated industries or agencies where approval trails matter. How would you like the feature to work:Each experience within an activity should automatically store a version history whe

Description –Managing Adobe Target activities often involves multiple roles across teams - marketers, developers, QA, and analysts. However, the current access control model does not allow fine-grained permission settings, making it difficult to delegate responsibilities securely and efficiently. For example, a QA specialist might need access to generate QA links but should not be able to modify offers or audiences. Similarly, a content editor might need to update offer text but not change targeting rules. The inability to configure such detailed roles leads to over-permissioned users and inefficient workflows. Why is this feature important to you –In large organizations or agencies managing multiple clients and campaigns, there is often a need to allow multiple team members to collaborate on activities. However, the current role-based access control lacks the flexibility to allow fine-tuned permissions (e.g., editing audiences but not offers, or managing QA links without publishi

Description - In the new UI update from last week, Adobe now requires 'non-Library' Offers created in FEC to be saved with a unique name. Can we remove that or improve on it so that it is less cumbersome for the authors?Why is this feature important to you - We predominantly use these non-saved Offers in our activities and having to create a unique name for each location is an unnecessary step and slows down the workflow.How would you like the feature to work - Could be a few options to help speed this up:1. Remove the requirement all together --like how it worked in the old UI; no name required.2. Maybe you could pre-fill a name in that field when creating a new Offer to make it easier for authors. Maybe something like the <location>_"offer1", etc. Something that would make it less cumbersome. 3. If the authors are going to HAVE to name the Offer anyway, why not add an option in the Create Offer screen where the user can select to go ahead and save the offert to Library? It

Description - It appears that with last week's UI update to the Forms Composer, some of the logic changed to where you cannot apply the same audience to more than one location in the Forms Composer.Why is this feature important to you - We often use audience refinements for audiences such as isolating to lower environments. So, if I have 2 locations in one experience, I want to be able to apply the same, saved  'lower environment audience' to both locations.How would you like the feature to work - Like it did in the old UI. Allow for a saved Library audience or an activity-only audience to be applied across multiple locations in an activity.Current Behaviour -  Similar to when you try to apply the same audience to multiple experiences, it errors out and says duplicate audiences are not allowed.So, you have to recreate the audience from scratch and give it a different name. That is very inefficient.

Description -Why is this feature important to you - Because occasionally we want to publish promotional (or other content) updates that are unrelated to an experiment but need to be published at a future time in a live experiment.How would you like the feature to work - Same as regular scheduling except allowing for the current Activity to be live Current Behaviour - Presently if you schedule an update to a Live experiment it gets deactivated. This feature would allow for that to not happen.

Description - I applaud for finally making some changes to the Target UI. However, there are several items that I think are needed to help improve it. 1. There's a lot of wasted space on the far left where it says 'all activities' 'failed and draft activities' . That takes up a whole 'column' of space in my layout.2. the columns still can't be adjusted for width. Our activity names are very long and it would be helpful to be able to adjust the width of that column so we can see more of the name. Even if you delete an multiple columns of data, it does not re-adjust column widths to fill page and show more of the activity name. 3. in the old UI, you could hover over the activity name and see the full name, that is no longer possible. The only way to see the full name is to click into it. That's very inefficient.4. You have a bug where often times when you click on an activity name, instead of loading that activity, it just reloads the main page.Why is this feature important to you -

DescriptionCreate a bulk update interface designed to efficiently manage and update multiple multi-site and multi-language experiences simultaneously. Why this feature is importantWe manage a large volume of experiences that often require coordinated updates across multiple sites and languages. Performing these updates manually is not only extremely time-consuming, but it also introduces a high risk of human error. A purpose-built solution would significantly streamline our workflows, improve accuracy, and free up valuable time for strategic initiatives. Ideal functionalityThe feature should provide a centralized interface where multiple activities can be selected and updated at once—without the need to drill into each one individually. This would include the ability to apply consistent changes across experiences, preview updates, and track changes in real time. Current workaroundWe’ve implemented a temporary solution using APIs and spreadsheets, which has helped address