Adobe Target

I'm struggling to find an efficient way to debug Recommendations. With at.js, I used mboxTrace, which provided a very clear "Recs Box" showing exactly which criteria were used, which entities were returned, and why certain items were excluded.Now that I'm using Web SDK and the AEP Debugger, I find the debugging process much more difficult. I can see the network calls, but I miss that high-level summary of the Recommendations logic.What I've tried: Using the AEP Debugger Extension to look at Edge Traces. Digging through the interact response payloads in the Network tab. My Questions: Is there a way to get a visual "Recs box" similar to the old mboxTrace functionality in at.js? In the AEP Debugger, where exactly should I look to see the Criteria details and Exclusion reasons for a specific Recommendations activity? Are there any third-party tools or specific "Edge Trace" configurations that make the JSON output more readable for Recs-heavy implementations? How do you effectively

When using the Target Admin API, I’m creating new JSON offers. My requests are returning a ‘201 Created’ response, but when looking at the Target UI, I’m not seeing the offers in the default workspace. I can confirm that the API has access to the correct workspaces, and response shows the offer created in workspace: default. The response also shows an OfferId that looks accurate.Additionally, some time has passed (>60 minutes), and no offer has appeared yet. Should the Offers be accessible from the Target UI after creation with the API?

I am implementing Adobe Target Recommendations via AEP Web SDK and Launch. While the network calls appear to be firing correctly with the necessary entity attributes, the Target Recommendations Catalog has not updated with these product details, even after waiting 24+ hours.Implementation:I am using a "Send Event" action within a Launch rule. Because my data layer is fully populated later in the page load, I have mapped the entity attributes to the "Web Webpagedetails Page Views" event type.Current Rule Configuration (See attached images): Extension: Adobe Experience Platform Web SDK Action Type: Send Event XDM: %XDM Payload: All Page Views% Data: %adobe-target-parameters [xdm]% (This is where my __adobe.target entity data is mapped). The Payload:In the browser network tab (interact call), the payload looks correct: events[0].data.__adobe.target.entity.id is present. entity.name, entity.value, and entity.pageUrl are all populating with the expected strings/numbers.   The Sequ

Hi Community,we are currently experiencing an issue when introducing new Adobe Target locations, while the existing setup is mainly based on the Global Mbox.At the moment, activities configured on the Global Mbox are correctly evaluated and returned in the response. However, when we attempt to create and use a new dedicated location for more targeted personalization, the Web SDK response consistently returns the following error:"errors": [{"type": "ODE-0001-404","detail": "The Decisioning Package was not found."}]On the AEP / Web SDK side, we are following the official documentation available here:https://experienceleague.adobe.com/en/docs/platform-learn/implement-web-sdk/applications-setup/setup-targetbut the error still persists.From the Adobe Launch side, there is a rule that sends a sendEvent call on page load once the required data is available in the data layer.In this call:personalization parameters derived from the data layer are passed to Target, a decisionScope is set with th

If an AB activity is running on Page X, then help me understand how a visit is counted in A4T for below scenario?User comes to Page X and leaves. This user comes back again in a new visit but doesn’t visit Page X (where activity is running) - Will this new visit be included in my AB activity? NOTE: We only do Visits level reporting in A4T for AB tests.

The activity was created with Adobe Analytics as the reporting source, but it is not present in Analytics Workspace.  

I’d like to use attribute weighting in an item-based criterion in a way that makes sense to me but apparently didn’t occur to Adobe devs. The current setup has a weighting % slider, then you choose the attribute, then an operator, then you must enter a static value, so this is really just a leaky filter.What I want I want from your AI is this:Look at the attributes of the current item Look at which attribute(s) I’ve selected to weight Then look at the catalog items that also have this/these attribute(s) Recommend items with rank based first on similarity in these attribute values Ideally, you could also apply an operator here to tailor matching vs. anti-matching, e.g., highly recommend items that are more or less different in these attribute values

