Adobe Target

Hi, I have a question about mapping of tracked clicks to experiences in an activity. I want to make sure the reporting data are correct.I created an activity with several experiences, each of which has <a> links.I enabled A4T and set the analytics as the primary reporting source.I configured the conversion as the primary goal; clicking any of those links is a conversion. The documentation says that "Click-tracking metrics are not linked to any specific experience in an activity". However, the reports (both in Target and Analytics) show the breakdown of the conversions by experiences.Can you tell me how the tracked clicks are mapped to experiences? I suspect that the click's eventToken is associated with a specific experience, but its logic is not clear to me: the eventToken is the same for some elements and different for the others in the same activity.

I'm trying to setup an XT where I show an offer to users who have visited a page via Organic channel for the last 30 days.The targeting is done using an AAM segment which identifies Organic users. If a user who qualifies for this segment in visit 1 comes back via a paid channel, he should not be able to see the offer. I was able to achieve this using a page delivery condition (pageurl does not contain a parameter) However, if the same user now comes back a 3rd time using organic channel, he should still not be able to see the experience. But in my setup, the experience is visible since the page delivery condition is met. Is there any way to set this up where as soon as a user visits the page using non-organic means, they are not considered in the targeting anymore? Thanks!

Hi, it's the first time I'm setting up an A/B test in Adobe Target and I followed the step-by-step instructions. However when I wanted to save and close, an error message popped up that says: At least one property is required when creating an activity in a non-default workspace. Tried googling but I can't find anything that explains what this means, can I get some help on this please thank you.

I recently implemented a custom script for Adobe Target using the trackEvent API, despite using the Web SDK for my setup. Surprisingly, the script is working, and the trackEvent is successfully passing parameters to Adobe Target. I would like to understand why this is happening, given that sendEvent is the recommended method for Web SDK.Here is the script I used:<script> const osTheme = window.matchMedia("(prefers-color-scheme: dark)"); if (osTheme.matches) { adobe.target.trackEvent({ "mbox": "themePreference", "params": { "userTheme": "dark" } }); } else { adobe.target.trackEvent({ "mbox": "themePreference", "params": { "userTheme": "light" } }); } </script>What I Observed:The event is being successfully logged in Adobe Target.The userTheme parameter is being sent and correctly recognized by Target.Debugging data confirms that the event is processed correctly:{ "eventType": "decisioning.propositionDisplay"

I've encountered several inconsistencies between different versions of the Adobe Target API documentation for creating activities. I'm hoping someone can clarify which documentation is current and correct.Documentation VersionsI'm comparing what appears to be two different schemas:A complete JSON schema definition (let's call it Schema 1): https://developer.adobe.com/target/administer/admin-api/#tag/Activities/operation/createActivity_3_1 An XT activity creation example (Schema 2): https://developers.adobetarget.com/api/#create-xt-activityInconsistencies found The documentation shows two different approaches for defining experiences:Schema 1:{    "experiences": [      {        "optionLocations": [          {            "locationLocalId": 0,            "optionLocalId": 0          }        ]  &nb

