Adobe Target

Hello Community,I'm working on granting permissions to the technical service account for API integration in the Adobe Admin Console. I received the following recommendations from another forum, but I couldn't find some of the details they mentioned. To grant the permissions, I followed these steps:Go to the Adobe Admin Console (adminconsole.adobe.com).Navigate to Products > Adobe Target.Click on the Product Profile (Target workspace).Go to the Users tab and click Add User.In the pop-up, switch to the Service Accounts tab.The issue is that I couldn't find any 'Service Accounts' tab in the Admin Console. I'm not sure if this is due to my access level. Has anyone seen or used this tab in the Admin Console?  Since there is no tab called 'Service Accounts', should I use the 'Users' section to add the technical service account (IMSe9c...@techacct.adobe.com)? I tried this, but it did not work when I verified the integration in AEM.Can anyone please advise on this? Thank you!

Hello, everyone! Would somebody mind helping me with the SDK implementation? I'm trying to integrate Adobe Target from the server but I'm not receiving the experiment when using the Node.js package on a Next.js app... import TargetClient from '@adobe/target-nodejs-sdk'; const CONFIG = { client: '*****', organizationId: '*****@AdobeOrg', events: { clientReady: () => console.log('Adobe Target client is ready.'), }, }; const targetClient = TargetClient.create(CONFIG); export async function getTargetAttributes(mboxNames, cookies) { const targetCookie = cookies[TargetClient.TargetCookieName]; try { const response = await targetClient.getAttributes(mboxNames, { targetCookie }); return { attributes: response.asObject(mboxNames[0]), targetCookie: response.getResponse().targetCookie, }; } catch (error) { console.error('Error fetching Target attributes:', error); return { attributes: {}, targetCookie: null }; } }export const ge

Hello Community,We have an AEM Target integration currently in place, and our API integration is configured with both the default and project workspaces, with both Approver and Editor access assigned. The issue lies with the API integration: we are able to successfully export the XF to the project-specific workspace in Target, but we are having trouble pulling audiences from Target.At present, we can sync audiences from the default workspace in Target, but we are unable to pull audiences from the project workspace. On the AEM side, we do not have any configuration that allows us to pull from a specific workspace, other than the API integration—where, ideally, we should be able to specify the workspace. Currently, it is configured to use the project workspace.Has anyone tried pulling audiences from Target’s project workspace? We are using a premium Target account, which should have the capability to access audiences from the project workspace. Can someone advise what access is required

Did the new Target UI affect/change the Adobe Target Views functionality for SPAs on Angular frameworks? I tried to find documentation but all I see is this article from 2023: https://experienceleague.adobe.com/en/docs/target/using/experiences/spa-visual-experience-composer @8695269 @1851629 

Hello everyone,I'm experiencing an issue with the VEC in the new Adobe Target UI and was hoping someone in the community might have a solution.When I try to edit an existing experience that is part of an activity with multiple experiences, the VEC gets stuck on an infinite loading screen with the message "Applying initial modifications," as shown in the attached screenshot.This issue seems to be specific to editing existing experiences. If I create a brand new activity, the VEC loads correctly. The problem only occurs when I go back into an activity to modify a specific experience.So far, I have tried the following troubleshooting steps without any success:Switching browsers (Chrome, Firefox, Edge).Using incognito/private browsing mode.Testing on different computers.Using different user accounts.The problem persists across all these scenarios, which suggests it might not be a local environment issue.Has anyone else run into this specific problem with the new UI? Is there a known bug or

When working with Adobe Target, understanding profile scripts is essential for tracking user behavior, storing preferences, and customizing experiences. However, many users get confused between profile and user when writing profile scripts.In this blog post, we’ll break down the differences between profile and user, their use cases, and how you can leverage both for effective personalization.What’s the Difference Between profile and user?Feature profile userScopeStores persistent user data (across sessions & visits).Retrieves real-time session-specific data.PersistenceData is stored permanently unless reset or expired.Data is only available during the session.UsageUsed for tracking user history, preferences, and behavior over time.Used for fetching live details like IP, referrer, and user-agent.Example Methodsprofile.set(), profile.get(), profile.increment(), profile.expireIn()user.header(), user.device(), user.ipAddress(), user.referrer()Common Use CasesCounting visits, storing us