In our SPA, we observed a specific behavior of Target activities: Even with renderDecisioning=false, some activities continued to trigger. The activities are present but not rendered. Since this is a SPA and there is no page refresh, in the subsequent Rule Page View we could not find the activities with the key expected by Target. Important: before user login, there were no Rule Page Views. Activities were therefore only processed after login, and everything worked correctly in that phase. Implemented SolutionTo properly handle the SPA flow without page refresh, the following was implemented: In the Rule Page View, after login, a custom code was added to handle view changes:   function onViewChange() {   var viewName = window.location.pathname || 'viewNamePage';   if (viewName.startsWith('/')) {     viewName = viewName.substring(1);   }   alloy("sendEvent", {     renderDecisions: true,     xdm: {       eventType: "view",       web: {         webPageDetails: {           name: view

Hello - Has anyone else had a similar experience that when you made the transition to the MobileSDK your post_tnt_action field in your data feed no longer was populating?  Looking for any type of troubleshooting ideas -- checkboxes that we might be missing, a step that is often overlooked, something new that needs to be setup, etc.  Thanks!

Hi, Can we use the Geo Audience for the Adobe Target usecases for the Apps or it only limited to the website?

i need to create a profile script to identify the last visited bike pdp by a visitor in real time and using that create an audience accordingly for each bike models mutually exclusive

I have a list of 3,784 users that I want to target with specific data. To achieve this, I created segments in Adobe Analytics, where I defined the condition as User ID equals any of x, y, z, using approximately 500 user IDs per segment. These segments are visible in Adobe Target via A4T, and I have used them to create an experience. However, I am unable to see the experience being delivered to the intended audience. Could you help identify what might be causing this issue?

I’m looking to enable the AI capabilities in Adobe Target. If you’ve already done this, I’d be interested in learning which use cases you tried.

I recently created a Recommendation activity, but the products are not appearing on the website. The activity qualifies, but the recommendation slot is not rendering any products.Has anyone else faced a similar issue while setting up recommendation activities?Also, are there any specific troubleshooting steps to identify why the recommendations are not showing? For example, checks related to criteria, entity attributes, mbox calls, catalog ingestion, or delivery calls.

I am in the process of connecting Adobe Target with AEP. When I select the audience, AEP asks me to select the profile attribute as well. My doubt is if I select First Name, Email, Adress XDM fields and these fields are PII fields, will the data be stored in Target somewhere or visible to Target users. Is it safe to map these attributes.I am asking this double with respect to security of PII data. Because, if I have to personalize the webpage, I would require PII data, but I am not sure if sending this data from AEP to Adobe target along with audience is safe ?

I need to target the homepage for an activity, but I'm running into an issue with URL matching. The activity fires correctly when users visit https://example.com/, but it doesn't trigger when users land on https://example.com/?utm_source=source or https://example.com/?abcdefjkl (any URL with query parameters).I've tried several different configurations, but none of them are working.I've attached screenshots showing my current setup.  

Hello !We have Analytics4Target on our website, we gets the data in Analytics and we are able to pull Activity/Experience results.But we would like to do some things that seems impossible, do you know how we can do these ?1. Get visits/visitors that got an activity/experience that were live between specifics dates.With the following dashboard, the “Activity” metric correctly show 0 for the activity that were off this month. But the other metrics are not relevant at all. Isn’t it possible to use other metrics ?2. Link an activity/experience to a PropIf I use a Prop that is also sent on the Adobe Target requests, I’m able to list activity linked to it when using “Activity impressions” (the activities that is are 0), but the other metrics give activities that are from other pages.Thanks a lot,Julien

Hello, I noticed a problem that this documentaiton page exists https://developers.adobetarget.com/api but when I try accessing it, it redurects to https://experienceleague.adobe.com/en/docs/target-dev/developer/api/admin-api/admin-api-overview. The orogonal page has content which is helpful, but I can noot read it because of the redirection. Is it broken ?

I have a question regarding the example on this documentation page (websdk):https://experienceleague.adobe.com/en/docs/experience-platform/collection/use-cases/personalization/top-bottom-page-eventsThe example looks like this:"... Second page view (Option 1) ..."alloy("sendEvent", {renderDecisions: true,xdm: {...,web: {webPageDetails: {viewName: "cart"}}}});Unfortunately, the example does not indicate which XDM event type is sent over the network. Could you clarify which xdmType should be specified here, or which one is sent by default?

How come I can only add dependecies on certain metrics in the Goals & Settings? I have three metrics. One of them is a conversion metric tracking pageviews. I don’t want it to track unless another success metric has been reached and when I select advanced settings, I have the option to click which one. However, I have another metric where I am tracking clicks. I want to set the exact same dependency to this metric but the drop down isn’t available: 

When I'm editing or saving the audience, the condition displayed shows "current page query is not empty."However, after saving the audience and viewing it in the rules section, it appears to show the opposite condition.  

Hello! I am having some issues with getting Adobe Target to fire on my Google Chrome since switching to a new computer. I am the platform owner for my team so as you can image, if the experiences are not firing for me on my main browser, this is a problem.  On my old computer the experiences (when activated) would show on microsoft edge and google chrome, now they are only showing on microsoft edge. However, others on google chrome can still see the experiences so it appears to be just me. Troubleshooting I have tried: 1. Accepting all cookies 2. Clearing my cache3. Restarting my computerClosing all tabs and trying againLooking for assistance and suggestions please and thank you! 

Hi folks -Thanks for the new Insights panel in Target, but I don’t need to see it as the home page every time I load Target, and when I’m working on activities and hit the back button, I want to go to Activities.

We are A/B testing an experience where Cohort B is redirected to a ‘/page-b’ while cohort A should see the default ‘/page-a’.What was happening initially- Initially we used AT’s redirect offers but it was conflicting with our Next.js routing/CDN . It caused flickering and messed up React's hydration process. It also prevented us from getting correct readings for our test experience in GA4This is what we did as a bypass solution -Created the A/B test using FEC with a redirect mbox and a JSON offer. Created a middleware at the Next.js level that intercepted the request from a user’s device on our server before the page loads (before any HTML is sent) It calls Adobe Target's Edge Network to get the redirect decision asking  "Should I redirect this user?" and Target responds with either a redirect decision or no action. If a redirect is needed, the middleware sends a display notification to Target for analytics tracking, then performs the redirect, and the user lands on the destination pag

I want to show 2 different offers(experiences) to 2 different audiences.  I have created the activity as Experience Targeting. My website is a SPA, but I have used different pages(the URL is not refresh when I move to next page).  The lightbox open when the user go to the PDP pages. The pop-up open again and again in single session. Example: product1, product2, product3,.... User come to product1 page the popup showing but the user close the popup again go to product3 the popup showing again.  But I want to control this, Once the user close the popup, it should not open in the same session. How can we achieve this?