I am using the Delivery API to fetch Recommendations data in a JavaScript script. Currently, I am reading the mbox cookie in order to get the sessionId. Then I use the sessionId to call the Delivery API. I am not providing a visitor id such as tntId. This is working fine for me and is maintaining the correct Activity Experience per visitor. However, the Delivery API documentation has this to say regarding tntId: (source: https://developer.adobe.com/target/implement/delivery-api)"Object that contains the identifiers for the visitor. If no id is provided in the first request, Target will generate a VisitorId with a tntId. The code that runs on the client side is then responsible for passing this tntId value on all subsequent calls." I'm not sure this applies to my case as my script only runs once per page load, and it is already working correctly. However, even if I run it concurrently, it works correctly. Do I need to store and pass the tntId somehow? For what reason? How can

My team wants to create a Recommendations Criteria that compares two multi-value entity attributes. We want to include entities that share at least one item within this multi-value attribute. There is conflicting information in the documentation about whether this is indeed possible. I have the option to do so (see screenshot), which is not currently working for me, but this could be an error on my end.  This note in the documentation says "Multi-value attributes are not currently supported in....entity attribute matching, or for lists on the left side of inclusion rules." https://experienceleague.adobe.com/en/docs/target/using/recommendations/criteria/work-with-multi-value-attributes#:~:text=Multi%2Dvalue%20attributes%20are%20not%20currently%20supported%20in%20promotions%2C%20entity%20attribute%20matching%2C%20or%20for%20lists%20on%20the%20left%20side%20of%20inclusion%20rules However, in another area of the documentation, it says the 'list contains an item in" oper

After Web SDK migration, we are seeing issues in the reports like data is not evenly distributed among the experiences in A/B Test. Although, experiences are getting delivered as expected.In Adobe Launch, I have a separate rule of Adobe Target which is firing at top of the page (Library loaded) and I am sending a web SDK event as shown below with "Include rendered propositions" checked nothing else in Data, XDM or custom code.Please help me fix the reporting issue. 

Hi, The use case is to use AD groups to target content. There are around 500+ AD groups.  How to sync the AD groups to Target and use the same to target content? Any example on the targeting of content based on AD groups.   

We have a business requirement to send out automatic notifications when journeys are activated and deactivated. Is there any way in Adobe Target to have a notification sent out when an experience is deactivated?

Hi everyone,I’m currently configuring the Adobe WebSDK extension and need some clarification regarding the "Auto Click Collection for Adobe Target" setting, especially when using Adobe Analytics as a reporting source (A4T integration).Here’s my scenario:In the data collection section, I’m already tracking internal, external, download links, and all default context information.Adobe Analytics is set up as the reporting source for Adobe Target.My questions are:Should I still set Auto Click Collection to "Always" if I’m using A4T for reporting?Does enabling this feature provide any added value or redundancy when I’m already tracking internal, external, download links, and all default context information?I want to ensure that I capture all necessary data for Adobe Target activities without introducing unnecessary overhead or duplicating efforts.Thank you!

Hi all. I am attempting to track click and page view events in an AB test I'm running.  However, I'm having some issues as the site we are working on is both a multi-page and a SPA website.In the test, we are primarily tracking a button click from the home page, which navigates the user to a separate page in the site. This new page operates essentially as a SPA, it has a funnel the user goes through similar to a "quote" application process, but it is all one page with sequential endpoints as "steps" in the process.TLDRSelection events aren't re-attaching to the page on a multi-page + SPA solutionBetter way to force attach selection events than getOffers/applyOffers?getOffers/applyOffers is executed every time the url changes on an event listenerClick tracking on nav menu in the home page is not consistent at all in live audience modeIs it possible that this is due to navigation happening too quick for target to log the event?More InformationWe have a primary goal (tracki

I am working with the Recommendations API as detailed in the Adobe Experience League documentation. I am encountering an issue with the format of the recommendation content within the JSON response.https://{{CLIENTE_CODE}}.tt.omtrdc.net/rest/v1/delivery?client={{CLIENTE_CODE}}&sessionId=1234567Initially, I was receiving a 400 status error with the message "Errors: field - [context.channel] - must not be null;". To address this, I amended my request body as follows:{"context": {"channel": "web"},"execute": {"mboxes": [{"name": "api-mbox","index": 1}]}}This rectified the error, and I am now successfully receiving responses. However, despite having specified in the design of the recommendation within Adobe Target that the format should be JSON, the recommendation content is being returned in HTML format.This is a crucial aspect for me, as I need the recommendation content to be in JSON to align with the configurations I've set in Adobe Target. Could anyone advise how to ensure th

Good afternoon community.I'm looking for advice on where to go to install a local instance of Target?I'm currently training on the platform and am hoping to add my own version to my own laptop to train building activities, texts, etc. I have a local version of AEM (WKND Site) I'm unsure of you can add Target in the same way and am trolling through documentation to find an answer. Any advice is welcome.Thank you in advance 🙂

Hi there I have been working under the assumption that 'Is Mobile Device' includes phones and tablets, and that 'Is Mobile Phone' is only phones. Is this correct?  Or are they mutually exclusive? Screenshot for reference  ThanksJoe

Hi everybody,We've been trying to create a personalization where the banner changes if users come from a specific referrer URL. However, we're having issues replacing that image. We already uploaded the new image to Adobe Assets (we don’t have AEM but have some other Experience Cloud products). Even though Target can find it, it seems the image is not made public, so Target can’t use it.We also tried to find the Adobe Assets settings to make the image public but had no luck. When we uploaded the image to a random image-sharing site, it worked. After reading the documentation, we saw the option to upload assets to Target itself with Dynamic Media. We are checking with Adobe now if our configuration was already done before, but when we go to Replace Content > Image, it opens Adobe Assets, and we can choose the image, but it does not work.Any idea of what is wrong and a solution for that? 

Hi,I am implementing experience target activity using the at.js approach through Tealium.I don't have access to Tealium as its managed by different team and I can ensure its loading correctly through Adobe Experience Platform Debugger.After saving the modifications for injecting html and styling for different components using 'Insert after' method on webpage, the changes are reverted to default.Once the activity is live, "Action could not be applied due to missing or invalid mbox name" error is shown in modifications.I haven't implemented any mbox for this activity.Can anyone please help me to resolve this issue?

I tried setting up adobe target, but somehow it isn't working stable in chrome, most of the time i get this message and some times it works. I also installed the browser extension and changed the setting Enable Enhanced Composer in the Page delivery.Somehow Fire Fox don't seems to have these issues.

Hi All,I have  done adobe target integration using below approach1.Download the  latest at.js from the adobe target implementation.2.Create the clientlibs in aem and added that at.js3.calling this clientlibs in my headlibs.html.4.In the network tab verified delivery related call happened  and gives 200.5.Created A/B test on the adobe target  and added different experience for All visitor.whenever i checked the URL   it shows default content not the activity content, I tried to check Activity QA Url as well it display the same default content.did i missed anything .Thanks 

How I would match Target Property with Visual Experience Composer? 

Use Case: Create an XT activity for specific CRM IDs In Launch: There's an existing Target Load and Fire rule. In that rule, there's an Add Params to Page Load Request action.Name: mbox3rdpartyidValue: (a variable that contains the CRM ID value, from a data element)I believe this part works, it's how to pull this in Target that I need help with. In Target>Profile Scripts, I made a profile script called id_mbox3rdpartyid with this code: return profile.get('mbox3rdpartyid');Then in Audience Library, I made an audience called IDaudience, set up as this: Visitor Profile: user.id_mbox3rdpartyid equals (case sensitive) 0000000000(The id I used is the real ID and not zeroes.) I created the activity and set the audience to IDaudience. The experience is not being shown. This is set up on a password protected site. I made sure the user has the ID I entered in the audience. I also tried making a second Audience set up as: Custom: mbox3rdpartyid

Ok - I would like to set some frequency capping on some experiences. I know this involves passing some kind of unique identifier of that experience, creating a profile script so it can be counted and then creating an audience depending on my how many times I'd like customers to see the experience. We use JSON offers and I'm struggling with Step 1. How to I pass a unique identifier for the experience? Can I create a unique mbox through JSON and count that?  Thanks for any help.

Hi all,  The Node.js getOffers() method seems to be ignoring my QA parameters. The docs for Node.js getOffers() method indicate that it conforms to the spec for the REST-based Delivery API . My request object contains the request.qaMode value as described in the Delivery API spec. const offers = targetClient.getOffers({ // ... "request": { //... "qaMode": { "token": "s_c15OYe-jBHIvKsmzAuL7zP_DDcGGb87aV06x_KWVo", "listedActivitiesOnly": true, "evaluateAsTrueAudienceIds": [], "previewIndexes": [ { "activityIndex": 1, "experienceIndex": 2 } ] }, // ...});However, getOffers() seems to be ignoring this. (I'm 100% sure it's correctly formatted, etc. - it's created & populated using the same code that's creating the qaMode object we pass to the Delivery API endpoint in production.)Can anyone point me to any documentation on this? 

Hi! I have implemented views on SPA using web sdk. When I am on home page, xdm object returns view name as "index" and page name as "home".when I proceed further and click a SPA component, xdm object returns view name as "men" and page name as "men category". I want to run an activity on view name "men" and audience with revised page name as "men category".  

After migration from SDK v1 to v3 the target response delivers no data.