I created a new A/B test and added modification code (Mbox code) under Experience A using the Custom Code option. The changes saved successfully in the VEC editor.However, during validation:Experience A delivers nothing (and appears empty in the VEC editor).Experience B, where I did not add any code, is unexpectedly delivering the Mbox code. The Mbox code is appended on Experience B, and when I open the VEC it shows up there.Has anyone faced this issue before? How can I resolve it so that the custom code applies only to Experience A?

If the personalization was rendered using Mobile SDK which method to use?offer.displayed() ?https://developer.adobe.com/client-sdks/edge/adobe-journey-optimizer-decisioning/#single-offer-interactions-events-tracking

Dear Team I couldnt attend the webinar session on Target 'Leveraging Adobe Target AI for Optimization Excellence and Scale' It happened on below dateDate: Thursday, September 18, 2025Time: 8:00 am PDT Can i get recording link for the same?Thanks

Do you feel Adobe Target is being used to its full potential in your organization? What features or capabilities are under used — and why?  I’m curious to hear how others are approaching it.   In many cases, we use the core features (A/B testing, VEC, simple personalization), but I wonder how often the full capabilities of the platform are actually being leveraged.   Are features like Automated Personalization, Auto Target, Recommendations, or server-side delivery being used regularly in your setup? Or do they stay on the sidelines due to complexity, lack of knowledge, resource constraints, or due to any other issues?   What capabilities are underused in your organization — and what’s holding them back?   Would love to hear real examples — both wins and blockers

Hi everyone,I'm trying to create audiences in Adobe Target using profile scripts. This is my first time attempting this, so I followed this guide to send the data I need for the profile scripts from Data Collection:https://experienceleague.adobe.com/en/docs/platform-learn/implement-web-sdk/applications-setup/setup-target#send-parameters-to-targetThis is how we map the data to be send. In a data element: var data = { __adobe: { target: { "profile.comprobarIngresosSimulador": _satellite.getVar("originadorSimulacion | comprobarIngresosSimulador"), "profile.montoPrestamoSimulado": _satellite.getVar("originadorSimulacion | montoPrestamoSimulado"), "profile.pagoFijo": _satellite.getVar("originadorSimulacion | pagoFijo"), "profile.plazoSimulado": _satellite.getVar("originadorSimulacion | plazoSimulado"), "profile.producto": _satellite.getVar("originadorSimulacion | producto"), "profile.tasaInteres": _satellite.getVar("originadorSim

Hi @gaureshk_kodag ,Need your help in getting the issues rectified which I am facing for creating a recommendation activity in adobe target. Please note that we are utilizing the web SDK implementation here and we are validating the Target calls in the interact call preview section. I have created a recommendation activity with VEC on a specific page with Recently Viewed Items as a criteria and selected a default design.  1. I have uploaded a product in the Catalog via the Recommendations API using the 3 entity attributes such as entity.id, name ,category, thumbNail URL . Here only thumbNail URL is the one which I acquired by inspecting the specific product available in a page (https://abc.com/image.png) and the remaining attributes such as entity.id and entity.category are the ones which I manually defined by giving some hardcoded values such as Dose1 for entity.id and medicine for entity.category since I couldn't find these available in the dat

wanted to check if web crawlers works on Adobe target so SEO and AI can still pickup the experiments content?

Hi everyone, we are trying to implement Adobe Target on SFCC without Tag Manager. Currently we have downloaded the at.js file from Target and tried importing the file directly, but during the build process, the file gets removed and is no longer accessible. Could you please provide us with a guide with the correct steps for a proper installation and integration on SFCC? We only found documentation for the implementation on AEM and we are stuck with the file being canceled. We also reached the SFCC support who invited us to ask directly to you for this kind of guide. Thank you in advance. Best regards, Sara

On our webpage, there's a page with a button that downloads a PDF when clicked. I need to create two audiences:1) Audience 1-visitors who went to the page but did not click the Download PDF button2) Audience 2-visitors who went to the page clicked the Download PDF button Audience 1 works. There's an issue with Audience 2. We use Web SDK. I needed a way to detect button clicks on the page. There is only a single PDF on that page.In Launch, I built a rule that fires when the Download PDF button is clicked. That rule is firing; it was verified using the Chrome console. When the rule files, the action is this script.<script>console.log('Data collection: download button was clicked');adobe.target.trackEvent({mbox: 'downloadClickMbox',params: {clickedButton: 'downloadPDF'}});</script> In Target, I built a profile script to catch instances of the Download PDF clicks from Launch using this code.Profile script name: 2025_Downloaded_PDFif (mbox.name == "

I was trying to implement the adobe target in our website. I was new to Adobe Target.can anyone help to integrate the adobe target(at.js).

Is there any way to catch up custom event in Target audiences like: user.login? Is there any different way to send to Target infor that the user logged in using Web SDK?

In my experience, the hardest part of experimentation often isn’t the tool itself – Adobe Target is powerful and flexible – but the context it lives in. For some organizations, the blocker is the data foundation: experiments become guesswork if the right data streams aren’t stitched together, or if audiences aren’t well-defined. For others, it’s the organization: running tests is easy, but aligning teams, stakeholders, and processes around experimentation can be painfully slow. I’ve seen companies where the bottleneck wasn’t in setting up a Target activity, but in getting approval to launch it.   👉 I’m curious: what’s the toughest challenge you’re facing right now when it comes to running experiments in Adobe Target?   Is it data (getting the right foundation in place)? Is it organizational (building trust and speed in decision-making)? Or is it something entirely different?   Would love to hear how you’re tackling it — and maybe we can all steal a few id

How to Deliver Personalized Experiences Without Compromising Site Security Delivering personalized digital experiences while keeping your site secure? It’s not a pipedream anymore. This guide shows how to make Adobe Target and Content Security Policy (CSP) work together—so marketers can personalize freely, and developers can sleep soundly. What Is CSP? Think of Content Security Policy (CSP) as your site’s gatekeeper. It defines a set of rules that tells browsers which sources of content such as scripts, styles, images are safe to load and blocks anything suspicious. CSP is your knight in shining armor against cross-site scripting attacks. For Marketers: Why You Should Care A strict CSP, if not configured for Adobe Target, can disrupt your personalization efforts. Problems may include: Failed rendering of personalized experiences Broken reporting and Analytics Unexpected errors in the Visual Experience Composer (VEC) The fix? Collaborate with your development team to configure CS

Hello,We’ve encountered an issue with our AEM-Target integration: although targeted content is being replaced, it appears blank on the UI because the CSS class (mboxDefault) is not removed after content injection. We have tried different timeout settings, but haven’t had any success.Also the content personalization is specific to the component not for the complete page.We’re using the at.js 2.11.8 version. Can someone help identify what might be causing the issue and suggest possible solutions? I don’t see any errors in the console or failures in the network calls. I’m not sure if we need to introduce a listener to change the visibility. I appreciate any help you can provide. @hrishikeshkagne 

Hi,I’ve run into an issue with the Visual Experience Composer (VEC). Previously, I was able to use the “Add Before” and “Add After” features to insert multiple HTML elements at once (for example, multiple HTML elements added after an element).Recently, whenever I try this, Target throws an error saying that more than one element is being added. The only way to proceed is to split the HTML into separate insertions (one element at a time), which is tedious and error-prone.I’ve checked the latest Adobe Target release notes, but I couldn’t find any mention of this being an intentional deprecation or limitation.So my questions are:Has Adobe officially deprecated inserting multiple elements at once via “Add Before” / “Add After”?If yes, could you point me to the official documentation or release notes that confirm this change?If not, is this a bug in the new VEC, and should we open a support ticket?This change is impacting our workflow, so any clarification would be very helpful.Thanks in ad

I am building an A/B Test activity in Adobe Target. In the variant, I am inserting a recommendation on to the page. In my goals, I want to set it up to track clicks on the recommendation. However, I don't have an option to do that. If I do Conversions > Click an Element, the recommendation just shows a blank box that says recommendaiton offer. So I can't select an item to track as a click. Is there something I am missing or a work around?